Crashes on login with dbus_g_method_return_error()

Bug #68347 reported by sumsoul
54
Affects Status Importance Assigned to Milestone
bluez-gnome (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This appears to happen on Dapper, at least on amd64, and seems related to dbus_g_method_return_error() which segfaults.

Revision history for this message
sumsoul (summerauer-andreas) wrote :
Revision history for this message
dushkal (dushkal) wrote :

I also have this crash in Edgy sometimes (especially when I'm using WiFi)

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Me too

Revision history for this message
Daniel Holbach (dholbach) wrote :

Confirmed by Duplicate. Bug 66323 has two proposed patches for this:
http://librarian.launchpad.net/4822238/implement_icon_policy_settings.patch and a much shorter version (not touching the icon show policy).

Changed in bluez-gnome:
assignee: nobody → bluetooth
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Otto Jongerius (otto-0tt0) wrote :

Ubuntu 6.10, running 2.6.17-10-386

Revision history for this message
Vyacheslav Rodionov (bepcyc) wrote :

Ubuntu 6.10, kernel 2.6.17-10-generic (AMD64)
using WiFi (WPA)

$ lspci|grep -i network
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

Simon Law (sfllaw)
description: updated
Revision history for this message
Jad Madi (jad) wrote :

I've same problem

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Is this still an issue?, there has been several upgrades since the last report, but no activity in this bug since January, could this be solved by any of those upgrades?. Thanks in advance.

Changed in bluez-gnome:
status: Confirmed → Incomplete
Revision history for this message
Basilio Kublik (sourcercito) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks again!

Changed in bluez-gnome:
assignee: bluetooth → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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