Bug 380705 - NEEDINFO: Rkward crashes under Ubuntu 8.04
Summary: NEEDINFO: Rkward crashes under Ubuntu 8.04
Status: RESOLVED WORKSFORME
Alias: None
Product: rkward
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: RKWard Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-09 10:23 UTC by RKWard Team
Modified: 2009-04-21 01:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RKWard Team 2008-10-09 10:23:37 UTC
-- Originally posted by (AT sourceforge.net): wiedy --

-- This ticket was imported from http://sourceforge.net/p/rkward/bugs/33 on 2017-05-30 15:26:40 +0100 --
Rkward crashes frequently for no apparent reason. Backtracking:

\(no debugging symbols found\)
\[Thread debugging using libthread\_db enabled\]
\[New Thread 0xb58876c0 \(LWP 26714\)\]
\[KCrash handler\]
\#19 0x08131f46 in ?? \(\)
\#20 0x08132d67 in ?? \(\)
\#21 0x080a7b91 in ?? \(\)
\#22 0x0807245c in ?? \(\)
\#23 0xb6540f2f in QWidget::close \(this=0x81d5bf8, alsoDelete=true\)
at kernel/qwidget.cpp:4324
\#24 0x080b38d0 in ?? \(\)
\#25 0x080b39f3 in ?? \(\)
\#26 0xb6507704 in QObject::activate\_signal \(this=0x8242790, clist=0xa9051e80, 
o=0xbfd7b428\) at kernel/qobject.cpp:2359
\#27 0xb6896aba in QSignal::signal \(this=0x8242790, t0=@0x82427b8\)
at .moc/debug-shared-mt/moc\_qsignal.cpp:100
\#28 0xb65267b2 in QSignal::activate \(this=0x8242790\) at kernel/qsignal.cpp:215
\#29 0xb652e936 in QSingleShotTimer::event \(this=0x8242768\)
at kernel/qtimer.cpp:289
\#30 0xb649bc36 in QApplication::internalNotify \(this=0xbfd7ba2c, 
receiver=0x8242768, e=0xbfd7b738\) at kernel/qapplication.cpp:2638
\#31 0xb649da5f in QApplication::notify \(this=0xbfd7ba2c, receiver=0x8242768, 
e=0xbfd7b738\) at kernel/qapplication.cpp:2361
\#32 0xb6c5c672 in KApplication::notify \(this=0xbfd7ba2c, receiver=0x8242768, 
event=0xbfd7b738\)
at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550
\#33 0xb642c28d in QApplication::sendEvent \(receiver=0x8242768, 
event=0xbfd7b738\) at ../include/qapplication.h:523
\#34 0xb648eb19 in QEventLoop::activateTimers \(this=0x81b9b80\)
at kernel/qeventloop\_unix.cpp:559
\#35 0xb644164b in QEventLoop::processEvents \(this=0x81b9b80, flags=4\)
at kernel/qeventloop\_x11.cpp:392
\#36 0xb64b6f90 in QEventLoop::enterLoop \(this=0x81b9b80\)
at kernel/qeventloop.cpp:201
\#37 0xb64b6c8e in QEventLoop::exec \(this=0x81b9b80\)
at kernel/qeventloop.cpp:148
\#38 0xb649d7df in QApplication::exec \(this=0xbfd7ba2c\)
at kernel/qapplication.cpp:2761
\#39 0x0807821e in ?? \(\)
\#40 0xb5ca7450 in \_\_libc\_start\_main \(\) from /lib/tls/i686/cmov/libc.so.6
\#41 0x080717b1 in ?? \(\)
Comment 1 Thomas Friedrichsmeier 2009-04-02 19:59:32 UTC
Sorry for not getting back on you any sooner.

Which exact version of RKWard was this?

Do you still see this issue with RKWard 0.5.0c?

Did you figure out a pattern, when these crashes occur?
Comment 2 Thomas Friedrichsmeier 2009-04-02 19:59:32 UTC
- **summary**: Rkward crashes under Ubuntu 8.04 --> NEEDINFO: Rkward crashes under Ubuntu 8.04
Comment 3 RKWard Team 2009-04-02 20:39:07 UTC
-- Originally posted by (AT sourceforge.net): nobody --
I couldn't tell you. Meanwhile I've upgraded to Kubuntu 8.10, and haven't used Rkwardd much since then. I'll let you know if the problem persists.
Comment 4 Thomas Friedrichsmeier 2009-04-06 20:17:39 UTC
Thanks for your reply.  I'll set this bug to "Pending" status, which means it will close automatically, if you don't add any further message \(IIRC the period is two weeks\). Should you see similar problems after that, feel free to open a new report. If I don't hear back from you, I'll assume the problem has gone away with new versions of RKWard or other packages.

Again, sorry for taking so long to writing an answer to your report.
Comment 5 Thomas Friedrichsmeier 2009-04-06 20:17:39 UTC
- **status**: open --> pending-works-for-me
Comment 6 RKWard Team 2009-04-21 01:22:47 UTC
-- Originally posted by (AT sourceforge.net): sf-robot --
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days \(the time period specified by
the administrator of this Tracker\).
Comment 7 RKWard Team 2009-04-21 01:22:47 UTC
-- Originally posted by (AT sourceforge.net): sf-robot --
- **status**: pending-works-for-me --> closed-works-for-me