dude67

If you haven't deleted the photos from the camera/memory card or stick try downloading them again to your HD. Perhaps the .jpg files are corrupted someway...

As for the version history, there's a file for changes from 2.6.0 to the latest 2.6.3 (not from the earlier version though) here: http://developer.gimp.org/NEWS-2.6

I would have asked the same question as Ian: what's the file format you were trying to open?

This suggests that it's not Gimp itself that's giving you the problem, but it needs a plug-in to open it and the plug-in cannot open it. If it was due to size, I would have imagined gimp to say something about the size of the image...

'Plug-In could not open image'.

There is a setup in preferences for max image size (in Environment - Resource consumption - Maximun new image size). The Gimp sometimes tells the user that the image you are trying to work on is bigger than the set max image size. But this would only ask you what to do (keep working on it or not) - it would not refuse to open the image.

BTW, have you updated Gimp from 2.4.x to 2.6.0?

Disclaimer: I'm currently at work on my WinXP Pro and I have only access to a Windows version of the Gimp. I'm not sure if the menu items are 100% the same in win and Linux versions.

With the obvious large community public backlash that is occurring at the moment, we may be lucky and see some rethinking and backtracking of intended moves. :)

 

Cheers. John.

Well, that may soon be too late, John. If any of the other companies are any wiser they will seize the opportunity (of hiring Adam).

And Hervé's response is...

 

http://blog.mandriva.com/2008/12/03/new-ceos-first-30-days/

 

Yes, the CEO's letter is full of BS, but the replies are quite the opposite (I didn't read the French replies though)

ditto

Wow, I would have thought that a smarter move would have been to hire a few more people like Adam. :unsure: IMO Adam has done a lot more to help spread Mandriva than their own marketing...

Adam; if you're reading this: I'm really sorry to see you leave Mandriva!

When rebooted I got Mandriva back!

I don't know what went wrong with the system updates (or something else), but now this made it work just fine! Perhaps when updating the mdadm package the '/etc/mdadm.conf' file was overwritten and replaced by a std new file!

Thanks a million Ian - you're the man!

Let me buy you (again) a whole bunch of virtual beers!

This is my current array:

$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md2 : active raid1 sdc9[1] sda9[0]
   506272256 blocks [2/2] [UU]

md1 : active raid1 sda8[0] sdc8[1]
   102398208 blocks [2/2] [UU]

md0 : active raid1 sda6[0] sdc6[1]
   20474688 blocks [2/2] [UU]

unused devices: <none>

Thanks Ian for helping out!

OK, I'm starting in shell mode as I can get there when booting failsafe. Now I have root privileges.

Then I'm assuming that you meant that I really write '/dev/sda*' and not '/dev/sda6' in the first line.

I do remember my partitions:

md0 = /

md1 = /home

md2 = /storage

md0 was (and is) sda6 and sdc6

md1 was sda8 and sdc8

md2 was sda9 and sdc9

But now I can only see md0 in my /proc/mdstat:

md0 : active raid1 sda6[0] sdc6[1]
				  20474688 blocks [2/2] [UU]

	 unused devices: <none>

I added these lines to /etc/mdadm.conf

	 DEVICE		/dev/sda*
		   DEVICE		/dev/sdc*
		   ARRAY		/dev/md1 devices=/dev/sda8,/dev/sdc8
		   ARRAY		/dev/md2 devices=/dev/sda9,/dev/sdc9
		   MAILADDR	root@localhost

I couldn't see the md1 of md2 with 'ls /dev/md*' so I rebooted.

Again I turn to you with a problem. I have a dual boot with Mandriva 2009.0 KDE4 and WinXP home. I also have a RAID1 array of two 750 GB disks - only the winXP is left out as I've got software raid built with Mandriva.

Then the issue at hand: I turned Mandy on today after work and downloaded some updates (at least urpmi and then gurpmi and bunch of other stuff). I don't remember what they were. Everything was just fine at that time.

Then I booted to windows as my son wanted to play some games and no problem there either. But when I rebooted back to Mandriva I couldn't get Mandriva to load anymore. Finally I booted to failsafe and was brought to shell. There was a problem with filesystem, at least this much I could catch from the screen:

