dude67

Are you runnig Gnome or KDE? The only time I've experienced this behaviour was when I had chosen the "wrong" display manager for my window manager; i.e. GDM for KDE or vice versa.

I thought I'd post my winXP desktop at work here. As I am forced to use WinXP at work I thougt it'd be nice to have the desktop from my Mandriva here to make me feel more "at home" at work. :P

Love A.I.'s desktop; it's very stylish! What's that launcher/docker up left? Is that gimmie? It looks very nice! And the Mac-type launchbar on the right is also very slick. I was once looking for something like that, but really couldn't find one that would work properly and I would have liked. What is that?

Ditto

Aren't we glad we live in democratic and free societies. We can choose freely which products and services we use. :P

@ scarecrow, this is what turned me from Canon to HP... Here in Europe/Finland, when asking for linux drivers from Canon, I get an answer: "go look for some independent open source software; we will not provide one for you!", whereas with HP you don't even need to ask, it works out-of-box (by HP)! How's that for service! for HP! BTW: the papers and inks are ridiculous for both HP and Canon - at least here in Finland!

OK; so you mean replacing the text 'localhost'? Or somewhere right after the 127.0.0.1?

Well, I'm not experiencing any problems with gnome once it's all up. The only thing is that it takes several minutes to start (with the small gnome flash thingy in the center screen) and that wasn't always so. One more note: I can start apps while the thing is loading. So far the only thing I've noticed that I'm unable to do is log out or shut down before everything is fully loaded. And the other weird thing is the Terminal that starts as regular user once all is up. If there are any more suggestions, I'd be glad to hear them.

One possibility would be to purchase an external USB or NAS HDD for your data. Have you not considered that option?

/etc/hosts 127.0.0.1 localhost The other two files are empty.

OK, I was unable to turn 3D off (!), but I'm still doubtful that the 3D (compiz-fusion) is the source... Hmm... I restarted the system several times and this 'gconfd' line sometimes seems to take some two minutes; any ideas could that be the problem? Dec 29 13:38:33 localhost gconfd (dude67-21290): Resolved address "xml:readwrite:/home/dude67/.gconf" to a writable configuration source at position 0 Dec 29 13:40:33 localhost mdkapplet[21366]: ### Program is starting ### and on another occasion: Dec 29 17:41:30 localhost gconfd (dude67-6322): Resolved address "xml:readwrite:/home/dude67/.gconf" to a writable configuration source at position 0 Dec 29 17:43:28 localhost mdkapplet[6518]: ### Program is starting ### This always happens when X has started and Gnome is beeing deployed. I can see the Gnome flash (or whatever) logo in the middle of the screen, but I'm still able to use the system. I can e.g. start MCC and Firefox. So: I'm able to use Mandriva, but the system takes some two minutes still to be fully up (before e.g. the firestarter GUI is loaded in the panel along with a few other icons) and the (a bit annoying) terminal window will appear.

Sorry, I forgot to mention that I turned it back on as it didn't make any difference... Sounds like a plan. I'll try that. It just doesn't explain why it takes all this time to start Gnome all of a sudden.

