gnunet-qt crash at startup

Bug #189917 reported by lamyseba
4
Affects Status Importance Assigned to Milestone
gnunet-qt (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: gnunet-qt

I installed gnunet-qt on Kubuntu 7.10 Gutsy 64-bit version, up to date.

When launching the programm, it crashes with a simple error:
Segmentation fault (core dumped)

I don't know where to look for the log files

gnunet-gtk works fine for me

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Thanks for your bug.
Could you have a look at /var/crash/ and search for a file called _usr_bin_gnunet-qt*** ?
Then simply double-click on it and you'll be proposed to report a bug with more information. Right now we can do nothing.

Changed in gnunet-qt:
status: New → Incomplete
Revision history for this message
lamyseba (lamyseba) wrote :
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Could you just double-click on this file and follow the instructions to create a new bug report using the file? Launchpad will then automatically process the file to get more accurate informations using debugging packages. I cannot do this for you ATM because of my customized setup, and the report tool may get more data about your system configuration. Then we'll simply close this bug and see with the new one. Thanks

Revision history for this message
lamyseba (lamyseba) wrote : Re: [Bug 189917] Re: gnunet-qt crash at startup

Double click on the file opens kate (text editor), don't know with wich
program I should open this file. Thanks for your help!

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Oh, sorry, I don't use KDE myself so I believed this would work.
What you should do is:
- start a terminal (konsole)
- type in "/usr/share/apport/apport-qt XXX", replacing XXX with the path to the crash file (if you save it into your home folder, simply use the filename) and removing the quotes; and hit Enter

Then you should get a wizard that will ask you to report a new bug using the informations found, and that hopefully should be right... ;-)

Thanks for your work on this bug

Revision history for this message
lamyseba (lamyseba) wrote :

Done

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

Other bug subscribers

Bug attachments

Remote bug watches

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