[Bug 474907] Re: Startup fails somewhere around "filesystem" or HAL being started
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474907] Re: Startup fails somewhere around "filesystem" or HAL being started
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474907] Re: Startup fails somewhere around "filesystem" or HAL being started
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 dbus-sysdeps-unix.c:1970 #3 0x00be019f in socket_do_iteration (transport=0x8f4fa48, flags=6, timeout_milliseconds=-1) at dbus-transport-socket.c:1066 #4 0x00bde3bc in _dbus_transport_do_iteration (transport=0x8f4fa48, flags=6, timeout_milliseconds=-1) at dbus-transport.c:956 #5 0x00bc8cf3 in _dbus_connection_do_iteration_unlocked ( connection=0x8f4fe08, flags=6, timeout_milliseconds=1) at dbus-connection.c:1163 #6 0x00bcb354 in _dbus_connection_block_pending_call (pending=0x8f500e0) at dbus-connection.c:2328 #7 0x00bd8b71 in dbus_pending_call_block (pending=0xfdfc) at dbus-pending-call.c:705 #8 0x0804afe0 in emit_action (command=0x8f4f580, args=0x8f4f744) at initctl.c:976 #9 0x08065f33 in nih_command_handle (parent=, argc=, argv=0x8f4f484, options=0x8074660, commands=0x8f4f4f4, command=0x) at command.c:344 #10 0x0806644a in nih_command_parser (parent=0x0, argc=3, argv=0xbfbcad84, options=0x8074660, commands=0x80746c0) at command.c:182 #11 0x0804a3d2 in main (argc=3, argv=0xbfbcad84) at initctl.c:1372 #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 dbus-sysdeps-unix.c:1970 #3 0x00be019f in socket_do_iteration (transport=0x8f4fa48, flags=6, timeout_milliseconds=-1) at dbus-transport-socket.c:1066 #4 0x00bde3bc in _dbus_transport_do_iteration (transport=0x8f4fa48, flags=6, timeout_milliseconds=-1) at dbus-transport.c:956 #5 0x00bc8cf3 in _dbus_connection_do_iteration_unlocked ( connection=0x8f4fe08, flags=6, timeout_milliseconds=1) at dbus-connection.c:1163 #6 0x00bcb354 in _dbus_connection_block_pending_call (pending=0x8f500e0) at dbus-connection.c:2328 #7 0x00bd8b71 in dbus_pending_call_block (pending=0xfdfc) at dbus-pending-call.c:705 #8 0x0804afe0 in emit_action (command=0x8f4f580, args=0x8f4f744) at initctl.c:976 #9 0x08065f33 in nih_command_handle (parent=, argc=, argv=0x8f4f484, options=0x8074660, commands=0x8f4f4f4, command=0x) at command.c:344 #10 0x0806644a in nih_command_parser (parent=0x0, argc=3, argv=0xbfbcad84, options=0x8074660, commands=0x80746c0) at command.c:182 #11 0x0804a3d2 in main (argc=3, argv=0xbfbcad84) at initctl.c:1372 #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 dbus-sysdeps-unix.c:1970 #3 0x00be019f in socket_do_iteration (transport=0x8f4fa48, flags=6, timeout_milliseconds=-1) at dbus-transport-socket.c:1066 #4 0x00bde3bc in _dbus_transport_do_iteration (transport=0x8f4fa48, flags=6, timeout_milliseconds=-1) at dbus-transport.c:956 #5 0x00bc8cf3 in _dbus_connection_do_iteration_unlocked ( connection=0x8f4fe08, flags=6, timeout_milliseconds=1) at dbus-connection.c:1163 #6 0x00bcb354 in _dbus_connection_block_pending_call (pending=0x8f500e0) at dbus-connection.c:2328 #7 0x00bd8b71 in dbus_pending_call_block (pending=0xfdfc) at dbus-pending-call.c:705 #8 0x0804afe0 in emit_action (command=0x8f4f580, args=0x8f4f744) at initctl.c:976 #9 0x08065f33 in nih_command_handle (parent=, argc=, argv=0x8f4f484, options=0x8074660, commands=0x8f4f4f4, command=0x) at command.c:344 #10 0x0806644a in nih_command_parser (parent=0x0, argc=3, argv=0xbfbcad84, options=0x8074660, commands=0x80746c0) at command.c:182 #11 0x0804a3d2 in main (argc=3, argv=0xbfbcad84) at initctl.c:1372 ** Attachment added: "bt-mountall.log" http://launchpadlibrarian.net/36232968/bt-mountall.log -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474907] Re: Startup fails somewhere around "filesystem" or HAL being started
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, acpid and dbus are started on local-filesystems event. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474907] Re: Startup fails somewhere around "filesystem" or HAL being started
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" 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324854] Re: DRI2: (UXA) white transparency artifacts with compiz [patch]
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324854] Re: DRI2: (UXA) white transparency artifacts with compiz [patch]
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 correct behaviour. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324854] Re: DRI2: (UXA) white transparency artifacts with compiz [patch]
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 seemed correct, glxgear ~500fps, installed extra plugins for compiz Then for the night i shutdowned the laptop and in the morning UXA alpha blending was off again , glxgears ~320fps openGL stuff throw: get fences failed: -1 param: 6, val: 0 ** Attachment added: "info.txt" http://launchpadlibrarian.net/26018974/info.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246800] Re: no sound on intrepid
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246800] Re: no sound on intrepid
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 might work without this. ~$ asoundconf list Names of available sound cards: Intel pcsp -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119194] Re: ps2 mouse erratic - parity errors
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119194] Re: ps2 mouse erratic - parity errors
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119194] Re: ps2 mouse erratic - parity errors
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 bytes away. ** Attachment added: "lspci vvnn" http://launchpadlibrarian.net/14982829/lspci.log -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164302] Re: it takes an awful long time to boot 2.6.22-14-generic - probably related to some ATA/IDE problem in the kernel
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 in [ 149.216000] ata1.00: configured for UDMA/100 [ 149.404000] ata1.01: configured for UDMA/33 [ 149.404000] ata1: EH complete [ 151.604000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 151.604000] ata1.00: (BMDMA stat 0x65) [ 151.604000] ata1.00: cmd c8/00:a0:29:dc:42/00:00:00:00:00/e3 tag 0 cdb 0x1e data 81920 in [ 151.628000] ata1.00: configured for UDMA/100 [ 151.816000] ata1.01: configured for UDMA/33 [ 151.816000] ata1: EH complete *-ide description: IDE interface product: 82801G (ICH7 Family) IDE Controller vendor: Intel Corporation physical id: 1f.1 bus info: [EMAIL PROTECTED]:00:1f.1 logical name: scsi0 version: 02 width: 32 bits clock: 33MHz capabilities: ide bus_master emulated configuration: driver=ata_piix latency=0 module=ata_piix *-disk description: SCSI Disk product: SAMSUNG HM160HC vendor: ATA physical id: 0.0.0 bus info: [EMAIL PROTECTED]:0.0.0 logical name: /dev/sda version: LQ10 serial: S12TJD0PA33274 size: 149GB capabilities: partitioned partitioned:dos configuration: ansiversion=5 -- 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164302] Re: it takes an awful long time to boot 2.6.22-14-generic - probably related to some ATA/IDE problem in the kernel
** 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
