7216 – kfilebox - after I install and synchronize, the kfilebox closes, and displays error message

Bug 7216 - kfilebox - after I install and synchronize, the kfilebox closes, and displays error message

Summary: kfilebox - after I install and synchronize, the kfilebox closes, and displays...

Status:	RESOLVED OLD

Alias:	None

Product:	Mageia
Classification:	Unclassified
Component:	RPM Packages (show other bugs)
Version:	2
Hardware:	i586 Linux

Priority:	Normal Severity: normal
Target Milestone:	---
Assignee:	Sander Lepik
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-08-27 00:28 CEST by macxi
Modified:	2013-11-23 16:14 CET (History)
CC List:	0 users

See Also:
Source RPM:	kfilebox-0.4.7-3.mga2.i586.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description macxi 2012-08-27 00:28:33 CEST

Description of problem:

After installed and synchronized, the KFILEBOX closes, and displays error message, and after the Mageia 2 boot, a window appears: "Kfilebox - The KDE crash handler"

This software is functioning without error in Mageia 1, but is closing in Mageia 2.

Even with mistakes, if I click again on the icon in the "Application Launcher Menu", the kfilebox works properly synchronizing all packages.

The problem is the "error message" that appears after the Mageia 2 start, and "warnings" error that appears when I choose to stop or quit Kfilebox.

Version-Release number of selected component (if applicable):
kfilebox-0.4.7-3.mga2.i586.rpm - KDE front end for Dropbox

How reproducible:
After the Mageia 2 start and when I choose to stop or quit Kfilebox.


Steps to Reproduce:
1. Install package kfilebox-0.4.7-3.mga2.i586.rpm
2. Click in icone Kfilebox to install
3. After install, a window appears: "Kfilebox - The KDE crash handler"
4. After the Mageia 2 start and
5. when I choose to stop or quit Kfilebox.

Note: I installed the following packages: 

- kfilebox-0.4.7-3.mga2.i586
- kfilebox-debug-0.4.7-3.mga2.i586

- gdb-7.3.50.20110722-4.mga2.i586
- gdb-debug-7.3.50.20110722-4.mga2.i586

- akonadi-debug-1.7.2-1.mga2.i586
- kdeadmin4-debug-4.8.2-2.mga2.i586
- kdebase4-runtime-debug-4.8.2-3.mga2.i586
- kdebase4-workspace-debug-4.8.2-5.mga2.i586
- kdelibs4-debug-4.8.2-3.mga2.i586
- kdenetwork4-debug-4.8.2-2.mga2.i586
- kdepim4-debug-4.8.2-3.mga2.i586


I sent an email to the developer of Kfilebox: kfilebox@gmail.com, with the text below:


***********
Subject: Automatic crash report generated by DrKonqi for kfilebox.
********************************

Application: kfilebox (0.4.7)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.2
Operating System: Linux 3.3.8-desktop586-2.mga2 i686
Distribution: "Mageia 2"

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The kfilebox closed soon after installation

-- Backtrace:
Application: kfilebox (kfilebox), signal: Segmentation fault
Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Current thread is 1 (Thread 0xb54026e0 (LWP 3106))]