I've been having this problem for quite some time and I have been unable to resolve this. So I'm again turning to you for help. When starting Gnome it takes ages (i.e. a few minutes) to get Gnome up & running. It used to fire up in no time. Another sidenote is that I'm getting a terminal session opened (as a reg. user) every time Gnome starts up. It all started when I looked for a way to start Firestarter from boot. I did it according to this: https://mandrivausers.org/index.php?showtopic=35278 But even when disabling it (commenting out the line in the sudoers file and removing Firestarter from the Sessions), it still takes forever to start up Gnome and it still brings up the terminal window. Here's syslog from one Gnome startup. I cannot find any one item that would consume a great deal of time. Dec 29 13:02:25 localhost gconfd (dude67-20620): starting (version 2.20.0), pid 20620 user 'dude67' Dec 29 13:02:25 localhost gconfd (dude67-20620): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Dec 29 13:02:25 localhost gconfd (dude67-20620): Resolved address "xml:readonly:/etc/gconf/gconf.xml.local-mandatory" to a read-only configuration source at position 1 Dec 29 13:02:25 localhost gconfd (dude67-20620): Resolved address "xml:readwrite:/home/dude67/.gconf" to a writable configuration source at position 2 Dec 29 13:02:25 localhost gconfd (dude67-20620): Resolved address "xml:readonly:/etc/gconf/gconf.xml.local-defaults" to a read-only configuration source at position 3 Dec 29 13:02:25 localhost gconfd (dude67-20620): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 4 Dec 29 13:02:26 localhost gconfd (dude67-20620): Resolved address "xml:readwrite:/home/dude67/.gconf" to a writable configuration source at position 0 Dec 29 13:03:52 localhost drakconf.real[20689]: ### Program is starting ### Dec 29 13:03:55 localhost drakconf.real[20694]: ### Program is starting ### Dec 29 13:03:58 localhost kernel: floppy0: no floppy controllers found Dec 29 13:03:58 localhost modprobe: FATAL: Error inserting floppy (/lib/modules/2.6.22.12-desktop-1mdv/kernel/drivers/block/floppy.ko.gz): No such device Dec 29 13:04:01 localhost kernel: floppy0: no floppy controllers found Dec 29 13:04:01 localhost modprobe: FATAL: Error inserting floppy (/lib/modules/2.6.22.12-desktop-1mdv/kernel/drivers/block/floppy.ko.gz): No such device Dec 29 13:04:08 localhost logdrake[20719]: ### Program is starting ### Dec 29 13:04:25 localhost mdkapplet[20731]: ### Program is starting ### Dec 29 13:04:26 localhost sudo: dude67 : TTY=unknown; PWD=/home/dude67; USER=root; COMMAND=/usr/sbin/firestarter --start-hidden Dec 29 13:04:26 localhost gconfd (root-20759): starting (version 2.20.0), pid 20759 user 'root' Dec 29 13:04:26 localhost gconfd (root-20759): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Dec 29 13:04:26 localhost gconfd (root-20759): Resolved address "xml:readonly:/etc/gconf/gconf.xml.local-mandatory" to a read-only configuration source at position 1 Dec 29 13:04:26 localhost gconfd (root-20759): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 2 Dec 29 13:04:26 localhost gconfd (root-20759): Resolved address "xml:readonly:/etc/gconf/gconf.xml.local-defaults" to a read-only configuration source at position 3 Dec 29 13:04:26 localhost gconfd (root-20759): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 4 Dec 29 13:04:26 localhost net_applet[20743]: ### Program is starting ### Dec 29 13:04:27 localhost mdkapplet[20731]: ### Program is exiting ### Dec 29 13:04:56 localhost logdrake[20953]: ### Program is starting ### Dec 29 13:04:59 localhost logdrake[20953]: ### Program is exiting ### Dec 29 13:05:10 localhost logdrake[20957]: ### Program is starting ### Dec 29 13:05:10 localhost logdrake[20958]: ### Program is starting ### Dec 29 13:05:12 localhost logdrake[20958]: ### Program is exiting ### [moved from Installing Mandriva by spinynorman]

If you have your personal data secured either in a separate /home partition or somewhere else (external HD, CD/DVD, USB dongle), I would definitely suggest a clean install of 2008 with keeping your /home intact. At least, that's what I'd do... Here's an excellent walkthrough for installing 2008 and (imho) an indispensible guide for getting the most of MDV desktop.

Exactly what daniewicz said: I have /tmp folder (containing some tmp files but not taking that much disk space) and then I have /home/dude67/tmp folder that is taking huge amounts of HD space. There are quite a few folders and files there and I'm not really sure what they are. Some folders are named "keyring-xxx", most of them are named "virtual-dude67.xxxx", but the ones taking the most spece are the two folders under /home/dude67/tmp/kde-dude67. The two big folders contain some temp tar files (judging by the names of the folders: temp_tarGjMn9R and temp_tarRjylbb). I did already delete the whole kde folder (freed some 34,5 GB HD space), but what are those keyring and virtual folders under the tmp folder?

I, too, run WinXP and MDV (2008). I would also suggest running a clean install in stead of upgrade (reasons listed above posts). The MDV installation does not touch your WinXP partition if you do not let it. Just search this forum for advice, if you need them. Do you have a separate /home partition? If you do, then it's easy to keep all the personal information you have (e-mails, documents etc.). If you choose the "Custom disk partitioning" (or was it "use existing partitions"?) you will be asked during the installation process which partitions you would like to format. Just leave the /home partition alone and format the rest of the Mandriva partitions (not the windoze ones - but I guess it will not even ask to format that).

Actually I was running Beagle, but just killed it. It kept the system slow and didn't quite see any point in using it. I hopefully also managed to stop loading it in the next boot. OK, if it was Beagle, I would be able to delete the folders safely then?

