I have been testing LinuxFromScratch and wanted to use only upstart with it (
no old sysv scripts ).
Mountall hangs when emitting events using some ~20% cpu if root is mounted as
read-only at boot.
Changing it to rw seems to make it boot just fine.
--
Startup fails somewhere around filesystem
So far on every boot.
I have set up tty1 to start on local-filesystems. initctl emit works and
returns immediatly.
Then emitting local-filesystems for second time, without rebooting, initctl
itself hangs, i'll have to ctrl+c it and then it usually returns immediately
again. Currently tty1,
Ok, not very handy with gdb yet. mountall backtrace in attachment.
initctl backtrace:
0x00393422 in __kernel_vsyscall ()
#0 0x00393422 in __kernel_vsyscall ()
#1 0x001e4b9c in poll () from /lib/libc.so.6
#2 0x00be80fb in _dbus_poll (fds=0xbfbcaa34, n_fds=1, timeout_milliseconds=-1)
at
Meant to add, that is 'vanilla' upstart-0.6.3 , ubuntu 0.6.3-10 is the
same, but 'local-filesystems' isn't emitted until 'filesystem' is
emitted too.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification
So mountall keeps writing mtab over and over again.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I did fresh install on Jaunty and if i wasn't imagining things then i did this:
1.) X running in EXA (in default mode), alpha blending is correct, though
compiz is bit sluggish, glxgears ~195fps (compiz vsync off)
2.) Added AccelMethod UXA to xorg.conf, init.d/gdm stop/start, alpha blending
I managed to find my cause, it is the fusion-icon.
Reproduce:
1.) install fusion-icon
2.) Set window manager to compiz
3.) Reload window manager
Appearently as fusion-icon starts at login, it forces compiz to reload.
Doing metacity --replace compiz --replace , returns alpha blending
to
More correctly, it is compiz with --indirect-rendering
--
DRI2: (UXA) white transparency artifacts with compiz [patch]
https://bugs.launchpad.net/bugs/324854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Your pulseaudio could have set pc speaker as default sink as mine did.
Anyway i forced with uncommenting in the default.pa this, because killing pa
daemon and running it from terminal complained that it something was using
hw0,0 already.
load-module module-alsa-sink device=hw:0,0
But it
Pulseaudio's default sink is set to
alsa_output.platform_pcspkr_alsa_playback_0
--
no sound on intrepid
https://bugs.launchpad.net/bugs/246800
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hope that this gets fixed soon. Old gutsy kernel seemed fine.
[ 130.843926] psmouse.c: failed to re-enable mouse on isa0060/serio1
[ 130.843932] psmouse.c: resync failed, issuing reconnect request
[ 131.468100] psmouse.c: Wheel Mouse at isa0060/serio4/input0 lost
synchronization, throwing 2
Dmesg too
** Attachment added: dmesg
http://launchpadlibrarian.net/14982831/dmesg
--
ps2 mouse erratic - parity errors
https://bugs.launchpad.net/bugs/119194
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Forgot.
cat /proc/version_signature
Ubuntu 2.6.24-18.32-generic
--
ps2 mouse erratic - parity errors
https://bugs.launchpad.net/bugs/119194
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Getting same errors on Compal HEL81C board, using intel 945 chipset.
including bios bug #81
[ 149.192000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 149.192000] ata1.00: (BMDMA stat 0x65)
[ 149.192000] ata1.00: cmd c8/00:a0:29:dc:42/00:00:00:00:00/e3 tag 0 cdb 0x1e
data 81920
** Attachment added: dmesg
http://launchpadlibrarian.net/10899804/dmesg.txt
--
it takes an awful long time to boot 2.6.22-14-generic - probably related to
some ATA/IDE problem in the kernel
https://bugs.launchpad.net/bugs/164302
You received this bug notification because you are a member of
15 matches
Mail list logo