Thread 5 (Thread 0xb3a9eb70 (LWP 3108)):
#0  0xb5b647d7 in pthread_mutex_lock () from /lib/i686/libpthread.so.0
#1  0xb5f9bb54 in pthread_mutex_lock () from /lib/i686/libc.so.6
#2  0xb5a11200 in g_mutex_lock () from /lib/libglib-2.0.so.0
#3  0xb59d1f6a in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb62e7e87 in 
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#5  0xb62b3d2d in 
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#6  0xb62b3fc9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#7  0xb619d70c in QThread::exec() () from /usr/lib/libQtCore.so.4
#8  0xb619d7fb in QThread::run() () from /usr/lib/libQtCore.so.4
#9  0xb61a0bf0 in ?? () from /usr/lib/libQtCore.so.4
#10 0xb5b62a37 in start_thread () from /lib/i686/libpthread.so.0
#11 0xb5f8d98e in clone () from /lib/i686/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 4 (Thread 0xb30ffb70 (LWP 3109)):
#0  0xb5b65594 in __pthread_mutex_unlock_usercnt () from 
/lib/i686/libpthread.so.0
#1  0xb5f9bb94 in pthread_mutex_unlock () from /lib/i686/libc.so.6
#2  0xb5a11240 in g_mutex_unlock () from /lib/libglib-2.0.so.0
#3  0xb59d1e1b in ?? () from /lib/libglib-2.0.so.0
#4  0xb59d1f81 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb62e7e87 in 
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#6  0xb62b3d2d in 
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#7  0xb62b3fc9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#8  0xb619d70c in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xb619d7fb in QThread::run() () from /usr/lib/libQtCore.so.4
#10 0xb61a0bf0 in ?? () from /usr/lib/libQtCore.so.4
#11 0xb5b62a37 in start_thread () from /lib/i686/libpthread.so.0
#12 0xb5f8d98e in clone () from /lib/i686/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 3 (Thread 0xb1cffb70 (LWP 3113)):
#0  0xb5a10f00 in ?? () from /lib/libglib-2.0.so.0
#1  0xb5a111f8 in g_mutex_lock () from /lib/libglib-2.0.so.0
#2  0xb59d193e in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#3  0xb59d1ea5 in ?? () from /lib/libglib-2.0.so.0
#4  0xb59d1f81 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb62e7e87 in 
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#6  0xb62b3d2d in 
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#7  0xb62b3fc9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#8  0xb619d70c in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xb619d7fb in QThread::run() () from /usr/lib/libQtCore.so.4
#10 0xb61a0bf0 in ?? () from /usr/lib/libQtCore.so.4
#11 0xb5b62a37 in start_thread () from /lib/i686/libpthread.so.0
#12 0xb5f8d98e in clone () from /lib/i686/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xb14feb70 (LWP 3116)):
#0  0xb55ccb40 in clock_gettime () from /lib/i686/librt.so.1
#1  0xb61ff5b5 in ?? () from /usr/lib/libQtCore.so.4
#2  0xb62e87c6 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb62e83b6 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb59d182b in g_main_context_check () from /lib/libglib-2.0.so.0
#5  0xb59d1dc2 in ?? () from /lib/libglib-2.0.so.0
#6  0xb59d1f81 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#7  0xb62e7e87 in 
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#8  0xb62b3d2d in 
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#9  0xb62b3fc9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#10 0xb619d70c in QThread::exec() () from /usr/lib/libQtCore.so.4
#11 0xb619d7fb in QThread::run() () from /usr/lib/libQtCore.so.4
#12 0xb61a0bf0 in ?? () from /usr/lib/libQtCore.so.4
#13 0xb5b62a37 in start_thread () from /lib/i686/libpthread.so.0
#14 0xb5f8d98e in clone () from /lib/i686/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb54026e0 (LWP 3106)):
[KCrash Handler]
#7  0xb628cc67 in ?? () from /usr/lib/libQtCore.so.4
#8  0xb62419c4 in QProcess::waitForStarted(int) () from 
/usr/lib/libQtCore.so.4
#9  0x08055ead in SystemCall::executeDetached (this=0x90b29f0, command=) at 
util/SystemCall.cpp:67
#10 0x080591a4 in installer::Daemoninstaller::executeWizzard (this=0x0) at 
installer/Daemoninstaller.cpp:63
#11 0x080592d2 in installer::Daemoninstaller::extract (this=0x8e482e8) at 
installer/Daemoninstaller.cpp:52
#12 0x0805930f in installer::Daemoninstaller::onFileDownloaded 
(this=0x8e482e8) at installer/Daemoninstaller.cpp:90
#13 0xb62cbb6f in QMetaObject::activate(QObject*, QMetaObject const*, int, 
void**) () from /usr/lib/libQtCore.so.4
#14 0x0805f4b7 in util::Downloader::fileDownloaded (this=0x8e5ad58) at 
moc_Downloader.cpp:113
#15 0x0805886a in util::Downloader::downloadFinished (this=0x8e5ad58) at 
util/Downloader.cpp:66
#16 0xb62cbb6f in QMetaObject::activate(QObject*, QMetaObject const*, int, 
void**) () from /usr/lib/libQtCore.so.4
#17 0xb650d715 in QNetworkReply::finished() () from /usr/lib/libQtNetwork.so.4
#18 0xb6491087 in ?? () from /usr/lib/libQtNetwork.so.4
#19 0xb647029e in ?? () from /usr/lib/libQtNetwork.so.4
#20 0xb6476f91 in ?? () from /usr/lib/libQtNetwork.so.4
#21 0xb650ce90 in ?? () from /usr/lib/libQtNetwork.so.4
#22 0xb62c70a1 in QMetaCallEvent::placeMetaCall(QObject*) () from 
/usr/lib/libQtCore.so.4
#23 0xb62d01fb in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#24 0xb6693c14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () 
from /usr/lib/libQtGui.so.4
#25 0xb6698f53 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libQtGui.so.4
#26 0xb74c8741 in KApplication::notify (this=0xbfb0e6b4, receiver=0x90b0a18, 
event=0xb1d0d2c0) at 
/usr/src/debug/kdelibs-4.8.2/kdeui/kernel/kapplication.cpp:311
#27 0xb62b54ae in QCoreApplication::notifyInternal(QObject*, QEvent*) () from 
/usr/lib/libQtCore.so.4
#28 0xb62b90d8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, 
QThreadData*) () from /usr/lib/libQtCore.so.4
#29 0xb62b940c in QCoreApplication::sendPostedEvents(QObject*, int) () from 
/usr/lib/libQtCore.so.4
#30 0xb62e7a34 in ?? () from /usr/lib/libQtCore.so.4
#31 0xb59d1a9a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0xb59d1ea5 in ?? () from /lib/libglib-2.0.so.0
#33 0xb59d1f81 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0xb62e7e27 in 
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#35 0xb674754a in ?? () from /usr/lib/libQtGui.so.4
#36 0xb62b3d2d in 
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
/usr/lib/libQtCore.so.4
#37 0xb62b3fc9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () 
from /usr/lib/libQtCore.so.4
#38 0xb62b94ba in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#39 0xb6691ab4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#40 0x0804fb72 in main (argc=) at main.cpp:36