I just had a closer look at what my HD has "eaten" and realized I have a huge tmp folder. That tmp contains only one notable folder: kde-dude67 with the size of 34,6 GB! In that folder I have two very large folders in it: ark5DEZfz (16,1 GB) and arkXeFDBv (14,9 GB). What are these folders and do I really need them? In windoze I'd just delete the contents of tmp or temp folders, but I never thought that KDE or Gnome would collect a very large temporary folder. I'm currently using Gnome, but I have KDE installed. I use KDE very seldom, but do so every 2 months or so. Should I just delete the tmp folder and it's contents, or would that lead to problems with KDE?

I haven't figured this thing out yet. What I did was format this DVD-RAM in Windoze with InCD (came with NERO 6) to different versions of udf. I thought: Hey, this will solve my problems! Alas, no... I now get Mandriva to recognize the DVD - it even let's me see the contents of the DVD, but it won't let me do anything with it. In other words, I don't have any rights to the DVD - even as root. This is what I now get in Terminal: [root@localhost /]# umount /dev/sr0 [root@localhost /]# mount /media/cdrom mount: block device /dev/sr0 is write-protected, mounting read-only [root@localhost /]# umount /dev/sr0 [root@localhost /]# mount /dev/sr0 mount: can't find /dev/sr0 in /etc/fstab or /etc/mtab [root@localhost /]# cdrwtool -d /dev/sr0 -q using device /dev/sr0 wait_cmd: Input/output error Command failed: 5c 00 00 00 00 00 00 00 0c 00 00 00 - sense 05.30.02 [root@localhost /]# mount /media/cdrom mount: block device /dev/sr0 is write-protected, mounting read-only [root@localhost /]# Any ideas how to proceed?

I would suggest a little more patience. Just because someone hasn't answered your question in 15 or 30 mins doesn't mean that you will not get an answer. We are not bunch of people hanging around waiting for someone to post a question in MUB and in that very minute getting ready to answer. [We are a bunch of people without real lives and hangin on two dozen forums waiting for someone to ask questions :P ]

Thanks Yves; I didn't see anything there that would give me something new. It may be that I'm just too thick to figure it out... :unsure:

Nope... [root@localhost ~]# mkudffs /dev/sr0 trying to change type of multiple extents [root@localhost ~]# mkudffs /dev/dvd trying to change type of multiple extents [root@localhost ~]# mkudffs /dev/cdrom trying to change type of multiple extents [root@localhost ~]# mkudffs --media-type=dvdram /dev/sr0 trying to change type of multiple extents [root@localhost ~]# And once again, the same I tried earlier: [root@localhost ~]# cdrwtool -d /dev/sr0 -q using device /dev/sr0 wait_cmd: Input/output error Command failed: 5c 00 00 00 00 00 00 00 0c 00 00 00 - sense 05.30.02 [root@localhost ~]# cdrwtool -d /dev/dvd -q using device /dev/dvd wait_cmd: Input/output error Command failed: 5c 00 00 00 00 00 00 00 0c 00 00 00 - sense 05.30.02 [root@localhost ~]# cdrwtool -d /media/cdrom -q using device /media/cdrom set_options can't unlock door [root@localhost ~]# In the last try (as well as a few posts earlier) it says: "set_options | can't unlock door". What's all that?

:huh: Did you try here; this is the official site: http://www.mandriva.com/en/download/free That should give you an .iso file to download.

Thanks, pindakoe. I appreciate your input. I will give it one last go, but if that doesn't work, I don't know what to do. I'm a little skeptical that it will work, but definitely will give it a go. After this, the only thing left to do is to go to w.... hrmh.... to 'another place' and format it there to UDF. :blink:

Pindakoe, thanks for your tips. Let's see what I got. 1. I have installed udftools as I said earlier. That I think covers point 1. 2. I did that with the following changes: in /etc/sysconfig/pktcdvd I wrote dvd /dev/hdc (I was contemplating on writing dvd /dev/sr0) 3. Then I went and run [root@localhost dev]# pktsetup dvd /dev/sr0 [root@localhost dev]# chmod a+rw /dev/pktcdvd/dvd 4. And then it failed on this one [root@localhost dev]# cdrwtool -d /dev/sr0 -q using device /dev/sr0 wait_cmd: Input/output error Command failed: 5c 00 00 00 00 00 00 00 0c 00 00 00 - sense 05.30.02 [root@localhost dev]# The DVD is not mounted as it tries to do that every time I insert the disk, but it says it fails. Any thoughts?