Thread: [aKregator-devel] Crash when switching viewing mode
Brought to you by:
lippel
From: Lars L. <lar...@gm...> - 2006-10-04 03:12:00
|
Hi! Immediately after startup I selected the combined view. I didn't select any feed or folder before doing so. This crashed the program. But what is worse, now it crashes immediately upon startup and without digging in the configuration and somehow changing the viewing mode setting I have no way to recover from this state. $ akregator -v Qt: 3.3.6 KDE: 3.5.4 Akregator: 1.2.4 $ Lars |
From: Frank O. <fra...@gm...> - 2006-10-04 07:37:22
|
Hi Lars, On Sunday 01 October 2006 16:46, Lars Lindner wrote: > Hi! > > Immediately after startup I selected the combined view. I didn't > select any feed or folder before doing so. This crashed the program. Do you use a fresh install or do you have old config files around? I can't reproduce it neither with my own configuration nor with a fresh KDE= =20 setup. There was a bug in switching to the combined view when having the unofficia= l=20 (and unfinished) tagging support enabled [1]. However, that one was fixed i= n=20 1.2.3. > But what is worse, now it crashes immediately upon startup and > without digging in the configuration and somehow changing the > viewing mode setting I have no way to recover from this state. Do you have a backtrace available? > $ akregator -v > Qt: 3.3.6 > KDE: 3.5.4 > Akregator: 1.2.4 =46rank [1] http://akregator.kde.org/blog/?p=3D24 |
From: Lars L. <lar...@gm...> - 2006-10-04 08:58:15
|
Am Mittwoch, den 04.10.2006, 09:43 +0200 schrieb Frank Osterfeld: > Hi Lars, > > On Sunday 01 October 2006 16:46, Lars Lindner wrote: > > Hi! > > > > Immediately after startup I selected the combined view. I didn't > > select any feed or folder before doing so. This crashed the program. > > Do you use a fresh install or do you have old config files around? > I can't reproduce it neither with my own configuration nor with a fresh KDE > setup. > There was a bug in switching to the combined view when having the unofficial > (and unfinished) tagging support enabled [1]. However, that one was fixed in > 1.2.3. I assume that there is some old config hanging around. I first tried it without changing anything and then removed ~/.kde/share/apps/akregator which didn't help. Are there other files that should be deleted? > > But what is worse, now it crashes immediately upon startup and > > without digging in the configuration and somehow changing the > > viewing mode setting I have no way to recover from this state. > > Do you have a backtrace available? Yes, but with incomplete debugging symbols: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1241794880 (LWP 16797)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0xb5c6c111 in Akregator::View::slotNodeSelected () from /usr/lib/kde3/libakregatorpart.so #6 0xb5c6c296 in Akregator::View::slotCombinedView () from /usr/lib/kde3/libakregatorpart.so #7 0xb5c70a1b in Akregator::View::View () from /usr/lib/kde3/libakregatorpart.so #8 0xb5c71212 in Akregator::Part::Part () from /usr/lib/kde3/libakregatorpart.so #9 0xb5c7f441 in KParts::GenericFactory<Akregator::Part>::createPartObject () from /usr/lib/kde3/libakregatorpart.so #10 0xb7fa4b3f in KParts::Factory::createPart () from /usr/lib/libkparts.so.2 #11 0xb7fa4ba1 in KParts::Factory::createObject () from /usr/lib/libkparts.so.2 #12 0xb7729c81 in KLibFactory::create () from /usr/lib/libkdecore.so.4 #13 0x080513da in ?? () #14 0x08107c18 in ?? () #15 0x080bd800 in ?? () #16 0x0805253d in _IO_stdin_used () #17 0x08052528 in _IO_stdin_used () #18 0xbffff0e0 in ?? () #19 0x080bd800 in ?? () #20 0x080525a6 in _IO_stdin_used () #21 0x00000000 in ?? () I checked with another local user account and had no problem. So I assume it is caused by something in my configuration. Lars |
From: Frank O. <fra...@gm...> - 2006-10-04 10:48:09
|
On Wednesday 04 October 2006 10:58, Lars Lindner wrote: > #5 0xb5c6c111 in Akregator::View::slotNodeSelected () > from /usr/lib/kde3/libakregatorpart.so > #6 0xb5c6c296 in Akregator::View::slotCombinedView () > from /usr/lib/kde3/libakregatorpart.so > #7 0xb5c70a1b in Akregator::View::View () > from /usr/lib/kde3/libakregatorpart.so Weird, I can't see how it could crash in there if normal view works. And th= e=20 only configuration option that should influence slotNodeSelected() is the=20 searchbar (Settings->show/hide quick filter). The only other dereferenced=20 pointers are from widgets (which should be all created properly) and the no= de=20 pointer passed around (which is the same for all view modes). > I checked with another local user account and had no problem. > So I assume it is caused by something in my configuration. Did you ever use akregator from SVN or edited configuration options manuall= y? =46rank |
From: Lars L. <lar...@gm...> - 2006-10-04 11:01:11
|
On 10/4/06, Frank Osterfeld <fra...@gm...> wrote: > On Wednesday 04 October 2006 10:58, Lars Lindner wrote: > > > #5 0xb5c6c111 in Akregator::View::slotNodeSelected () > > from /usr/lib/kde3/libakregatorpart.so > > #6 0xb5c6c296 in Akregator::View::slotCombinedView () > > from /usr/lib/kde3/libakregatorpart.so > > #7 0xb5c70a1b in Akregator::View::View () > > from /usr/lib/kde3/libakregatorpart.so > > Weird, I can't see how it could crash in there if normal view works. And the > only configuration option that should influence slotNodeSelected() is the > searchbar (Settings->show/hide quick filter). The only other dereferenced > pointers are from widgets (which should be all created properly) and the node > pointer passed around (which is the same for all view modes). > > > I checked with another local user account and had no problem. > > So I assume it is caused by something in my configuration. > > Did you ever use akregator from SVN or edited configuration options manually? No, I never did. I always used the Debian Unstable package and I never edited the configuration by hand. Lars |