Re: abrt issue
On Wednesday 09 December 2009 14:23:47 Neal Becker wrote: > Jiri Moskovcak wrote: > > On 12/09/2009 02:05 PM, Neal Becker wrote: > >> Jiri Moskovcak wrote: > >>> On 12/09/2009 01:47 PM, Neal Becker wrote: > I just got a crash in kde plasma. Traceback is not useful, because of > missing debug pacakges. > > I'm told I can reload after 'installing the needed packages', but > there is no clue what packages are needed. > > A bit of a mystery. It seems sometimes abrt will go ahead and > download needed debuginfo packages, but other times (like today), it > doesn't, and doesn't offer any clue what packages are missing. > >>> > >>> Weird, ABRT should tell you the exact package you should install > >>> debuginfo for. I just tried that and abrt says this: > >>> > >>> Reporting disabled because the backtrace is unusable. > >>> Please try to install debuginfo manually by using command: > >>> *debuginfo-install python* > >>> the use the Refresh button to regenerate the backtrace. > >>> > >>> Jirka > >> > >> Yes, I've gotten messages like this sometimes, and that's what I was > >> looking > >> for. But not today. > >> > >> Maybe related? > >> Dec 9 07:50:11 localhost abrtd: New crash, saving > >> Dec 9 07:50:11 localhost abrtd: Activation of plugin 'RunApp' was not > >> successful: Plugin 'RunApp' is not registered > > > > This shouldn't be related, but I'm wondering where did you get the line > > "reload after 'installing the needed packages'" it doesn't come from > > ABRT. > > This is not an exact quote, but it's what I got from abrt when I clicked on > 'next'. You probably mean Dr. Konqui and not Abrt ;-) KDE is still using Dr. Konqui! There's some sort of debuginfo packages auto downloading but we're considering Abrt usage in Fedora KDE too as it better integrates to Fedora. The plan is even for native KDE/Qt Abrt GUI! Ping Abrt people - do you need a help? What's the status? Jaroslav > I don't know what debuginfo package is needed. rpm -qa '*plasma*' doesn't > give a good answer. Why isn't abrt telling me? > -- Jaroslav Řezník Associate Software Engineer - Base Operating Systems Brno Office: +420 532 294 275 Mobile: +420 731 455 332 Red Hat, Inc. http://cz.redhat.com/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
Neal Becker wrote: > I don't know what debuginfo package is needed. rpm -qa '*plasma*' doesn't > give a good answer. Probably kdebase-workspace (and its dependencies, like kdelibs, but debuginfo-install takes care of that automatically). Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
On Wednesday 09 December 2009 12:47:44 Neal Becker wrote: > I just got a crash in kde plasma. Traceback is not useful, because of > missing debug pacakges. Downgrading hal and hal-libs fixes the crash. I noticed the other thread where this bug is reported. I was seeing both https://bugzilla.redhat.com/show_bug.cgi?id=545639 https://bugzilla.redhat.com/show_bug.cgi?id=545258 You need to downgrade hal-libs as well or else yum will pick hal-libs.i686 and that will require to install glibc.i686 and friends. -- José Abílio -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
On 12/09/2009 02:23 PM, Neal Becker wrote: Jiri Moskovcak wrote: On 12/09/2009 02:05 PM, Neal Becker wrote: Jiri Moskovcak wrote: On 12/09/2009 01:47 PM, Neal Becker wrote: I just got a crash in kde plasma. Traceback is not useful, because of missing debug pacakges. I'm told I can reload after 'installing the needed packages', but there is no clue what packages are needed. A bit of a mystery. It seems sometimes abrt will go ahead and download needed debuginfo packages, but other times (like today), it doesn't, and doesn't offer any clue what packages are missing. Weird, ABRT should tell you the exact package you should install debuginfo for. I just tried that and abrt says this: Reporting disabled because the backtrace is unusable. Please try to install debuginfo manually by using command: *debuginfo-install python* the use the Refresh button to regenerate the backtrace. Jirka Yes, I've gotten messages like this sometimes, and that's what I was looking for. But not today. Maybe related? Dec 9 07:50:11 localhost abrtd: New crash, saving Dec 9 07:50:11 localhost abrtd: Activation of plugin 'RunApp' was not successful: Plugin 'RunApp' is not registered This shouldn't be related, but I'm wondering where did you get the line "reload after 'installing the needed packages'" it doesn't come from ABRT. This is not an exact quote, but it's what I got from abrt when I clicked on 'next'. I don't know what debuginfo package is needed. rpm -qa '*plasma*' doesn't give a good answer. Why isn't abrt telling me? It definitely is telling you. You can see it either in main window in column "Package" or in the report window if you scrolldown the backtrace you'll see row "package" J. <>-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
Jiri Moskovcak wrote: > On 12/09/2009 02:05 PM, Neal Becker wrote: >> Jiri Moskovcak wrote: >> >>> On 12/09/2009 01:47 PM, Neal Becker wrote: I just got a crash in kde plasma. Traceback is not useful, because of missing debug pacakges. I'm told I can reload after 'installing the needed packages', but there is no clue what packages are needed. A bit of a mystery. It seems sometimes abrt will go ahead and download needed debuginfo packages, but other times (like today), it doesn't, and doesn't offer any clue what packages are missing. >>> >>> Weird, ABRT should tell you the exact package you should install >>> debuginfo for. I just tried that and abrt says this: >>> >>> Reporting disabled because the backtrace is unusable. >>> Please try to install debuginfo manually by using command: >>> *debuginfo-install python* >>> the use the Refresh button to regenerate the backtrace. >>> >>> Jirka >> >> Yes, I've gotten messages like this sometimes, and that's what I was >> looking >> for. But not today. >> >> Maybe related? >> Dec 9 07:50:11 localhost abrtd: New crash, saving >> Dec 9 07:50:11 localhost abrtd: Activation of plugin 'RunApp' was not >> successful: Plugin 'RunApp' is not registered >> > > This shouldn't be related, but I'm wondering where did you get the line > "reload after 'installing the needed packages'" it doesn't come from > ABRT. This is not an exact quote, but it's what I got from abrt when I clicked on 'next'. I don't know what debuginfo package is needed. rpm -qa '*plasma*' doesn't give a good answer. Why isn't abrt telling me? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
$ yum update abrt --enablerepo=updatetesting and try the updated version which should fix some problems with debuginfo installing. It should be: yum update abrt --enablerepo=updates-testing, but it seems it didn't hit the repository yet even thou I got the email. J. <>-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
On 12/09/2009 02:05 PM, Neal Becker wrote: Jiri Moskovcak wrote: On 12/09/2009 01:47 PM, Neal Becker wrote: I just got a crash in kde plasma. Traceback is not useful, because of missing debug pacakges. I'm told I can reload after 'installing the needed packages', but there is no clue what packages are needed. A bit of a mystery. It seems sometimes abrt will go ahead and download needed debuginfo packages, but other times (like today), it doesn't, and doesn't offer any clue what packages are missing. Weird, ABRT should tell you the exact package you should install debuginfo for. I just tried that and abrt says this: Reporting disabled because the backtrace is unusable. Please try to install debuginfo manually by using command: *debuginfo-install python* the use the Refresh button to regenerate the backtrace. Jirka Yes, I've gotten messages like this sometimes, and that's what I was looking for. But not today. Maybe related? Dec 9 07:50:11 localhost abrtd: New crash, saving Dec 9 07:50:11 localhost abrtd: Activation of plugin 'RunApp' was not successful: Plugin 'RunApp' is not registered This shouldn't be related, but I'm wondering where did you get the line "reload after 'installing the needed packages'" it doesn't come from ABRT. If ABRT thinks the BT is ok it won't give you any advice, but if the developer wants you to install additional debuginfo packages, then the formula is quite simple if the refresh button fails then: $ debuginfo-install and it should handle the rest. or you can try: $ yum update abrt --enablerepo=testing and try the updated version which should fix some problems with debuginfo installing. Jirka <>-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
Jiri Moskovcak wrote: > On 12/09/2009 01:47 PM, Neal Becker wrote: >> I just got a crash in kde plasma. Traceback is not useful, because of >> missing debug pacakges. >> >> I'm told I can reload after 'installing the needed packages', but >> there is no clue what packages are needed. >> >> A bit of a mystery. It seems sometimes abrt will go ahead and download >> needed debuginfo packages, but other times (like today), it doesn't, and >> doesn't offer any clue what packages are missing. > > Weird, ABRT should tell you the exact package you should install > debuginfo for. I just tried that and abrt says this: > > Reporting disabled because the backtrace is unusable. > Please try to install debuginfo manually by using command: > *debuginfo-install python* > the use the Refresh button to regenerate the backtrace. > > Jirka Yes, I've gotten messages like this sometimes, and that's what I was looking for. But not today. Maybe related? Dec 9 07:50:11 localhost abrtd: New crash, saving Dec 9 07:50:11 localhost abrtd: Activation of plugin 'RunApp' was not successful: Plugin 'RunApp' is not registered -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
On Wed, 09 Dec 2009 07:47:44 -0500, Neal wrote: > I just got a crash in kde plasma. Traceback is not useful, because of > missing debug pacakges. Seems to happen more frequently recently. The latest backtraces I've seen in bugzilla all were missing dozens of debuginfo packages. > I'm told I can reload after 'installing the needed packages', but > there is no clue what packages are needed. ABRT once told me to use debuginfo-install, but it doesn't [or can't] get that hint right if an app uses plugins/modules from separate packages. > A bit of a mystery. It seems sometimes abrt will go ahead and download > needed debuginfo packages, but other times (like today), it doesn't, and > doesn't offer any clue what packages are missing. > > Either way, still not very user friendly. It would be an improvement if it worked. With dozens of missing debuginfo packages and missing "steps on how to reproduce a problem" the filed tickets are close to useless. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt issue
On 12/09/2009 01:47 PM, Neal Becker wrote: I just got a crash in kde plasma. Traceback is not useful, because of missing debug pacakges. I'm told I can reload after 'installing the needed packages', but there is no clue what packages are needed. A bit of a mystery. It seems sometimes abrt will go ahead and download needed debuginfo packages, but other times (like today), it doesn't, and doesn't offer any clue what packages are missing. Weird, ABRT should tell you the exact package you should install debuginfo for. I just tried that and abrt says this: Reporting disabled because the backtrace is unusable. Please try to install debuginfo manually by using command: *debuginfo-install python* the use the Refresh button to regenerate the backtrace. Jirka <>-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
