[Bug 859161] New: firefox,debug,debug installed in strange place
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c0 Summary: firefox,debug,debug installed in strange place Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla@forge.provo.novell.com ReportedBy: epistemepromeneur@free.fr QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 kde report generator expects debug symbols in /usr/lib64/firefox but they are in /usr/lib/debug/usr/lib64/firefox/ then no track crash report can be generated see the extract from yast software manager *************************************************************************** /usr/lib/debug/.build-id/f1/c2a8846c52fd97d69734c27fc2422b2b51b84a.debug /usr/lib/debug/.build-id/fb/c6af02b4cfe7baee385528f07f3e97377c15cc /usr/lib/debug/.build-id/fb/c6af02b4cfe7baee385528f07f3e97377c15cc.debug /usr/lib/debug/usr/lib64/firefox/browser/components/libbrowsercomps.so.debug /usr/lib/debug/usr/lib64/firefox/components/libdbusservice.so.debug /usr/lib/debug/usr/lib64/firefox/components/libmozgnome.so.debug /usr/lib/debug/usr/lib64/firefox/crashreporter.debug /usr/lib/debug/usr/lib64/firefox/firefox.debug /usr/lib/debug/usr/lib64/firefox/libmozalloc.so.debug /usr/lib/debug/usr/lib64/firefox/libmozsqlite3.so.debug /usr/lib/debug/usr/lib64/firefox/libxul.so.debug /usr/lib/debug/usr/lib64/firefox/mozilla-xremote-client.debug *********************************************************************** Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c1 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2014-01-17 09:21:47 UTC --- There is a standardized way where packages on openSUSE install debugsymbols. That's even automated and cannot be changed in the package. So the KDE report generator should adapt IMHO. btw. Firefox has its own crashreporter which works w/o debug symbols (actually there is currently an unknown issue so reports aren't decoded currently). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c2 --- Comment #2 from Episteme PROMENEUR <epistemepromeneur@free.fr> 2014-01-17 09:38:11 UTC ---
So the KDE report generator should adapt IMHO.
what do you mean ? do you mean there is abug in kde crash report generator then i must send a kde bug report ?
btw. Firefox has its own crashreporter which works w/o debug symbols (actually there is currently an unknown issue so reports aren't decoded currently).
how to use it ? thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c3 --- Comment #3 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2014-01-17 09:44:51 UTC --- (In reply to comment #2)
So the KDE report generator should adapt IMHO.
what do you mean ?
do you mean there is abug in kde crash report generator then i must send a kde bug report ?
I think there is because on openSUSE all binaries are stripped and do not contain debug symbols. Therefore we create debugsymbols packages automatically in the buildsystem and the file location for them is consistent on the whole distribution. If KDE does not respect that it needs to be fixed or modified for openSUSE. So feel free to open a bug against that.
btw. Firefox has its own crashreporter which works w/o debug symbols (actually there is currently an unknown issue so reports aren't decoded currently).
how to use it ?
Usually if you haven't changed anything manually once Firefox crashes a popup will shop up asking you if you want to submit the crash report to mozilla. Since we are working together with them our debug symbols are provided to their decoder so we can actually look into crashes on their webservice. You can find a reference to your submitted crashes via about:crashes. In case you don't get the crashreporter popup I'm wondering what's blocking it and finding a reason for that would be interesting for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c4 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> 2014-01-17 09:54:29 UTC --- (In reply to comment #3)
(In reply to comment #2)
So the KDE report generator should adapt IMHO.
what do you mean ?
do you mean there is abug in kde crash report generator then i must send a kde bug report ?
I think there is because on openSUSE all binaries are stripped and do not contain debug symbols. Therefore we create debugsymbols packages automatically in the buildsystem and the file location for them is consistent on the whole distribution. If KDE does not respect that it needs to be fixed or modified for openSUSE. So feel free to open a bug against that.
KDE's bug reporter does not care where the debug symbols are installed. It just uses gdb to get a backtrace. And this did work the last time I tried. But: you have to have the exact same version of the debuginfo package installed. If that is different, gdb will refuse to load the symbols. So please check that your MozillaFirefox and MozillaFirefox-debuginfo packages have the exact same version. Probably you have Firefox from the update repo, but the debuginfo from the standard debug repo (you would need the one from debug-update in that case) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c5 --- Comment #5 from Episteme PROMENEUR <epistemepromeneur@free.fr> 2014-01-17 11:00:27 UTC ---
KDE's bug reporter does not care where the debug symbols are installed. It just uses gdb to get a backtrace. And this did work the last time I tried.
if i send this bug report it is because it does not work . when crash comes then in the bug generator i ask to install debug symbol then debug packets were installed then when i tried to generate a report then it loaded again an incomplete trace . if i click on "files to install" then i have the message it expects debug symbols in "/usr/lib64/firefox/" i checked that there is same version for firefox packets 26.0-4.2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c6 --- Comment #6 from Wolfgang Bauer <wbauer@tmo.at> 2014-01-17 11:17:41 UTC --- (In reply to comment #5)
if i click on "files to install" then i have the message it expects debug symbols in "/usr/lib64/firefox/" Yes, but that doesn't matter.
Again, it just calls gdb to get the backtrace, so gdb has to find the symbols. If your backtrace is incomplete although you have MozillaFirefox-debuginfo-26.0-4.2 installed, you may be missing some other necessary debuginfo packages. Please check in YaST->Software Repositories that both the debug and the debug-update repo are enabled, the KDE bug reporter does not do that for you. Then "Install debug symbols" should work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c7 --- Comment #7 from Wolfgang Bauer <wbauer@tmo.at> 2014-01-17 11:21:07 UTC --- (In reply to comment #6)
(In reply to comment #5)
if i click on "files to install" then i have the message it expects debug symbols in "/usr/lib64/firefox/" Yes, but that doesn't matter.
PS: It _does not_ say that it expects debug symbols in "/usr/lib64/firefox". It displays a list of files for which debug symbols are missing. And some of them are of course in /usr/lib64/firefox/. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c8 --- Comment #8 from Episteme PROMENEUR <epistemepromeneur@free.fr> 2014-01-17 11:30:06 UTC ---
In case you don't get the crashreporter popup I'm wondering what's blocking it and finding a reason for that would be interesting for me.
this is the case no popup window and randomly when i relaunch firefox then it asks for me what i want to do : close or restore that's all -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c9 --- Comment #9 from Episteme PROMENEUR <epistemepromeneur@free.fr> 2014-01-17 11:35:35 UTC --- in firefox options in "collected data" tab "crash report" is activated -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c10 --- Comment #10 from Episteme PROMENEUR <epistemepromeneur@free.fr> 2014-01-17 11:38:47 UTC ---
Please check in YaST->Software Repositories that both the debug and the debug-update repo are enabled, the KDE bug reporter does not do that for you. Then "Install debug symbols" should work.
Debug Update-Debug Update-Debug-non-oss are installed and activated -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c11 --- Comment #11 from Episteme PROMENEUR <epistemepromeneur@free.fr> 2014-01-17 11:42:57 UTC --- ok i guess where the pb is . this not firefox which crashes directly but an extension "kde wallett plugin" then for firefox this is not a firefox crash then it is very important that kde report generator works according to send the report to kde for the kwallet part and to mozilla for the firefox part and to the dev of the plugin -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=859161 https://bugzilla.novell.com/show_bug.cgi?id=859161#c12 --- Comment #12 from Wolfgang Bauer <wbauer@tmo.at> 2014-01-17 12:08:07 UTC --- AFAICS this is a binary plugin, so maybe it was compiled without debug information? Nothing the KDE crash reporter can do in that case. Btw, I don't even get the KDE bug reporter when I make Firefox crash. I only get the Mozilla crash reporter... I just tested with kwrite (made it crash by sending SIGILL with kill) and the KDE crash reporter successfully installed the debuginfo packages and generated a backtrace with full symbol information. (you may have to refresh your repos manually though) And yes, the debug information has been installed to /usr/lib/debug/. ;-) But the KDE bug reporter won't of course report anything to the Firefox or "KDE wallet plugin" developers anyway. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com