[yakuake] [Bug 429478] New: Blue artefacts when scrolling console contents
https://bugs.kde.org/show_bug.cgi?id=429478 Bug ID: 429478 Summary: Blue artefacts when scrolling console contents Product: yakuake Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Created attachment 133545 --> https://bugs.kde.org/attachment.cgi?id=133545=edit Yakuake blue bar artedact SUMMARY When scrolling console contents, either via mouse wheel or as a result of console output, there appears a thin blue bar on the left of the console contents. The bar height is consistent with the amount of scrolling you perform. When the scrolling stops, after about 200 ms, this bar becomes darker, but still visible. STEPS TO REPRODUCE 1. Open Yakuake with an empty console with a command line prompt. 2. Press Enter for some time, so that many empty lines are created and the console can be scrolled. 3. Scroll the console up and down, by the mouse wheel, Shift+PageUp and Shift+PageDown or Shift+Arrow keys. OBSERVED RESULT As you are pressing Enter (when that results in scrolling the console contents down) or you are scrolling the console in step 3, there appears a blue bar, between the leftmost character on the console and the Yakuake window frame. When you stop scrolling, the blue bar turns darker, after a small delay. EXPECTED RESULT There should be no such artefact. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 Yakuake: 20.08.1 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-29-lowlatency OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4700HQ CPU @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 ADDITIONAL INFORMATION Global UI scaling is disabled (100%). This is a regression since Kubuntu 20.04 (Yakuake 19.12.3). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429014] Network Monitor update interval cannot be changed
https://bugs.kde.org/show_bug.cgi?id=429014 Lastique changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Lastique --- As replied in that bug, this is a standard widget that is shipped with KDE. It is not installed from elsewhere (it has no trash bin icon). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429017] Network Monitor settings Units tab has no icon
https://bugs.kde.org/show_bug.cgi?id=429017 --- Comment #3 from Lastique --- Created attachment 133286 --> https://bugs.kde.org/attachment.cgi?id=133286=edit Network Monitor widget in the Add Widgets menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429017] Network Monitor settings Units tab has no icon
https://bugs.kde.org/show_bug.cgi?id=429017 Lastique changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Lastique --- This is a standard widget that is shipped with KDE. It is not installed from elsewhere (it has no trash bin icon). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429017] New: Network Monitor settings Units tab has no icon
https://bugs.kde.org/show_bug.cgi?id=429017 Bug ID: 429017 Summary: Network Monitor settings Units tab has no icon Product: plasmashell Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 133261 --> https://bugs.kde.org/attachment.cgi?id=133261=edit Network Monitor settings window SUMMARY In the settings window of the Network Monitor widget, the Units tab has no icon. The other tabs do have icons. STEPS TO REPRODUCE 1. Add a Network Monitor widget to the panel. 2. Open its settings. OBSERVED RESULT The Units tab has no icon (see the screenshot). EXPECTED RESULT There should be an icon. A single tab without an icon looks odd. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-53-lowlatency OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429014] New: Network Monitor update interval cannot be changed
https://bugs.kde.org/show_bug.cgi?id=429014 Bug ID: 429014 Summary: Network Monitor update interval cannot be changed Product: plasmashell Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Update interval of the Network Monitor widget cannot be changed in the settings. STEPS TO REPRODUCE 1. Add a Network Monitor widget on the panel. 2. Go to the widget settings. 3. In the Interfaces tab, try changing the Update interval value. OBSERVED RESULT The value cannot be changed by using the spin arrows, it always stays at "0 seconds". If I type a different value on keyboard, it resets to "0 seconds". EXPECTED RESULT The value should be adjustable. And "0 seconds" should not be a valid value. I would suggest using millisecond units instead of seconds as well, so that sub-second intervals are allowed. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-53-lowlatency OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363816] Network monitor widget unreadable when placed on panel
https://bugs.kde.org/show_bug.cgi?id=363816 Lastique changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #10 from Lastique --- It does look better in my case (on a horizontal panel), as the widget is now much wider and the network interface does not overlap with the network readings. I did not test it on a vertical panel, as others have commented earlier. Thus I will keep the bug open for the other people to comment. As for me, the widget is taking too much space on the panel. I realize that this was probably what fixed the problem reported here, but as it is I probably won't be using the widget anyway. It would probably be more helpful if the widget offered a way to configure its appearance. For example, disable the network interface name, change the font size, make upload/download bitrates displayed on top of one another instead of horizontally. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-53-lowlatency OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 347756] Incorrect size of existing files on torrent update
https://bugs.kde.org/show_bug.cgi?id=347756 Lastique changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Lastique --- KTorrent 5.1.2 from Kubuntu 20.04 doesn't seem to display the size of the existing files at all. It displays the total size of the files in the torrent and shows the amount of space that will be left free after downloading, which is calculated without accounting that some of the files are already downloaded (i.e. the resulting number if not correct). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427628] New: Black window flashes after restarting compositing
https://bugs.kde.org/show_bug.cgi?id=427628 Bug ID: 427628 Summary: Black window flashes after restarting compositing Product: kwin Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Created attachment 132317 --> https://bugs.kde.org/attachment.cgi?id=132317=edit KWin config file (~/.config/kwinrc) SUMMARY After restarting compositing in KWin (for example, due to a Nvidia driver crash or via a hotkey or VT switch), contents of some windows begin flashing black upon certain activities. For example, when "Open/Save File" dialog window opens, Firefox window in the background momentarily turns black and then back to normal. This is not tied to any particular applications or GUI toolkits. I've seen black flashes with both GTK and Qt applications. This is also not reliably reproducible and may not show right away after restarting compositing. STEPS TO REPRODUCE 1. Restart KWin compositing. 2. Try interacting with desktop, like open or close windows, resize windows, etc. OBSERVED RESULT Some windows begin flashing black. EXPECTED RESULT No black flashing is expected. SOFTWARE/OS VERSIONS Linux: Kubuntu 20.04 x86_64, X11 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Nvidia driver: 455.26.1 (also reproducible with other versions) ADDITIONAL INFORMATION In my /etc/environment I have: KWIN_TRIPLE_BUFFER=1 KWIN_USE_BUFFER_AGE=0 KWIN_PERSISTENT_VBO=1 __GL_YIELD="USLEEP" __GL_SYNC_TO_VBLANK=1 KWin is started with the command line `__GL_THREADED_OPTIMIZATIONS=0 kwin_x11 "$@"`. The __GL_THREADED_OPTIMIZATIONS env variable has no effect on the issue, it is just used to reduce CPU consumption by kwin_x11. The usual workaround is to restart KWin by running `kwin_x11 --replace` from krunner. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen when using Plasma Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=389448 --- Comment #39 from Lastique --- Is the fix only enabled by PLASMA_USE_QT_SCALING=1? If so, why is it not the default? I would prefer that the bug stays open until it works as intended out of the box. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 421904] New: KTorrent does IO in the GUI thread
https://bugs.kde.org/show_bug.cgi?id=421904 Bug ID: 421904 Summary: KTorrent does IO in the GUI thread Product: ktorrent Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: andy...@mail.ru Target Milestone: --- SUMMARY Apparently, KTorrent performs file IO in the main GUI thread. This results in GUI becoming unresponsive at times when KTorrent performs heavy IO activity (e.g. when it downloads or seeds torrents at high bitrates). This is more prominently seen when the files are stored on rotational HDD. I'm experiencing multi-second GUI freezes at times. It would be better to use separate threads for file/network IO and GUI. Operating System: Kubuntu 20.04 KTorrent: 5.1.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-31-lowlatency OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421304] New: Plasma panel stops updating at some point
https://bugs.kde.org/show_bug.cgi?id=421304 Bug ID: 421304 Summary: Plasma panel stops updating at some point Product: plasmashell Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: andy...@mail.ru Target Milestone: 1.0 At some seemingly random points in time Plasma panel stops updating. The last drawn panel contents stay frozen until I interact with the panel - for example, right click on it or launch an application through an icon on the panel. At that point of interaction a single update is made and the panel freezes again. I can see that applets continue to function while the panel is frozen. E.g. CPU load monitor shows a graph with proper CPU load history when the panel is redrawn. I do not have any fixed steps to reproduce the problem. It just happens by itself, while the PC is idle or while it's doing some work. I don't log out or lock the screen or put the PC to sleep or hibernate or switch to a VT - the PC stays logged in, with Plasma desktop active for the whole time. I can "fix" the problem by killing and restarting plasmashell. After that the panel starts updating again. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-29-lowlatency OS Type: 64-bit Nvidia driver: 440.66.12 This did not happen in Kubuntu 19.10 with Plasma 5.16.5. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 421166] New: KRunner shortcuts duplicated as "Run Command"
https://bugs.kde.org/show_bug.cgi?id=421166 Bug ID: 421166 Summary: KRunner shortcuts duplicated as "Run Command" Product: krunner Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: andy...@mail.ru Target Milestone: --- SUMMARY In the KDE System Settings, KRunner hotkey shortcuts are duplicated in two categories: "KRunner" and "Run Command". The available actions and default key bindings are the same. However, the key bindings in the "Run Command" category do not work. STEPS TO REPRODUCE 1. Go to KDE System Settings -> Shortcuts -> Global Shortcuts. 2. In the Components column, see the two categories: "KRunner" and "Run Command". 3. Make sure a hotkey for a given action is bound in the "Run Command" category. For example, make "Run Command" -> "Run Command" is bound to Alt+F2. 4. Press Alt+F2. 5. Change Alt+F2 to be used in "KRunner" -> "KRunner" action (this will unbind it from "Run Command" -> "Run Command"). 6. Press Alt+F2 again. OBSERVED RESULT The available actions and default hotkeys in "KRunner" and "Run Command" are the same. At step 4, pressing Alt+F2 doesn't do anything. At step 6, pressing Alt+F2 does invoke KRunner, as expected. EXPECTED RESULT I don't see the reason for this duplication, especially when one of the shortcut categories doesn't work. There should be one place to configure KRunner shortcuts, and the shortcuts configured there should work. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420758] New: Clipboard and selection synchronization resets selection in GTK apps
https://bugs.kde.org/show_bug.cgi?id=420758 Bug ID: 420758 Summary: Clipboard and selection synchronization resets selection in GTK apps Product: plasmashell Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When Selection and Clipboard synchronization is enabled (i.e. the Ignore selection option is NOT enabled), text selection in GTK (or, possibly, PyGTK) application spuriously gets reset sometimes. STEPS TO REPRODUCE 1. In the Clipboard widget settings, General tab, make sure "Prevent empty clipboard" is enabled and "Ignore selection" is disabled. 2. Open a GTK application. I use Meld. In it, create a blank text file comparison or initiate comparison of two text files. I've also seen this problem in Sublime Text editor. 3. In the application, select a piece of text with mouse. Try multiple times, if needed. OBSERVED RESULT The selection gets reset sometimes. Possibly, this happens when the widget automatically copies the selection to the clipboard. EXPECTED RESULT The selection should stay. SOFTWARE/OS VERSIONS Linux: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION The workaround is to enable the "Ignore selection" option in the widget settings. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 420701] New: ksgrd_network_helper is consuming 100% CPU
https://bugs.kde.org/show_bug.cgi?id=420701 Bug ID: 420701 Summary: ksgrd_network_helper is consuming 100% CPU Product: ksysguard Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When System Monitor is running, the ksgrd_network_helper process is constantly consuming 100% of a single CPU core. STEPS TO REPRODUCE 1. Start System Monitor (KSysGuard) and watch ksgrd_network_helper CPU consumption. OBSERVED RESULT ksgrd_network_helper is constantly consuming 100% of a single CPU core. EXPECTED RESULT It should not hog CPU. SOFTWARE/OS VERSIONS Linux: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 420701] ksgrd_network_helper is consuming 100% CPU
https://bugs.kde.org/show_bug.cgi?id=420701 Lastique changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use
https://bugs.kde.org/show_bug.cgi?id=328987 --- Comment #27 from Lastique --- As a personal workaround I'm using the lightsOn.sh script written by someone. Here is my fork with some improvements: https://github.com/lastique/lightson It works on X11 system and blocks powersaving if there are any fullscreen windows. It works for fullscreen video players in browsers and games. I know that KWin is not involved in DPMS, but I wonder if it would be possible to implement that kind of rule in it. Or more generally - block DPMS if there is a window matching some criteria set by user, with "fullscreen" being one example. As a bonus, it could work in Wayland as well (I'm not sure if lightsOn.sh is even possible to implement on Wayland). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use
https://bugs.kde.org/show_bug.cgi?id=328987 --- Comment #26 from Lastique --- (In reply to Kai Uwe Broulik from comment #25) > Most modern games actually do. No, I wouldn't say so. You can see it happen even on Windows if you leave a game running with no user input - the display turns off after a while. But on Windows games don't have to do anything about it as gamepad input cancels powersaving on that OS. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 418743] Package download progress bar jumps from 0% to 100% with no intermediate values
https://bugs.kde.org/show_bug.cgi?id=418743 --- Comment #1 from Lastique --- I can add that the progress bar updates if the window with the list of packages being downloaded needs to be redrawn. For example, when I hover mouse over the line with the package being downloaded or switch focus to another window and back. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 418743] New: Package download progress bar jumps from 0% to 100% with no intermediate values
https://bugs.kde.org/show_bug.cgi?id=418743 Bug ID: 418743 Summary: Package download progress bar jumps from 0% to 100% with no intermediate values Product: muon Version: 5.8.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: andy...@mail.ru CC: silh...@gmail.com Target Milestone: --- SUMMARY Package download progress bar does not display the actual progress and instead hangs at 0% for the duration of package download and jumps to 100% when download is complete. STEPS TO REPRODUCE 1. Mark a package for installation or upgrade. Preferably a large one, that would take time to download. For example, firefox-dbg (>400 MiB). 2. Click Apply Changes and watch the download progress bar against the package name. OBSERVED RESULT The progress bar hangs at 0% for the duration of the download (you can monitor the download by external tools for network activity monitoring), then jumps to 100% and the process continues to the next package or package installation. EXPECTED RESULT The progress bar should reflect the actual downloading progress. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 417806] Open/Save File dialogs do not adhere to current directory modification
https://bugs.kde.org/show_bug.cgi?id=417806 --- Comment #2 from Lastique --- (In reply to Ahmad Samir from comment #1) > Well, if you type a path and don't press Enter then for all intents and > purposes you're still in the same dir... Yes, and that is a problem. As I described in the bug description, the effect of pressing Enter is ambiguous. Therefore I'm asking to update the directory on focus loss. > You could type the path in the Name: box /path/to/wherever/file.txt and > it'll save the file there. Right, that's my current workaround. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 418449] New: KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=418449 Bug ID: 418449 Summary: KSysGuard crashed on close Product: ksysguard Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-40-lowlatency x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: KSysGuard crashed when I closed its window. The crash is not 100% reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc32424ef00 (LWP 15815))] Thread 4 (Thread 0x7fc31b7fe700 (LWP 15822)): #0 0x7fc32de48c3d in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc32ddfc940 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc32ddfcb73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc336099653 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc3360405cb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc335e79a45 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc3363c7efa in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fc335e7ac92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc32e658669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fc337a4c323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc31bfff700 (LWP 15821)): #0 0x7fc32e65f6e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7fc31bffe600, clockid=, expected=0, futex_word=0x7fc314000d2c) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7fc32e65f6e0 in __pthread_cond_wait_common (abstime=0x7fc31bffe600, clockid=, mutex=0x560286b2ea38, cond=0x7fc314000d00) at pthread_cond_wait.c:520 #2 0x7fc32e65f6e0 in __pthread_cond_timedwait (cond=0x7fc314000d00, mutex=0x560286b2ea38, abstime=0x7fc31bffe600) at pthread_cond_wait.c:656 #3 0x7fc321446794 in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.64 #4 0x7fc3211a444c in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.64 #5 0x7fc32144596c in () at /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.64 #6 0x7fc32e658669 in start_thread (arg=) at pthread_create.c:479 #7 0x7fc337a4c323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc323634700 (LWP 15819)): #0 0x7fc337a3fc2f in __GI___poll (fds=0x7fc3236335a8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc32e6bb917 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc32e6bd53a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc323b6f288 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fc335e7ac92 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc32e658669 in start_thread (arg=) at pthread_create.c:479 #6 0x7fc337a4c323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fc32424ef00 (LWP 15815)): [KCrash Handler] #6 0x7fc335efd6dd in operator==(QString const&, QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc336cd833b in QLabel::setText(QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fc337b92223 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_ksysguard.so #9 0x7fc3377bc378 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #10 0x7fc3377c3802 in () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #11 0x7fc33606d558 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fc335fbd49e in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fc335fc3ba9 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fc335fc3f12 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fc33606d3f8 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fc33607a0c5 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fc33607a421 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fc336b9ca86 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
[frameworks-kio] [Bug 417806] New: Open/Save File dialogs do not adhere to current directory modification
https://bugs.kde.org/show_bug.cgi?id=417806 Bug ID: 417806 Summary: Open/Save File dialogs do not adhere to current directory modification Product: frameworks-kio Version: 5.62.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: andy...@mail.ru CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY The Open/Save File dialogs do not notice the current directory field modification by user and open/save the file to the original current directory. STEPS TO REPRODUCE 1. Run an application that will use the common Save File dialog. For example, Kate. 2. Invoke the Save File dialog. E.g. File -> Save As in Kate. 3. In the Save File dialog, click on the current directory input field at the top and modify it by typing a new path. 4. Click on the file name input field and type the file name. 5. Click on the Save button. OBSERVED RESULT The new file is created at the original current directory, not the one I typed at step 3. EXPECTED RESULT The Save File dialog should use the directory I typed. Preferably, when the input field focus is lost, the dialog should update the directory view to the directory I typed, so that the path and the directory view are in sync. STEPS TO REPRODUCE 1. Run an application that will use the common Open File dialog. For example, Kate. 2. Invoke the Open File dialog. E.g. File -> Open in Kate. 3. In the Open File dialog, click on the current directory input field at the top and modify it by typing a new path. 4. Click on the file name input field or the directory view. 5. Click on the file name input field and type the file name. 6. Click on the Open button. OBSERVED RESULT At step 4, the directory view keeps showing the original current directory contents, the dialog does not seem to register that the current directory was updated. At step 6, the file is opened at the original current directory (provided that the file exists at that location), not at the modified one. EXPECTED RESULT Same as with the Save File dialog. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.10 x86_64 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION: The current directory is updated if while typing the new path the user selects one of the suggested auto-completion options and presses Enter. However, that does not solve the problem because auto-completion does not appear in all cases (e.g. not when you paste the path from clipboard or when you switch to another window temporarily). Also, the user is reluctant to press Enter in a dialog as, depending on the current focus, pressing Enter could immediately confirm the whole file open/save operation. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #185 from Lastique --- I know nothing about how the code works, but doesn't incrementing height have the potential to corrupt the surrounding previously rendered content when the increment is not needed? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 417080] New: Add support for huge pages
https://bugs.kde.org/show_bug.cgi?id=417080 Bug ID: 417080 Summary: Add support for huge pages Product: ksysguard Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Created attachment 125634 --> https://bugs.kde.org/attachment.cgi?id=125634=edit Example of a /proc//status file with huge pages Currently, the Memory column for a process in KSysGuard does not include memory allocated in anonymous huge pages. There seems to be no way to see how much RAM, including huge pages, the process is using. Note that Virtual Size does not work as it includes all mapped address space of the process, not necessarily the amount of RAM used. Since huge pages cannot be swapped out to a page file (as of the time of this writing and to my knowledge), it seems reasonable to include them into the Memory column value. If not, at least a separate column would be useful. For an example, I'm attaching /proc//status of an ffmpeg process, which uses huge pages for most of its allocations (through a custom memory allocator). For this process, KSysGuard shows 64300 K in its Memory column, while there is actually 1606 MiB more allocated in huge pages. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 401904] Volume feedback gets enabled by itself sometimes
https://bugs.kde.org/show_bug.cgi?id=401904 Lastique changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Lastique --- I will not be able to test until the new plasma is released in Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #158 from Lastique --- (In reply to Arthur Peters from comment #157) > > Locale affects parsing as well as printing, so in the, say, de_DE locale a > ',' may well parse as a decimal separator instead of a "thousands" > separator. This is true of most European locales I think. So the original > poster of the config was probably correct for their own machine, but for > yours you might need to use a '.' (if you are in en_US for instance). Locale-dependent config files are probably not a good idea. If the user changes his locale settings, suddenly all config files become invalid. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 411936] After upgrade to PulseAudio 13, Plasma changes the default output device to HDMI port after every login and after I wake up my monitor connected to HDMI port from power save m
https://bugs.kde.org/show_bug.cgi?id=411936 --- Comment #8 from Lastique --- I think I found the issue that I'm seeing: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749 The workaround of disabling module-switch-on-connect in /etc/pulse/default.pa helps in my case. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 411936] After upgrade to PulseAudio 13, Plasma changes the default output device to HDMI port after every login and after I wake up my monitor connected to HDMI port from power save m
https://bugs.kde.org/show_bug.cgi?id=411936 Lastique changed: What|Removed |Added CC||andy...@mail.ru --- Comment #6 from Lastique --- This happens to me on Kubuntu 19.10. PulseAudio 13.0, Plasma 5.16.5. Even with the start-pulseaudio-x11 script fixed as I suggested in https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/162#note_276465 the default output device in Audio Volume applet is the HDMI output (the first one of the multiple output devices). The default output device gets reset to HDMI after every reboot. Please, reopen. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 363852] Ktorrent no longer starts hidden in tray
https://bugs.kde.org/show_bug.cgi?id=363852 --- Comment #10 from Lastique --- Oh, and Size & Position is also applied when Ktorrent gets restored from the tray icon, which means it always gets restored minimized. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 363852] Ktorrent no longer starts hidden in tray
https://bugs.kde.org/show_bug.cgi?id=363852 --- Comment #9 from Lastique --- (In reply to kikox1 from comment #8) > I found an workarround > > In application settings for it (in Window Rules) (click right buttom in > title bar of ktorrent) > > Size & Position: minimized - apply initially > Arrangement & Access: skip taskbar - apply initially This doesn't work as intended. After these steps Ktorrent never appears in the taskbar, neither after start, nor after minimizing and restoring. Size & Position workaround has the tendency to affect other Ktorrent windows beside the main window. For example, the dialog for adding a new torrent gets created minimized. You have to create a very specific rule to match just the main window (in my case, I have to match the window title, and I'm not sure how stable the title is). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 410542] Add "Lock and suspend" option on lid close
https://bugs.kde.org/show_bug.cgi?id=410542 --- Comment #2 from Lastique --- Thanks, I found it. Still, looking for the option in the Desktop Behavior section is kind of non-obvious. Is it possible to make that option accessible from the Energy Saving as well? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 410542] New: Add "Lock and suspend" option on lid close
https://bugs.kde.org/show_bug.cgi?id=410542 Bug ID: 410542 Summary: Add "Lock and suspend" option on lid close Product: Powerdevil Version: 5.15.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andy...@mail.ru Target Milestone: --- SUMMARY I'd like to be able to configure KDE Energy Saving (in System Settings, Power Management) so that when laptop lid is closed, the screen would lock and the laptop would go into suspend mode. The intention is that when the lid is opened, the laptop wakes up in the locked mode. Currently, there are two separate options in the Energy Saving: either lock the screen (in which case the laptop remains active) or suspend (in which case it wakes up unlocked). My current workaround is to lock the screen manually before closing the lid, but it is too easy to forget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 x86_64 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 409048] New: System Monitor crashed on close
https://bugs.kde.org/show_bug.cgi?id=409048 Bug ID: 409048 Summary: System Monitor crashed on close Product: ksysguard Version: 5.15.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Created attachment 121080 --> https://bugs.kde.org/attachment.cgi?id=121080=edit Crash backtrace SUMMARY KDE System Monitor crashed when I closed the application. STEPS TO REPRODUCE I don't have a set of steps to reproduce. It just happened once, most of the time it doesn't crash. Before closing, I used System Monitor to browse the processes in the process list and sent SIGSTOP to one of the processes. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Nvidia driver: 430.26 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408048] Selection by words is sticky in Midnight Commander
https://bugs.kde.org/show_bug.cgi?id=408048 --- Comment #2 from Lastique --- Technically, this is reproducible in both mc and mcedit (i.e. the file manager itself and the editor). I can't reproduce it in bare console or nano. I suspect this might be related to the fact that those don't handle mouse events and I don't have to hold Shift while selecting text. I can reproduce it with htop, which does handle mouse events. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #92 from Lastique --- Could it be that the bug is masked with --notransparency by the black window background? (In reply to Nate Graham from comment #90) > Looks like that issue is tracked by Bug 406770. Note that on my screenshot vertical and horizontal dashes are garbled. I don't see that in Bug 406770. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #87 from Lastique --- This is on Kubuntu 19.04. Konsole: 18.12.3 KDE Plasma: 5.15.4 KDE Frameworks: 5.56.0 Qt: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408048] New: Selection by words is sticky in Midnight Commander
https://bugs.kde.org/show_bug.cgi?id=408048 Bug ID: 408048 Summary: Selection by words is sticky in Midnight Commander Product: konsole Version: 18.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: andy...@mail.ru Target Milestone: --- SUMMARY Somewhere between Konsole 18.04.3 in Kubuntu 18.10 and 18.12.3 in Kubuntu 19.04, selecting text with mouse in Midnight Commander running in Konsole or Yakuake became sticky. This is super annoying. STEPS TO REPRODUCE 1. Start Konsole, run "mc". 2. In Midnight Commander, open a text file and start typing. 3. Select a piece of text by pressing Shift, Left mouse button and moving the mouse. Notice that selection is adjusted by character, you can start and end selection in the middle of a word. 4. Select a word in the text by pressing Shift and double-clicking Left mouse button on the word. The whole word is selected. 5. Try again to select a piece of text, like in step 3. OBSERVED RESULT In step 5, moving the mouse selects text by words, not by characters. You can try starting the selection multiple times, every time it will select text by words. It is not possible to restore the original behavior of selection by characters, except by Left clicking somewhere in the text. EXPECTED RESULT 1. Shift + Left click should always start selection by character. 2. Shift + Double left click should always start selection by words. The two rules should be true no matter what kind of selection had been done before. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #85 from Lastique --- Created attachment 120365 --> https://bugs.kde.org/attachment.cgi?id=120365=edit Konsole with Midnight Commander correct For reference, this is how it should look. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #84 from Lastique --- Created attachment 120364 --> https://bugs.kde.org/attachment.cgi?id=120364=edit Konsole with Midnight Commander garbled In my case, --notransparency helps with raw console output, but running e.g. Midnight Commander shows somewhat garbled output with some rows and columns around characters undrawn. See the attached screenshot, it is with scaling factor 1.7. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 408045] "Bit edit" checkboxes have uneven borders when desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=408045 --- Comment #1 from Lastique --- Created attachment 120363 --> https://bugs.kde.org/attachment.cgi?id=120363=edit KCalc with uneven Bit Edit checkbox borders -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 408045] New: "Bit edit" checkboxes have uneven borders when desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=408045 Bug ID: 408045 Summary: "Bit edit" checkboxes have uneven borders when desktop scaling is enabled Product: kcalc Version: 18.12 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: andy...@mail.ru Target Milestone: --- SUMMARY When desktop scaling is enabled, "Bit edit" checkboxes have uneven border widths. See attached screenshot. STEPS TO REPRODUCE 1. Go to KDE System Settings -> Display and Monitor -> Scale Display. 2. Select scale factor greater than 1.0. I used 1.7. 3. Reboot. 4. Launch KCalc. Make sure it is in Numerical System Mode and Show Bit Edit is enabled. OBSERVED RESULT Bit edit checkboxes have borders of uneven width, as if scaled using nearest neighbour filter. EXPECTED RESULT The checkboxes should be drawn according to the scaling factor, not scaled post-drawing. This would result in a more uniform look of the checkboxes. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 KCalc: 18.12.3 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 388217] Yakuake height incorrect if desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=388217 --- Comment #6 from Lastique --- While that works as a workaround, it keeps Yakuake UI elements unscaled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407024] Panel texture flickering
https://bugs.kde.org/show_bug.cgi?id=407024 --- Comment #2 from Lastique --- I think, I found a workaround. In xorg.conf, for the Intel iGPU, I've added this option: Option "DRI" "3" In my case, I have Intel iGPU section in a separate file /etc/X11/xorg.conf.d/20-intel.conf, which now looks like this: Section "Device" Identifier "card0" Driver "intel" Option "Backlight" "intel_backlight" Option "DRI" "3" BusID "PCI:0:2:0" EndSection -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407024] Panel texture flickering
https://bugs.kde.org/show_bug.cgi?id=407024 --- Comment #1 from Lastique --- Created attachment 120326 --> https://bugs.kde.org/attachment.cgi?id=120326=edit Screencast showing the problem I've recorded a video showing the problem. The problem reproduces with different plasma themes: Breeze, Breeze Light, Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407024] New: Panel texture flickering
https://bugs.kde.org/show_bug.cgi?id=407024 Bug ID: 407024 Summary: Panel texture flickering Product: plasmashell Version: 5.15.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I noticed texture flickering in a few cases. STEPS TO REPRODUCE Scenario 1. 1. Create a horizontal panel with a few application icons. 2. Move the mouse over the icons on the panel. Try moving fast enough so that tooltips with the icon name don't appear. Scenario 2. 1. Invoke logout/reboot/shutdown effect. OBSERVED RESULT Scenario 1. The panel texture is flickering. I can see its opacity vary, as well as contents jitter during the flickering. Scenario 2. The screen dimming effect of the logout/reboot/shutdown animation has flickering opacity. After the animation completion, sometimes the effect darkens the desktop contents more than usual, and then after a fraction of a second (or maybe after I move the mouse) opacity gets restored to usual (which looks like desktop contents become less darkened). While the animation is in progress, the logout/reboot/shutdown icons flicker. EXPECTED RESULT No flickering should happen. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Mesa: 19.0.2 X.org: 1.20.4 ADDITIONAL INFORMATION I'm seeing this on a laptop with Intel Haswell iGPU (i915 driver). I've also seen the problem with logout/reboot/shutdown effect on a different machine, also with Kubuntu 19.04, but with Nvidia GPU (430.09 driver). Not the panel flickering, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406983] Thermal monitor list of sensors does not resize vertically
https://bugs.kde.org/show_bug.cgi?id=406983 Lastique changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Lastique --- The Thermal monitor widget is not a built-in part of Plasma, it was probably installed from https://store.kde.org/p/998915. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406982] Thermal monitor does not show lm-sensor readings
https://bugs.kde.org/show_bug.cgi?id=406982 Lastique changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Lastique --- The name is "Thermal Monitor", and apparently it's not a built-in widget of Plasma and it was installed from elsewhere, probably from here: https://store.kde.org/p/998915. Sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406982] Thermal monitor does not show lm-sensor readings
https://bugs.kde.org/show_bug.cgi?id=406982 Lastique changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406983] Thermal monitor list of sensors does not resize vertically
https://bugs.kde.org/show_bug.cgi?id=406983 Lastique changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406983] New: Thermal monitor list of sensors does not resize vertically
https://bugs.kde.org/show_bug.cgi?id=406983 Bug ID: 406983 Summary: Thermal monitor list of sensors does not resize vertically Product: plasmashell Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 119678 --> https://bugs.kde.org/attachment.cgi?id=119678=edit Thermal monitor settings window SUMMARY The list of sensors in the Thermal monitor widget options only shows two entries. It does not resize vertically, even when the options window is resized. STEPS TO REPRODUCE 1. Open Thermal monitor settings. 2. Try resizing the settings window or the list of sensors. OBSERVED RESULT The list is showing only 2 lines and cannot be resized vertically. EXPECTED RESULT The list should be resizable and display more entries by default (as long as they fit in the settings window). SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406982] New: Thermal monitor does not show lm-sensor readings
https://bugs.kde.org/show_bug.cgi?id=406982 Bug ID: 406982 Summary: Thermal monitor does not show lm-sensor readings Product: plasmashell Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After reboot, lm-sensor readings, such as CPU temperatures, are displayed as OFF. At the same time, the "sensors" command displays temperatures as expected. STEPS TO REPRODUCE 1. Add Thermal Monitor widget on the horizontal panel. 2. In the widget options, add lm-sensor sources, lmsensors/coretemp-isa-/Package_id_0, lmsensors/coretemp-isa-/Core_0, etc. 3. Reboot. OBSERVED RESULT After reboot, the added sensors are displayed as OFF. The "sensors" command show expected temperatures. Sometimes, if I open the widget options, change one of the sensors to something else, then change back, and click Apply, the sensors start displaying valid readings. EXPECTED RESULT Sensor readings should be displayed correctly. SOFTWARE/OS VERSIONS Linux/: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406980] New: Panel widget options are inaccessible
https://bugs.kde.org/show_bug.cgi?id=406980 Bug ID: 406980 Summary: Panel widget options are inaccessible Product: plasmashell Version: 5.15.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Accessing options of widgets on the panel is virtually impossible as Plasma closes the options menu when mouse moves away from the widget. STEPS TO REPRODUCE 1. Unlock desktop widgets. 2. Make sure you have widgets on the panel. In my case, the panel is horizontal, and the widget is an icon. 3. On the panel, click on the sliders icon on the right. This will open the panel options allowing to adjust the panel width, etc. 4. Move the mouse over the icon widget. An option window appears, showing the icon name, "Configure" and "Remove" options. 5. Start moving the mouse towards the "Configure" and "Remove" options. OBSERVED RESULT The menu disappears as soon as the mouse is moved away from the icon, even if the mouse is over the menu. EXPECTED RESULT The menu should not disappear, it should stay open as long as the mouse is over the widget or the menu. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 402077] SaveFile does not set the current_name
https://bugs.kde.org/show_bug.cgi?id=402077 Lastique changed: What|Removed |Added CC||andy...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392286] Display turns on twice after going into powersaving mode
https://bugs.kde.org/show_bug.cgi?id=392286 Lastique changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Lastique --- The problem has been resolved in Nvidia driver 415.x, which introduced the new xorg.conf option "HardDPMS". With this option set to true, the driver will disable the display with modeset instead of one of the powersaving modes, which solves the problem for me. https://download.nvidia.com/XFree86/Linux-x86_64/415.18/README/xconfigoptions.html#HardDPMS -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 401904] New: Volume feedback gets enabled by itself sometimes
https://bugs.kde.org/show_bug.cgi?id=401904 Bug ID: 401904 Summary: Volume feedback gets enabled by itself sometimes Product: plasma-pa Version: 5.13.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: --- SUMMARY For some reason, the "Volume feedback" option gets enabled sometimes for no apparent reason. I think, it happens on reboot, and not on every reboot but only sometimes. I don't know what triggers the problem. SOFTWARE/OS VERSIONS Kubuntu 18.10 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 327692] Search page is tiled and garbled
https://bugs.kde.org/show_bug.cgi?id=327692 Lastique changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Lastique --- Cannot test it because of https://bugs.kde.org/show_bug.cgi?id=400930. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 400930] Enabling Search plugin freezes Ktorrent
https://bugs.kde.org/show_bug.cgi?id=400930 Lastique changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 400930] New: Enabling Search plugin freezes Ktorrent
https://bugs.kde.org/show_bug.cgi?id=400930 Bug ID: 400930 Summary: Enabling Search plugin freezes Ktorrent Product: ktorrent Version: 5.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: andy...@mail.ru Target Milestone: --- SUMMARY When I enable Search plugin on the Plugins tab, UI freezes and the ktorrent process starts consuming 100% of one CPU core. STEPS TO REPRODUCE 1. Start Ktorrent. 2. Go to Plugins tab. 3. Enable Search plugin. OBSERVED RESULT The search tab appears on the toolbar, UI freezes, ktorrent starts busy looping on one CPU core. EXPECTED RESULT Search should get enabled, Ktorrent should continue to be operational. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.10, Ktorrent 5.1.1. KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 400155] KIO http.so periodically loads CPU
https://bugs.kde.org/show_bug.cgi?id=400155 --- Comment #1 from Lastique --- Created attachment 115827 --> https://bugs.kde.org/attachment.cgi?id=115827=edit High CPU load by http.so 2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 400155] New: KIO http.so periodically loads CPU
https://bugs.kde.org/show_bug.cgi?id=400155 Bug ID: 400155 Summary: KIO http.so periodically loads CPU Product: frameworks-kio Version: 5.50.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: andy...@mail.ru CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 115826 --> https://bugs.kde.org/attachment.cgi?id=115826=edit High CPU load by http.so 1 Periodically, http.so processes started by Ktorrent begin to load CPU intensively. There are multiple such processes running, so the total effect is 20-40% CPU load, according to KSysGuard. This period of high CPU usage lasts for about 20-30 seconds, then the CPU load goes back to normal. These high CPU usage periods happen repeatedly at various intervals, I've seen anywhere from about a minute and around 5 minutes. I suspect, the intervals may have to do with how often Ktorrent contacts the torrent trackers. I've attached a couple screenshots showing high CPU usage. SOFTWARE VERSIONS Kubuntu 18.10 x86_64 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399824] New: Plasma crashed when I closed Thermal Monitor settings
https://bugs.kde.org/show_bug.cgi?id=399824 Bug ID: 399824 Summary: Plasma crashed when I closed Thermal Monitor settings Product: plasmashell Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I was browsing Thermal Monitor widget settings. When I closed the settings by pressing Cancel, Plasma crashed. -- 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 0x7f449a2bd800 (LWP 2699))] Thread 8 (Thread 0x7f43b67fc700 (LWP 3446)): #0 0x7f44938b8bd0 in __GI___poll (fds=0x7f43b0008c00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:27 #1 0x7f448e422439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f448e42254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f449420190b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f44941a69ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4493fc522a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f44971376f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f4493fca16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f449314b6db in start_thread (arg=0x7f43b67fc700) at pthread_create.c:463 #9 0x7f44938c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f43ca015700 (LWP 3329)): #0 0x7f44938b40b4 in __GI___libc_read (fd=30, buf=0x7f43ca014b50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f448e466a00 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f448e421f27 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f448e4223e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f448e42254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f449420190b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f44941a69ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4493fc522a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f43cc971747 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #9 0x7f4493fca16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f449314b6db in start_thread (arg=0x7f43ca015700) at pthread_create.c:463 #11 0x7f44938c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f43e0283700 (LWP 3323)): #0 0x7f448e467d94 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f448e421e49 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f448e4223e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f448e42254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f449420190b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f44941a69ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4493fc522a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4497cd12a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f4493fca16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f449314b6db in start_thread (arg=0x7f43e0283700) at pthread_create.c:463 #10 0x7f44938c588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4467773700 (LWP 3321)): #0 0x7f44931519f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f4499ca6fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f44931519f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4499ca6f68, cond=0x7f4499ca6f90) at pthread_cond_wait.c:502 #2 0x7f44931519f3 in __pthread_cond_wait (cond=0x7f4499ca6f90, mutex=0x7f4499ca6f68) at pthread_cond_wait.c:655 #3 0x7f44999b05f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f44999b0639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f449314b6db in start_thread (arg=0x7f4467773700) at pthread_create.c:463 #6 0x7f44938c588f in clone () at
[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=360072 --- Comment #16 from Lastique --- Yakuake 3.0.5 in Kubuntu 18.04. "Manage Profiles..." works for me now, opens the profile selection dialog. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394558] Looking for updates is hanging forever
https://bugs.kde.org/show_bug.cgi?id=394558 --- Comment #6 from Lastique --- Created attachment 113485 --> https://bugs.kde.org/attachment.cgi?id=113485=edit pkmon log I've attached pkmon log taken while Discover starts. All log records were written when Discover started. When I clicked on "Checking for Updates" no additional activity happened in the log. I currently have no outstanding updates. BTW, for completeness, I also don't have the Snap backend installed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394558] Looking for updates is hanging forever
https://bugs.kde.org/show_bug.cgi?id=394558 Lastique changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #4 from Lastique --- I'm not using Flatpak on my system. plasma-discover-flatpak-backend is not even installed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395066] KWin crashes if while taking a screenshot I click on a panel
https://bugs.kde.org/show_bug.cgi?id=395066 --- Comment #5 from Lastique --- The total screen area is 5760x2160, which is two displays (3840x2160 and 1920x1080) combined. The panel I'm clicking on is on the 3840x2160 display. But the screenshot is configured to an Active Window, not the full screen. I'm not sure what is the active window in this case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395066] KWin crashes if while taking a screenshot I click on a panel
https://bugs.kde.org/show_bug.cgi?id=395066 --- Comment #3 from Lastique --- Setting a breakpoint on `exit` shows this backtrace: #0 0x7f760c4e5120 in __GI_exit (status=1) at exit.c:139 #1 0x7f7602930b05 in _XDefaultIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x7f75f405ac97 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #3 0x7f7602930d3e in _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #4 0x7f760292e058 in () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x7f760292e835 in _XFlush () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #6 0x7f760290fffa in XFlush () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x7f75f010ae5e in KWin::GlxBackend::present() (this=0x56151a4d8c70) at ./plugins/platforms/x11/standalone/glxbackend.cpp:737 #8 0x7f75f0103059 in KWin::GlxBackend::endRenderingFrame(QRegion const&, QRegion const&) (this=0x56151a4d8c70, renderedRegion=..., damagedRegion=...) at ./plugins/platforms/x11/standalone/glxbackend.cpp:809 #9 0x7f75dc731587 in KWin::SceneOpenGL::paint(QRegion, QList) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #10 0x7f760c109252 in KWin::Compositor::performCompositing() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #11 0x7f76099930db in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f760a6e182c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f760a6e90f4 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f76099639a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f76099bbd8e in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f76099b9f42 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f75f40c05cd in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #18 0x7f76099619ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f760996aa84 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f760c89bdbb in kdemain(int, char**) (argc=, argv=0x7ffd41b452c8) at ./main_x11.cpp:468 #21 0x7f760c4c3b97 in __libc_start_main (main=0x56151905b730 , argc=1, argv=0x7ffd41b452c8, init=, fini=, rtld_fini=, stack_end=0x7ffd41b452b8) at ../csu/libc-start.c:310 #22 0x56151905b76a in _start () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395066] KWin crashes if while taking a screenshot I click on a panel
https://bugs.kde.org/show_bug.cgi?id=395066 Lastique changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|BACKTRACE |--- --- Comment #2 from Lastique --- Apparently, it's not a crash per se but the kwin process exiting. In gdb, when I reproduce the issue, I can see the following: [Thread 0x7f07ad7f4700 (LWP 19391) exited] [Thread 0x7f078df0b700 (LWP 19479) exited] [Thread 0x7f078cd0d700 (LWP 19396) exited] [Thread 0x7f079ee9e700 (LWP 19393) exited] [Thread 0x7f07afe4f700 (LWP 19390) exited] [Thread 0x7f07c9900cc0 (LWP 19389) exited] [Inferior 1 (process 19389) exited with code 01] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395066] New: KWin crashes if while taking a screenshot I click on a panel
https://bugs.kde.org/show_bug.cgi?id=395066 Bug ID: 395066 Summary: KWin crashes if while taking a screenshot I click on a panel Product: kwin Version: 5.12.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Steps to reproduce: 1. Press Print Screen. Spectacle launches. 2. In its settings, select: - Area: Active Window - Delay: On Click checked - Include mouse pointer: unchecked - Include window titlebar and borders: checked - Capture the current popup only: unchecked, greyed out 3. Click Take a New Screenshot. 4. With the cross mouse cursor, click on the panel (e.g. on the task list area). 5. KWin crashes. Kubuntu 18.04, Plasma 5.12.5, KDE Frameworks 5.44.0, Qt 5.9.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395065] New: First attempt to open a USB stick in a file manager fails
https://bugs.kde.org/show_bug.cgi?id=395065 Bug ID: 395065 Summary: First attempt to open a USB stick in a file manager fails Product: plasmashell Version: 5.12.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: andy...@mail.ru Target Milestone: 1.0 Created attachment 113104 --> https://bugs.kde.org/attachment.cgi?id=113104=edit The error that appears when trying to open a file manager. After inserting a USB flash stick, Device Notifier displays a notification with the new device. When I select the USB stick and click "Open with File Manager", Dolphin doesn't start and instead an error dialog is displayed (see the attached screenshot). The error appears only after the first attempt to open the USB drive in the file manager. After that the drive appears to be mounted and attempting to open it the second time succeeds. It looks like the first time the file manager is started before the drive has been mounted. Kubuntu 18.04, Plasma 5.12.5, KDE Frameworks 5.44.0, Qt 5.9.5. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 394925] Logout/Reboot/Shutdown UI has badly rendered fonts when UI scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=394925 --- Comment #3 from Lastique --- Plasma 5.12.5, KDE Frameworks 5.44, Qt 5.9.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394925] Logout/Reboot/Shutdown UI has badly rendered fonts when UI scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=394925 --- Comment #1 from Lastique --- Forgot to mention that this is on Kubuntu 18.04. I can also add that the KDE loading splash screen (from the Breeze theme) has the similar problem with the "Plasma made by KDE" text in the bottom right corner of the screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394925] New: Logout/Reboot/Shutdown UI has badly rendered fonts when UI scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=394925 Bug ID: 394925 Summary: Logout/Reboot/Shutdown UI has badly rendered fonts when UI scaling is enabled Product: plasmashell Version: 5.12.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112999 --> https://bugs.kde.org/attachment.cgi?id=112999=edit Logout/Reboot/Shutdown UI with scale factor 1.7 In the attached screenshot, you can see that the fonts are poorly rendered, as if they were scaled using the nearest neighbour method. This screenshot was taken with scale factor 1.7 in System Settings and no additional font DPI settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #13 from Lastique --- Thank you, Nate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #11 from Lastique --- For the reference, I created Qt bug: https://bugreports.qt.io/browse/QTBUG-68606 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 388217] Yakuake height incorrect if desktop scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=388217 Lastique changed: What|Removed |Added Summary|Konsole height incorrect if |Yakuake height incorrect if |desktop scaling is enabled |desktop scaling is enabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #10 from Lastique --- Some of the bugs you know already ;). These are the showstoppers for me: https://bugs.kde.org/show_bug.cgi?id=373232 https://bugs.kde.org/show_bug.cgi?id=388217 Most of the work I do is from Yakuake, so it not working properly is critical for me. There are minor ones like https://bugs.kde.org/show_bug.cgi?id=388218 I can also see that the Logout/Reboot/Shutdown UI is rendered rather poorly (again, as if scaled with the nearest neighbour method) when UI scaling is enabled. I don't think I reported this one - mostly because I can't take a screenshot and didn't have time. But given the problems with Konsole/Yakuake I didn't test too much to discover more issues and settled with my current solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #8 from Lastique --- Thanks for the link. I would say, the fonts in this bug report look like a result of a nearest neighbour scaling, although there shouldn't be any scaling at all. > That said, using Qt scaling is the recommended method of accomplishing your > goal rather than changing the font DPI. UI scaling produces much more graphical issues than the DPI setting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #6 from Lastique --- Also, the Desktop Theme page in the System Settings that is used to illustrate the problem in bug 393724 is rendered correctly on my system, no blurry fonts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #5 from Lastique --- Bug 393724 reporter mentions that he is using UI scaling. In my case UI scaling is not used (i.e. the scale factor is 1.0). I only set "Xft.dpi: 162" in ~/.Xresources to make fonts look larger. Are you sure this bug is the same? Also, note that font corruption is only visible in Plasma widget settings and nowhere else in the system, including applications, KDE or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #3 from Lastique --- Was this problem reported to Qt previously? Could you provide a reference to that bug report? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394558] Looking for updates is hanging forever
https://bugs.kde.org/show_bug.cgi?id=394558
--- Comment #2 from Lastique ---
> Can you still reproduce?
Yes, the behavior is exactly the same. The currently installed plasma-discover
version is 5.12.5.
> What happens if you press the "check for updates" button? Does it complain
> that it's still updating?
You mean "Checking for updates..." section on the left? Nothing happens. It
just selects or deselects that option (the background of that option changes
between the normal grey and light blue).
BTW, "Checking for updates..." does not look like an appropriate name for a
section name or a tab. The other names are plural nouns ("Applications", "...
Addons", "Settings") or past participle ("Installed") but not present
continuous verbs. In other words, tab names are items, not ongoing activities.
It would be fitting to name the tab just "Updates".
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 394558] New: Looking for updates is hanging forever
https://bugs.kde.org/show_bug.cgi?id=394558 Bug ID: 394558 Summary: Looking for updates is hanging forever Product: Discover Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: andy...@mail.ru Target Milestone: --- Created attachment 112808 --> https://bugs.kde.org/attachment.cgi?id=112808=edit Discover is looking for updates When I click on the Updater applet indicating there are updates, Discover window opens with "Fetching..." in the title, "Checking for updates..." selected and "Looking for updates" in the main area (see the attached screenshot). However, this screen stays in this state forever with no change (I've waited for about 10 minutes, maybe more) and there is no indication of progress or completion anywhere to be seen. If there is some potentially time-consuming work to be done, there should be a progress bar of some sort. It should be possible to place it somewhere in that large unused area of the window. If the process has ended, successfully or not, an indication of that completion should be given to the user. Window title and contents should not imply that the work is still going. Kubuntu 18.04. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394043] Updater icon doesn't go away after updates are installed
https://bugs.kde.org/show_bug.cgi?id=394043 --- Comment #6 from Lastique <andy...@mail.ru> --- In that bug, you say the Updater starts to work as expected if you remove the Flatpak backend. In my case I do *not* have Flatpak installed and it still doesn't work. Are you sure it is a duplicate? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394043] Updater icon doesn't go away after updates are installed
https://bugs.kde.org/show_bug.cgi?id=394043 --- Comment #3 from Lastique <andy...@mail.ru> --- Also, plasma-discover-flatpak-backend and plasma-discover-snap-backend packages are not installed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394043] Updater icon doesn't go away after updates are installed
https://bugs.kde.org/show_bug.cgi?id=394043 Lastique <andy...@mail.ru> changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Lastique <andy...@mail.ru> --- No, I assume I don't. I didn't install it explicitly and Discover shows "Install" buttons for both Flatpak and Snap backends. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 --- Comment #1 from Lastique <andy...@mail.ru> --- Created attachment 112534 --> https://bugs.kde.org/attachment.cgi?id=112534=edit Garbled fonts in Updater settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394044] New: Widget settings dialog has badly rendered fonts
https://bugs.kde.org/show_bug.cgi?id=394044 Bug ID: 394044 Summary: Widget settings dialog has badly rendered fonts Product: plasmashell Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112533 --> https://bugs.kde.org/attachment.cgi?id=112533=edit Garbled fonts in Digital Clock settings In the Plasma widget settings, the dialog window contains badly rendered fonts. This is not specific to any particular widget. For example, see the attached screenshot for Digital Clock settings (right-click on the Digital Clock widget on the panel, click on "Digital Clock Settings"). You can see on the screenshot that the fonts on the window title, buttons and other controls are rendered properly. So are the other fonts in the system. The problem is with the fonts used in the window contents. The fonts don't get fixed on window resizes or switching to another tab. Kubuntu 18.04, Plasma 5.12.4. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394043] New: Updater icon doesn't go away after updates are installed
https://bugs.kde.org/show_bug.cgi?id=394043 Bug ID: 394043 Summary: Updater icon doesn't go away after updates are installed Product: Discover Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: andy...@mail.ru Target Milestone: --- When a security package update is available, Updater icon with a red dot appears in the system tray. If I install updates (in the command line using apt or using Muon package manager or Discover), the icon doesn't disappear but changes to the "non-security updates available" (i.e. the one without the red dot). Clicking on the icon says "1 package to update". `sudo apt update && sudo apt dist-upgrade` does not find any packages to update. I'm on Kubuntu 18.04, KDE Discover 5.12.4. The problem didn't appear in Kubuntu 17.10. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 --- Comment #2 from Lastique <andy...@mail.ru> --- Created attachment 112428 --> https://bugs.kde.org/attachment.cgi?id=112428=edit Screenshot after reboot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 --- Comment #1 from Lastique <andy...@mail.ru> --- Created attachment 112427 --> https://bugs.kde.org/attachment.cgi?id=112427=edit Screenshot before reboot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] New: Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 Bug ID: 393881 Summary: Desktop widget position lost after reboot Product: plasmashell Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 I have two displays, the primary is a 3840x2160 display and the secondary is a 1920x1080 display that is configured as an extension to the right of the primary display. The primary display has two horizontal panels, on the top and bottom edge of the screen. No other widgets on the desktop. 1. Unlock widgets and add a Calendar widget on the top right corner of the primary display. Resize the widget so that the calendar grid is visible. 2. Reboot. 3. After the reboot the Calendar widget position is changed. It is now placed in the top right corner of the top left quarter of the primary screen. Widget position should be preserved across reboot. This is a regression in Kubuntu 18.04, the position did save in 17.10. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347934] Part of the desktop visible in the lock screen
https://bugs.kde.org/show_bug.cgi?id=347934 Lastique <andy...@mail.ru> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #20 from Lastique <andy...@mail.ru> --- I tried with another laptop (Asus N550JV, Intel GPU, the other screen is a Samsung TV connected over HDMI). Kubuntu 17.10, kscreen 5.10.5. When I close the lid, the other screen blinks a few times (some portions of the screen turn black and back the lock screen) but eventually the lock screen is displayed as expected, covering the whole screen, the focus is on the password field. When I open the lid back, the lid screen is black, but I can move the mouse over it. In a few tests I've done it never showed the lock screen. On the other screen the lock screen is still displayed but loses focus, so I have to manually click on the password field to login. I think the two problems (the lid screen not showing the lock screen and the focus loss) still need fixing. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347934] Part of the desktop visible in the lock screen
https://bugs.kde.org/show_bug.cgi?id=347934 --- Comment #18 from Lastique <andy...@mail.ru> --- Sorry, I no longer have the laptop that showed the problem, so I can't test it. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 393192] New: Time Downloaded column has incorrect values
https://bugs.kde.org/show_bug.cgi?id=393192 Bug ID: 393192 Summary: Time Downloaded column has incorrect values Product: ktorrent Version: 5.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: andy...@mail.ru Target Milestone: --- I have added a torrent to the download queue and it has finished downloading a few hours later. However, the "Time Downloaded" column for this torrent says it has been downloading for 66 days. The torrent hasn't even been in the queue for that long. The column "Added" displays the correct date and time when the torrent was added. I did not pause or resume downloading or seeding. The torrent has been downloaded completely, all files, 100%. Kubuntu 17.10, Ktorrent 5.1.0. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update
https://bugs.kde.org/show_bug.cgi?id=364593 --- Comment #12 from Lastique <andy...@mail.ru> --- I've created a Qt bug: https://bugreports.qt.io/browse/QTBUG-67535 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update
https://bugs.kde.org/show_bug.cgi?id=364593 --- Comment #10 from Lastique <andy...@mail.ru> --- I've created this thread: https://devtalk.nvidia.com/default/topic/1031836/linux/opengl-context-cannot-be-created-after-nvidia-driver-update-cannot-reboot-the-system/ Please, feel free to add any technical details. I still think this is a bug in KDE as well, even if the driver behaves not as you'd expect. A crash is always a bug in the application. I will reopen this bug if I get the response from Nvidia indicating that the fix should be done in the application. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update
https://bugs.kde.org/show_bug.cgi?id=364593 Lastique <andy...@mail.ru> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 --- Comment #8 from Lastique <andy...@mail.ru> --- I understand the source of the problem - the updated OpenGL part of the driver may not be binary compatible with the loaded kernel module or X11 driver or something and therefore refuses to load. But "reboot after updating the driver" is not a resolution because *I cannot reboot* except by killing X server. This bug requests a better solution than killing X server. For example, cache OpenGL context on boot or draw the logout/reboot UI in software. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 373183] CPU load is reported as more than 100%
https://bugs.kde.org/show_bug.cgi?id=373183 Lastique <andy...@mail.ru> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from Lastique <andy...@mail.ru> --- I have since moved away from Liquorix kernel, so I cannot verify. On the stock Kubuntu 17.10 kernel CPU load indicator never reaches 100%. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392286] New: Display turns on twice after going into powersaving mode
https://bugs.kde.org/show_bug.cgi?id=392286 Bug ID: 392286 Summary: Display turns on twice after going into powersaving mode Product: Powerdevil Version: 5.10.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andy...@mail.ru Target Milestone: --- I have two displays attached to my GTX980, the main display on DisplayPort-4 and a secondary display on HDMI-0. The system is configured to turn off the displays after 10 minuses of inactivity. PowerDevil turns off the displays as expected. However, ~5 minutes after that the main display on DP-4 turns on only to show that there is no signal (the display's on-screen message) and turns off again. Another ~5 minutes later this happens again. After that the display stays off as it should be. The other display on HDMI-0 is actually a TV and it shows a blank screen all the time with no activity while DP-4 wakes up. This only happens when the display turns off for power saving. It does not happen if I issue `xset dpms force off` from the command line (the displays turn off and don't wake up). This is 100% reproducible and I'm sure it's not due to some activity (e.g. an event from the mouse) because when the display wakes up it does not show desktop/lock screen. I would like the display to not wake up like that. Kubuntu 17.10, x86_64, Nvidia driver 390.42, GTX980, DP-4 display is NEC EA275UHD. -- You are receiving this mail because: You are watching all bug changes.
