[plasma-nm] [Bug 452355] A notification asking to log-in to the network is displayed for every single network
https://bugs.kde.org/show_bug.cgi?id=452355 --- Comment #25 from John van Spaandonk --- (In reply to Nate Graham from comment #23) > Is this still reproducible in Plasma 6.1? I never had the problem anymore for at least one year. Suspect some relevant component updated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467703] I got locked out from my account after closing and opening my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=467703 John van Spaandonk changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from John van Spaandonk --- apparently I forgot to set the state to reported. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467703] I got locked out from my account after closing and opening my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=467703 --- Comment #6 from John van Spaandonk --- [john@fedora ~]$ kwin_wayland [a window opens saying .. press right control key to grab input, the following is the command line output] No backend specified, automatically choosing X11 because DISPLAY is set kf.globalaccel.kglobalacceld: Failed to register service org.kde.kglobalaccel OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics (ILK) OpenGL version string: 2.1 Mesa 22.3.7 OpenGL shading language version string: 1.20 Driver: Intel GPU class: Unknown OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 22.3.7 Linux kernel version: 6.2.8 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_core: eglPostSubBufferNV not supported, have to enable buffer preservation - which breaks v-sync and performance kwin_core: Parse error in tiles configuration for monitor "d3b3d9bc-06de-5748-bbfe-56dd26acb3ce" : "illegal value" Creating default setup kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker" kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate" -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 467703] I got locked out from my account after closing and opening my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=467703 John van Spaandonk changed: What|Removed |Added Version|5.27.3 |1.10.0 Product|Powerdevil |plasma-wayland-protocols Component|general |general CC||aleix...@kde.org --- Comment #3 from John van Spaandonk --- I finally managed to solve this by choosing X11 instead of Wayland. So the conclusion, which I verified multiple times, is that something related to Wayland, and outside of the .config directory, causes my screen to go black immediately after logging in. I changed the component to plasma-wayland-protocols, that is the only one that seemed to fit. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467703] I got locked out from my account after closing and opening my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=467703 --- Comment #2 from John van Spaandonk --- Additional information: 1. After I log in, I see the monitor backlight switch off, as when the monitor goes to sleep. The monitor then stays off and also does not wake on key strokes or mouse movement. 2. I can press CTRL-ALT-DEL and then enter to log out, or I can press the power button once, which I configured to shut down. Then the laptop shuts down. Perhaps the session starts and runs normally, but somehow KDE causes the backlight of the monitor to switch off, exactly like it did when I closed the lid the last time that it still was switched on. But the backlight is now stuck in this position and also KDE does not wake up the monitor anymore. How to restore the power configuration without removing the user account? I tried moving my .config directory to .config_old but this did has no effect on the problem. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467703] I got locked out from my account after closing and opening my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=467703 --- Comment #1 from John van Spaandonk --- In the session (looking at a black screen), I can press CTRL-ALT-DEL and then enter, and the computer shuts down. Perhaps everything is running, but it is just the screen that is black? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467703] New: I got locked out from my account after closing and opening my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=467703 Bug ID: 467703 Summary: I got locked out from my account after closing and opening my laptop lid. Classification: Plasma Product: Powerdevil Version: 5.27.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jwork12...@yahoo.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY I have a DELL xps 15 (l501x) laptop with KDE (Fedora 37 with plasma 27.3). I closed the lid and immediately opened it after the display went dark. At this point my session was locked with a black screen. I killed the power by holding the power button. Since then I cannot login to that account anymore (I get to the login screen, can enter the credentials and press enter, after this the black screen) As a workaround I I created a new user (after logging in as root) and that user works fine. Following a suggestion at reddit.com/r/kde I used the new account to type (as root) loginctl unlock-sessions but this did not help. Perhaps there is a config file or something that I need to delete? I would like to be able to access my account in KDE, I did not expect it was so easy to get locked out :-( STEPS TO REPRODUCE 1. cl.ose laptop lid 2. open laptop lid immediately after the screen goes dark. OBSERVED RESULT Black screen, no response to keypresses. Cannot use the virtual terminals CTRL-F1 etc. CTRL-F2 shows the login screen grayed out, but unresponsive. Laptop fan is blowing and I see some disk activity. It is almost as if the session is started normally but there is a problem with the power state so the display does not work. How to reset this? EXPECTED RESULT Computer is either asleep (flashing on-button, I should be able to press the button once to wake up) OR wakes up. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The laptop has (in Fedora) two screens, the primary screen uses the graphics of the intel processor, the secondary screen uses an nvidea graphics card. Not sure if this info is useful... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409852] Okular takes an extreme amount of time to load a djvu file over samba
https://bugs.kde.org/show_bug.cgi?id=409852 John van Spaandonk changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #7 from John van Spaandonk --- This seems to have been solved, perhaps by updating a backend. I will close my bug report. I also tested the duplicate bug 418691 by downloading the attached picture to a samba share and opening it with okular. This also works for me. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462208] Monitor does not wakeup when I move the mouse after the computer wakes up from sleep.
https://bugs.kde.org/show_bug.cgi?id=462208 John van Spaandonk changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from John van Spaandonk --- Tried with another usb port and it works. Must be something related to my hardware. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462208] New: Monitor does not wakeup when I move the mouse after the computer wakes up from sleep.
https://bugs.kde.org/show_bug.cgi?id=462208 Bug ID: 462208 Summary: Monitor does not wakeup when I move the mouse after the computer wakes up from sleep. Classification: Plasma Product: Powerdevil Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jwork12...@yahoo.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY *** After waking my computer from sleep by pressing the power button, I expect the monitor to wake up from slipe by moving my mouse. However this does not wake the monitor. This worked before kde 5.25. *** STEPS TO REPRODUCE 1. Computer is asleep (choose sleep from the start menu), the power light is flashing to indicate this. 2. Press power button to wake it up 3. Move the mouse, which should wake the monitor so I can see the lock screen to enter my password. OBSERVED RESULT The monitor stays asleep so I cannot see the login screen. I have to press a key on the keyboard to wake up the monitor. I do not want to do this because I am already focused on the password field, so my password is wrong. As a workaround I have to press an arrow key. EXPECTED RESULT I expect the monitor to wake up when moving the mouse so I can enter my password in the lock screen. SOFTWARE/OS VERSIONS I am on neon, 5.26.3, using X11. Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 452355] A notification asking to log-in to the network is displayed for every single network
https://bugs.kde.org/show_bug.cgi?id=452355 John van Spaandonk changed: What|Removed |Added CC||jwork12...@yahoo.com --- Comment #8 from John van Spaandonk --- This started about a month ago for me too, I am now asked to log in to a fixed network after every boot/wakeup. I read that it is claimed that there were possibly changes in some other component, but I am using Neon. Can I expect the components of this distribution to work seamlessly or do developers only work on the KDE part without testing as a whole? I am asking this since I am considering moving to another distro, that is better maintained and more stable as a whole. Thanks for any insights! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450131] In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right)
https://bugs.kde.org/show_bug.cgi?id=450131 John van Spaandonk changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from John van Spaandonk --- I changed the status NEEDSINFO to REPORTED to ensure that the bug will not be automatically closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450131] In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right)
https://bugs.kde.org/show_bug.cgi?id=450131 --- Comment #7 from John van Spaandonk --- No, I never, ever, had more than 1 screen attached in the last 12 years that I used this computer :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450131] In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right)
https://bugs.kde.org/show_bug.cgi?id=450131 --- Comment #5 from John van Spaandonk --- Created attachment 147074 --> https://bugs.kde.org/attachment.cgi?id=147074=edit Video of the windows minimizing vaguely toward the right I click on the taskbar icons one by one a few times, working from left to right. This demonstrates that, under Wayland, the windows minimization lets the windows fly off somewhere towards the right, but not ending at their representation in the taskbar. Taking this video was fiddly using my webcam, so I hope you trust me that under X-windows it works as it should :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450131] In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right)
https://bugs.kde.org/show_bug.cgi?id=450131 --- Comment #3 from John van Spaandonk --- Thanks for looking into this! What's bugged me with this one is that I have the simplest possible setup! (I always use the most standard setup to obtain the most stable system.) My desktop system has one monitor, a DELL U2410F, using the built in graphics of my 2500k processor. I had to look up the word "panel", I take it this is the taskbar with the start menu, the tray area and the representations of running applications. It lives at its default position (at the bottom of the screen). Perhaps there are some configuration files I could try to reset? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 450086] No notifications for nordvpn under Wayland
https://bugs.kde.org/show_bug.cgi?id=450086 --- Comment #6 from John van Spaandonk --- I asked nordvpn for help, let's see what they say. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 450086] No notifications for nordvpn under Wayland
https://bugs.kde.org/show_bug.cgi?id=450086 --- Comment #4 from John van Spaandonk --- It does! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 450086] No notifications for nordvpn under Wayland
https://bugs.kde.org/show_bug.cgi?id=450086 --- Comment #2 from John van Spaandonk --- Created attachment 146670 --> https://bugs.kde.org/attachment.cgi?id=146670=edit nordvpn disconnect notification, as requested -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450131] In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right)
https://bugs.kde.org/show_bug.cgi?id=450131 --- Comment #1 from John van Spaandonk --- Forgot to mention: the relevant desktop effect is called "squash", and the little animation (movie) shows that the behavior under Wayland is not as intended. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450131] New: In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right)
https://bugs.kde.org/show_bug.cgi?id=450131 Bug ID: 450131 Summary: In Wayland, the "windows minimize" animation moves in the wrong direction (towards the right) Product: kwin Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: jwork12...@yahoo.com Target Milestone: --- SUMMARY See title: this problem is specific to wayland STEPS TO REPRODUCE 1. you start with several open windows, corresponding to icons+text in the taskbar (taskbar at the bottom) Icons+text is important to give the "buttons" in the taskbar enough width to clearly observe the intended effect. 2. Minimize a window. OBSERVED RESULT The minimization animation moves from the outlines of the window location towards the right of the screen, not ending on the outline of the "button" in the taskbar. Thus the minimization gives a false/incorrect hint of where the window is minimized to. I had to turn it of since it was too confusing. EXPECTED RESULT I expect the same behavior as in X-windows: the minimization should end precisely at the outline of the "button" (representation of the window) in the taskbar, because that is where it always "is". SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Graphics Processor: Mesa DRI Intel® HD Graphics 3000 ADDITIONAL INFORMATION I checked with Nate Graham who asked to create this bug report since it is not an intended behavior, so I guess we should see it as a regression from the desired behavior (still working under X-windows). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 450086] New: No notifications for nordvpn under Wayland
https://bugs.kde.org/show_bug.cgi?id=450086 Bug ID: 450086 Summary: No notifications for nordvpn under Wayland Product: frameworks-knotifications Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: jwork12...@yahoo.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY *** Notification do not work for the command line utility nordvpn under Wayland. It works under X11 *** STEPS TO REPRODUCE No idea how to reproduce this if you do not have a subscription to nordvpn but the command line utility can be downloaded from their website. 1. You are not connected to a VPN 2. open a konsole and type nordvpn connect OBSERVED RESULT Under X11 I get a notification that I am connected to the VPN server, under Wayland I get no notification. Same for disconnecting if you are already connected to a VPN server. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest kde neon with Plasma 5.24 and framworks 5.90, QT 5.13.3 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 449414] "system activity" reports wrong cpu usage
https://bugs.kde.org/show_bug.cgi?id=449414 --- Comment #2 from John van Spaandonk --- Thanks for the advice, may I say that this right-mouse button click is not very discoverable? I see now how I need to interpret the tooltip "The current total CPU usage of a process" as "Process CPU usage relative to available CPU". Although you can reason that this is not true since if a program is designed to work only on 1 CPU, the available CPU is only 1 CPU. In other words: I guarantee that a user will not understand why his softsynth is not working because it hugs one CPU while it is being reported as only 25%. So then let me ask this: why do you choose a different convention than top? Why not be in line with what is used on the command line? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 449414] "system activity" reports wrong cpu usage
https://bugs.kde.org/show_bug.cgi?id=449414 John van Spaandonk changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 449414] New: "system activity" reports wrong cpu usage
https://bugs.kde.org/show_bug.cgi?id=449414 Bug ID: 449414 Summary: "system activity" reports wrong cpu usage Product: plasma-systemmonitor Version: 5.23.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: j...@van-spaandonk.nl CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY I compared with top in a command shell, and the cpu activity reported there is much higher. Basically, the cpu load according to top goes all the way to 100 and the load as reported by system activity does not go beyond about 25 procent for the same process. Thus it gives a wrong view of my system load. It almost looks as though the single CPU load is divided by the number of cores, which is not correct IMHO. This bug has been with us for a while it seems, see also this: https://forum.kde.org/viewtopic.php?t=75027 Perhaps this is something for the 15 minutes bug initiative? STEPS TO REPRODUCE 1. see above, pick any process that generates some load. MY example is a soft synth that also reports the CPU load itself (identical by the way to the load reported by top) 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS lates KDE neon 5.23.90 Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 John van Spaandonk changed: What|Removed |Added CC||j...@van-spaandonk.nl --- Comment #56 from John van Spaandonk --- This occurs especially when I press the windows key and start typing, directly after I logged on. It it the case that the krunner app must load from disk the first time it is run? If this is so then perhaps it is possible to always load the krunner part on startup to prevent this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 445065] Dolphin gets stuk when using Samba after the NAS falls asleep
https://bugs.kde.org/show_bug.cgi?id=445065 John van Spaandonk changed: What|Removed |Added Version|21.08.3 |5.90.0 Assignee|dolphin-bugs-n...@kde.org |baloo-bugs-n...@kde.org Product|dolphin |frameworks-baloo Component|general |general --- Comment #3 from John van Spaandonk --- I managed to solve this by the command 'balooctl disable.' Wow. I changed this bug report's product to frameworks-baloo. FYIP: The hint was the following info in the systemlog ( journalctl -b): Jan 25 13:58:13 Big-PC systemd[1466]: plasma-baloorunner.service: Control process exited, code=exited, status=1/FAILURE Jan 25 13:58:13 Big-PC systemd[1466]: plasma-baloorunner.service: Skipped due to 'exec-condition'. Jan 25 13:58:13 Big-PC systemd[1466]: Condition check resulted in KRunner provider for baloo file indexer being skipped. After this I got the disk-sleep version of Dolphin (It did not start up anymore) and after a while the whole plasma gets stuck. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 416035] Bluetooth does not reconnect automatically to a paired device
https://bugs.kde.org/show_bug.cgi?id=416035 --- Comment #8 from John van Spaandonk --- I confirm that since using Pipewire this works. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445065] Dolphin gets stuk when using Samba after the NAS falls asleep
https://bugs.kde.org/show_bug.cgi?id=445065 --- Comment #2 from John van Spaandonk --- A while ago I reconfigured the NAS to not fall asleep. Now sometimes, after a suspend and a wakeup, all Dolphin instances are blocked for 1-2 minutes. All blocked instances were showing directories on the NAS. After 2 minutes the instances work again. Here is the part of the syslog from the moment Networkmanager woke up: Jan 02 16:26:29 Big-PC NetworkManager[932]: [1641137189.0177] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 02 16:26:32 Big-PC kwin_x11[1780]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19807, resource id: 81788978, major code: 18 (ChangeProperty), minor cod> Jan 02 16:26:33 Big-PC ovpn-openvpn[1288]: TCP/UDP: Preserving recently used remote address: [AF_INET]95.211.112.9:443 Jan 02 16:26:33 Big-PC ovpn-openvpn[1288]: UDP link local: (not bound) Jan 02 16:26:33 Big-PC ovpn-openvpn[1288]: UDP link remote: [AF_INET]95.211.112.9:443 Jan 02 16:26:39 Big-PC systemd[1]: NetworkManager-dispatcher.service: Succeeded. Jan 02 16:27:12 Big-PC NetworkManager[932]: [1641137232.3289] dhcp6 (eno1): request timed out Jan 02 16:27:12 Big-PC NetworkManager[932]: [1641137232.3289] dhcp6 (eno1): state changed unknown -> timeout Jan 02 16:27:12 Big-PC NetworkManager[932]: [1641137232.3290] dhcp6 (eno1): canceled DHCP transaction Jan 02 16:27:12 Big-PC NetworkManager[932]: [1641137232.3290] dhcp6 (eno1): state changed timeout -> done Jan 02 16:27:33 Big-PC ovpn-openvpn[1288]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Jan 02 16:27:33 Big-PC ovpn-openvpn[1288]: TLS Error: TLS handshake failed Jan 02 16:27:33 Big-PC ovpn-openvpn[1288]: SIGUSR1[soft,tls-error] received, process restarting Jan 02 16:27:36 Big-PC plasmashell[1820]: kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed Jan 02 16:27:36 Big-PC plasmashell[1820]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Jan 02 16:27:36 Big-PC dbus-daemon[1660]: [session uid=1000 pid=1660] Activating via systemd: service name='org.kde.runners.baloo' unit='plasma-baloorunner.service' requested > Jan 02 16:27:36 Big-PC systemd[1647]: Starting KRunner provider for baloo file indexer... Jan 02 16:27:36 Big-PC systemd[1647]: plasma-baloorunner.service: Control process exited, code=exited, status=1/FAILURE Jan 02 16:27:36 Big-PC systemd[1647]: plasma-baloorunner.service: Skipped due to 'exec-condition'. Jan 02 16:27:36 Big-PC systemd[1647]: Condition check resulted in KRunner provider for baloo file indexer being skipped. Jan 02 16:27:37 Big-PC systemd[1647]: Started Konsole - Terminal. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445065] Dolphin gets stuk when using Samba after the NAS falls asleep
https://bugs.kde.org/show_bug.cgi?id=445065
--- Comment #1 from John van Spaandonk ---
I configured my NAS to not fall asleep anymore but that was not the cause
problem.
The problem still occurs, after I log in again after the computer falls asleep.
I noticed that I also cannot find any results in krunner that are related to
files on the NAS after this happens.
When the problem happens, the Dolphin process has status disk-sleep, which
always for me is a sign of serious trouble.
Even after killing Dolphin and all kio-slaves that are running ( using kill -9)
and starting a new Dolphin the problem persists.
There are many threads I find when I google ("plasma freezes"), from those I
got the idea to try another kernel version and see if that solves the problem.
Will report back if that helps.
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 445153] krunner causes error messages in my system log because kconfig reads each line of an .ods file I open
https://bugs.kde.org/show_bug.cgi?id=445153 --- Comment #2 from John van Spaandonk --- To be honest I have no idea. I just press the windows key, type the first few letters of the document until it appears at the top of the list and then press enter. Just tried it again with the same result. The last few lines in the log are these, perhaps that can provide a hint. /Nov 08 12:57:27 Big-PC plasmashell[1710]: kf.config.core: "KConfigIni: In file /media/nas_data/xxx.ods, line 376: " Invalid entry (missing '=') Nov 08 12:57:27 Big-PC plasmashell[1710]: kf.service.services: The desktop entry file "///media/nas_data/xxx.ods" has Type= "Application" but no Exec line Nov 08 12:57:27 Big-PC plasmashell[1710]: kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found Nov 08 12:57:27 Big-PC plasmashell[1710]: QObject::disconnect: Unexpected nullptr parameter Nov 08 12:57:27 Big-PC kwin_x11[1654]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36824, resource id: 39846722, major code: 18 (ChangeProperty), minor code: 0 Nov 08 12:57:27 Big-PC systemd[1523]: Started LibreOffice Calc - Spreadsheet. Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/hwdata/pnp.ids" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 08 12:57:27 Big-PC kernel: audit: type=1400 audit(1636372647.817:105): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/hwdata/pnp.ids" pid=14037 comm="soffice.bin" requested_mask="r> Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/kdedefaults/kdeglobals" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" > Nov 08 12:57:27 Big-PC kernel: audit: type=1400 audit(1636372647.853:106): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/kdedefaults/kdeglobals" pid=14037 comm="soffice.bin" r> Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/proc/sys/kernel/core_pattern" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 o> Nov 08 12:57:27 Big-PC kernel: audit: type=1400 audit(1636372647.861:107): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/proc/sys/kernel/core_pattern" pid=14037 comm="soffice.bin" requested_mas> Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/breezerc" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 oui> Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/kdedefaults/kwinrc" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" fsui> Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/kwinrc" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=> Nov 08 12:57:27 Big-PC kernel: audit: type=1400 audit(1636372647.865:108): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/breezerc" pid=14037 comm="soffice.bin" requested_mask=> Nov 08 12:57:27 Big-PC kernel: audit: type=1400 audit(1636372647.865:109): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/kdedefaults/kwinrc" pid=14037 comm="soffice.bin" reque> Nov 08 12:57:27 Big-PC kernel: audit: type=1400 audit(1636372647.865:110): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/kwinrc" pid=14037 comm="soffice.bin" requested_mask="r> Nov 08 12:57:27 Big-PC audit[14037]: AVC apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/john/.config/breezerc" pid=14037 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 oui> Nov 08 12:57:27 Big-PC audit[14037]: AV
[krunner] [Bug 445153] New: krunner causes error messages in my system log because kconfig reads each line of an .ods file I open
https://bugs.kde.org/show_bug.cgi?id=445153 Bug ID: 445153 Summary: krunner causes error messages in my system log because kconfig reads each line of an .ods file I open Product: krunner Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: j...@van-spaandonk.nl CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I press the windows key to open the search dialog and then type the first part of an (Openoffice spreadsheet) document name. The document is found and started correctly, but there are many error messages in my syslog. It looks like KDE tries to read the full document because it mistakenly thinks that is is a configuration file?? STEPS TO REPRODUCE 1. See above 2. 3. OBSERVED RESULT kconfigini tries to read the complete .ods XML document. This does not look good (I replaced the file name by xxx) I get many lines like this: Nov 08 11:11:50 Big-PC plasmashell[1710]: kf.config.core: "KConfigIni: In file /media/nas_data/xxx.ods, line 5: " "Invalid escape sequence \"\\^\"." Nov 08 11:11:50 Big-PC plasmashell[1710]: kf.config.core: "KConfigIni: In file /media/nas_data/xxx.ods, line 5: " "Invalid escape sequence \"\\m\"." Nov 08 11:11:50 Big-PC plasmashell[1710]: kf.config.core: "KConfigIni: In file /media/nas_data/xxx.ods, line 5: " "Invalid escape sequence \"\\À\"." EXPECTED RESULT No error messages. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445065] New: Dolphin gets stuk when using Samba after the NAS falls asleep
https://bugs.kde.org/show_bug.cgi?id=445065 Bug ID: 445065 Summary: Dolphin gets stuk when using Samba after the NAS falls asleep Product: dolphin Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: j...@van-spaandonk.nl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143273 --> https://bugs.kde.org/attachment.cgi?id=143273=edit system log showing a problem with dolphin - the kde file system SUMMARY I use a QNAP NAS wit a samba filesystem, the drives are mounted via fstab - see below. Sometimes, but not always, Dolphin gets stuck when writing or reading NAS files. This problem occurs much more in the last one or two months. Also I often get a 1 to 2 -second delay when I first click on a NAS directory in Dolphin. (This occurs mainly in the last month or so separate issue, not topic of this bug report). I realize that this situation difficult to reproduce for the typical developer working on a local filesystem on a laptop. Let me know what extra info I need to provide / what experiments to do to stabilize the network scenario for KDE. I gave the bug a high priority since it prevents the use of KDE in a professional environment with networked storage. STEPS TO REPRODUCE 1. Try to open or save a file on the NAS, mounted with smb, especially after it has fallen asleep 2. 3. OBSERVED RESULT Dolphin stuck, everything using the file system stuck, such as the upload dialog window for creating this bug report. If I open a konsole window then I can normally access the NAS. After a while the whole of KDE freezes and I I cannot shutdown the PC anymore because after a while nothing reacts anymore in KDE, the keyboard does not work anymore, only the mouse cursor still moves. EXPECTED RESULT 1. If the NAS is sleeping I expect a delay of up to 10 seconds for the NAS drives to spin up and the NAS, and thus KDE, to react again. 2. I expect a message from Dolphin that a network storage is not responding / Dolphin and KDE as a whole should never get stuck due to a network problem. (This has always always the main problem for me with KDE since I started using it on a daily basis some 20 years ago) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The last line shows how the relevant NAS directory is mounted # # / was on /dev/sdc2 during installation UUID=440e0d66-6a8d-4c7d-b0e4-7db611d24385 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sdc1 during installation #UUID=C2C4-CCA8 /boot/efi vfatumask=0077 0 1 /swapfile noneswapsw 0 0 # ssd data directory, for downloads, thunderbird email, dropbox UUID=d4f31c28-01ee-4252-bde7-671b459317fe /media/ssd_data ext4rw 0 2 # QNAP TS219P+ //192.168.1.2/data /media/nas_data cifs user=,password=,rw,user,nosuid,uid=1000,gid=100,_netdev,vers=1.00 0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434175] Move to wastebin functionality is so slow that is unusable when it already has a lot of stuff in it
https://bugs.kde.org/show_bug.cgi?id=434175 --- Comment #14 from John van Spaandonk --- On 8/5/21 10:43 AM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=434175 > > --- Comment #13 from tagwer...@innerjoin.org --- > (In reply to John van Spaandonk from comment #12) >> I tried seeing the location of trash by right-clicking it, choosing edit >> and pressing the folder symbol. >> This completely froze Dolphin. > Doesn't sound right. I think sidestep Dolphin and use the command line. > > cd ~/.local/share/Trash > ls files > ls info > > I'm guessing there are more than the 78 files there than Dolphin is counting. > I did what you suggested, and after removing the 78 files using the trash "delete" function in Dolphin, ls~/.local/share/Trash shows 0 files. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434175] Move to wastebin functionality is so slow that is unusable when it already has a lot of stuff in it
https://bugs.kde.org/show_bug.cgi?id=434175 --- Comment #12 from John van Spaandonk --- On 8/5/21 10:02 AM, Michał Zubkowicz wrote: > https://bugs.kde.org/show_bug.cgi?id=434175 > > --- Comment #11 from Michał Zubkowicz --- > I can confirm that it's strictly related to number of files in trash. I've put > 1 000 000 files in trash and then deleting was very slow. After emptying trash > it is fast again. > I had only 78 files in the trash, and it did not get beyond deleting the first one. I tried seeing the location of trash by right-clicking it, choosing edit and pressing the folder symbol. This completely froze Dolphin. I solved everything it by simply restarting KDE! It might be there is some problem related to a temporary storage that is cleaned by restarting KDE. I do tend to use my computer without rebooting for days, and sometimes a week. Anyway, the expected robustness is not there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434175] Move to wastebin functionality is so slow that is unusable when it already has a lot of stuff in it
https://bugs.kde.org/show_bug.cgi?id=434175 John van Spaandonk changed: What|Removed |Added CC||j...@van-spaandonk.nl --- Comment #9 from John van Spaandonk --- I have this as well for a long time now. KDE neon. I keep everything at default and updated, so ext3 filesystem, KDE neon unmodified etc. Problem is on a local SSD partition. Moving to thrash takes a long time, it makes it impossible to delete files. Deleting 75 files from trash also takes forever, waiting > 5 minutes now and still not done. process monitor shows 3 processes trash.so, all have status "disk sleep". I see many complaints about this on forum.kde.org as well. https://forum.kde.org/viewtopic.php?t=140002 Is it possible to give this more focus since this is the absolute basic stuff that really should work? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 439850] New: Suggestion for search not updated anymore in the default application launcher after I type a space
https://bugs.kde.org/show_bug.cgi?id=439850 Bug ID: 439850 Summary: Suggestion for search not updated anymore in the default application launcher after I type a space Product: krunner Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: j...@van-spaandonk.nl CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I want to press meta and then use the keyboard to start the `System Information' module, but I cannot get past the first suggestion that starts with the word `system' It seems there is a bug in the application laucher search where it does not update the best suggestion after you type a space. That is unfortunate because spaces are used in the names of system modules. STEPS TO REPRODUCE 1. press meta key 2. type `system information' 3. OBSERVED RESULT After I type `system' the first module that is selected is `System Settings' Even though I type ` information', the System Settings module keeps selected. Thus I have to use the down arrow key to select it. EXPECTED RESULT I expect the preselection to be updated if i continue typing, even though I may type a space. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: ADDITIONAL INFORMATION The behavior of ALT-F2 is also not what I expect but different (ie, inconsistent). Here the `System Information' module is selected, but only after I type at least three letters of the word `information'. The behavior overall is inconsistent and also not what I expect in both cases. Hope all this helps! -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 438617] screen flashes when starting a new game
https://bugs.kde.org/show_bug.cgi?id=438617 --- Comment #1 from John van Spaandonk --- I think it is related to the "fade in" effect where the background changes from grayed out to normal again. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 438617] New: screen flashes when starting a new game
https://bugs.kde.org/show_bug.cgi?id=438617 Bug ID: 438617 Summary: screen flashes when starting a new game Product: ksudoku Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: j...@van-spaandonk.nl CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY The screen flashes in some situations, it started with KDE5.22 100% reproducible for me. STEPS TO REPRODUCE 1. Start new game 2. Overview screen is drawn (where you can select the type of game) 3. Screen flashes, perhaps the screen is drawn again 4 After you select a game and press OK, the overview screen flashes again before we go to the game itself. This works OK. OBSERVED RESULT see step 3. EXPECTED RESULT No flashes, like before SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: NEON, KDE 5.22 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425631] I lost the radio buttons to swith the audio sink
https://bugs.kde.org/show_bug.cgi?id=425631 John van Spaandonk changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from John van Spaandonk --- The reason was that I unplugged the bluetooth speaker. I guess this is intentional behavior so I will close this report. Sorry for the spam. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425631] New: I lost the radio buttons to swith the audio sink
https://bugs.kde.org/show_bug.cgi?id=425631 Bug ID: 425631 Summary: I lost the radio buttons to swith the audio sink Product: plasma-pa Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: j...@van-spaandonk.nl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 131073 --> https://bugs.kde.org/attachment.cgi?id=131073=edit no radio buttons in volume control widget SUMMARY I cannot see the radio buttons anymore. Error occurred yesterday, not sure how to reproduce. I would be happy with any advice on how to reset any possible wrong configuration or do other experiments to narrow this down. STEPS TO REPRODUCE 1. Start audio in youtube 2. click volume control 3. OBSERVED RESULT no radio buttons EXPECTED RESULT radio buttons SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425498] The calender widget is extremely large
https://bugs.kde.org/show_bug.cgi?id=425498 --- Comment #3 from John van Spaandonk --- On 8/18/20 2:39 PM, John van Spaandonk wrote: > https://bugs.kde.org/show_bug.cgi?id=425498 > > --- Comment #2 from John van Spaandonk --- > Forgot to mention: the calendar widget increased it's size after upgrading > from > neon 18.04 to neon 20.04 today. > I played a bit with the settings of the clock, changing it to various types (analog etc). After this the problem was gone, but also my week numbers did not show anymore since that setting was reset. I am surprised that by playing with the clock's appearance, you can reset settings of the calendar. This appears to be a bug to me, just let me know if I should file a separate report for that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425498] The calender widget is extremely large
https://bugs.kde.org/show_bug.cgi?id=425498 --- Comment #2 from John van Spaandonk --- Forgot to mention: the calendar widget increased it's size after upgrading from neon 18.04 to neon 20.04 today. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcalendarcore] [Bug 425498] New: The calender widget is extremely large
https://bugs.kde.org/show_bug.cgi?id=425498 Bug ID: 425498 Summary: The calender widget is extremely large Product: frameworks-kcalendarcore Version: 5.73.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- Created attachment 130967 --> https://bugs.kde.org/attachment.cgi?id=130967=edit Opened calendar widget takes up too much space SUMMARY I think the calendar widget mistakes my high resolution monitor for a smartphone It's size is disproportionally large. For example it uses more than 20cm2 of my valuable screen estate to display "No events for today". See screenshot. (The events mechanism is not useful for most users, since you cannot enter events except by installing a complete suite of applications they don't need, but that is another discussion.) STEPS TO REPRODUCE 1. start kde 2. click on calendar widget 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425492] Okular introduces an artificial delay when scrolling through a file
https://bugs.kde.org/show_bug.cgi?id=425492 --- Comment #1 from John van Spaandonk --- I made an error in the bug report, For all clarity: EXPECTER RESULT: I expect to be able to scroll to the document at the limit of computing power of my computer. No artificial delays. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425492] New: Okular introduces an artificial delay when scrolling through a file
https://bugs.kde.org/show_bug.cgi?id=425492 Bug ID: 425492 Summary: Okular introduces an artificial delay when scrolling through a file Product: okular Version: 1.11.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- SUMMARY There is an artificial delay in okular that prevents me from quickly paging up/down through a document. This delay should be removed. Perhaps it is related to an attempt to implement an (unnecessary) smooth scroll? If so then please remove this unneeded smooth scroll feature, it is in the way of a good user experience. STEPS TO REPRODUCE 1. start okular 2. load pdf 3. scroll OBSERVED RESULT EXPECTED RESULT I have to wait until the smooth scroll is completed before I can scroll again. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 424929] New: Wrong audio target indicated in audio control widget
https://bugs.kde.org/show_bug.cgi?id=424929 Bug ID: 424929 Summary: Wrong audio target indicated in audio control widget Product: plasma-pa Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: j...@van-spaandonk.nl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 130580 --> https://bugs.kde.org/attachment.cgi?id=130580=edit picture showing two radio buttons lighted SUMMARY I noticed that audio is playing on headphones, so I want to use the volume control widget to switch to USB speaker. Clicking the USB switches the audio to USB but now two radio buttons are lighted: the one for the headphones and the one for my usb speaker (see screenshot). I first thought it is a new feature: you can now play audio on multiple targets at once. But no, the headphones radio button always remains lighted even though audio is switched correctly by pressing the buttons. So it seems only a display problem. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: neon, latest version (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420313] Night color location detection returns the wrong location
https://bugs.kde.org/show_bug.cgi?id=420313 John van Spaandonk changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from John van Spaandonk --- Indeed Nate! I played a bit and the setting is caused by my VPN to another time zone. I switched to manual time zone in Nightlight now and the issue seems resolved. Although this makes me feel a little stupid I will continue trying to create good bug reports :-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420313] Night color location detection returns the wrong location
https://bugs.kde.org/show_bug.cgi?id=420313 John van Spaandonk changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420313] New: Night color does not respect my time zone
https://bugs.kde.org/show_bug.cgi?id=420313 Bug ID: 420313 Summary: Night color does not respect my time zone Product: systemsettings Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: j...@van-spaandonk.nl CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set the time zone to Amsterdam in system settings - date & time 2. open night color module in system settings 3. OBSERVED RESULT Observe longitude and lattitude that do not match with Amsterdam) Lattitude: 25,8295, Longitude: -80,2927 EXPECTED RESULT I would expect to see the lattitude and longitude of Amsterdam, About 5 and 52 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION This worked before but stopped working a few weeks ago. Sorry that I cannot be more specific. At the moment I use night color in manual mode. Another bug: Night color shows latitude 0 Longitude 0 before quickly updating it to the above reporting results. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418653] System settings audio module extremely narrow
https://bugs.kde.org/show_bug.cgi?id=418653 John van Spaandonk changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from John van Spaandonk --- solved in plasma 5.18.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418653] New: System settings audio module extremely narrow
https://bugs.kde.org/show_bug.cgi?id=418653 Bug ID: 418653 Summary: System settings audio module extremely narrow Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- Created attachment 126686 --> https://bugs.kde.org/attachment.cgi?id=126686=edit wrongly scaled audio settings SUMMARY See screenshot. Unusable without rescaling STEPS TO REPRODUCE 1. Start kde from scratch 2. press kde button - type audio - press enter 3. OBSERVED RESULT See screenshot. EXPECTED RESULT no scrolbar, everything visible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.2 -> I could not select this in the obligatory "Version" field KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION See attachment for information about my system. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 417502] Sleep does not work if you close the laptop lid too fast after specifying that you want to power off.
https://bugs.kde.org/show_bug.cgi?id=417502 --- Comment #2 from John van Spaandonk --- On 2020-02-12 17:15, Kai Uwe Broulik wrote: > https://bugs.kde.org/show_bug.cgi?id=417502 > > Kai Uwe Broulik changed: > > What|Removed |Added > > CC||k...@privat.broulik.de > > --- Comment #1 from Kai Uwe Broulik --- > There's definitely code in Powerdevil that checks if ksmserver is exiting and > then ignores the suspend request. > Possible that PowerDevil at this point was already killed and then logind > takes > over and just goes ahead anyway. > I think that powermanagement in particular benefits from a system-wide development view. Too bad I do not have any experience with this. As a first step, is this problem reproducable? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 417502] Sleep does not work if you close the laptop lid too fast after specifying that you want to power off.
https://bugs.kde.org/show_bug.cgi?id=417502 John van Spaandonk changed: What|Removed |Added CC||j...@van-spaandonk.nl -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 417502] New: Sleep does not work if you close the laptop lid too fast after specifying that you want to power off.
https://bugs.kde.org/show_bug.cgi?id=417502 Bug ID: 417502 Summary: Sleep does not work if you close the laptop lid too fast after specifying that you want to power off. Product: Powerdevil Version: 5.18.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- SUMMARY My laptop is set up to power off if I press the power button, and to go to sleep if I close the laptop lid. No screensaver active when the problem occurs. Also no full-screen video. STEPS TO REPRODUCE 1. Press power button to put laptop to sleep 2. Close laptop lid directly after pressing power button 3. that's it! OBSERVED RESULT Laptop goes to sleep (suspend?), apparently erroneously triggered by closing the laptop lid. EXPECTED RESULT The laptop should power off. I asked it to and it should not ignore it and do something else instead. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This bug has been there for years. It looks like the developers did not test this scenario. No idea if the problem is in Powerdevil or not, feel free to reassign to appropriate component. Also let me know what other info you want! -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 416035] Bluetooth does not connect automatically to a paired device
https://bugs.kde.org/show_bug.cgi?id=416035 --- Comment #1 from John van Spaandonk --- I experimented some more: Bluetooth ONLY connects to a device automatically if the device is switched on AFTER the laptop has booted. So after boot, bluetooth does not connect to an already-on speaker, even though I configured it to do this. Is this on purpose or is it an oversight? The behaviour is different to other devices that can connect to a Bluetooth speaker. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416229] Zooming out with CTRL+mousewheel does not work correctly anymore
https://bugs.kde.org/show_bug.cgi?id=416229 --- Comment #6 from John van Spaandonk --- (In reply to Yuri Chornoivan from comment #2) > Can you tell if the "View -> Trim view -> Trim margins" menu item is > selected? > > Thanks in advance for your answer. [this reply might be double with another reply I did via email but I changed it a bit] Yes indeed, If I deselect "Trim Margins" and also do not select "Trim to selection" it works as expected. Please close this bug report if you do not agree to the suggestion below. I still think this is a usability issue. While I now understand the behavior, my honest expectation was that the keyboard controls for zoom would always mirror the behavior of the "zoom level" box, so overriding any trim views. I think it makes perfect sense if the keyboard controls just mirror making a selection in the "zoom level" window. Therefore they should have the same freedom in entering another zoom level, irrespective of the selected "zoom to" option. ps. I am very happy that you react instantaneously to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416229] Zooming out with CTRL+mousewheel does not work correctly anymore
https://bugs.kde.org/show_bug.cgi?id=416229 --- Comment #5 from John van Spaandonk --- On 2020-01-14 18:17, Yuri Chornoivan wrote: > https://bugs.kde.org/show_bug.cgi?id=416229 > > Yuri Chornoivan changed: > > What|Removed |Added > > CC||yurc...@ukr.net > > --- Comment #2 from Yuri Chornoivan --- > Can you tell if the "View -> Trim view -> Trim margins" menu item is selected? > > Thanks in advance for your answer. > Yes indeed, If I deselect "Trim Margins" and also do not select "Trim to selection" it works as expected. I will close this report then. In all honesty, while I now understand the behavior, my honest expectation was that the keyboard controls for zoom would always zoom, overriding / disabling any trim views. But I understand why you see the keyboard controls as mirroring the behavior of the "zoom level" window, and not overriding other settings. ps. I am very happy that you react instantaneously to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416229] New: Zooming out with CTRL+mousewheel does not work correctly anymore
https://bugs.kde.org/show_bug.cgi?id=416229 Bug ID: 416229 Summary: Zooming out with CTRL+mousewheel does not work correctly anymore Product: okular Version: 1.9.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- SUMMARY Zooming with CTRL+mousewheel does not work correctly anymore since a while ago. This behavior changed somewhere in the last half year. STEPS TO REPRODUCE 1. Open a document in Okular 2. Try to zoom out by holding the CTRL key and rolling the mouse wheel towards you OBSERVED RESULT Loosely speaking, Okular can zoom in but cannot zoom out, after zooming in I observe the values in the "zoom input box" under the menu bar jump to "fit width" and after that I cannot zoom out further than that. More details (help you find the bug): After I select 17% zoom value, I can zoom in and out, but if I zoom in past the "fit page" value, then that value becomes the maximum: I cannot zoom out any further. When I then zoom in still further I meet the "fit width" value and then that value becomes the maximum: I cannot zoom out any further. So you can zoom in, but cannot zoom out past the fixed values in the "zoom box" that you encounter along the way. So somehow when these values are selected, the zooming with the keyboard/mouse is affected. EXPECTED RESULT I should be able to zoom all the way out until the maximum value is reached. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION 1. Zooming in and out in Firefox with CTRL + mouse wheel works as expected 2. I can zoom by selecting (using the mouse) an explicit zoom value in the "zoom input box". So it is just using the described keys that does not work with Okular, reducing its usability (accessibility). -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 416035] New: Bluetooth does not connect automatically to a paired device
https://bugs.kde.org/show_bug.cgi?id=416035 Bug ID: 416035 Summary: Bluetooth does not connect automatically to a paired device Product: Bluedevil Version: 5.17.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: j...@van-spaandonk.nl Target Milestone: --- SUMMARY KDE does not connect automatically to a paired Bluetooth speaker. STEPS TO REPRODUCE 1. Pair the Bluetooth speaker, set it as default device 2. Connect to it, using the plasmoid menu 3. Switch off notebook 4. Switch on notebook, login to plasma OBSERVED RESULT The speaker is visible in the Bluetooth plasmoid, but no automatic connection is made, although it is set as the default device EXPECTED RESULT I expect the connection to be made automatically as soon as both plasma and Bluetooth speaker are both turned on. SOFTWARE/OS VERSIONS See bug properties ADDITIONAL INFORMATION If desired I could do some more experiments to narrow down the problem, please tell me what info you need. BTW: I selected "system tray" as "Component", no idea if this is correct. Additional remark: I feel that you cannot expect a normal user to make a useful selection here! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415237] New: Crash in system settings
https://bugs.kde.org/show_bug.cgi?id=415237 Bug ID: 415237 Summary: Crash in system settings Product: systemsettings Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: 1. start system settings by pressing windows icon and typing system settings and pressing enter 2. click global theme 3. click plasma style 4. click application style 5. Click (in the left part) GNOME/GTK Application Style (the first time, system settings became sluggish here) 6. Click (in the left part) Window Decorations - At this stage system setting crashes I managed to reproduce it one time. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff242b5e800 (LWP 30097))] Thread 8 (Thread 0x7ff1f743a700 (LWP 30112)): #0 0x7ff23e0890b4 in __GI___libc_read (fd=42, buf=0x7ff1f7439b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff2375462d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2375010b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff237501570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff2375016dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff23e9e0b9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff23e98106a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff23e79c3aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff23c540815 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7ff23e79db52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff2398c06db in start_thread (arg=0x7ff1f743a700) at pthread_create.c:463 #11 0x7ff23e09a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7ff208c98700 (LWP 30110)): #0 0x7ff23e08dbf9 in __GI___poll (fds=0x7ff1fc107c70, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff2375015c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2375016dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff23e9e0b9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff23e98106a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff23e79c3aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff23c540815 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7ff23e79db52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff2398c06db in start_thread (arg=0x7ff208c98700) at pthread_create.c:463 #9 0x7ff23e09a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7ff20c5ff700 (LWP 30103)): #0 0x7ff237547649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff237500b33 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2375014fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff2375016dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff23e9e0b9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff23e98106a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff23e79c3aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff23c540815 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7ff23e79db52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff2398c06db in start_thread (arg=0x7ff20c5ff700) at pthread_create.c:463 #10 0x7ff23e09a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ff2150c6700 (LWP 30102)): #0 0x7ff23e08dbf9 in __GI___poll (fds=0x7ff210004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff2375015c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2375016dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff23e9e0b9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
[okular] [Bug 409852] Okular takes an extreme amount of time to load a djvu file over samba
https://bugs.kde.org/show_bug.cgi?id=409852 --- Comment #5 from John van Spaandonk --- Good idea nate! On the workstation: Same problem with the smb client, server timeout. Tried with my kde laptop, which was kubuntu 18.04 also but I managed to rebase it to muon, it is current. So plasma 5.16.2 I think. Here the kio-slave works: book read in about 2 seconds, over wifi even. using (in another Dolphin tab) a mounted smb share (via fstab) I had to kill okular after 1:30 had passed. Laptop is 8 years old dell XPS, not as fast as the desktop. Note that Okular blocks also that Dolphin instance until I kill it. But at least I managed to show that using smb: on the laptop it is much faster than via a mounted drive on the desktop. Same book takes about 40 seconds on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409852] Okular takes an extreme amount of time to load a djvu file over samba
https://bugs.kde.org/show_bug.cgi?id=409852 --- Comment #3 from John van Spaandonk --- Nate thanks for looking into this. Answering your information request: 1. I tried recent files from the Okular file menu, also takes very long / same as double clicking in Dolphin 2. smb://192.168.1.2/data/ (this is the literal string I typed in Dolphin) reports a timeout on server in Dolphin. TheKIO smb slave does not seem to work for me. The address is correct. 3. The file opens in kate in about .5 second, the same file in Okular in about 30 seconds. 4. Using Okular to open a PDF document is not as fast as local, but still about 10 times faster than a .djv or .djvu file. For me the analysis points to the .djv part of Okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409852] Okular takes an extreme amount of time to load a djvu file over samba
https://bugs.kde.org/show_bug.cgi?id=409852 --- Comment #1 from John van Spaandonk --- Additional information: other Okular document windows stay usable as well. So only the newly created Okular window is frozen, and displays part of what was under it, since it does not update. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409852] New: Okular takes an extreme amount of time to load a djvu file over samba
https://bugs.kde.org/show_bug.cgi?id=409852 Bug ID: 409852 Summary: Okular takes an extreme amount of time to load a djvu file over samba Product: okular Version: 1.3.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DjVu backend Assignee: okular-de...@kde.org Reporter: j...@van-spaandonk.nl Target Milestone: --- SUMMARY Loading a book (djvu) from my NAS in okular can take up to 30 seconds. The problems seems less big with PDF books. Book size 2 to 3 megabytes, so not particularly big. Copying the same book from the NAS by dragging it from Dolphin to a local folder (SSD) takes about .2 seconds. Opening in Okular from there takes about .2 seconds (difficult to time, but very fast). So the underlying infrastructure seems to work fine, therefore I think the problem is related to Okular. I conclude that when I open a document in Okular over samba I pay a performance penalty of a factor of 50 - 100. This makes it unusable to browse books there. My setup I used to reproduce this problem. Kubuntu18.04, desktop computer connected to NAS via 1Gbit ethernet cable. Note that this is a fast network setup, so now slow links / wireless etc. The NAS drive is listed in the fstab with this line, and thus mounted a system startup: /192.168.1.2/NAME/media/MOUNT_POINT cifs user=,password=,rw,user,nosuid,uid=1000,gid=100,_netdev,vers=1.00 0 STEPS TO REPRODUCE 1. Browse to the document folder on the NAS 2. Double click a document to open it in Okular 3. OBSERVED RESULT The whole Okular interface blocks for 30-40 seconds (also does not redraw so it messes up the desktop view). The rest of the desktop is usable as normal. EXPECTED RESULT View the book in Okular in less than .5 seconds SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04 LTS (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION I used journalctl to look in the syslog, but all it says is ResourceScoreUpdated: "4625dd2c-8a74-4017-8be6-6dc7c47d29ab" "okularapplication_djvu" . -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 402116] Audio device switch notification when confirmation dialog sounds occur
https://bugs.kde.org/show_bug.cgi?id=402116 --- Comment #2 from John van Spaandonk --- I am using kubuntu 18.04, forgot to tell this -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 402116] Audio device switch notification when confirmation dialog sounds occur
https://bugs.kde.org/show_bug.cgi?id=402116 John van Spaandonk changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 402116] Audio device switch notification when confirmation dialog sounds occur
https://bugs.kde.org/show_bug.cgi?id=402116 John van Spaandonk changed: What|Removed |Added CC||j...@van-spaandonk.nl --- Comment #1 from John van Spaandonk --- Created attachment 118807 --> https://bugs.kde.org/attachment.cgi?id=118807=edit Inappropriate audio device switching dialog For me this bug occurs even when the audio notifications are switched off, so they do not even produce any sound. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 396799] New: Please add "send to device xxx" to menu of each playback stream
https://bugs.kde.org/show_bug.cgi?id=396799 Bug ID: 396799 Summary: Please add "send to device xxx" to menu of each playback stream Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: j...@van-spaandonk.nl CC: plasma-b...@kde.org Target Milestone: --- Scenario: I plug in the headphone in my pc (not laptop - no autosensing headphone jacket) I need to manually reroute the playing audio application (eg youtube) from the usb speakers to the headphone. I want to use the plasma "audio volume" widget to change the playback stream in the "Applications" tab to a certain device (one of these visible in the "Devices" tab) I try to click the menu on the right of the playback stream but this does not offer an opportunity to route the stream to a certain device. I am now stuck - have to resort to pavucontrol, which of course offers this functionality. (as does Linux Mint which I used until a few weeks ago) Distro: kubuntu 18.04 I searched on +audio +stream +device before entering this bug report and could not find a suitable one yet. Still I think one must already exist ... Please feel free to mark this one a duplicate in that case. ps I found out via a web search that you can long-click the icon to the left of the Application, which then opens up the devices tab, after which you can drop on a certain device. I think this is not what we want: not discoverable, not in line with other solutions out there. Thanks! John van Spaandonk -- You are receiving this mail because: You are watching all bug changes.
