[Bug 292606] Re: dkms - error when installing custom kernel
"man 7 debconf" states- * Avoid outputting anything to stdout in your postinst, since that can confuse debconf, and postinst should not be verbose anyway. Output to stderr is ok, if you must. It might be better to redirect stdout to file descriptor 3. I see this comment in /usr/share/debconf/confmodule # Redirect standard output to standard error. This prevents common # mistakes by making all the output of the postinst or whatever # script is using this library not be parsed as confmodule commands. # # To actually send something to standard output, send it to fd 3. But I don't see any documentation outside that file that directly says that fd 3 should be used in the role of stdout. The nvidia-common package certainly cannot be expected to make up for the problem that the dkms package creates. The bad output is already sitting in a pipe headed to the debconf frontend before the nvidia-common postinst script is ever run. -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 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 292606] Re: dkms - error when installing custom kernel
This is not actually a defect in nvidia-common. It is a defect in dkms. The /etc/kernel/postinst.d/dkms script is sending messages to stdout. That script is run under /usr/share/debconf/frontend, which expects that stdout will only be used for messages to it. The actual response to the output does not occur while /etc/kernel/postinst.d/dkms is running. The error message is deferred until the /etc/kernel/postinst.d/nvidia-common script runs. That second script tries to send debconf requests to stdout. That triggers the debconf error message in response to the junk that dkms wrote earlier. Patching /etc/kernel/postinst.d/dkms to redirect stdout fixes the problem. Adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller keeps stdout clean. ** Attachment added: "Redirect stdout to stderr in /etc/kernel/postinst.d/dkms ." http://launchpadlibrarian.net/27310838/dkms.patch -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 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 250211] Re: Intrepid: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop
I had a look at the new Tx/Rx blinking and made changes to make it less annoying for me as seen with the big bright LED on my HP dv5000. The really distracting part is the slow blinking with long periods of off and on. I changed the driver to have uniformly short off_time values of 10 in the blink_tbl array. That gives a little flicker when there is network activity without a really distracting effect. The off times could be set even lower to make the blinking barely discernable. I have attached a patch that implements the change. If other folks think that is more like they want I could try pushing this upstream. ** Attachment added: "Patch to make blinking less obnoxious" http://launchpadlibrarian.net/18304734/iwl3945blink.patch -- Intrepid: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop https://bugs.launchpad.net/bugs/250211 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 237156] Re: SETRANS + libavg = SIGSEGV on Hardy
The crash occurs when the libselinux1 library is trying to do its 'fini' destructor functions when unloading. It references some thread local storage variables that were statically initialized to NULL. That first reference fails when it actually tries to allocate the variables. This patch explicity initializes those variables during the init function, making the fini function work. It seems that the real defect is in a corner case of the implementation of "__thread" feature. But changing libselinux1 this way is a practical workaround. ** Attachment added: "libselinux1_patch" http://launchpadlibrarian.net/15599819/libselinux1_patch -- SETRANS + libavg = SIGSEGV on Hardy https://bugs.launchpad.net/bugs/237156 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 99949] Re: [apport] udevd crashed with SIGSEGV in _fini()
The crash occurs when the libselinux1 library is trying to do its 'fini' destructor functions when unloading. It references some thread local storage variables that were statically initialized to NULL. That first reference fails when it actually tries to allocate the variables. This patch explicity initializes those variables during the init function, making the fini function work. It seems that the real defect is in a corner case of the implementation of "__thread" feature. But changing libselinux1 this way is a practical workaround. ** Attachment added: "libselinux1_patch" http://launchpadlibrarian.net/15605202/libselinux1_patch -- [apport] udevd crashed with SIGSEGV in _fini() https://bugs.launchpad.net/bugs/99949 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 297225] Re: rhythmbox crashed with SIGSEGV in IA__g_type_check_instance_cast()
Here is a debug backtrace of a similar crash with the same 0.11.6svn20081008-0ubuntu4 version of rhythmbox. It also has a call from podcast_download_thread() to IA__g_type_check_instance_cast(). But it is not from the same spot inside podcast_download_thread(). ** Attachment added: "DebugThreadStacktrace" http://launchpadlibrarian.net/25289900/DebugThreadStacktrace -- rhythmbox crashed with SIGSEGV in IA__g_type_check_instance_cast() https://bugs.launchpad.net/bugs/297225 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 297225] Re: rhythmbox crashed with SIGSEGV in IA__g_type_check_instance_cast()
Requested debug information provided. ** Changed in: rhythmbox (Ubuntu) Status: Invalid => New -- rhythmbox crashed with SIGSEGV in IA__g_type_check_instance_cast() https://bugs.launchpad.net/bugs/297225 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 292606] Re: dkms - error when installing custom kernel
Flushing stdout is not going to help with this problem. As I said in comment #17, the error is caused by /etc/init.d/dkms_autoinstaller sending text to debconf via stdout. Flushing output within /etc/kernel/postinst.d/nvidia-common won't undo that error. Debconf has already gotten the bad command before /etc/kernel/postinst.d/nvidia-common is started. Patching /etc/kernel/postinst.d/dkms to redirect stdout DOES FIX the problem. Adding "1>&2" to the invocation of /etc/init.d/dkms_autoinstaller keeps stdout clean. -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 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 292606] Re: dkms - error when installing custom kernel
** Package changed: nvidia-common (Ubuntu) => dkms (Ubuntu) -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 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 194029] Re: 2.6.24-8 Introduces Network Issue
This problem with synergyc is actually synergy's own defect related to using X11 from multiple threads. The connection to the kernel schedule is seen because a race condition in the application is turning out badly more often than it used to. But the right fix for this problem is in synergy. I just added this fix as a comment to the upstream report at http://sourceforge.net/tracker/index.php?func=detail&aid=1930587&group_id=59275&atid=490467 This problem is caused by a bad assumption in the use of poll or select on the X11 socket connection when waiting for an event in CXWindowsEventQueueBuffer::waitForEvent*(). The assumption is that any new event will wake the thread when the socket becomes ready to read. The flaw in that reasoning is that Xlib will read the data for several events at once if it is available. The calls to XSendEvent and XFlush in CXWindowsEventQueueBuffer::flush can read data from the X11 socket and put it in an Xlib buffer. That will change the XPending and isEmpty status without ever finishing the poll or select call. The flush function can be called either from another thread via addEvent or in the direct call to flush in waitForEvent itself. The severity of these problems will vary greatly with changes to the scheduling of threads and the X server. It is not surprising that they show up more often with some kernels than with others. The attached diffs fix the two cases. The call to flush in waitForEvent is followed by a new call to isEmpty to check if the flush caused any events to be read. The call to flush in addEvent is followed by writing a character to the write side of a pipe. The poll or select call in waitForEvent then waits for a readable state on either the X11 socket or the pipe. ** Attachment added: "fix for lag of synergyc on input" http://launchpadlibrarian.net/13995863/synergy_diffs -- 2.6.24-8 Introduces Network Issue https://bugs.launchpad.net/bugs/194029 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 194029] Re: 2.6.24-8 Introduces Network Issue
I found a couple of problems in the previous patch. The test for isEmpty had the sense backwards. I also reduced the number of writes to the wake-up pipe and increased the amount read from the pipe per call. The select-based code (which ubuntu doesn't use) also had a couple of defects that I found and fixed after forcing the non-poll based code to be used. I don't see how those problems could lead to the assertion in XGetXCBBuffer. There may be a latent problem with reentrant calls to Xlib that still hides on my single cpu system. A dual core system may help to bring out that bad behavior. But I haven't put hardy on such a system yet. ** Attachment added: "fix for lag of synergyc on input" http://launchpadlibrarian.net/14027236/synergy_diffs -- 2.6.24-8 Introduces Network Issue https://bugs.launchpad.net/bugs/194029 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 109309] Re: restricted manager dies on startup using live CD
It may have been a problem with the CD burned from an ISO. I tried this again with an official CD and it ran the restricted-manager successfully for two trials. Unfortunately, I didn't keep track of the CD that I was using when the problem occurred. -- restricted manager dies on startup using live CD https://bugs.launchpad.net/bugs/109309 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 109309] Re: restricted manager dies on startup using live CD
** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7392668/Dependencies.txt ** Attachment added: "Devices.txt" http://librarian.launchpad.net/7392669/Devices.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7392670/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7392671/ProcStatus.txt ** Attachment added: "Traceback.txt" http://librarian.launchpad.net/7392672/Traceback.txt ** Attachment added: "XorgConf.txt" http://librarian.launchpad.net/7392673/XorgConf.txt -- restricted manager dies on startup using live CD https://bugs.launchpad.net/bugs/109309 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 109309] restricted manager dies on startup using live CD
Public bug reported: Binary package hint: restricted-manager restricted-manager died when started from the panel icon. The system was a HP dv5020us laptop. ProblemType: Crash Architecture: i386 Date: Mon Apr 23 01:23:20 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/restricted-manager InterpreterPath: /usr/bin/python2.5 Package: restricted-manager 0.20 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/restricted-manager --check ProcCwd: /home/ubuntu ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/restricted-manager', '--check'] SourcePackage: restricted-manager Uname: Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux ** Affects: restricted-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- restricted manager dies on startup using live CD https://bugs.launchpad.net/bugs/109309 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 292606] Re: dkms - error when installing custom kernel
The actual fix to dkms is not adding flushing of stdout. The fix is redirecting /etc/init.d/dkms_autoinstaller output to stderr so that it doesn't send confusing output to debconf via stdout. -- dkms - error when installing custom kernel https://bugs.launchpad.net/bugs/292606 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 250211] Re: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop
The 3.0 kernel in the 11.11 release has a similar module parameter, but in a different module name. Adding this iwl_legacy parameter to a /etc/modprobe.d/wlan.conf file calms the blinking on 11.11. options iwl_legacy led_mode=1 (But I have sometimes seen the light remain off when the the wlan device is active on 11.11.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/250211 Title: WLAN LED blinks incessantly on iwl3945 | iwl4965 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/250211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
