[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-08 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/empathy/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed with SIGABRT in g_assertion_message() To manage

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-08 Thread Bug Watch Updater
** Changed in: empathy Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed with SIGABRT in g_assertion_message() To manage

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-06 Thread Launchpad Bug Tracker
This bug was fixed in the package empathy - 3.6.0-0ubuntu2 --- empathy (3.6.0-0ubuntu2) quantal-proposed; urgency=low * debian/patches/50_uoa_no_crash_database.patch: Take patch from upstream bug #685498 to not crash MC when the accounts database cannot be read, commonly

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-05 Thread Iain Lane
** Bug watch added: GNOME Bug Tracker #685498 https://bugzilla.gnome.org/show_bug.cgi?id=685498 ** Also affects: empathy via https://bugzilla.gnome.org/show_bug.cgi?id=685498 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-05 Thread Bug Watch Updater
** Changed in: empathy Status: Unknown = New ** Changed in: empathy Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-04 Thread Iain Lane
Yes, that's a good hint. Thanks! Oct 4 11:56:30 raleigh kernel: [11256.440807] type=1400 audit(1349348190.236:43): apparmor=DENIED operation=open parent=32517 profile=/usr/lib/telepathy/mission-control-5 name=/srv/home/laney/.config/libaccounts-glib/accounts.db pid=32519 comm=mission-control

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-04 Thread Iain Lane
Yeah, seems like something is dereferencing my /home - /srv/home symlink and passing this to apparmor, which denies it. If I add this to HOMEDIRS in tunables then everything works. We can see from my above strace that the open() call is using the path in /home/ though. So I suspect the problem is

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-04 Thread Jamie Strandboge
Sorry for the problems you are facing. I confirmed that the access was due to a file in /srv/home/ AppArmor necessarily resolves symlinks when making access decisions. As such, if your home directory is not in HOMEDIRS then you will get these sorts of denials. Adjusting HOMEDIRS is the correct

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-04 Thread Iain Lane
** Also affects: empathy (Ubuntu) Importance: Undecided Status: New ** Changed in: libaccounts-glib (Ubuntu) Status: New = Invalid ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: Triaged = Invalid ** Changed in: empathy (Ubuntu) Status: New = Triaged

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Apport retracing service
** Tags added: running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
Pasting my comments from the dupe. Starting program: /usr/lib/telepathy/mission-control-5 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. (process:23949): accounts-glib-WARNING **: Error opening accounts DB: unable to open

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
I'm providing a trace myself. ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: Invalid = Triaged ** Changed in: telepathy-mission-control-5 (Ubuntu) Importance: Undecided = High ** Attachment added: gdb-tp-mc5.txt

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
(gdb) break empathy-webcredentials-monitor.c:91 Breakpoint 3 at 0x7ffbf800a059: file empathy-webcredentials-monitor.c, line 91. (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/lib/telepathy/mission-control-5 [Thread

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
(gdb) print ag_manager_new_for_service_type (IM) (process:26835): accounts-glib-WARNING **: Error opening accounts DB: unable to open database file (process:26835): accounts-glib-CRITICAL **: ag_manager_new_for_service_type: assertion `AG_IS_MANAGER (manager)' failed $4 = 0 so it's because

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
I tracked this down to a failure to open the sqlite3 DB in libaccounts- glib (ag-manager.c) , | ret = sqlite3_open (filename, priv-db); | g_free (filename); | | if (ret != SQLITE_OK) | { | if (priv-db) | { | g_warning (Error opening accounts DB: %s, |

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
Hmm, no, that was a red herring sadly. If I specify the file as a path instead of a URI in my example then it always succeeds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title:

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
OK I basically duplicated the first half of libaccounts-glib's open_db() into my example and it still reliably works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
strace: open(/home/laney/.config/libaccounts-glib/accounts.db, O_RDONLY|O_CLOEXEC) = -1 EACCES (Permission denied) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
in my example; open(/home/laney/.config/libaccounts-glib/accounts.db, O_RDWR|O_CREAT|O_CLOEXEC, 0644) = 3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed with

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Iain Lane
strace: open(/home/laney/.config/libaccounts-glib/accounts.db, O_RDWR|O_CREAT|O_CLOEXEC, 0644) = -1 EACCES (Permission denied) open(/home/laney/.config/libaccounts-glib/accounts.db, O_RDONLY|O_CLOEXEC) = -1 EACCES (Permission denied) -- You received this bug notification because you are a

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-10-03 Thread Jamie Strandboge
Do you have any apparmor denials? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed with SIGABRT in g_assertion_message() To manage notifications about this

[Bug 1059233] Re: mission-control-5 crashed with SIGABRT in g_assertion_message()

2012-09-30 Thread Perfecto
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059233 Title: mission-control-5 crashed with SIGABRT in g_assertion_message() To manage notifications about this bug