Ubuntu
update-notifier package

update-notifier crashed with SIGSEGV in __libc_start_main()

Bug #286037 reported by Michał Derbiszewski
116
This bug affects 5 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Fix Released
Medium
Unassigned
Intrepid
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: update-notifier

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/update-notifier
NonfreeKernelModules: nvidia
Package: update-notifier 0.71.6
ProcAttrCurrent: unconfined
ProcCmdline: update-notifier
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: update-notifier crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups:

Tags: apport-crash

Related branches

lp:update-notifier/ubuntu
Dennis Kaarsemaker: Pending requested
Diff: 0 lines
lp:ubuntu/lucid/update-notifier
Revision history for this message
Michał Derbiszewski (derbich1) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:guest_user () at update-notifier.c:364
main (argc=1, argv=0x7fff0ae18868) at update-notifier.c:439

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in update-notifier:
importance: Undecided → Medium
Revision history for this message
Martin Pitt (pitti) wrote :

Confirmed by me and two duplicates.

One possible reason might be the change in http://bazaar.launchpad.net/~ubuntu-core-dev/update-notifier/ubuntu/revision/387: getlogin() can return NULL.

I don't think we need this test in the first place. Just not starting u-n for any system user (uid < 500) should suffice.

Changed in update-notifier:
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-notifier - 0.71.7

---------------
update-notifier (0.71.7) intrepid; urgency=low

  * src/update-notifier.c:
    - check for all system user UIDs and do not start in this case
      (LP: #286037)

 -- Michael Vogt <email address hidden> Mon, 20 Oct 2008 15:13:27 +0200

Changed in update-notifier:
status: Confirmed → Fix Released
Revision history for this message
Prosthetic Head (propanone) wrote :

I just experienced this and I am up to date as of 30 mins ago! I'm using update manager version 0.93.27. So this is a different bug to that fixed in 0.71.7 or is a regression. (I'm beta testing 8.10)

    "crispin@carnifex:~$ update-manager --version
     update-manager: version 0.93.27"

Revision history for this message
Prosthetic Head (propanone) wrote :

Please disregard my previous post.

My apologies, i miss-read your post. I now realize it should be fixed in " update-notifier - 0.71.7" and NOT update manager as i incorrectly assumed. Thanks and sorry for causing confusion.

Revision history for this message
David D Miller (justdave) wrote :

I'd like to request this be backed out. I run a Mythbuntu system, and the system automatically logs in as the 'mythtv' user, which is a system user. Now I can no longer tell when my system needs an update because you've disabled the update-manager on me.

Revision history for this message
David D Miller (justdave) wrote :

hmm, nevermind, current Mythbuntu apparently has you create a normal user for the desktop/frontend, and only uses the mythtv userid for the backend. I'm a victim of upgrading this thing over and over since Edgy or so. I'll create a new user and migrate everything over.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.