Set as Invalid as it's seem to not be a conduit bug. Please re-open it
with you think it's not the case.
** Changed in: conduit (Ubuntu)
Status: Incomplete = Invalid
--
conduit crashed with GError in __init__()
https://bugs.launchpad.net/bugs/315792
You received this bug notification
Thanks for the test.
Looking at the xsession output, conduit seems ok (no errors from it).
python-pycurl-dbgsym is a package only used for debug.If you don't need it, you
should remove it and try again conduit to see if you have a apport report from
it.
** Changed in: conduit (Ubuntu)
Thanks for your bug report.
Do you still have this problem ?
If so, could you describe the steps to reproduce this bug ?
** Changed in: conduit (Ubuntu)
Status: New = Incomplete
--
conduit crashed with GError in __init__()
https://bugs.launchpad.net/bugs/315792
You received this bug
Hi Julien,
no I did not experience it again as I downgraded to 8.10 and did not
have it installed. I installed it now on 8.10. I do not remember what
triggered this on jaunty. Notice it was the dirty kernel.
Cheers,
Thomas
--
conduit crashed with GError in __init__()
Thanks for the test. I close the bug for now, but if you find this bug
again, feel free to reopen it.
** Changed in: conduit (Ubuntu)
Status: Incomplete = Invalid
--
conduit crashed with GError in __init__()
https://bugs.launchpad.net/bugs/315792
You received this bug notification
Sorry Julien, reopening and confirming in 8.10, due to .xsession-errors.
I will try for valgrind and gdb.
** Changed in: conduit (Ubuntu)
Status: Invalid = New
--
conduit crashed with GError in __init__()
https://bugs.launchpad.net/bugs/315792
You received this bug notification because
** Attachment added: .xsession-errors
http://launchpadlibrarian.net/23089903/.xsession-errors
--
conduit crashed with GError in __init__()
https://bugs.launchpad.net/bugs/315792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Valgrind does not seem to indicate much to me, two added lines in
xsession-errors:
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a
timestamp of 0 for 0x380001f (Conduit - )
Window manager warning: meta_window_activate called by a pager with a 0
timestamp; the pager
No gdb possible, but valgrind does seem to be important, forget my
previous remark.
Also:
tho...@thomas-laptop:~$ ls -la /var/crash
total 560
drwxr-xr-x 2 root root 4096 2009-02-22 21:07 .
drwxr-xr-x 16 root root 4096 2009-02-24 03:09 ..
-rw--- 1 root root 557805 2009-02-22 21:08
Sorry,
end of story:
tho...@thomas-laptop:~$ apport-cli --crash-file=/var/crash/python-
pycurl-dbgsym.0.crash
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
*** Problem in
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21081695/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/21081696/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/21081697/ProcStatus.txt
** Attachment
** Tags removed: need-duplicate-check
--
conduit crashed with GError in __init__()
https://bugs.launchpad.net/bugs/315792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
12 matches
Mail list logo
