"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 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 doe
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 b
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 explici
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 explici
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: "DebugThrea
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
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
** 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@lis
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
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
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 l
** 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 ad
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
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 b
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 de
16 matches
Mail list logo
