Ubuntu
update-notifier-kde package

update-notifier-kde crashes on logout

Bug #351224 reported by Marco Di Fresco on 2009-03-29

This bug report is a duplicate of: Bug #349419: jockey-kde crashed with SIGSEGV in QWidget::metric() on kubuntu 9.04 startup. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	update-notifier-kde (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

Every time I log off from KDE I get a window that reports that update-notifier-kde has crashed.

I have Kubuntu 8.10 64 bits. KDE 4.2 upgraded as for http://www.kubuntu.org/news/kde-4.2.

I have attached the error log.

Let me know if you need more info.

Revision history for this message

Marco Di Fresco (marco-di-fresco) wrote on 2009-03-29:

update-notifier-kde.kcrash Edit (1.9 KiB, text/plain)

Jonathan Thomas (echidnaman) on 2009-03-30

affects:

ubuntu → update-notifier-kde (Ubuntu)

Revision history for this message

Marco Di Fresco (marco-di-fresco) wrote on 2009-04-11:

No one is experiencing this problem too?

Revision history for this message

Marco Di Fresco (marco-di-fresco) wrote on 2009-04-24:

After a re-install from scratch, the problem did NOT present itself.

Probably the error was due to some corrupted configuration file or something alike.

Changed in update-notifier-kde (Ubuntu):
status:	New → Incomplete

Revision history for this message

Marco Di Fresco (marco-di-fresco) wrote on 2009-04-24:

I want share some changes about this problem.

Last Sunday my hard drive died so, after getting a new one, I had to re-install everything from scratch (Kubuntu 8.10 & KDE 4.22). This time the problem is not showing up.

I do not know if, by chance, the software has been fixed during my downtime (making me downloading the new version when I had to reinstall KDE 4.22), but unless so I assume that the problem must have been due to some corrupted configuration file rather than the update-notifier-kde code itself. Since the old HD is dead, I cannot investigate if it was indeed a corrupted configuration file and eventually which one.

I am not yet familiar with all the Launchpad standard: is it correct if I mark this bug as "Incomplete" (since it should be still something to check and fix, but there is not enough info to triangulate the source of the problem)?