| Summary: | Amarok crash on launch from kicker favorites menu [mem2chunk_check, free_check, ~QImageData] | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Shaun Hunter <shaunehunter> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | thomas.luebking |
| Priority: | NOR | ||
| Version: | 2.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Shaun Hunter
2009-12-19 20:49:30 UTC
are you using bespin style? does it work with oxygen? I am using bespin. I haven't had a duplicate crash. On Sun, Dec 20, 2009 at 3:20 AM, Mikko C. <mikko.cal@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=219346 > > > Mikko C. <mikko.cal@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution| |WAITINGFORINFO > > > > > --- Comment #1 from Mikko C. <mikko cal gmail com> 2009-12-20 10:20:26 --- > are you using bespin style? does it work with oxygen? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > this happened on the raster engine and in combination with pseudo widgets (as used by the systray) but should meanwhile be catched (though i'd need the relevant part of the backtrace to really tell) - which bespin version do you use? - do you use the raster engine (by default or "-graphicssystem raster" flag) on amarok or (aparently involved) kwallet? Shaun, Thomas: is this still valid? I haven't had it happen since the update after I last ripped some CD's. I'll rip a few to test it and report what I find. On Sun, Jan 24, 2010 at 5:38 PM, Myriam Schweingruber <myriam@kde.org>wrote: > https://bugs.kde.org/show_bug.cgi?id=219346 > > > > > > --- Comment #4 from Myriam Schweingruber <myriam kde org> 2010-01-25 > 00:38:26 --- > Shaun, Thomas: is this still valid? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Any news on this? i think you can mark this as closed or outdated or whatever. since about rev. 600 (mid september 2009) bespin is _really_ picky before calling the winId() function (first checks whether the native widget is really created and has a present winId) so the code path in the backtrace: #11 0x00007f873e795fcf in QWidget::winId (this=0x1a4f730) at #10 0x00007f873e795858 in QWidget::create (this=0x1a4f730, window=0, initializeWindow=<value optimized out>, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1350 should never occur anymore at all. I know there was a bug on this (but only reported on the raster graphicssystem) related to a dummywidget used by KSystrayIcon (that classname may be not exact). The constructor is overridden, doesn't really construct a widget, thus segfaults on ::create() native widget attempts. Thank you for the feedback. |