Opened 11 years ago

Last modified 13 months ago

#38222 new defect

akregator crashing at start up

Reported by: tj.trevelyan@… Owned by: NicosPavlov
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: bjoern.ricks@…, mkae (Marko Käning), ShadSterling (Shad Sterling)
Port: kdepim4

Description

akregator fails to start on my system (10.7). See attached log.

There is also a dialog about not being able to load the 'metakit' plugin.

Attachments (1)

akregator.log (7.6 KB) - added by tj.trevelyan@… 11 years ago.
akregator: kdepim4 build and gdb bt

Download all attachments as: .zip

Change History (7)

Changed 11 years ago by tj.trevelyan@…

Attachment: akregator.log added

akregator: kdepim4 build and gdb bt

comment:1 Changed 11 years ago by jmroot (Joshua Root)

Cc: bjoern.ricks@… added
Keywords: akregator removed
Owner: changed from macports-tickets@… to sharky@…

Please remember to Cc the maintainers.

comment:2 Changed 11 years ago by tj.trevelyan@…

Further info that seems relevant to this bug:

I deleted akregator's config files:

$ rm -rf ./Library/Preferences/KDE/share/apps/akregator ./Library/Preferences/KDE/share/config/akregatorrc

and then it worked once again.

However I then went into preferences and made my customisations to its settings. This led to it crashing once again.

After some trail and error, I found the setting that is causing it to crash:

Preferences -> Browser -> Tabs -> 'Show close button on each tab'

After turning this on, akregator starts to crash, and then fails to start altogether.

I don't know, but suspect that other settings also cause it to be unstable.

-Thorben

(When I reported this bug I was running OS X Lion 10.7, but now I'm on Mountain Lion 10.8.)

comment:3 Changed 11 years ago by sharky@…

Owner: changed from sharky@… to nicos@…

comment:4 Changed 11 years ago by NicosPavlov

I can indeed reproduce the bug with version 4.11.1, which is the present one in Macports.

However, it seems more to be bug to report upstream (https://bugs.kde.org), as it consists in a bad access error, which is not likely to be due to the Macports install by itself.

comment:5 Changed 10 years ago by mkae (Marko Käning)

Cc: mk@… added

Cc Me!

comment:6 Changed 13 months ago by ShadSterling (Shad Sterling)

Cc: ShadSterling added
Note: See TracTickets for help on using tickets.