Invalidating stale software suspend images... done.
			 Checking filesystems
			 fsck.ext3: No such file or directory while trying to open /dev/md1
			 /dev/md1:
			 The superblock could not be read or does not describe a correct ext2
			 filesystem. If the device is valid and it really contains an ext2
			 filesystem (and not swap or ufs or something else), then the superblock
			 is corrupt, and you might try running e2fsck with an alternate superblock:
				 e2fsck -b 8193 <device>

			 fsck.ext3: No such file or directory while trying to open /dev/md2
			 /dev/md2:
			 The superblock could not be read or does not describe a correct ext2
			 filesystem. If the device is valid and it really contains an ext2
			 filesystem (and not swap or ufs or something else), then the superblock
			 is corrupt, and you might try running e2fsck with an alternate superblock:
				 e2fsck -b 8193 <device>

								 [FAILED]

			 *** An error occured during the file system check.
			 *** Dropping you to a shell: the system will reboot
			 *** when you leave the shell.
			 Give root password for maintenance
			 (or type Contro-D to continue):

As I said, I have RAID 1 array and the only thing I could make of this is that there seems to be a problem with md1 and md2. This leads me to suspect something's not right with the raid system. I saw an mdadm update note in the advisories section paul posts: (https://mandrivausers.org/index.php?showtopic=74454&hl=), but I cannot remember if that was one of the updates I downloaded. I did update everything that was suggested - just don't remember if I saw that one on my list.

Anyway, are there any advice as to what to do next?

[moved from Installing Mandriva by spinynorman]

Here's my two cents..

256 MB & 800 MHz Celeron processor is perhaps too little to run any KDE or Gnome desktops. I would recommend installing XFCE4 or IceWM window managers. I'm using XFCE4 in my _very old_ HW (256MB RAM, Pentium II 400 MHz processor, ATI 9200 PCI graphics controller - more here: https://mandrivausers.org/index.php?showtopic=43498). I would not install KDE or Gnome anymore on that.

I installed 2009.0 without KDE or Gnome. It installed IceWM and later I installed XFCE (I couldn't find XFCE for an installation during initial installation).

Just an update to this thread if anyone is wondering about running linux on old hardware.

I'm now running Mandriva 2009.0 with XFCE on this and it's working nicely! It's not the fastest machine around, but it's OK.

Otherwise the HW is the same as in the first post, but I've got a Sony 40" HD flat TV as a screen.

Here's my current KDE4 desktop.

Thanks R.I.P. - that did the trick for Doom3. I guess the other problems I'm having with 3D and other games are not related then.

(To admins: This may belong under another sub-forum - perhaps in HW section or installation. Please move it, if this is a wrong forum.)

I don't know what happened with my display settings, but I cannot play Doom3 with my current login (at KDE4) anymore. Originally I was able to play Doom3 (or the RoE exp. pack) in my MDV 2009.0, but when I changed my 3D desktop to No-3D I noticed that I cannot play Doom3! Something must have gone wrong with the display settings because, when I start doom3 from konsole I get "no signal" on my screen, but still hear the sounds of the game perfectly. So the game is running well, but I just can't get any signal to my screen.

I changed it back to 3D, but nothing. I also have installed the Nvidia drivers again and tried the latest Nvidia driver (177.80) from Non-free backports. Nothing.

My display adapter is GeForce 7600 GT and I'm running the Nvidia driver 177.70.

I cannot see any error messages from the konsole as the only way to get the screen back is to restart X (Crtl - Alt - Backspace). Then I loose the konsole screen.

One other thing is that I can play the game with another login (I have two IDs at KDE4)! So how can I see what the difference is?

It occured to me that perhaps I messed the screen settings within the game itself (I did change some settings); but how can I change the settings of Doom3 without entering the game? (Catch 22)

There is something odd also with some other games as well. E.g. Tuxracer has the same effect, i.e. I don't get any signal to my screen.

The screen is connected to a DVI connector with a VGA/DVI adapter piece - if that makes any difference.

So A.I., when can we see your new desktop of the 8.10 release? I always enjoy your excellent taste in desktop colours and styles!

Just an endnote to this topic: I managed to remove beagle, but that didn't help with my problem. I guess it wasn't the same issue that what was cured by removing beagle.

My problem is general slowness of certain programmes (e.g. MCC Software managent takes ages to load after anything I do - even clicking Quit for exiting the tool - I just timed it: it took 10 seconds to close sw management and get back to the main MCC window after I clicked Quit).

Then the list for MDV 2009.0 w/ KDE4 continues:

- I lost window decoration colors (the window decorations are even duller when active than when inactive) in 3D-land (have to live without that now)

- for some reason I cannot play Doom3 anymore (even though I did manage to play it initially after installing 2009.0) as the screen goes empty (no signal to my screen). This same applies to various other games as well (like tuxracer).

I'm seriously thinking of getting back to KDE 3 (the version I had in 2008.1).

But that's something that we could continue over another topic. This one is closed (the libbeable1 issue).

Wow, I didn't know that. What type of problems... Removing something that it's not supposed to?

OK, that went nicely. This is what was removed

# urpme beagle
  To satisfy dependencies, the following 3 packages will be removed (4.1MB):
	beagle-0.3.8-13.1mdv2009.0.i586
	beagle-evolution-0.3.8-13.1mdv2009.0.i586
	 (due to unsatisfied mono(BeagleDaemonLib) == 0.0.0.0,
	  due to unsatisfied beagle == 0.3.8)
	beagle-gui-0.3.8-13.1mdv2009.0.i586
	 (due to unsatisfied beagle == 0.3.8)
  Remove 3 packages? (y/N)

I'll see if that helped for the slow responses of the system; I'll report back.

-EDIT-

OK, it left these packages orphan, so I just removed them also.

The following packages are now orphans, use "urpme --auto-orphans" to remove them.
  beagle-libs-0.3.8-13.1mdv2009.0.i586
  evolution-sharp-0.18.0-1mdv2009.0.i586
  galago-sharp-0.5.0-8mdv2009.0.noarch
  gmime-sharp-2.2.23-1mdv2009.0.i586
  gsf-sharp-0.8.1-3mdv2009.0.i586
  poppler-0.8.7-2mdv2009.0.i586

OK, thanks adamw. I'll test that tonight.

Thanks, that would do it. Just one question though: if I remove the package and something is broken, I guess I can just reinstall the packege, right? :unsure:

OK, thanks both. But I still seem to need a bit more push...

i) I don't know how to uninstall a package without removing the dependency-packages...

