[plasmashell] [Bug 360862] Settings -> Wallpaper: Switch from Hunyango to Haenau does not work directly
https://bugs.kde.org/show_bug.cgi?id=360862 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Can confirm this on KDE Neon 5.7. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362836] "Short date" option in clock is not short
https://bugs.kde.org/show_bug.cgi?id=362836 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- This one is fixed on plasma 5.7.90, frameworks 5.25.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362836] "Short date" option in clock is not short
https://bugs.kde.org/show_bug.cgi?id=362836 --- Comment #4 from Tony --- My short date now is: 7/8/16 Is no the same length as the ISO Date or format. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362096] Can't find apps I want to install using the "search" field
https://bugs.kde.org/show_bug.cgi?id=362096 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #8 from Tony --- Possible duplicate/related to this one: https://bugs.kde.org/show_bug.cgi?id=362585 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #5 from Tony --- I have the same issue. When i try to add a new "default panel" the desktop will crash, no restart no errors pop up, i have to logout and log in again. Afterwards the desktop have been reset to its default settings and the new "default panel" is present. I tried to remove "System Tray" and repeat, same crash. If you select "Empty System Tray" the desktop will crash as well. This happens on KDE Neon Dev Edition Unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366584] New: "Alternatives" not working.
https://bugs.kde.org/show_bug.cgi?id=366584 Bug ID: 366584 Summary: "Alternatives" not working. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jodr...@live.com Choosing any alternatives on a panel widget (in this case "task manager" or "application launcher") will remove the present widget without adding the new one/alternative. In case of "task manager", any launchers added to it are also removed. Reproducible: Always Steps to Reproduce: 1.Right click "task manager" or "application launcher" 2.Select "alternatives" 3.Choose one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366585] New: Can't drag and drop widgets.
https://bugs.kde.org/show_bug.cgi?id=366585 Bug ID: 366585 Summary: Can't drag and drop widgets. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: bhus...@gmail.com, plasma-b...@kde.org Can't add new widgets anywhere by dragging and dropping them, be it the desktop or a panel, have to double click on them. Reproducible: Always Steps to Reproduce: 1.Browse for a widget. 2.Select one 3.Try to drag it (left click+hold) to your desire location. Some widgets will by default be added to the desktop or to the panel, it depends on how you browsed for them. If right click on desktop + Add widget, it will be added to the desktop. If browsed from "a" pane options it will be added to said panel. In either case drag and drop does not work. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 366707] New: Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 Bug ID: 366707 Summary: Dual monitor, desktop crash while moving panel. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jodr...@live.com Application: plasmashell (5.7.90) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.6-6.1-liquorix-amd64 x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: I was trying to move/drag a default panel from 1 screen to another. - Unusual behavior I noticed: You need to drag it in 1 fast swop 1 screen to another. If the panel gets stuck on either side of a screen while still dragging the desktop will crash. If you stopped dragging the panel while a part of it is shown on both screens the desktop will crash. - Custom settings of the application: None, i deleted .cache and .config from my home folder, logout and in, tried again the problems persists. I must add that one of the monitors is a pretty old one, DELL 1503FP with a max res of 1024x768, the other is AOC 2243W a 1080p monitor. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2067dd68c0 (LWP 5244))] Thread 14 (Thread 0x7f1f87fff700 (LWP 5600)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2062d92adb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3d3b0c0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3cc10d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f2062d91c28 in QThreadPrivate::start (arg=0x3cc1050) at thread/qthread_unix.cpp:344 #6 0x7f2061e5a6fa in start_thread (arg=0x7f1f87fff700) at pthread_create.c:333 #7 0x7f2062691b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f1f8580a700 (LWP 5531)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2062d92adb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x39e36f0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x38e5e30, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f2062d91c28 in QThreadPrivate::start (arg=0x38e5db0) at thread/qthread_unix.cpp:344 #6 0x7f2061e5a6fa in start_thread (arg=0x7f1f8580a700) at pthread_create.c:333 #7 0x7f2062691b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f1f8f3f7700 (LWP 5509)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2062d92adb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x244ade0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x29d7060, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f2062d91c28 in QThreadPrivate::start (arg=0x29d6fe0) at thread/qthread_unix.cpp:344 #6 0x7f2061e5a6fa in start_thread (arg=0x7f1f8f3f7700) at pthread_create.c:333 #7 0x7f2062691b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f1f8700 (LWP 5508)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2062d92adb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2c99d00) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x1f53a70, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f2066030f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f2066031835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f2062d91c28 in QThreadPrivate::start (arg=0x1f539f0) at thread/qthread_unix.cpp:344 #6 0x7f2061e5a6fa in start_thread (arg=0x7f1f8700) at pthread_create.c:333 #7 0x7f2062691b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f1f9cb13700 (LWP 5507)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/uni
[kde] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 Tony changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 Tony changed: What|Removed |Added Product|kde |plasmashell Component|general |Panel Version|unspecified |5.7.3 Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365828] add firefox icon to kde panel (comes up blank)
https://bugs.kde.org/show_bug.cgi?id=365828 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #3 from Tony --- Fixed/not happening in KDE Neon, plasma 5.7.90, framework 5.25.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366739] New: 2nd monitor is not being forgotten after turning it off and reboot.
https://bugs.kde.org/show_bug.cgi?id=366739 Bug ID: 366739 Summary: 2nd monitor is not being forgotten after turning it off and reboot. Product: plasmashell Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: jodr...@live.com CC: plasma-b...@kde.org My setup: I have it setup as fallows, my "primary display" is connected to the 2nd dvi port (DVI-I-2) of my video card. The one that's off is connected to DVI-I-1, i never have set this one as my "primary display". The issue: I shutdown my pc, turn off the 2nd monitor (DVI-I-1) but left it plugged into the video card. When i boot again and log in i get the desktop that belongs to my 2nd screen, the one that is off as my "primary display". On System Settings > Display and monitor i see that both monitors are detected, even though one of them is off and that my "primary display" (DVI-I-2) haven't changed. I have to restart plasma (kstart plasma-desktop) in order to get thinks right. Reproducible: Didn't try Steps to Reproduce: 1.Set (DVI-I-2) as primary display. 2.Turn off your PC, turn off the monitor on (DVI-I-1) and leave it plugged. 3.Reboot and log in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366742] New: Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.
https://bugs.kde.org/show_bug.cgi?id=366742 Bug ID: 366742 Summary: Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time. Product: kwin Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: jodr...@live.com Today i wanted to download a few distros , got a few torrents from linuxtracker.org and proceed to download. Now Neon does not ship with a torrent downloader so i got Qbittorent (i found ktorrent too heavy on resources imo) . I got it from the official ppa: https://launchpad.net/~qbittorrent-team/+archive/ubuntu/qbittorrent-stable If i try to add more than one torrent at the same time Xorg and kwin_x11 cpu usage will skyrocket freezing the desktop, in my case adding 4 torrents at the same time will do it. Adding 2 or 3 will make the desktop unresponsive due to the CPU being hit in the face. I hit ctrl+alt+F12, tried again, same issue. Qbittorrent default behavior when adding torrents is to open a window showing the torrent contents and options related to it. If you add 4 torrents at the same time like me, 4 of this windows will open. This can be turn off so the torrents go straight away to the download list, avoiding this issue. Now i am not entirely sure if this is a KDE related issue, i posted here since i don't have this problem on Windows or MacOS while using qbittorrent. Reproducible: Always Steps to Reproduce: 1.Install qbitorrent 2.Get some torrents 3.Open 4 or more at the same time -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.
https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #3 from Tony --- Sadly can't provide a proper backtrace When i try to do it as non-root i get "ptrace: Operation not permitted." Using sudo + having the compositor on, gdb won't even open on the terminal and the desktop locks. Tried to cancel the command ctrl+c, no go, i killed x to regain control I tried again with compositor off, .It works but while gdb is running i can't click on anything, i mean i can, but there is no response, can't drag windows, right click menus etc. so cannot switch to it. Tried to open it from the terminal and i got this error: "Could not resolve property : linearGradient4566" I ran "bt" before closing gdb, this is what i got: Attaching to process 3820 [New LWP 3825] [New LWP 3827] [New LWP 3854] [New LWP 3915] [New LWP 6011] [New LWP 6012] [New LWP 6013] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f5378455e8d in poll () at ../sysdeps/unix/syscall-template.S:84 84 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) bt #0 0x7f5378455e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5376328614 in poll (__timeout=, __nfds=5, __fds=0x1906118) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 qt_ppoll (timeout_ts=, nfds=5, fds=0x1906118) at kernel/qcore_unix.cpp:93 #3 qt_safe_poll (fds=0x1906118, nfds=nfds@entry=5, timeout_ts=timeout_ts@entry=0x7ffee2132320) at kernel/qcore_unix.cpp:121 #4 0x7f5376329fb8 in QEventDispatcherUNIX::processEvents (this=, flags=..., flags@entry=...) at kernel/qeventdispatcher_unix.cpp:495 #5 0x7f536255e87d in QUnixEventDispatcherQPA::processEvents (this=, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:68 #6 0x7f53762d7d9a in QEventLoop::exec (this=this@entry=0x7ffee2132460, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7f53762e03ac in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #8 0x7f5376622dbc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1639 #9 0x7f5376bc57f5 in QApplication::exec () at kernel/qapplication.cpp:2975 #10 0x7f5378734206 in kdemain (argc=1, argv=0x7ffee21326f8) at /workspace/build/main_x11.cpp:466 #11 0x7f537837b830 in __libc_start_main (main=0x400710 , argc=1, argv=0x7ffee21326f8, init=, fini=, rtld_fini=, stack_end=0x7ffee21326e8) at ../csu/libc-start.c:291 #12 0x00400749 in _start () (gdb) quit A debugging session is active. Inferior 1 [process 3820] will be detached. Quit anyway? (y or n) y Detaching from program: /usr/bin/kwin_x11, process 3820 At this point i gave up installed ktorrent, not a single issue, so this is on qbitorrent if you ask me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.
https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #5 from Tony --- Ok, i gave it another try. Had to read about gdb a bit The desktop still locks while using gdb though so here is what i did: First i delete .config and .cache from "home" and start the desktop clean. I login to VT3 and VT4. In VT4 have top running, VT3 i used it to run gdb. So i opened 4 torrents with qbitorrent switch to VT4 check that X and kwin are using a lot cpu power. Switch to VT3 and ran gdb, set logging on, and ran bt. I got this on from "gdb.txt" on my home folder: #0 QVector::detach (this=0x1470800) at ../../../../include/QtCore/../../src/corelib/tools/qvector.h:384 #1 QVector::end (this=0x1470800) at ../../../../include/QtCore/../../src/corelib/tools/qvector.h:208 #2 QXcbConnection::processXcbEvents (this=0x14704f0) at qxcbconnection.cpp:1731 #3 0x7f54ce159ad9 in QObject::event (this=0x14704f0, e=) at kernel/qobject.cpp:1263 #4 0x7f54cea1989c in QApplicationPrivate::notify_helper (this=, receiver=0x14704f0, e=0x7f54b4a5aef0) at kernel/qapplication.cpp:3799 #5 0x7f54cea21296 in QApplication::notify (this=0x7ffc2242e190, receiver=0x14704f0, e=0x7f54b4a5aef0) at kernel/qapplication.cpp:3556 #6 0x7f54ce12dda8 in QCoreApplication::notifyInternal2 (receiver=0x14704f0, event=event@entry=0x7f54b4a5aef0) at kernel/qcoreapplication.cpp:988 #7 0x7f54ce13046b in QCoreApplication::sendEvent (event=0x7f54b4a5aef0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #8 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1456d30) at kernel/qcoreapplication.cpp:1649 #9 0x7f54ce17ddea in QEventDispatcherUNIX::processEvents (this=0x14abdf0, flags=flags@entry=...) at kernel/qeventdispatcher_unix.cpp:461 #10 0x7f54ba3b287d in QUnixEventDispatcherQPA::processEvents (this=, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:68 #11 0x7f54ce12bd9a in QEventLoop::exec (this=this@entry=0x7ffc2242e080, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #12 0x7f54ce1343ac in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #13 0x7f54ce476dbc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1639 #14 0x7f54cea197f5 in QApplication::exec () at kernel/qapplication.cpp:2975 #15 0x7f54d0588206 in kdemain (argc=1, argv=0x7ffc2242e318) at /workspace/build/main_x11.cpp:466 #16 0x7f54d01cf830 in __libc_start_main (main=0x400710 , argc=3, argv=0x7ffc2242e318, init=, fini=, rtld_fini=, stack_end=0x7ffc2242e308) at ../csu/libc-start.c:291 #17 0x00400749 in _start () Detaching from program: /usr/bin/kwin_x11, process 10843 Hopefully it helps. But now i noticed something else, when i ran gdb attached to kwin process the cpu usage from both X and kwin goes down right away, but as soon as i quit it it goes up again. Both spike well above 50% cpu usage on a FX832 up to 90% for X and stay there until i killed qbittorrent. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.
https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #7 from Tony --- For that bactrace no i did not. But it happens in any case compositing on/off, the only difference is that when off i does not happen right away i need to move the windows around, click on them or wait a little with them open. This is a backtrace i get with compositing off: #0 0x7f8669d60c74 in QXcbConnection::checkEvent<(anonymous namespace)::PropertyNotifyEvent> (this=0x23a64c0, checker=) at qxcbconnection.h:695 #1 QXcbConnection::getTimestamp (this=0x23a64c0) at qxcbconnection.cpp:1467 #2 0x7f8669d812b2 in QXcbNativeInterface::getTimestamp (this=this@entry=0x239ee10, screen=screen@entry=0x23b8c80) at qxcbnativeinterface.cpp:413 #3 0x7f8669d82242 in QXcbNativeInterface::nativeResourceForScreen (this=0x239ee10, resourceString=..., screen=0x23b8420) at qxcbnativeinterface.cpp:243 #4 0x7f86803a6c90 in QX11Info::getTimestamp() () from /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5 #5 0x7f867f7f7dd9 in KWin::updateXTime () at /workspace/build/utils.cpp:87 #6 0x7f867f827355 in KWin::Client::updateUserTime (this=0x2753740, time=time@entry=0) at /workspace/build/activation.cpp:706 #7 0x7f867f828472 in KWin::Workspace::activateClient (this=0x24812b0, c=0x2753740, force=) at /workspace/build/activation.cpp:330 #8 0x7f867e97a0dc in NETRootInfo::event(xcb_generic_event_t*, QFlags*, QFlags*) () from /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 #9 0x7f867f80d946 in KWin::Workspace::workspaceEvent (this=0x24812b0, e=0x7f86653a00f0) at /workspace/build/events.cpp:265 #10 0x7f867db50f0f in QAbstractEventDispatcher::filterNativeEvent (this=, eventType=..., message=message@entry=0x7f86653a00f0, result=result@entry=0x7fff9943a698) at kernel/qabstracteventdispatcher.cpp:466 #11 0x7f8669d64684 in QXcbConnection::handleXcbEvent (this=this@entry=0x23a64c0, event=event@entry=0x7f86653a00f0) at qxcbconnection.cpp:1103 #12 0x7f8669d65300 in QXcbConnection::processXcbEvents (this=0x23a64c0) at qxcbconnection.cpp:1735 #13 0x7f867db7fad9 in QObject::event (this=0x23a64c0, e=) at kernel/qobject.cpp:1263 #14 0x7f867e43f89c in QApplicationPrivate::notify_helper (this=, receiver=0x23a64c0, e=0x7f8665022110) at kernel/qapplication.cpp:3799 #15 0x7f867e447296 in QApplication::notify (this=0x7fff9943ad50, receiver=0x23a64c0, e=0x7f8665022110) at kernel/qapplication.cpp:3556 #16 0x7f867db53da8 in QCoreApplication::notifyInternal2 (receiver=0x23a64c0, event=event@entry=0x7f8665022110) at kernel/qcoreapplication.cpp:988 #17 0x7f867db5646b in QCoreApplication::sendEvent (event=0x7f8665022110, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #18 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x238cd30) at kernel/qcoreapplication.cpp:1649 #19 0x7f867dba3dea in QEventDispatcherUNIX::processEvents (this=0x23e5f20, flags=flags@entry=...) at kernel/qeventdispatcher_unix.cpp:461 #20 0x7f8669dd887d in QUnixEventDispatcherQPA::processEvents (this=, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:68 #21 0x7f867db51d9a in QEventLoop::exec (this=this@entry=0x7fff9943ac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #22 0x7f867db5a3ac in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #23 0x7f867de9cdbc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1639 #24 0x7f867e43f7f5 in QApplication::exec () at kernel/qapplication.cpp:2975 #25 0x7f867ffae206 in kdemain (argc=1, argv=0x7fff9943aed8) at /workspace/build/main_x11.cpp:466 #26 0x7f867fbf5830 in __libc_start_main (main=0x400710 , argc=1, argv=0x7fff9943aed8, init=, fini=, rtld_fini=, stack_end=0x7fff9943aec8) at ../csu/libc-start.c:291 #27 0x00400749 in _start () Detaching from program: /usr/bin/kwin_x11, process 3126 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 367535] New: Ark opening rar files, "no suitable plugin found"
https://bugs.kde.org/show_bug.cgi?id=367535 Bug ID: 367535 Summary: Ark opening rar files, "no suitable plugin found" Product: ark Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plugins Assignee: rthoms...@gmail.com Reporter: jodr...@live.com CC: elvis.angelac...@kdemail.net As title says, ark is unable to find the proper plugin even-though i already have installed rar, unrar and p7zip-rar. I get this when i run it from the terminal: ark.kerfuffle: Mimetype for filename extension ( "application/x-rar" ) did not match mimetype for content ( "application/pdf" ). Using content-based mimetype. ark.kerfuffle: Could not find a plugin to handle "/home/joder/VBoxShare/1.rar" How that change? no idea haven't touch anything related to "mimetypes". Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 367535] Ark opening rar files, "no suitable plugin found"
https://bugs.kde.org/show_bug.cgi?id=367535 --- Comment #3 from Tony --- :( yep shared-mime-info=1.5, so package bug since this is already fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367612] New: Plasma desktop options are not being safe/restore.
https://bugs.kde.org/show_bug.cgi?id=367612 Bug ID: 367612 Summary: Plasma desktop options are not being safe/restore. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: jodr...@live.com Changing your desktop layout to "folder view" is not preserve after logging out or rebooting. It will reset back to "Desktop". Reproducible: Always Steps to Reproduce: 1.Right click on the desktop and select "Configure Desktop" 2.Set layout to "Folder View" 3.Log out and back in or reboot Actual Results: Desktop layout goes back to "Desktop" Expected Results: The change to be safe/restored. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367612] Plasma desktop options are not being safe/restore.
https://bugs.kde.org/show_bug.cgi?id=367612 --- Comment #1 from Tony --- ...Forgot to mention that this goes for changing your wallpaper type to tweaks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.
https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #9 from Tony --- I did as you said, suspended the compositor, removed qbitorrent icon from notification area. Like this, it does not happen right away as i said before, it only takes longer to pop up, have to force it (opening many torrents). Kwin and qbitorrent cpu usage only go up when Xorg usage goes up by a lot in this case. So is more like your 1st case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 Tony changed: What|Removed |Added Version Fixed In||5.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365759] "Cog" icon on desktop has odd behavior.
https://bugs.kde.org/show_bug.cgi?id=365759 --- Comment #1 from Tony --- Close this one, fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367612] Plasma desktop options are not being safe/restore.
https://bugs.kde.org/show_bug.cgi?id=367612 --- Comment #2 from Tony --- Here's another way you can reproduce this one and also notice another, although related bug: Logout and delete .config and .cache from your home folder. Login again and Right click on the desktop and select "Configure Desktop". You'll see that 2 windows for "Configure Desktop" will open. Any change you do here will not get safe, until you change your desktop layout, which will silently crash the window after doing so. Logout/in to see the desktop layout has been reseted. The other related issue... While having the 2 "Configure Desktop" windows open, Clicking/giving focus to one them will mess up the desktop, it will og black, will be unable take "right click", clicking/focusing the other one again will fix it. This 2 windows only apear when there is no .cache and .config folder present in your home folder. If no changes where made to the desktop layout, this 2 windows will keep poping until you. If you made a layout change but close first the window that does not mess up the desktop, you will end up with a mess up desktop until login again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367612] Plasma desktop "Configure Desktop" window and layout options problems.
https://bugs.kde.org/show_bug.cgi?id=367612 Tony changed: What|Removed |Added Summary|Plasma desktop options are |Plasma desktop "Configure |not being safe/restore. |Desktop" window and layout ||options problems. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366707] Dual monitor, desktop crash while moving panel.
https://bugs.kde.org/show_bug.cgi?id=366707 --- Comment #2 from Tony --- Yes it is fixed, close it down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369214] Keyboard "Lock" keys (Caps/Num/Scroll) leds not turning on.
https://bugs.kde.org/show_bug.cgi?id=369214 Tony changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369210] Wayland, changing compositor options gets me a "black screen"
https://bugs.kde.org/show_bug.cgi?id=369210 --- Comment #4 from Tony --- Sorry, i got you the wrong kwin version my bad, is 5.26 not 5.5.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369210] Wayland, changing compositor options gets me a "black screen"
https://bugs.kde.org/show_bug.cgi?id=369210 --- Comment #6 from Tony --- Sorry again, just updated Neon VM and my main system. apt-cache policy kwin kwin: Installed: 4:5.8.0+p16.04+git20161005.0500-0 My screen still goes black as soon i hit apply on any changes made to the compositor. On the VM instead of a black screen the desktop freeze/hangs instead. But as i was browsing the list of packages and noticed i was missing some that i think i should have had installed already kwin-wayland-backend-wayland xwayland-lts-xenial plasma-wayland-desktop kwin-wayland-backend-x11 ibus-wayland wayland-protocols libwayland-egl1-mesa-lts-xenial I installed them, problem still there, but now sometimes instead of getting a black screen i get thrown out to sddm which is better imo. .. 2 commands, tons of options, same goal, i get confuse i'll stick to apt-cache policy and muon from now on -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369866] System Tray crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=369866 --- Comment #3 from Tony --- This sort itself out today after i updated my main system and vm. Whatever it was is not happening anymore. Maybe a package/configuration conflict. Also downloaded today's neon unstable iso to check out as i did with yesterday's one, all good. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370346] "Add Widget" applet doesn't receive keyboard inputs
https://bugs.kde.org/show_bug.cgi?id=370346 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Similar/duplicated > https://bugs.kde.org/show_bug.cgi?id=369867 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369866] System Tray crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=369866 Tony changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 370358] GIve sddm user home folder and .face.icon ACL rights in order to load the avatar
https://bugs.kde.org/show_bug.cgi?id=370358 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- I can confirm this one, but i believe it is a regression. On my main system i've changed the avatar with no issues more than once a while back, now i've tried on a VM and the problem is there. The newly selected avatar gets display on the lock and "leave" screen but not sddm. Avatars from the gallery work fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370359] Unable to use autostart in system config
https://bugs.kde.org/show_bug.cgi?id=370359 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Working fine here, Neon unstable. Now be mindful of the extra "options" like %u, in my case when i added firefox to auto start it would also open www.%u.com. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364746] Crash when accessing 'Font Management' inside Fonts section of 'Settings'
https://bugs.kde.org/show_bug.cgi?id=364746 --- Comment #4 from Tony --- (In reply to miku84 from comment #3) > So the issue happens on wayland only. Yes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370520] New: Dolphin crash while renaming a text file.
https://bugs.kde.org/show_bug.cgi?id=370520 Bug ID: 370520 Summary: Dolphin crash while renaming a text file. Product: dolphin Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jodr...@live.com Application: dolphin (16.11.70) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-42-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: I hit F2 on text file to change its name, dolphin crashed as soon as i hit "enter". The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd4feac38c0 (LWP 16993))] Thread 3 (Thread 0x7fd4dc325700 (LWP 16996)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:68 #1 0x7fd4fe4b49c2 in read () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fd4f355b740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd4f3517e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd4f3518340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd4f35184ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd4f91b023b in QEventDispatcherGlib::processEvents (this=0x7fd4d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7fd4f915acea in QEventLoop::exec (this=this@entry=0x7fd4dc324d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #8 0x7fd4f8f7ffb4 in QThread::exec (this=) at thread/qthread.cpp:507 #9 0x7fd4f8f84b98 in QThreadPrivate::start (arg=0x17124f0) at thread/qthread_unix.cpp:344 #10 0x7fd4f563d6fa in start_thread (arg=0x7fd4dc325700) at pthread_create.c:333 #11 0x7fd4fe4c4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fd4e9c15700 (LWP 16995)): #0 0x7fd4f8f7c03c in QMutex::lock (this=this@entry=0x1344300) at thread/qmutex.cpp:231 #1 0x7fd4f91af98f in QMutexLocker::QMutexLocker (m=0x1344300, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:137 #2 QThreadData::canWaitLocked (this=0x13442d0) at ../../include/QtCore/5.7.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #3 postEventSourcePrepare (s=0x7fd4e40012d0, timeout=0x7fd4e9c14b04) at kernel/qeventdispatcher_glib.cpp:259 #4 0x7fd4f351792d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd4f35182cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd4f35184ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fd4f91b023b in QEventDispatcherGlib::processEvents (this=0x7fd4e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fd4f915acea in QEventLoop::exec (this=this@entry=0x7fd4e9c14cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #9 0x7fd4f8f7ffb4 in QThread::exec (this=this@entry=0x7fd4fec1fd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #10 0x7fd4febab7a5 in QDBusConnectionManager::run (this=0x7fd4fec1fd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #11 0x7fd4f8f84b98 in QThreadPrivate::start (arg=0x7fd4fec1fd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #12 0x7fd4f563d6fa in start_thread (arg=0x7fd4e9c15700) at pthread_create.c:333 #13 0x7fd4fe4c4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fd4feac38c0 (LWP 16993)): [KCrash Handler] #6 QMimeData::hasUrls (this=0x0) at kernel/qmimedata.cpp:387 #7 0x7fd4fcd113aa in KIO::ClipboardUpdater::update (srcUrl=..., destUrl=...) at /workspace/build/src/widgets/clipboardupdater.cpp:160 #8 0x7fd4fc543992 in KIO::SimpleJob::slotFinished (this=0x19108b0) at /workspace/build/src/core/simplejob.cpp:226 #9 0x7fd4f9187b09 in QMetaObject::activate (sender=sender@entry=0x13a2130, signalOffset=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3740 #10 0x7fd4f91884b7 in QMetaObject::activate (sender=sender@entry=0x13a2130, m=m@entry=0x7fd4fc7f0840 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3602 #11 0x7fd4fc51b723 in KIO::SlaveInterface::finished (this=this@entry=0x13a2130) at /workspace/build/obj-x86_64-linux-gnu/src/core/moc_slaveinterface.cpp:424 #12 0x7fd4fc51d6f1 in KIO::SlaveInterface::dispatch (this=0x13a2130, _cmd=, rawdata=...) at /workspace/buil
[dolphin] [Bug 370520] Dolphin crash while renaming a text file.
https://bugs.kde.org/show_bug.cgi?id=370520 Tony changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370521] New: [Regresion] SDDM breeze theme unable to change backgound.
https://bugs.kde.org/show_bug.cgi?id=370521 Bug ID: 370521 Summary: [Regresion] SDDM breeze theme unable to change backgound. Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com Can't change the background while using breeze theme, there is not problem while using any of the other themes on the repos (circles, elarun, maldives, maui). This is the version i have installed: sddm: Installed: 0.14.0+p16.04+git20161011.1715-0 sddm-theme-breeze: Installed: 4:5.8.1+p16.04+git20161012.0430-0 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 368776] Kontact crashing on wayland.....
https://bugs.kde.org/show_bug.cgi?id=368776 Tony changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Tony --- Akregator is working now on wayland. kontact does not crashes anymore. Knotes and korganizer. If you install either individually without kontact they will crash. If you already have kontact installed they will work ONLY by running kontact, individually they will still crash. I am marking thit as "resolved/works for me" since kontact do not crashes anymore, and there are bugs already reported for knotes and korganizer crahsing on wayland. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 371246] New: [Wayland] Plasma crashed while switching between "Folder" and "Desktop" view.
https://bugs.kde.org/show_bug.cgi?id=371246 Bug ID: 371246 Summary: [Wayland] Plasma crashed while switching between "Folder" and "Desktop" view. Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jodr...@live.com Application: plasmashell (5.8.90) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-43-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: As the title says. It does not happen all the time you need to keep switching and hitting apply for it to trigger a couple of times. I know there is a bug with the "Configure Desktop" window, it silently closes after you've changed the view type and hit apply, never got a desktop crash before. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6508d18c0 (LWP 4075))] Thread 17 (Thread 0x7fa56f610700 (LWP 4222)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fa64b878986 in QWaitConditionPrivate::wait_relative (time=3, this=0x415ffd0) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x415ffd0) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x3df2a00, mutex=mutex@entry=0x3608bc0, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7fa64b87423a in QThreadPoolThread::run (this=0x3df29f0) at thread/qthreadpool.cpp:133 #5 0x7fa64b877b98 in QThreadPrivate::start (arg=0x3df29f0) at thread/qthread_unix.cpp:344 #6 0x7fa64a9406fa in start_thread (arg=0x7fa56f610700) at pthread_create.c:333 #7 0x7fa64b177b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fa56fff8700 (LWP 4219)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa64b878a4b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x38d6bc0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3739e50, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fa64eb16eed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fa64eb177c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fa64b877b98 in QThreadPrivate::start (arg=0x3739dd0) at thread/qthread_unix.cpp:344 #6 0x7fa64a9406fa in start_thread (arg=0x7fa56fff8700) at pthread_create.c:333 #7 0x7fa64b177b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fa580b38700 (LWP 4218)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa64b878a4b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3678de0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3678840, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fa64eb16eed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fa64eb177c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fa64b877b98 in QThreadPrivate::start (arg=0x36787c0) at thread/qthread_unix.cpp:344 #6 0x7fa64a9406fa in start_thread (arg=0x7fa580b38700) at pthread_create.c:333 #7 0x7fa64b177b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fa58135f700 (LWP 4214)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fa64b878986 in QWaitConditionPrivate::wait_relative (time=3, this=0x2862de0) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x2862de0) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x25e5a90, mutex=mutex@entry=0x3608bc0, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7fa64b87423a in QThreadPoolThread::run (this=0x25e5a80) at thread/qthreadpool.cpp:133 #5 0x7fa64b877b98 in QThreadPrivate::start (arg=0x25e5a80) at thread/qthread_unix.cpp:344 #6 0x7fa64a9406fa in start_thread (arg=0x7fa58135f700) at pthread_create.c:333 #7 0x7fa64b177b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fa581dd8700 (LWP 4213)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa64b878a4b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2e46bf0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x331f5b0, time=18446744073709551615) at thread/qwaitco
[plasmashell] [Bug 371246] [Wayland] Plasma crashed while switching between "Folder" and "Desktop" view.
https://bugs.kde.org/show_bug.cgi?id=371246 Tony changed: What|Removed |Added Product|kde |plasmashell Version|unspecified |master Platform|unspecified |Neon Packages Component|general |generic-wayland Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371246] [Wayland] Plasma crashed while switching between "Folder" and "Desktop" view.
https://bugs.kde.org/show_bug.cgi?id=371246 Tony changed: What|Removed |Added Component|generic-wayland |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364425] CSV import only shows checking accounts when selecting Banking
https://bugs.kde.org/show_bug.cgi?id=364425 Tony changed: What|Removed |Added CC||t...@marshall.name -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 371395] New: Ktorrent crash while adding magnet link.
https://bugs.kde.org/show_bug.cgi?id=371395 Bug ID: 371395 Summary: Ktorrent crash while adding magnet link. Product: ktorrent Version: 4.3.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: jodr...@live.com Application: ktorrent (4.3.1) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.8.3-040803-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: As title says. First time it happens to me, i did notice that sometimes it takes a long time to add them. - What I was doing when the application crashed: Adding a magnet link from firefox. The crash can be reproduced sometimes. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcac03be900 (LWP 20697))] Thread 5 (Thread 0x7fca98f33700 (LWP 20706)): #0 0x7fcabc16fe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcab19b8235 in send_dg (ansp2_malloced=0x0, resplen2=0x0, anssizp2=0x0, ansp2=0x0, anscp=0x7fca98f31eb0, gotsomewhere=, v_circuit=, ns=0, terrno=0x7fca98f316d8, anssizp=0x7fca98f31810, ansp=0x7fca98f316c8, buflen2=0, buf2=0x0, buflen=43, buf=0x7fca98f31840 "", statp=0x7fca98f33db8) at res_send.c:1165 #2 __libc_res_nsend (statp=statp@entry=0x7fca98f33db8, buf=buf@entry=0x7fca98f31840 "", buflen=buflen@entry=43, buf2=buf2@entry=0x0, buflen2=buflen2@entry=0, ans=ans@entry=0x7fca98f31a50 "\217\212\201\200", anssiz=1024, ansp=0x7fca98f31eb0, ansp2=0x0, nansp2=0x0, resplen2=0x0, ansp2_malloced=0x0) at res_send.c:538 #3 0x7fcab19b5e32 in __GI___libc_res_nquery (statp=0x7fca98f33db8, name=name@entry=0x7fca98f31ec0 "239.40.137.2.in-addr.arpa", class=class@entry=1, type=type@entry=12, answer=0x7fca98f31a50 "\217\212\201\200", anslen=anslen@entry=1024, answerp=0x7fca98f31eb0, answerp2=0x0, nanswerp2=0x0, resplen2=0x0, answerp2_malloced=0x0) at res_query.c:227 #4 0x7fcaa886ffa1 in __GI__nss_dns_gethostbyaddr2_r (addr=0x7fca98f32a54, len=4, af=2, result=0x7fca98f32430, buffer=0x7fca98f325f0 "\377\002", buflen=1024, errnop=0x7fca98f33670, h_errnop=0x7fca98f32424, ttlp=0x0) at nss_dns/dns-host.c:485 #5 0x7fcaa8870723 in _nss_dns_gethostbyaddr_r (addr=, len=, af=, result=, buffer=, buflen=, errnop=0x7fca98f33670, h_errnop=0x7fca98f32424) at nss_dns/dns-host.c:544 #6 0x7fcabc18e11d in __gethostbyaddr_r (addr=addr@entry=0x7fca98f32a54, len=len@entry=4, type=type@entry=2, resbuf=resbuf@entry=0x7fca98f32430, buffer=0x7fca98f325f0 "\377\002", buflen=1024, result=0x7fca98f32428, h_errnop=0x7fca98f32424) at ../nss/getXXbyYY_r.c:266 #7 0x7fcabc195c47 in __GI_getnameinfo (sa=sa@entry=0x7fca98f32a50, addrlen=, host=host@entry=0x7fca98f32ad0 "", hostlen=hostlen@entry=199, serv=serv@entry=0x7fca98f32ba0 "", servlen=servlen@entry=199, flags=8) at getnameinfo.c:245 #8 0x7fcabff3fcf6 in net::ReverseResolver::resolve (this=this@entry=0x3597d10, addr=...) at ../../src/net/reverseresolver.cpp:65 #9 0x7fcabff3fd78 in net::ReverseResolver::run (this=this@entry=0x3597d10) at ../../src/net/reverseresolver.cpp:74 #10 0x7fcabff400da in net::ReverseResolverThread::run (this=0x22015d0) at ../../src/net/reverseresolver.cpp:119 #11 0x7fcabcd6fe3c in QThreadPrivate::start (arg=0x22015d0) at thread/qthread_unix.cpp:352 #12 0x7fcab904c6fa in start_thread (arg=0x7fca98f33700) at pthread_create.c:333 #13 0x7fcabc17bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fca99734700 (LWP 20705)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7fcabc0f4e8d in _int_free (av=0x7fcabc438b20 , p=0x2f9de90, have_lock=0) at malloc.c:3963 #2 0x7fcabc0f8abc in __GI___libc_free (mem=) at malloc.c:2969 #3 0x7fcabff6621c in bt::Packet::~Packet (this=0x3368ac0, __in_chrg=) at ../../src/download/packet.cpp:99 #4 bt::Packet::~Packet (this=0x3368ac0, __in_chrg=) at ../../src/download/packet.cpp:100 #5 0x7fcabff38f11 in QtSharedPointer::ExternalRefCount::deref (value=0x3368ac0, d=0x30d2730) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:342 #6 QtSharedPointer::ExternalRefCount::internalCopy (other=..., this=0x2e2ef98) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:412 #7 QSharedPointer::operator= (other=..., this=0x2e2ef98) at /usr/include/qt4/QtCore/qsharedpointer_impl.h:483 #8 net::PacketSocket::write (this=0x2e2ef30, max=439, now=1476990068932) at ../../src/net/packetsocket.cpp:135 #9 0x7fcabff3e9b8 in net::SocketGroup::processLimited (this=0x1c134b0, up=true, now=1476990068932, allowance=@0x7fca99733c04: 2712) at ../../src/net/socketgroup.cpp:77 #10 0x7fcabff3ec40 in net::SocketGroup::process (this=0
[ktorrent] [Bug 371395] Ktorrent crash while adding magnet link.
https://bugs.kde.org/show_bug.cgi?id=371395 Tony changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370913] Logout from Wayland session locks up system
https://bugs.kde.org/show_bug.cgi?id=370913 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #5 from Tony --- I've been having this mostly on my virtualbox vm install but i thought it was a virtualbox issue. On my main system, well wayland is too "unstable" on it so i gave it a pass, until now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371399] New: [Wayland] Firefox either hangs my desktop or crashes the session.
https://bugs.kde.org/show_bug.cgi?id=371399 Bug ID: 371399 Summary: [Wayland] Firefox either hangs my desktop or crashes the session. Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jodr...@live.com Today i did i full update on my main system and added a ppa to get a newer nouveau driver (newer mesa is also included there) for my gtx 760. https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/?field.series_filter=xenial All fine on X. Switch to a wayland session to check out if the "new stuff" makes things more stable for me. As soon as i opened firefox some artifacts showed on the firefox window and the desktop hanged could not even switch vts. Rebooted, tried again, the same. On X i turned off "hardware acceleration" for firefox to see if that may be related, nope still hangs on wayland. I get no crash the desktop just goes black and hangs. Sorry i can't (don't know) how to get you a backtrace with this one. kwin: Installed: 4:5.8.2+p16.04+git20161020.0545-0 kwin-wayland: Installed: 4:5.8.2+p16.04+git20161020.0545-0 xserver-xorg-video-nouveau: Installed: 1:1.0.13+git1609221931.e64798~gd~x libdrm-nouveau2: Installed: 2.4.71+git1610191830.7dd284~gd~x xwayland: Installed: 2:1.18.4-0ubuntu0.1 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371399] [Wayland] Firefox either hangs my desktop or crashes the session.
https://bugs.kde.org/show_bug.cgi?id=371399 Tony changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from Tony --- ..Yea is not firefox, i reset my desktop configs and now it hangs soon after ksplash logo ends. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 368563] Cantor does not provide a bug reporting address.
https://bugs.kde.org/show_bug.cgi?id=368563 --- Comment #3 from Tony --- I use kde neon cantor version 16.11.70. My system if up to date, no new updates available right now, still have the issue.So i bet there is no package for cantor with the fix on the repos yet. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 362204] Does not work on wayland
https://bugs.kde.org/show_bug.cgi?id=362204 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #11 from Tony --- I bet you a beer that you use nvidia card + nouveau -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 317683] Impossible select archived file by keyboard
https://bugs.kde.org/show_bug.cgi?id=317683 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- Well is not entirely impossible, you can hit "space" and it will select the file. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 349043] while typing in search muon discover will freeze for short amounts of time
https://bugs.kde.org/show_bug.cgi?id=349043 Tony changed: What|Removed |Added CC||jodr...@live.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365118] New: Discover crashes while using search field.
https://bugs.kde.org/show_bug.cgi?id=365118 Bug ID: 365118 Summary: Discover crashes while using search field. Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jodr...@live.com Created attachment 99866 --> https://bugs.kde.org/attachment.cgi?id=99866&action=edit Log from running discover from konsole. Using Discover's 5.7 search field will crash it. In order to avoid the crash you have to type the name of the app really fast or copy paste it in the search field otherwise the crash will occur. Eg, if i search for "firefox" and typed "f", wait a little, it will crash. Also if i copy-paste "firefox" on the field it will work, BUT, if i backspace a couple of characters it'll crash. The attached log is what i get from running Discover from konsole. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365118] Discover 5.7 crashes while using search field.
https://bugs.kde.org/show_bug.cgi?id=365118 Tony changed: What|Removed |Added Summary|Discover crashes while |Discover 5.7 crashes while |using search field. |using search field. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365118] Discover 5.7 crashes while using search field.
https://bugs.kde.org/show_bug.cgi?id=365118 --- Comment #4 from Tony --- Updated Neon today, and got KDE Frameworks: 5.24. The problem persists although it happen less often and only (as far as i noticed) when you backspace and few characters are left in the search field, on rare occasions it crashed when you backspace all characters. Speed is "key" to trigger the bug, if you backspace fast it will not happen. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 364265] Fresh install of KDE Neon with no sources configured in Discover application
https://bugs.kde.org/show_bug.cgi?id=364265 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- I am on 5.7, this still happens. Although you can make discover display them Do: ALT+S > hit the "+" button> Software manager, a box will pop. Don't click or type anything, wait a few seconds and they will appear. Then you'll encounter this: https://bugs.kde.org/show_bug.cgi?id=327178 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365118] Discover 5.7 crashes while using search field.
https://bugs.kde.org/show_bug.cgi?id=365118 --- Comment #6 from Tony --- Created attachment 100011 --> https://bugs.kde.org/attachment.cgi?id=100011&action=edit plasma-discover-20160711-121148.kcrash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365118] Discover 5.7 crashes while using search field.
https://bugs.kde.org/show_bug.cgi?id=365118 --- Comment #7 from Tony --- Comment on attachment 100011 --> https://bugs.kde.org/attachment.cgi?id=100011 plasma-discover-20160711-121148.kcrash I have installed plasma-discover-dbgsym and plasma-discover-private-dbgsym. It says its not useful still. [quote]The packages containing debug information for the following application and libraries are missing: /usr/bin/plasma-discover /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5[/quote] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365118] Discover 5.7 crashes while using search field.
https://bugs.kde.org/show_bug.cgi?id=365118 --- Comment #8 from Tony --- ...Well as was figuring out how to install the missing "dbgs" (which have some unmet dependencies) to do a proper backtrace, i got "new updates to install". Did so and magic is fixed. The problem is gone, looks like i did not get the needed package in my last update, weird. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365759] New: "Cog" icon on desktop has odd behavior.
https://bugs.kde.org/show_bug.cgi?id=365759 Bug ID: 365759 Summary: "Cog" icon on desktop has odd behavior. Product: plasmashell Version: 5.7.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: bhus...@gmail.com, plasma-b...@kde.org If you move the "cog" icon from the top left corner of the desktop you'll notice the words "default" right next to it appears. The issue comes when you try to place it anywhere else on the desktop, it will start showing odd behavior. The word "default" will not hide as it happens when you place it back on the top left corner. The word "default" appears top vertically when moved to the left side of the desktop. On bottom on the right side. You cant place it on the center of the desktop or near it, it will snap to either top/bottom/right/left side of the desktop. (May be this is ok, not sure.) If you want to place it on the top right corner, like me, and you click over any character of the word "default" and drag it there, an endless auto-hide animation loop will trigger. Do the same but instead of click and drag over the "cog". Now it will not auto-hide, you'll need to click over it for it to happen, but when you click it again it will pop to the right again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363673] Popup menu - Create New - Link to Application does nothing useful
https://bugs.kde.org/show_bug.cgi?id=363673 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- Can confirm this is present and occurs exactly as described on kde neon 5.7.1. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365795] Setting extended permissions do not work
https://bugs.kde.org/show_bug.cgi?id=365795 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- Can confirm this one. Present on KDE Neon 5.7.2, Dolphin ver.16.04.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 337711] Dragging a Firefox tab to the desktop (so it creates a new firefox window for it) doesn't work.
https://bugs.kde.org/show_bug.cgi?id=337711 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #6 from Tony --- Still present on KDE Neon 5.7.2, Frameworks 5.24.0. I asked a question about this bug in the forum a couple of days ego. https://forum.kde.org/viewtopic.php?f=309&t=135028 "Locking Widgets" is a workaround of sorts to this one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359220] Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked
https://bugs.kde.org/show_bug.cgi?id=359220 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #4 from Tony --- I need to add that some widgets do not fallow the new behavior fully. Eg, for the analog clock, calculator widget you do need to long press to be able to move it from where you initially placed it. In the other hand the color picker, cpu load monitor widget, you can move it around without long press, although to resize them you need to. If there is a bug it would be a per widget bug the way i see it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343537] Resize plasmoid on desktop is extremely slow and not to correct size
https://bugs.kde.org/show_bug.cgi?id=343537 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #7 from Tony --- I get no slow downs while resizing in Plasma 5.7.2. Although some widgets (analog clock, trash) their width (x) size is proportional to their hight (y), which imo seems ok. Eg, i can place the calculator widget on the desktop and resize it by dragging the handle all the way to the right and the icon width (x) wont change. No numbers will be shown only the operations buttons. As soon as i increase (y) the numbers and extra buttons appear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351217] top panel auto-hide issue: hidden panel still occupies desktop space for some widget functions
https://bugs.kde.org/show_bug.cgi?id=351217 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #5 from Tony --- Experienced the same behavior on KDE Neon 5.7.2. This one is kind of annoying/tricky, if you lock the widgets this won't happen, but you also can't add/remove/resize/move them either since doing so affects the whole desktop not the panel. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366235] New: Crashed on usb-hdd failure.
https://bugs.kde.org/show_bug.cgi?id=366235 Bug ID: 366235 Summary: Crashed on usb-hdd failure. Product: dolphin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jodr...@live.com Application: dolphin (16.04.3) Qt Version: 5.7.0 Frameworks Version: 5.24.0 Operating System: Linux 4.4.0-31-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: I was opening a pretty big compress file (Bz2) ~1.5 GiB, and got and error stating the reading of the file did not reach the end of it. I noticed the other files on the same directory where missing as well as the disk on the devices list. Checked the power to the hdd and it was cut due to a loose connector, while fastenig it i got the crashed. - Unusual behavior I noticed: First a hang, then kwin sort of crashed as well, since the close/minimize buttons disappeared then the whole desktop crashed as well and restarted a moment later with the crash reporting assitant on the panel. This may related to bug 362841 -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7b6a10e8c0 (LWP 5539))] Thread 4 (Thread 0x7f7b44d32700 (LWP 5542)): #0 0x7f7b5ebc9ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7b5eb84939 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b5eb852cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b5eb854ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7b6482d30b in QEventDispatcherGlib::processEvents (this=0x7f7b48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7b647d7d9a in QEventLoop::exec (this=this@entry=0x7f7b44d31d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f7b645fd044 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f7b64601c28 in QThreadPrivate::start (arg=0xd2eae0) at thread/qthread_unix.cpp:344 #8 0x7f7b60cc26fa in start_thread (arg=0x7f7b44d32700) at pthread_create.c:333 #9 0x7f7b69b19b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f7b4f4c2700 (LWP 5541)): #0 0x7f7b69b099cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b5ebc8740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b5eb84e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b5eb85340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7b5eb854ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7b6482d30b in QEventDispatcherGlib::processEvents (this=0x7f7b480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7b647d7d9a in QEventLoop::exec (this=this@entry=0x7f7b4f4c1cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7f7b645fd044 in QThread::exec (this=this@entry=0x7f7b6a264d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #8 0x7f7b6a1f07a5 in QDBusConnectionManager::run (this=0x7f7b6a264d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #9 0x7f7b64601c28 in QThreadPrivate::start (arg=0x7f7b6a264d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #10 0x7f7b60cc26fa in start_thread (arg=0x7f7b4f4c2700) at pthread_create.c:333 #11 0x7f7b69b19b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f7b55692700 (LWP 5540)): #0 0x7f7b69b0de8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b5e2b4c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f7b5e2b68d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7b5825ea39 in QXcbEventReader::run (this=0xa49370) at qxcbconnection.cpp:1337 #4 0x7f7b64601c28 in QThreadPrivate::start (arg=0xa49370) at thread/qthread_unix.cpp:344 #5 0x7f7b60cc26fa in start_thread (arg=0x7f7b55692700) at pthread_create.c:333 #6 0x7f7b69b19b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7b6a10e8c0 (LWP 5539)): [KCrash Handler] #6 0x7f7b69a48418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f7b69a4a01a in __GI_abort () at abort.c:89 #8 0x7f7b645e8811 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1680 #9 QMessageLogger::fatal (this=this@entry=0x7ffc3c07f7e0, msg=msg@entry=0x7f7b6a24df80 "Cannot construct placeholder
[kio] [Bug 302705] ADD native EPUB thumbnail support
https://bugs.kde.org/show_bug.cgi?id=302705 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Related https://bugs.kde.org/show_bug.cgi?id=200017 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #25 from Tony --- Here's a work around Select a theme for sddm (in my case i only have the default "breeze"), hit clear image on the background selection button, then select your desire image afterward. Bear in mind this will only change sddm background, "K" animation that comes after it and the "lock screen" background need to be change separately. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368969] New: Crashed after changing look'n'feel
https://bugs.kde.org/show_bug.cgi?id=368969 Bug ID: 368969 Summary: Crashed after changing look'n'feel Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jodr...@live.com Application: dolphin (16.11.70) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: I had 1 instance of dolphin running, change look'n'feel from "Breeze Dark" to "Breeze", crash happen immediately after. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efc3946b8c0 (LWP 3815))] Thread 7 (Thread 0x7efc14bfa700 (LWP 3822)): #0 0x7efc38e55e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7efc2deb539c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efc2deb54ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efc33b4d23b in QEventDispatcherGlib::processEvents (this=0x7efc18c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7efc33af7cea in QEventLoop::exec (this=this@entry=0x7efc14bf9d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7efc3391cfb4 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7efc33921b98 in QThreadPrivate::start (arg=0x15f7e50) at thread/qthread_unix.cpp:344 #7 0x7efc2ffda6fa in start_thread (arg=0x7efc14bfa700) at pthread_create.c:333 #8 0x7efc38e61b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7efc18628700 (LWP 3821)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7efc22261aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7efc22261907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7efc2ffda6fa in start_thread (arg=0x7efc18628700) at pthread_create.c:333 #4 0x7efc38e61b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7efc18e29700 (LWP 3820)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7efc22261aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7efc22261907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7efc2ffda6fa in start_thread (arg=0x7efc18e29700) at pthread_create.c:333 #4 0x7efc38e61b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7efc1962a700 (LWP 3819)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7efc22261aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7efc22261907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7efc2ffda6fa in start_thread (arg=0x7efc1962a700) at pthread_create.c:333 #4 0x7efc38e61b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7efc20d12700 (LWP 3818)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7efc22261aa3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7efc22261907 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7efc2ffda6fa in start_thread (arg=0x7efc20d12700) at pthread_create.c:333 #4 0x7efc38e61b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7efc245b2700 (LWP 3817)): #0 0x7efc38e55e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7efc2deb539c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efc2deb54ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efc33b4d23b in QEventDispatcherGlib::processEvents (this=0x7efc1c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7efc33af7cea in QEventLoop::exec (this=this@entry=0x7efc245b1cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7efc3391cfb4 in QThread::exec (this=this@entry=0x7efc395c4d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7efc395507a5 in QDBusConnectionManager::run (this=0x7efc395c4d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #7 0x7efc33921b98 in QThreadPrivate::start (arg=0x7efc395c4d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #8 0x7efc2ffda6fa in start_thread (arg=0x7ef
[dolphin] [Bug 368969] Crashed after changing look'n'feel
https://bugs.kde.org/show_bug.cgi?id=368969 --- Comment #1 from Tony --- Forgot to mention, this happens on virtualbox vm + wayland session. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369126] New: Ark does not fallow "apply to all" check box.
https://bugs.kde.org/show_bug.cgi?id=369126 Bug ID: 369126 Summary: Ark does not fallow "apply to all" check box. Product: ark Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: jodr...@live.com CC: rak...@freebsd.org, rthoms...@gmail.com While extracting 2 or more compressed files (rar in this case) with a common file in each of the compressed ones, in the same folder, ark will not fallow/forced "apply to all" option when it encounters the "common" file already decompressed on the same folder. It does not matter if i picked "skip" or "overwrite", ark is not "applying to all" in neither case. I did not try to do the same from the command line. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369127] New: Wayland hangs my pc.
https://bugs.kde.org/show_bug.cgi?id=369127 Bug ID: 369127 Summary: Wayland hangs my pc. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: bhus...@gmail.com, plasma-b...@kde.org Under a wayland session i tried to check out if this https://bugs.kde.org/show_bug.cgi?id=367612 has been resolved... To my surprise is worst on wayland, it hangs my pc, have to hard reset it. I am not sure if it because i am using Nvidia(nouveau gtx 760), but wayland session its just too dam "unstable" right now. Reproducible: Always Steps to Reproduce: 1.Login to a wayland session. 2.Do the steps described on bug 367612 3.See your PC hang. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 369136] New: Krunner better plugin help/documentation.
https://bugs.kde.org/show_bug.cgi?id=369136 Bug ID: 369136 Summary: Krunner better plugin help/documentation. Product: krunner Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: jodr...@live.com Some of the krunner plugins don't have a "help" or "configuration" button showing how to use/configure them. Ex: the "Dictionary" plugin lets you "define" the keyword need it to run it, the web shortcuts can be change on system settings BUT the spell checker, although it can be configure in system settings, does not show how to use the krunner plugin or the unit converter which can't be configure on system settings and does not have a "help" button either. The lack of this may lead users (like me) to believe they do not work, are broken or something alike due to the lack of this information. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 369136] Krunner please add better plugin help/documentation button.
https://bugs.kde.org/show_bug.cgi?id=369136 Tony changed: What|Removed |Added Summary|Krunner better plugin |Krunner please add better |help/documentation. |plugin help/documentation ||button. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368969] Crashed after changing look'n'feel
https://bugs.kde.org/show_bug.cgi?id=368969 --- Comment #6 from Tony --- Created attachment 101205 --> https://bugs.kde.org/attachment.cgi?id=101205&action=edit System-settings crash on wayland 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368969] Crashed after changing look'n'feel
https://bugs.kde.org/show_bug.cgi?id=368969 --- Comment #7 from Tony --- Had another crashed today, on my main Neon install (not a vm), as soon as i clicked "Gnome application style". System setting does not have a reporting link added I attached the backtrace of this one, hope it helps clear things out. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369144] New: Partitionmanager lack of privilege under wayland.
https://bugs.kde.org/show_bug.cgi?id=369144 Bug ID: 369144 Summary: Partitionmanager lack of privilege under wayland. Product: partitionmanager Version: 2.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: jodr...@live.com When i run it i get the window asking for "root" password, but as soon as i typed it and hit OK i get another window saying i don't have "administrative privileges". On the "run as root" window this is the command being run: "partitionmanager --dontsu" Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 369144] Partitionmanager lack of privilege under wayland.
https://bugs.kde.org/show_bug.cgi?id=369144 --- Comment #1 from Tony --- I found this: http://gparted-forum.surf4.info/viewtopic.php?id=17446 Although the 2nd workaround works, it seems is not a KDE exclusive problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368989] Alt+F4 shortcut works only with XWayland windows
https://bugs.kde.org/show_bug.cgi?id=368989 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Yep can confirm this one. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 359883] Dolphin crash when I try to delete a folder (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=359883 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- .Also confirming it happens on my install of Neon :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows
https://bugs.kde.org/show_bug.cgi?id=368891 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #8 from Tony --- Similar Bug 367612 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369210] New: Wayland, changing compositor options gets me a "black screen"
https://bugs.kde.org/show_bug.cgi?id=369210 Bug ID: 369210 Summary: Wayland, changing compositor options gets me a "black screen" Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: jodr...@live.com Any change made to the backend, scaling or animation speed under wayland will get you a black/no output screen as soon as you hit the apply button. I can still switch to another vt to terminate the session, after login in again i noticed the previous changes that caused the "crash" where applied. This may be related to this one Bug 365471. Reproducible: Always Steps to Reproduce: 1.Log in to a wayland session 2.Go to system setting>display and monitor>compositor 3.Make any change and hit apply. Actual Results: The screen goes black with no output, as stated by my monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369214] New: Keyboard "Lock" keys (Caps/Num/Scroll) leds not turning on.
https://bugs.kde.org/show_bug.cgi?id=369214 Bug ID: 369214 Summary: Keyboard "Lock" keys (Caps/Num/Scroll) leds not turning on. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: jodr...@live.com On wayland the leds for "Lock" keys (Caps/Num/Scroll) are always off. In the case of Num Lock, the option to turn it on on plasma startup is not being honored either. I have one of the "supported" keyboards DELL SK-8135, and none of this happens on X. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)
https://bugs.kde.org/show_bug.cgi?id=348414 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #46 from Tony --- I believe i get this one (or similar) on opensuse tumbleweed with Frameworks version 5.26. See my attached bactrace please. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)
https://bugs.kde.org/show_bug.cgi?id=348414 --- Comment #47 from Tony --- Created attachment 101265 --> https://bugs.kde.org/attachment.cgi?id=101265&action=edit Tony_systemsettings5_crash-backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369332] New: Plasmashell crashed while configuring "Digital Clock"
https://bugs.kde.org/show_bug.cgi?id=369332 Bug ID: 369332 Summary: Plasmashell crashed while configuring "Digital Clock" Product: plasmashell Version: 5.7.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.4) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was editing the "Digital Clock" settings due to an issue with it, (it was gone) had to tick "Show local time zone" for it to appear again. The crash happen after a reboot and i wanted to untick "Show local time zone" so "UTC" is not shown in it, as i did that plasma crashed. After plasma came back, i tried again, "UTC" is shown no matter if i tick or untick "Show local time zone". The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85806c18c0 (LWP 1279))] Thread 26 (Thread 0x7f83121cf700 (LWP 25932)): #0 0x7f8579c786ed in poll () from /lib64/libc.so.6 #1 0x7f8576295876 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f857629598c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f857a5a8aab in QEventDispatcherGlib::processEvents (this=0x7f82f0011400, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f857a5506fa in QEventLoop::exec (this=this@entry=0x7f83121ced00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f857a3763c3 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f857a37b2e8 in QThreadPrivate::start (arg=0x449a2f0) at thread/qthread_unix.cpp:341 #7 0x7f857946f454 in start_thread () from /lib64/libpthread.so.0 #8 0x7f8579c813ff in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f830d6e7700 (LWP 25928)): #0 0x7f8579c7475d in read () from /lib64/libc.so.6 #1 0x7f85762d9ae0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8576295325 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8576295814 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f857629598c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f857a5a8aab in QEventDispatcherGlib::processEvents (this=0x7f82e40017e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #6 0x7f857a5506fa in QEventLoop::exec (this=this@entry=0x7f830d6e6ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f857a3763c3 in QThread::exec (this=) at thread/qthread.cpp:500 #8 0x7f857d754095 in ?? () from /usr/lib64/libQt5Qml.so.5 #9 0x7f857a37b2e8 in QThreadPrivate::start (arg=0x5237100) at thread/qthread_unix.cpp:341 #10 0x7f857946f454 in start_thread () from /lib64/libpthread.so.0 #11 0x7f8579c813ff in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f847dffb700 (LWP 25670)): #0 0x7f857947510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f857a37c19b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5060180) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4c2f3a0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f84bdd83e90 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f84bdd88048 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f84bdd8300d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f84bdd880a2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f84bdd8300d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f84bdd85ed9 in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f857a37b2e8 in QThreadPrivate::start (arg=0x7f846c002f90) at thread/qthread_unix.cpp:341 #10 0x7f857946f454 in start_thread () from /lib64/libpthread.so.0 #11 0x7f8579c813ff in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f847e7fc700 (LWP 25669)): #0 0x7f857947510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f857a37c19b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5060180) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4c2f3a0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f84bdd83e90 in ThreadWeaver::Weaver::takeFirstAva
[plasmashell] [Bug 369386] New: [Wayland] Panel "Auto-hide" option does not work.
https://bugs.kde.org/show_bug.cgi?id=369386 Bug ID: 369386 Summary: [Wayland] Panel "Auto-hide" option does not work. Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jodr...@live.com As the title says. I've tried adding a empty panel set the it to auto-hide, logout and in, rebooted, not working. It works OK on X. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 --- Comment #6 from Tony --- This one is fixed on Neon, for X and Wayland session. I can fill all corners of the dekstop with "empty" and "default" panels with no crashes. Plasma 5.8.90 Frameworks 5.27 Qt 5.7 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 369355] Touchpad configuration applet crashes
https://bugs.kde.org/show_bug.cgi?id=369355 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #2 from Tony --- I can confirm this happens on wayland, X is ok. In my case system settings dies silently with no errors. Worst i saw was on a virtual box vm where it hang the desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 369319] Black screen in Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=369319 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- I have a gtx 760 i've tried "nouveau.noaccel=1" due to "hangs" i was getting on wayland as well, the black screen happens due it. Don't boot with it. Sadly i dont know a "workaround", in my case i just don't dare to click on anything on the "panel" when i am on wayland else my pc hangs. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- I used to have a similar issue (before i ditch it and went full terminal...) and it was related to muon building a search index. Let it do its think, close and open it again, that's what worked for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)
https://bugs.kde.org/show_bug.cgi?id=348414 --- Comment #49 from Tony --- (In reply to Albert Astals Cid from comment #48) > (In reply to Tony from comment #46) > > I believe i get this one (or similar) on opensuse tumbleweed with Frameworks > > version 5.26. > > > > See my attached bactrace please. > > Tony, which app is that? Can you reproduce the crash easily? Sadly no, i messed up that system (i tinker too much). But the crash happen when i was changing font options in system settings, enabling anti-aliasing to be exact. I posted the bug here fallowing the suggestions of the bug reporting tool. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364746] Crash when accessing 'Font Management' inside Fonts section of 'Settings'
https://bugs.kde.org/show_bug.cgi?id=364746 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Can confirm this happens on Neon on wayland as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342816] kcmshell5 kwindecoration drag to reposition buttons is broken
https://bugs.kde.org/show_bug.cgi?id=342816 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #7 from Tony --- Working fine on Neon. Plasma 5.8.90, Frameworks 5.27 and Qt 5.7, although i must say that moving icons on the title bar is a bit "tricky". As for the "Defaults" button, i can confirm is not working, it does nothing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369568] Dolphin causes temporary freeze !
https://bugs.kde.org/show_bug.cgi?id=369568 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Can confirm this one on Neon, it only happens while moving files the panel and everything in it will "hang" until the notification of the moving process pops. Doing the same from a terminal within dolphin does not cause the issue. Changing task managers does not help as well as tuning off compositor. "Size" apparently is not a factor, but the amount of files is. I moved 10 pdfs ~500MiB and the hang was brief, almost not noticeable. Then i tried with 30 mp3 files ~ 200MiB, the panel hang hard until the notification showed up. I my case i don't have a SSD drive. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 369421] Kde Menu Editor crash while clicking a folder
https://bugs.kde.org/show_bug.cgi?id=369421 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- I have this one a while back, (on Neon stable) installed the "dbg" in order to report it tried to reproduced it but haven't got it ever since. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367612] Plasma desktop "Configure Desktop" window and layout options problems.
https://bugs.kde.org/show_bug.cgi?id=367612 Tony changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358231] desktop locks up when moving files
https://bugs.kde.org/show_bug.cgi?id=358231 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #4 from Tony --- Similar/duplicate 369568 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 351796] kinfocenter crashes on exit after processing command line switch
https://bugs.kde.org/show_bug.cgi?id=351796 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Tony --- Still present on Neon, kinfocenter 5.80.90 -- You are receiving this mail because: You are watching all bug changes.
