udisksd crashed with SIGSEGV in udisks_daemon_util_check_authorization_sync()

Bug #1032744 reported by Nicholas Skaggs
610
This bug affects 99 people
Affects Status Importance Assigned to Milestone
udisks2 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Udisks crashed upon login to desktop

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: udisks2 1.99.0-1
ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0
Uname: Linux 3.5.0-7-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Fri Aug 3 12:53:46 2012
ExecutablePath: /usr/lib/udisks2/udisksd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
ProcCmdline: /usr/lib/udisks2/udisksd --no-debug
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-7-generic root=UUID=240dad77-875f-4488-8f38-63a17ced0a83 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x42e62d: mov (%rax),%ebp
 PC (0x0042e62d) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
 ?? ()
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: udisksd crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to quantal on 2012-07-20 (13 days ago)
UserGroups:

dmi.bios.date: 06/25/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14
dmi.board.name: 965P-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 965P-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Nicholas Skaggs (nskaggs) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 udisks_daemon_util_check_authorization_sync (daemon=daemon@entry=0x2405700, object=<optimized out>, action_id=0x437110 "org.freedesktop.udisks2.filesystem-mount", options=options@entry=0x7f960c02d430, message=message@entry=0x4371d0 "Authentication is required to mount $(drive)", invocation=invocation@entry=0x246dcc0) at udisksdaemonutil.c:660
 handle_mount (filesystem=<optimized out>, invocation=0x246dcc0, options=0x7f960c02d430) at udiskslinuxfilesystem.c:1397
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=cif@entry=0x7f960bffe950, fn=fn@entry=0x41b9f0 <handle_mount>, rvalue=0x7f960bffe8b0, avalue=avalue@entry=0x7f960bffe850) at ../src/x86/ffi64.c:492
 g_cclosure_marshal_generic (closure=0x2463450, return_gvalue=0x7f960bffeaf0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x41b9f0) at /build/buildd/glib2.0-2.33.6/./gobject/gclosure.c:1454

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in udisks2 (Ubuntu):
importance: Undecided → Medium
summary: - udisksd crashed with SIGSEGV in ffi_call_unix64()
+ udisksd crashed with SIGSEGV in
+ udisks_daemon_util_check_authorization_sync()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in udisks2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

What happens here is that udisks2 expects polkit_authority_check_authorization_sync() to return an error if it returns NULL, but it doesn't:

        result = 0x0
        error = 0x0

polkit_authority_check_authorization_finish() looks reasonable, i. e. it returns NULL precisely if an error is set. So I suppose what happens here is that one of the initial assertions (g_return_val_if_fail) fails. The stack trace does not tell us already what's wrong, the authority, subject, etc. arguments look reasonable. So we'd need to capture stderr to see what's really going on here.

Half of the duplicates mention that this crash report is shown at system startup, but my hunch is that it really crashed during shutdown, and on the next system boot you get the crash notification from the past shutdown process.

Did anyone of the reporters encounter this crash during a running desktop session, i. e. not during login? Did anyone actually see something not work right due to this? If so, do you have a way to reproduce this crash?

Changed in udisks2 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jaydip Guha (guha-jaydip) wrote :

Already have experienced this issue few times

Revision history for this message
Jaydip Guha (guha-jaydip) wrote :

I am getting this error very frequently in my 12.10 box (upgraded from 12.04).

tags: added: bugpattern-needed
Revision history for this message
Martin Pitt (pitti) wrote :

This gets quite a number of duplicates, and yet none of the reporters answered to my questions in comment 7 yet. Do all of you get this crash report at the start of the session? (in which case it's rather likely that this happens on shutdown, and the next time you start the computer it shows the crash notification).

Did anyone actually see something not work right due to this? If so, do you have a way to reproduce this crash?

Revision history for this message
Stephen Dorman (nexusstephen) wrote :

@pitti

Only got an email for this today but I'll confirm your hunch, it's a crash report that is generated on login and relates to an error at shutdown. I'd need to check to see what precisely prompted this report since that particular behaviour has been common for me on Quantal and, most often, is related to "waking" Unity (sidebar or Dash) after a period of inactivity.

Revision history for this message
Stephen Dorman (nexusstephen) wrote :

https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1057869

That was my original bug report (thought that was the one but would rather check than send wrong info). This ceased to be a problem after an update a few days later. At the time it was entirely to do with trying to mount the Android device and I'm not aware of generating any other udisksd crash reports since then.

Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

I'll concur with Stephen, I've not had the error in awhile. I got it on login, and I believe it may have also been me trying to mount a usb or android device.

Revision history for this message
Tony Weddle (txa5822su-tony-csu0kx1kj) wrote :

I've also had this a few times in 12.04 and now 12.10. Following a read of the comments I note that the last occurrence was probably a result of a failed USB pendrive mount in the previous session. I inserted the pendrive and heard the hard disk whirring away (maybe capturing crash info) but no pendrive was mounted or even visible unmounted. So I restarted with the pendrive inserted and received the above error on startup, though the pendrive was now visible. It's a shame this seems to have been around for some time. It's certainly annoying if I have to reboot to get a USB drive mounted.

As possible further info, I now recall that, in Nautilus, besides not seeing the pendrive, I also did not see many of the drives I normally see (such as a USB hard drive and some other permanent hard disks (other than the main system drive).

Revision history for this message
Christian Semmens (christian-semmens) wrote :

(Dell Optiplex 990)
Still happening for me intermittently. The problem went away for a while, but seems to be back again now.
Always on first login after turning on computer.
Log in to Unity is slow for first attempt. I also have problems with X not starting every time, Just a mouse pointer overlaying the tty screen.. Sometimes this clears on its own after a couple of minutes, sometimes lightdm needs a restart. I realise this is a different bug, but mention it in passing.

tags: added: raring
Revision history for this message
Treize Hélicène (helicene13) wrote :

This happens to me at each startup when the update notifier starts

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for udisks2 (Ubuntu) because there has been no activity for 60 days.]

Changed in udisks2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.