[plasmashell] [Bug 366653] New: Plasmashell crash while dragging control bar

2016-08-11 Thread Marco Leise via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366653

Bug ID: 366653
   Summary: Plasmashell crash while dragging control bar
   Product: plasmashell
   Version: 5.7.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: marco.le...@gmx.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.3)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.5.7-aufs x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:

1. Hibernated
2. Plugged in external monitor
3. Woke system up from hibernation
- session unlock screen shows up and moves from integrated panel to extenal TFT
-
4. Unlocked session
5. Unlocked control bar and resized it
6. Dragged control bar from right side to bottom of the screen
- before the control bar displayed at the bottom, the plasmashell crashed -

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb9d8734800 (LWP 5816))]

Thread 10 (Thread 0x7fb9d7668700 (LWP 5817)):
#0  0x003d224e145d in poll () from /lib64/libc.so.6
#1  0x003d2540ab02 in ?? () from /usr/lib64/libxcb.so.1
#2  0x003d2540cd19 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fb9d7ed01d9 in QXcbEventReader::run (this=0x6e0980) at
qxcbconnection.cpp:1337
#4  0x0032b8eb53d2 in QThreadPrivate::start (arg=0x6e0980) at
thread/qthread_unix.cpp:344
#5  0x003d22c07434 in start_thread () from /lib64/libpthread.so.0
#6  0x003d224eb88d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7fb9d5bd0700 (LWP 5818)):
#0  0x7ffe6e9d0ab5 in clock_gettime ()
#1  0x003d224f8506 in clock_gettime () from /lib64/libc.so.6
#2  0x0032b8f6a9f5 in qt_clock_gettime (ts=0x7fb9d5bcfa70, clock=1) at
tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x0032b91035f1 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fb9c8002ed0) at kernel/qtimerinfo_unix.cpp:91
#6  0x0032b9103d06 in QTimerInfoList::timerWait (this=0x7fb9c8002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x0032b9104fb5 in timerSourcePrepareHelper (timeout=0x7fb9d5bcfb60,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7fb9d5bcfb60) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x003d24454bcf in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#10 0x003d24455640 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x003d2445583f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x0032b9105bfc in QEventDispatcherGlib::processEvents
(this=0x7fb9c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#13 0x0032b90a858b in QEventLoop::exec (this=this@entry=0x7fb9d5bcfd70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#14 0x0032b8eaf604 in QThread::exec (this=this@entry=0x32bb697d80) at
thread/qthread.cpp:507
#15 0x0032bb416e10 in QDBusConnectionManager::run (this=0x32bb697d80) at
qdbusconnection.cpp:196
#16 0x0032b8eb53d2 in QThreadPrivate::start (arg=0x32bb697d80) at
thread/qthread_unix.cpp:344
#17 0x003d22c07434 in start_thread () from /lib64/libpthread.so.0
#18 0x003d224eb88d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fb9c700 (LWP 5819)):
#0  0x7ffe6e9d0ab5 in clock_gettime ()
#1  0x003d224f8506 in clock_gettime () from /lib64/libc.so.6
#2  0x0032b8f6a9f5 in qt_clock_gettime (ts=0x7fb9cfffea90, clock=1) at
tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x0032b91035f1 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fb9c4002cd0) at kernel/qtimerinfo_unix.cpp:91
#6  0x0032b9103d06 in QTimerInfoList::timerWait (this=0x7fb9c4002cd0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x0032b9104fb5 in timerSourcePrepareHelper (timeout=0x7fb9cfffeb80,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7fb9cfffeb80) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x003d24454bcf in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#10 0x003d24455640 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x003d2445583f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x0032b9105bfc in QEventDispatcherGlib::processEvents
(this=0x7fb9c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#13 0x0032b90a858b in QEventLoop::exec (this=this@entry=0x7fb9cfffed90,
flags=...,

[plasmashell] [Bug 366027] New: Search field use results in plasmashell crash

2016-07-23 Thread Marco Leise via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366027

Bug ID: 366027
   Summary: Search field use results in plasmashell crash
   Product: plasmashell
   Version: 5.7.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: marco.le...@gmx.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.2)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.5.7-aufs x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:
I was typing in the search field of the application menu to find the control
panel for global keybindings. The list already provided some results while I
was typing but at some point plasmashell just crashed away.

