Version: Beta 1 Packages (using Devel) OS: Linux Installed from: Compiled sources One fairly bad bug and a couple of other minor issues: I tried out the new plasmoid in the current beta and proceeded to copy a file from a a remote computer using fish. First thing I noticed was that when I dragged the file to my home folder the popup in dolphin asked me whether to move/copy etc and the kui plasmoid showed a window saying examining file. I then selected copy and that extender disappeared and a new one popped up (briefly both were showing at the same time) with the copy progress. When the initial extender disappeared the new one displaced/slid itself leftwards with making its right edge align with the arrow in the systray (initially they were aligned against the screen edge). Now for the BIG bug: I was getting annoyed that it kept hiding itself so I clicked the arrow to make it show itself and then grabbed the handle to the extender, almost practically a click (to attempt to to drag it to the desktop). It then disappeared, including the arrow in the systray. Maybe relevant observations: 1) I had a window open and not the desktop showing. 2) The file couldn't have been copied so quickly 3) clicking on an empty space in the systray shows the last notification which was the copy, it still says copying in the title with stop+pause buttons showing. 4) the file did copy successfully. 5) not consistently reproducible (but was able to more than once) so quick recap (in case you fell asleep during my story): 1)weird notifications 2)distracting shifting plasmoids (could not reproduce a second time) 3) disappearing progress plasmoid Phew, sorry for writing an essay here
Created attachment 28846 [details] shows weird box that comes up before copy
Created attachment 28847 [details] shows both items coexisting and the changed location of the notification boxes
*** Bug 176200 has been marked as a duplicate of this bug. ***
"clicking on an empty space in the systray shows the last notification which was the copy, it still says copying in the title with stop+pause buttons showing. " i'll bet you simply clicked and released on the title and it collapsed (you can expand/collapse entries by click on the titles). the odd text-overwritten-in-the-title thing i've seen as well, however.
more information: the garbled entry is actually two entries superimposed on top of each other; one of them would be from an entry that gets created and then either not added to the layout or removed but not deleted from the layout. haven't identified the code responsible for this yet, but that's what's happening: you can confirm by dragging one of the two overlapping items out of the way.
I'm pretty sure that isn't what happened. I think when I clicked on grey area, dolphin said the copy operation was complete. Arg...just tried it again but this time it shows an empty box(0% in progress and no files listed). with "copying" in the title, there is a close button there instead. Does the title actually change from copying to copied when complete?
Ah...I finally see what you meant about it collapsing. You're right but the arrow still disappears, which is a bit confusing. Just tried to drag it to the canvas and plasma crashed...can't give a backtrace today tho...only tomorrow.
it doesn't crash for me here anymore, though it was a few days ago. and yeah, we have some polishing work left to do on these for sure =)
Could you check which of these problems still happen with a recent build? (at least revision 895118) Quite some improvements have been made and I'd like to confirm which problems are still there before investigating them further. I know the changing of position problem (2) has been fixed. I myself only experience the problem of "examaning" and other uninteresting jobs (1), but thats not really a plasma bug, since jobs marked with KIO::HideProgressInfo are not shown: just not all jobs that should be hidden are marked this way. I would like to know if (3) still happens for you. Thanks for your assistance.
It no longer crashes when pressing the stop or pause buttons (they don't do anything, is that known?) (2) Is better, but not totally fixed (if one is to be pedantic). The notifications no longer flicker and slide whilst displayed but still start out touching the screen edge, then hide, and when the icon is clicked they show up again but with the right edge aligned in line with the right edge of the systray. see attached screens kui_A->kui_B It only gets aligned with the systray when brought up manually. When it shows up automatically (because I started a second copy, it was aligned against screen edge). (3) I would answer that it appears to "nearly" work: -Collapsing by clicking the title bar manages to collapse and survives briefly and then causes plasma to crash. Dragging off a notification is the same, nearly works then crash (locked widgets) -Unlocked there are no problems except when trying to re-attach to systray. It looks as if it can be dragged there but then gets misses and falls behind the panel (not a bug?) See kui_C.png. It works when dragged to panel (shows the extender icon with the notification in a popup ...very neat). -Collapsing works better when widgets are unlocked whether on the panel or on the desktop. -Collapsing works if collapsed before the widget is auto-hidden. Collapsing a manually unhidden noti' fails 100% (crash). -Messing around with collapsing and dragging to/from panel will eventually lead to a plasma crash (if it survived the first time). Hrm...Just tried doing this sort of stuff with the calender extender from the clock and the same sort of things happen there too. Extenders still seem a bit fragile. Shall I open these in a new bug report? Do you want the back traces...and how can I get them as plasma auto-restarts?
Created attachment 29228 [details] initial position or auto unhide position
Created attachment 29229 [details] manual unhide position
Created attachment 29230 [details] missing the systray on re-attach
@Tiago: thanks for responding this fast. It worries me that you still experience crashes, since I thought I had fixed all of them by now. Could you tell me which version of kde and qt you are using, and could you add a backtrace of the crash you experience? Oh, and I fixed the crash with locked widgets just a few hours ago.
Right... just now compiled from source using the opensuse Qt repo (not the main oss repo) and all the other packages. Overall it's getting a lot better. collapsing and expanding notifications no longer crashes plasma. However, playing around with that and dragging general messing about does make the notification disappear along with the systray icon. Dragging onto a locked desktop still crashes (every time) and I'm attaching a backtrace. Dragging a "desktoped" notification onto the panel does not do anything (before it it crashed). Unlocked it works fine.
Created attachment 29366 [details] exactly as the filename says
Created attachment 29367 [details] exactly as the filename says
Tiago: please paste the backtraces right into the comment. do not attach them as backtraces, since bugzilla can't search through those making finding bugs a lot harder.
Tiago: could you specify exactly what makes a notification dissappear? About the locked crash... I've made a commit today that doesn't allow dragging of items when widgets are locked, so that problem is hereby solved.
Application: Plasma Workspace (plasma), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] 0x00007f3689062ce1 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f368e9b7790 (LWP 27335))] Thread 2 (Thread 0x7f3671152950 (LWP 27343)): #0 0x00007f3689a9ed59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f3689d0ffd9 in QWaitCondition::wait (this=0x910670, mutex=0x910668, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:82 #2 0x00007f3673bf96a8 in RenderThread::run (this=0x910658) at /home/kde-devel/kde/src/KDE/kdebase/workspace/plasma/wallpapers/image/renderthread.cpp:91 #3 0x00007f3689d0f022 in QThreadPrivate::start (arg=0x910658) at thread/qthread_unix.cpp:185 #4 0x00007f3689a9b070 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f36890940ed in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f368e9b7790 (LWP 27335)): [KCrash Handler] #5 0x00007f368ac6769c in QGraphicsScenePrivate::itemsAtPosition (this=0x70ddd0, screenPos=@0x7fff96af87b0, scenePos=@0x7fff96af8770, widget=0xdd1b50) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:438 #6 0x00007f368ac67f5b in QGraphicsScenePrivate::dispatchHoverEvent (this=0x70ddd0, hoverEvent=0x7fff96af8800) at graphicsview/qgraphicsscene.cpp:3371 #7 0x00007f368ac68086 in QGraphicsScene::mouseReleaseEvent (this=<value optimized out>, mouseEvent=0x7fff96af8dc0) at graphicsview/qgraphicsscene.cpp:3613 #8 0x00007f368ac683a0 in QGraphicsScene::event (this=0x6cfb30, event=0x7fff96af8dc0) at graphicsview/qgraphicsscene.cpp:2966 #9 0x00007f368a72517d in QApplicationPrivate::notify_helper (this=0x65f620, receiver=0x6cfb30, e=0x7fff96af8dc0) at kernel/qapplication.cpp:3803 #10 0x00007f368a72cf2a in QApplication::notify (this=0x64c950, receiver=0x6cfb30, e=0x7fff96af8dc0) at kernel/qapplication.cpp:3768 #11 0x00007f368cf7892b in KApplication::notify (this=0x64c950, receiver=0x6cfb30, event=0x7fff96af8dc0) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #12 0x00007f3689df7e81 in QCoreApplication::notifyInternal (this=0x64c950, receiver=0x6cfb30, event=0x7fff96af8dc0) at kernel/qcoreapplication.cpp:587 #13 0x00007f368ac77fbb in QGraphicsView::mouseReleaseEvent (this=0xe27af0, event=0x7fff96af9620) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #14 0x00007f368a777999 in QWidget::event (this=0x7f368b090d40, event=0x7fff96af9620) at kernel/qwidget.cpp:7163 #15 0x00007f368ac75f2b in QGraphicsView::viewportEvent (this=0xe27af0, event=0x7fff96af9620) at graphicsview/qgraphicsview.cpp:2337 #16 0x00007f3689df7148 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0xdd1b50, event=0x7fff96af9620) at kernel/qcoreapplication.cpp:694 #17 0x00007f368a72514c in QApplicationPrivate::notify_helper (this=0x65f620, receiver=0xdd1b50, e=0x7fff96af9620) at kernel/qapplication.cpp:3799 #18 0x00007f368a72d79a in QApplication::notify (this=<value optimized out>, receiver=0xdd1b50, e=0x7fff96af9620) at kernel/qapplication.cpp:3528 #19 0x00007f368cf7892b in KApplication::notify (this=0x64c950, receiver=0xdd1b50, event=0x7fff96af9620) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #20 0x00007f3689df7e81 in QCoreApplication::notifyInternal (this=0x64c950, receiver=0xdd1b50, event=0x7fff96af9620) at kernel/qcoreapplication.cpp:587 #21 0x00007f368a72cb38 in QApplicationPrivate::sendMouseEvent (receiver=0xdd1b50, event=0x7fff96af9620, alienWidget=0xdd1b50, nativeWidget=0xe27af0, buttonDown=<value optimized out>, lastMouseReceiver=@0x7f368b0a2760) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212 #22 0x00007f368a791259 in QETWidget::translateMouseEvent (this=0xe27af0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4040 #23 0x00007f368a78fc77 in QApplication::x11ProcessEvent (this=0x13b, event=0x7fff96afa0a0) at kernel/qapplication_x11.cpp:3158 #24 0x00007f368a7b655c in x11EventSourceDispatch (s=0x662cd0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142 #25 0x00007f36868ab0db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x00007f36868ae8ad in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x00007f36868aea6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f3689e203af in QEventDispatcherGlib::processEvents (this=0x65f080, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #29 0x00007f368a7b5ccf in QGuiEventDispatcherGlib::processEvents (this=0x7f368b090d40, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198 #30 0x00007f3689df6782 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1766874224}) at kernel/qeventloop.cpp:143 #31 0x00007f3689df690d in QEventLoop::exec (this=0x7fff96afa3d0, flags={i = -1766874144}) at kernel/qeventloop.cpp:194 #32 0x00007f3689df8dfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #33 0x00007f368e69c44b in kdemain (argc=1, argv=0x7fff96afa6d8) at /home/kde-devel/kde/src/KDE/kdebase/workspace/plasma/shells/desktop/main.cpp:54 #34 0x00007f3688fdf586 in __libc_start_main () from /lib64/libc.so.6 #35 0x0000000000400849 in _start () at ../sysdeps/x86_64/elf/start.S:113
to make the notifications disappear, basically you rapidly collapse/uncollapse by rapidly clicking on the title bars. Its hard to replicate consistently due to the speed. It may be that I'm also dragging off the notifications. I would like to refine what happens on drag with a locked screen. It doesn't crash straight away...If you only drag it a bit and it stays near the taskbar and doesn't crash, but it does show the white border around the plasmoid. It may be that your latest changes fix this. I'll give this a go when I get home later...
Do you have revision 897287 or later?
dunno, was that yesterday? (monday 20:00 UTC) I can't compile kdebase right now (some cmakelists.txt conflict under runtime)
As of today (with beta2) things seem to all work properly. Nice. Thanks a bunch
Re opening as dragging off notification on locked plasma still can crash it, see bug 178342 for description
Actually, commit 897287 was from after the tagging of beta2. Do you use beta2 or have a recent build? (beta 2 is like ancient ;)
aha...I'll give it a go compiling again...I couldn't compile kdebase earlier so I tried with just compiling workspace but plasma kept crashing at startup
you're quite right...it is fixed. However the buttons really need to do something otherwise i can't remove the notifications sanely (i.e. not killing the kio process)