The problem in this bug was due to filesystem corruption. If your
filesystem is not corrupt, you have a different problem. If you're unsure
where the problem is (and thus where to file the bug), consider opening a
question to get help before filing a bug report.
--
- mdz
--
After upgrade to
I can confirm this problem. It started for me after I upgraded to
Jaunty. My desktop preferences don't work. I have tried everything I
found on the Internet including the ones mentioned above. Please find a
screenshot attached.
This is definitely a problem with the gnome-settings-daemon as you can
Here is a screenshot of the gnome-settings-daemon command run in
terminal.
** Attachment added: "Term e2fsck.png"
http://launchpadlibrarian.net/25937239/Term%20e2fsck.png
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.l
ran e2fsck on HD, checked all partitions not just home (sda6), only home
was damaged,repaired the damage, rebooted, all things appear normal at
current time. (good to have backups) Marking bug invalid, will reopen
if symptoms reoccur.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: I
r...@dm-lappy:~# grep 'EXT3.*error' /var/log/syslog{.0,}
/var/log/syslog.0:Mar 30 13:16:30 dm-lappy kernel: [ 133.531625] EXT3-fs error
(device sda6): ext3_free_blocks_sb: bit already cleared for block 10444818
/var/log/syslog.0:Mar 30 13:16:30 dm-lappy kernel: [ 133.533535] EXT3-fs error
(dev
Attached fsck output for /home
** Attachment added: "e2fsck -n /dev/sda6"
http://launchpadlibrarian.net/24590045/fsck.txt.gz
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug
Your /home filesystem is corrupt. Many of the other symptoms are
potentially fallout from this.
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug notification because you are a
dmesg shows:
[36663.761623] EXT3-fs error (device sda6): htree_dirblock_to_tree: bad entry
in directory #1156372: rec_len % 4 != 0 - offset=0, inode=5312000, rec_len=59,
name_len=16
[36663.761635] Aborting journal on device sda6.
[36663.763203] ext3_abort called.
[36663.763207] EXT3-fs error (de
Attaching .xsession-errors
** Attachment added: ".xsession-errors"
http://launchpadlibrarian.net/24586102/.xsession-errors
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug n
Did so, results below and screenshot captured, it just launches more of
them when I access the system -> preferences -> keyboard and still
tosses an error.
dav...@dm-lappy:~$
dav...@dm-lappy:~$ ps ux | grep gnome-settings-daemon
davidm6039 0.0 0.2 28832 8040 ?Ssl 13:16 0:00
/
So, having three g-s-d's is definitively a bad thing here. Is it
possible to kill -9 them?
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug notification because you are a member
ps ux output from davidm account
** Attachment added: "Screenshot-ps_ux.png"
http://launchpadlibrarian.net/24581983/Screenshot-ps_ux.png
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You recei
gsd log such as it is
** Attachment added: "gsd.log"
http://launchpadlibrarian.net/24581726/gsd.log
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load, no meta key, etc.
https://bugs.launchpad.net/bugs/352362
You received this bug notification because you
Did not quite work as you expected but I'm attaching a screen shot.
** Attachment added: "Screenshot-gnome-settings-daemon.png"
http://launchpadlibrarian.net/24581680/Screenshot-gnome-settings-daemon.png
--
After upgrade to Jaunty Beta my machine shows different problems, , random high
load,
Ah, thanks! When you see that message, please open a terminal and do
killall gnome-settings-daemon # should say "no such process"
gnome-settings-daemon --debug --no-daemon 2>&1 | tee /tmp/gsd.log
let that run for a while (or wait until it exits), then please attach
/tmp/gsd.log. Please also a
15 matches
Mail list logo
