Bug 327141 - sending a file using bluetooth from tray icon results in crash
Summary: sending a file using bluetooth from tray icon results in crash
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: solid
Classification: Unmaintained
Component: bluetooth (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-04 19:29 UTC by Christoph Thielecke
Modified: 2014-01-19 23:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Thielecke 2013-11-04 19:29:12 UTC
crash on sending a file using right click on tray icon -> send file -> select device -> select file send

Reproducible: Always

Steps to Reproduce:
1. right click on bluetooth icon, select 'send file'
2. select decie and file on dialog
3. press send
Actual Results:  
crash

Expected Results:  
send file

maybe the reason was that the device was not paired. after pairing it  works


backtrace:
------
Application: Hilfsprogramm für Bluetooth-Dateiversand (bluedevil-sendfile), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4e65980 (LWP 17156))]

Thread 3 (Thread 0xb24deb40 (LWP 17157)):
#0  0xb77a5424 in __kernel_vsyscall ()
#1  0xb5d0b9db in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb53dc2db in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb53cd6d0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb53cd831 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb6b44c3f in QEventDispatcherGlib::processEvents (this=0xb1b00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb6b113ec in QEventLoop::processEvents (this=this@entry=0xb24de228, flags=...) at kernel/qeventloop.cpp:149
#7  0xb6b116e1 in QEventLoop::exec (this=this@entry=0xb24de228, flags=...) at kernel/qeventloop.cpp:204
#8  0xb69fcfec in QThread::exec (this=this@entry=0x90a19b8) at thread/qthread.cpp:542
#9  0xb6af0f2d in QInotifyFileSystemWatcherEngine::run (this=0x90a19b8) at io/qfilesystemwatcher_inotify.cpp:256
#10 0xb69ffb18 in QThreadPrivate::start (arg=0x90a19b8) at thread/qthread_unix.cpp:338
#11 0xb54e1d78 in start_thread (arg=0xb24deb40) at pthread_create.c:311
#12 0xb5d1afee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 2 (Thread 0xb17e4b40 (LWP 17158)):
#0  timerSourcePrepare (source=0xb0e02040, timeout=0xb17e408c) at kernel/qeventdispatcher_glib.cpp:160
#1  0xb53ccd21 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb53cd5cf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb53cd831 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6b44c3f in QEventDispatcherGlib::processEvents (this=0xb0e00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0xb6b113ec in QEventLoop::processEvents (this=this@entry=0xb17e4228, flags=...) at kernel/qeventloop.cpp:149
#6  0xb6b116e1 in QEventLoop::exec (this=this@entry=0xb17e4228, flags=...) at kernel/qeventloop.cpp:204
#7  0xb69fcfec in QThread::exec (this=this@entry=0x92753c8) at thread/qthread.cpp:542
#8  0xb6af0f2d in QInotifyFileSystemWatcherEngine::run (this=0x92753c8) at io/qfilesystemwatcher_inotify.cpp:256
#9  0xb69ffb18 in QThreadPrivate::start (arg=0x92753c8) at thread/qthread_unix.cpp:338
#10 0xb54e1d78 in start_thread (arg=0xb17e4b40) at pthread_create.c:311
#11 0xb5d1afee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 1 (Thread 0xb4e65980 (LWP 17156)):
[KCrash Handler]
#7  0xb6fe98e9 in BlueDevil::Device::name() const () from /usr/lib/i386-linux-gnu/libbluedevil.so.1
#8  0x0805573e in _start ()
------
Comment 1 Andrea Scarpino 2013-11-27 15:47:24 UTC
Which version is this? Which distribution?
Comment 2 Alex Fiestas 2013-12-19 16:11:18 UTC
Please provide the information asked by Andrea.
Comment 3 Alex Fiestas 2014-01-19 23:12:58 UTC
Closing the bug for lack of reply.

Please, if you are still able to reproduce the bug with BlueDevil 2.0RC1 feel free to re-open the bug.

Thanks !