This started happening to me this morning - killing devkit-daemon has no
effect, it just starts again. While it is going the disk is also going
crazy. It kept happening after a restart, so eventually I renamed the
devkit-daemon binary so it couldn't start.
--
large memory leak in devkit-daemon?
Is the patch available for amd64? I don't see 2.6.27-8 in proposed
--
kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100
https://bugs.launchpad.net/bugs/286285
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also on a WPA2 network, Dell inspiron 1720 with an intel wireless
4965. The problem seems to occur most often when there is a lot of
wireless activity, but it is too sporadic to pin down exactly.
--
kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100
On mine it starts like this:
Oct 28 16:15:47 jeremy-laptop kernel: [ 3226.329828] BUG: scheduling while
atomic: swapper/0/0x0100
Oct 28 16:15:47 jeremy-laptop kernel: [ 3226.329843] Modules linked in:
binfmt_misc rfcomm sco bridge stp bnep l2cap vboxdrv ppdev acpi_cpufreq
cpufreq_stats
I seem to be getting the same problem
--
extremely large log files in /var/log
https://bugs.launchpad.net/bugs/289581
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: f-spot
When launching F-Spot X crashes and I'm returned to the login screen in
hardy
f-spot version 0.4.2-Ubuntu2 or 0.4.2-Ubuntu1
Error when launched from console: f-spot: Fatal IO Error 11 (Resource
Temporarily Unavailable) on X server :0.0
**
tail /var/log/Xorg.0.log.old
(**) Option Device /dev/input/event9
(--) Mouse0 touchpad found
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7fc6420]
Fatal server error:
Caught signal 11. Server aborting
--
f-spot crashes X
https://bugs.launchpad.net/bugs/194926
You received
This is reproducible on new user accounts. However, I've found the
likely culprit is the NVidia drivers as it doesn't happen if I revert to
nv. I don't know why f-spot is triggering the problem.
--
f-spot crashes X
https://bugs.launchpad.net/bugs/194926
You received this bug notification because
Upgrading from NVIDIA driver from 169.07 to 169.09 fixed the problem
--
f-spot crashes X
https://bugs.launchpad.net/bugs/194926
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