My Mesa version is a recent git master checkout, so if anything hints at the
intel graphics driver, maybe it's that.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f05c8a2d800 (LWP 504))]

Thread 16 (Thread 0x7f05c7961700 (LWP 507)):
#0  0x003d224e145d in poll () from /lib64/libc.so.6
#1  0x003d2540ab02 in ?? () from /usr/lib64/libxcb.so.1
#2  0x003d2540cd19 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f05c81c91d9 in QXcbEventReader::run (this=0x6e08e0) at
qxcbconnection.cpp:1337
#4  0x0032b8eb53d2 in QThreadPrivate::start (arg=0x6e08e0) at
thread/qthread_unix.cpp:344
#5  0x003d22c07434 in start_thread () from /lib64/libpthread.so.0
#6  0x003d224eb88d in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f05c5ec9700 (LWP 508)):
#0  0x003d244a49b9 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x003d24454bc0 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x003d24455640 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x003d2445583f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x0032b9105bfc in QEventDispatcherGlib::processEvents
(this=0x7f05b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x0032b90a858b in QEventLoop::exec (this=this@entry=0x7f05c5ec8d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x0032b8eaf604 in QThread::exec (this=this@entry=0x32bb697d80) at
thread/qthread.cpp:507
#7  0x0032bb416e10 in QDBusConnectionManager::run (this=0x32bb697d80) at
qdbusconnection.cpp:196
#8  0x0032b8eb53d2 in QThreadPrivate::start (arg=0x32bb697d80) at
thread/qthread_unix.cpp:344
#9  0x003d22c07434 in start_thread () from /lib64/libpthread.so.0
#10 0x003d224eb88d in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f05b700 (LWP 523)):
#0  0x003d224e145d in poll () from /lib64/libc.so.6
#1  0x003d24455726 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x003d2445583f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x0032b9105bfc in QEventDispatcherGlib::processEvents
(this=0x7f05b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x0032b90a858b in QEventLoop::exec (this=this@entry=0x7f05bfffed90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x0032b8eaf604 in QThread::exec (this=this@entry=0x7ad720) at
thread/qthread.cpp:507
#6  0x0032c3b394c6 in QQmlThreadPrivate::run (this=0x7ad720) at
qml/ftw/qqmlthread.cpp:147
#7  0x0032b8eb53d2 in QThreadPrivate::start (arg=0x7ad720) at
thread/qthread_unix.cpp:344
#8  0x003d22c07434 in start_thread () from /lib64/libpthread.so.0
#9  0x003d224eb88d in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f05be3d0700 (LWP 542)):
#0  0x003d224dd41d in read () from /lib64/libc.so.6
#1  0x003d244a35a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x003d244551d2 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x003d244556bf in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x003d2445583f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x0032b9105bfc in QEventDispatcherGlib::processEvents
(this=0x7f05ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#6  0x0032b90a858b in QEventLoop::exec (this=this@entry=0x7f05be3cfd90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#7  0x0032b8eaf604 in QThread::exec (this=this@entry=0x804850) at
thread/qthread.cpp:507
#8  0x0032c3b394c6 in QQmlThreadPrivate::run (this=0x804850) at
qml/ftw/qqmlthread.cpp:147
#9  0x0032b8eb53d2 in QThreadPrivate::start (arg=0x804850) at
thread/qthread_unix.cpp:344
#10 0x003d22c07434 in start_thread () from /lib64/libpthread.so.0
#11 0x003d224eb88d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f05bc901700 (LWP 547)):
#0

[plasma4] [Bug 312919] high CPU usage for copying notification

2016-06-24 Thread Marco Leise via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=312919

Marco Leise  changed:

   What|Removed |Added

 CC||marco.le...@gmx.de

--- Comment #9 from Marco Leise  ---
I once copied a 2 GiB hiking map to a USB 1 GPS device from my notebook while
on battery in a car and I bit my lips that I used Dolphin and not "cp". The
tray icon seemed to say: "Do you want to play a little game? Guess what is done
earlier, the file transfer or your battery." It finished in time, but it would
be nice if these animations used a little less power than e.g. watching a HD
H.264 video (6-7W). :D

-- 
You are receiving this mail because:
You are watching all bug changes.