[KDE4] hardy, nspluginviewer crashed

Bug #201656 reported by Alexander Rødseth
4
Affects Status Importance Assigned to Milestone
kdebase-kde4 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

nspluginviewer crashed when I was about to watch "Look around you: maths" at youtube.com

Backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5bc9720 (LWP 7103)]
[New Thread 0xb122eb90 (LWP 7945)]
[New Thread 0xb07a5b90 (LWP 7944)]
[New Thread 0xb1eb3b90 (LWP 7940)]
[New Thread 0xb27c1b90 (LWP 7939)]
[KCrash handler]
#6 0xb3eb1a80 in ?? () from /usr/lib/firefox/plugins/libflashplayer.so
#7 0xb28f1770 in ?? ()
#8 0x081c9118 in ?? ()
#9 0xb28f1770 in ?? ()
#10 0xb44f5e20 in ?? () from /usr/lib/firefox/plugins/libflashplayer.so
#11 0xb2879000 in ?? ()
#12 0x00000000 in ?? ()
#0 0xb7ef9410 in __kernel_vsyscall ()

I'm using "konqueror-kde4" 4:4.0.2-0ubuntu1

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We need a bit more info, but thanks for the report all the same.
Is this error reproducible? Will going to this certain video crash Konqueror every time?
If so, what steps could someone take to reproduce it? (A quick search shows tons of different "Look around you: maths" videos on YouTube)

Changed in kdebase-kde4:
status: New → Incomplete
Revision history for this message
Alexander Rødseth (alexanro) wrote :

I don't think it was specific for that video in particular, but I'll try to use Konqueror some more and see if it happens again.
In general, many crashes I've experienced with KDE4 and Konqueror is really hard to reproduce since they happen so randomly.
I know the saying "if you can't reproduce it, it didn't happen", but when I have a backtrace to show for I still report the bugs. Should I only report reproducible bugs?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Somebody might find the backtrace useful, if nothing else. If you have a backtrace it is probably ok to report semi-random bugs.

Changed in kdebase-kde4:
status: Incomplete → New
Revision history for this message
Harald Sitter (apachelogger) wrote :

Yeah, generally it is better to report any bug than to leave stuff unnoticed.

However this backtrace is useless, maybe you can get a better one when installing kdebase-kde4-dbg before the next crash :)

I am marking the bug as incomplete, in case the crash re-appears within the next 2 months.

Changed in kdebase-kde4:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Alexander Rødseth (alexanro) wrote :

Harald, as is becoming a trend now, you are wrong in your assumptions. kdebase-kde4-dbg was installed not long after this bug was reported, which is some time ago now.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Yes, I probably should stop triaging bugs, I am wrong all the time anyway.

https://wiki.ubuntu.com/Backtrace

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase-kde4:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.