___________________

I sent an email to the developer of Kfilebox: kfilebox@gmail.com, with the text below:


***********
Subject: Automatic crash report generated by DrKonqi for kfilebox.
********************************

Application: kfilebox (0.4.7)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.2
Operating System: Linux 3.3.8-desktop586-2.mga2 i686
Distribution: "Mageia 2"

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

After the Mageia 2 boot, a window appears: "Kfilebox - The KDE crash 
handler"


-- Backtrace:
Application: kfilebox (kfilebox), signal: Segmentation fault
Using host libthread_db library "/lib/i686/libthread_db.so.1".
[KCrash Handler]
#7  0xb61ddc67 in ?? () from /usr/lib/libQtCore.so.4
#8  0xb61929c4 in QProcess::waitForStarted(int) () from 
/usr/lib/libQtCore.so.4
#9  0x08055ead in SystemCall::executeDetached (this=0x8c63fc8, command=) at 
util/SystemCall.cpp:67
#10 0x08056e3c in core::DropboxClient::start (this=0x8beaa78) at 
core/DropboxClient.cpp:22
#11 0x0805133d in MainWindow::MainWindow (this=0xbfdb4940, parent=0x0) at 
mainwindow.cpp:46
#12 0x0804fb6d in main (argc=) at main.cpp:34

Comment 1 macxi 2012-08-27 00:30:45 CEST

This error occurs in Mageia 2, KDE 4.8.2

Comment 2 macxi 2012-09-30 16:18:01 CEST

I ask if this package kfilebox-0.4.7-3, in Mageia 2, can be upgraded?

kfilebox-0.4.7-2 in Mageia 1 - KDE 4.6.5 works well. 
kfilebox-0.4.7-3 in Mageia 2 - KDE-4.8.2 works well - but always gives error message
I'm still testing  kfilebox-0.4.9-1 in Mageia 3 - KDE 4.9.1

Mageia Forum: https://forums.mageia.org/en/viewtopic.php?f=7&t=3594

Manuel Hiebel 2012-10-01 11:38:39 CEST

Assignee: bugsquad => sander.lepik
Source RPM: kfilebox-0.4.7-3.mga2.i586.rpm - KDE front end for Dropbox => kfilebox-0.4.7-3.mga2.i586.rpm

macxi 2012-12-18 13:55:33 CET

Summary: After I install and synchronize, the KFILEBOX closes, and displays error message => kfilebox - after I install and synchronize, the kfilebox closes, and displays error message

Comment 3 Manuel Hiebel 2013-10-22 12:11:03 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 4 Manuel Hiebel 2013-11-23 16:14:25 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Note You need to log in before you can comment on or make changes to this bug.