ii) I don't have the option Greg2 mentioned. I checked from MCC and I cannot find beagle nor kerry from the services list... So does that mean I don't have beagle or kerry running?

I noticed some problems with long opening times (and some other problems as well) so I wanted to go by this note in the errata:

http://wiki.mandriva.com/en/2009.0_Errata#...ed_applications

It basically suggested to remove libbeagle1 library. But when I was going to remove it, I got the message that the following packages are also to be removed (dependencies); why all these?:

Because of their dependencies, the following package(s) also need to be removed:

		  - brasero-0.8.2-1mdv2009.0.i586
		  - compiz-config-kconfig-0.7.8-2mdv2009.0.i586
		  - compiz-decorator-kde-0.7.8-2mdv2009.0.i586
		  - k3b-1.0.5-9mdv2009.0.i586
		  - kdebase-common-3.5.10-6mdv2009.0.i586
		  - kdebase-ksysguard-3.5.10-6mdv2009.0.i586
		  - kdebase-progs-3.5.10-6mdv2009.0.i586
		  - kdebase-servicemenu-2007-8mdv2009.0.noarch
		  - ksplash-engine-moodin-0.4.2-13mdv2009.0.i586
		  - libkdebase4-3.5.10-6mdv2009.0.i586
		  - mdklaunchhelp-2007-1mdv2007.0.i586
		  - task-gnome-minimal-2009.0-4mdv2009.0.noarch
		  - yelp-2.24.0-3mdv2009.0.i586

		  0B of additional disk space will be used.

Do e.g. compiz-config-kconfig or compiz-decorator-kde or k3b :o have something to do with a beagle lib?

Hi humpus, and welcome to the forum! :) And also, welcome to the world of Linux!

The first thing you can do is verify the .iso image you have downloaded against the md5sum provided by the site you downloaded the cd image from.

Then the next thing is to confirm that you did burn it as an .iso image (which I think you must have, if you were able to start the installation process).

The third thing to check is the md5 checksum of the burn you have done. I mean checking the cd you have just burned against the md5sum. Sometimes, even if the burnspeed has been OK, the process makes a tiny mistake (burn error) and the cd is a coaster (worthless as an installation media anyway).

The ability to browse through the cd is not an indication that the cd is faultless. Always check the md5sum.

I just checked, and the highest version I can find in the 2008.1 repositories is 169.12, which is the version that is installed on this computer.

Yes, I just found this, but as medo3891 said it's in the Non-free Backports. Mine is currently v177.70, but I think I'm going to keep that (as it is working fine for my card).

x11-driver-video-nvidia-current - NVIDIA proprietary X.org driver and libraries for GeForce 6 and later cards​

	   Version: 177.80-3mdv2009.0
	   Currently installed version: 177.70-2.3mdv2009.0
	   Group: System/Kernel and hardware
	   Architecture: i586
	   Size: 26930 KB
	   Medium: Non-free Backports (Official2009.0-20)

Is there anything else that must be done to install the driver after the package has been installed?

If you install the Nvidia-latest, it will get you the latest nvidia driver (it will tell you what the latest driver is and ask you to install it: "The following package will be installed...").