[Discover] [Bug 449530] Discover crashes on start
https://bugs.kde.org/show_bug.cgi?id=449530 --- Comment #2 from John Clark --- I can avoid the crash by disabling feedback in System Settings -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 449530] Discover crashes on start
https://bugs.kde.org/show_bug.cgi?id=449530 John Clark changed: What|Removed |Added CC||john.cl...@cantab.net --- Comment #1 from John Clark --- Created attachment 146219 --> https://bugs.kde.org/attachment.cgi?id=146219=edit Backtrace Backtrace of the offending crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 449530] New: Discover crashes on start
https://bugs.kde.org/show_bug.cgi?id=449530 Bug ID: 449530 Summary: Discover crashes on start Product: Discover Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: john.cl...@cantab.net CC: aleix...@kde.org Target Milestone: --- SUMMARY Crash on start: [~]$ plasma-discover ** (process:27020): WARNING **: 22:37:13.800: Not changing AppStream cache location: No longer supported. QDir::mkpath: Empty or null file name kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 adding empty sources model QStandardItemModel(0x55db5651a0d0) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/qt/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:14:1: QML ToolBarPageHeader: Binding loop detected for property "implicitWidth" (process:27020): Fwupd-CRITICAL **: 22:37:14.215: fwupd_client_download_bytes_async: assertion 'url != NULL' failed kf.newstuff.core: "Error transferring https://distribute.kde.org/khotnewstuff/fonts-providers.xml - server replied: Not Found" KNS error in "Fonts" : KNSCore::ProviderError "Loading of providers from file: https://distribute.kde.org/khotnewstuff/fonts-providers.xml failed" QVariant(QString, "https://distribute.kde.org/khotnewstuff/fonts-providers.xml;) invalid kns backend! "/usr/share/knsrcfiles/kfontinst.knsrc" because: "Invalid Fonts backend, contact your distributor." org.kde.plasma.libdiscover: Discarding invalid backend "kfontinst.knsrc" kns error "/usr/share/knsrcfiles/kfontinst.knsrc" "Invalid Fonts backend, contact your distributor." org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" QOpenGLFunctions created with non-current context 29 -- exe=/usr/bin/plasma-discover 17 -- platform=wayland 24 -- appname=plasma-discover 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=27020 18 -- appversion=5.23.5 21 -- programname=Discover 63 -- bugaddress=https://bugs.kde.org/enter_bug.cgi?product=Discover 30 -- productname=discover/discover 12 -- startupid=0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 27020 KCrash: Arguments: /usr/bin/plasma-discover The Wayland connection experienced a fatal error: Bad file descriptor kf.kio.slaves.file: readData() returned -1 STEPS TO REPRODUCE 1. Launch plasma-discover 2. 3. OBSERVED RESULT Crashes EXPECTED RESULT Running SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also seen on 5.23.90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449385] User changes can't be saved with accountsservice-22.04.62
https://bugs.kde.org/show_bug.cgi?id=449385 --- Comment #11 from John --- (In reply to Nate Graham from comment #10) > Darn. Guess we gotta fix it. Haha -- bro my bad i break it to often then i should be; just be happy your not as busy to fix my errors :D -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449512] New: Google Groupware does not display calendar events or tasks
https://bugs.kde.org/show_bug.cgi?id=449512 Bug ID: 449512 Summary: Google Groupware does not display calendar events or tasks Product: korganizer Version: 5.18.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: kde.jr...@grifent.com Target Milestone: --- SUMMARY *** The Google Calendar does not display even though enabled and authorized. *** STEPS TO REPRODUCE 1. Open korganizer 2. Observe that there are no calendar events, tasks, etc 3. reauthorize. Same result. OBSERVED RESULT No events, tasks, etc. EXPECTED RESULT Events and tasks should display and be editable. SOFTWARE/OS VERSIONS Fedora 35 Linux/KDE Plasma: Linux (x86_64) release 5.15.18-200.fc35.x86_64 / 5.90.0-1.fc35.x86_64 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449484] Could not get permission to save user
https://bugs.kde.org/show_bug.cgi?id=449484 John changed: What|Removed |Added Version|5.23.5 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449484] New: Could not get permission to save user
https://bugs.kde.org/show_bug.cgi?id=449484 Bug ID: 449484 Summary: Could not get permission to save user Product: systemsettings Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Settings Assignee: plasma-b...@kde.org Reporter: jheckman...@zohomail.com Target Milestone: --- new bug not sure if you fixed it or not.. the users/remove users in kde is bugged out, works okay on live ISO but when u install the OS the user added does not work as well the change password comes up with this "Could not get permission to save user" System: Kernel: 5.16.4-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0 parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=3796d841-e6f4-4301-a6e8-d0536f11f176 rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 resume=UUID=db8c9204-9512-4aa0-91ca-775989fd8d4e loglevel=3 Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux Machine: Type: Desktop Mobo: ASRock model: H470 Phantom Gaming 4 serial: UEFI: American Megatrends v: P1.10 date: 05/15/2020 CPU: Info: model: Intel Core i5-10400 bits: 64 type: MT MCP arch: Comet Lake family: 6 model-id: 0xA5 (165) stepping: 5 microcode: 0xEC Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB Speed (MHz): avg: 4190 high: 4310 min/max: 800/4300 scaling: driver: intel_pstate governor: performance cores: 1: 4160 2: 4201 3: 4201 4: 4207 5: 4203 6: 4202 7: 4204 8: 4310 9: 4188 10: 4114 11: 4154 12: 4147 bogomips: 69597 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: eVga.com. driver: nvidia v: 510.47.03 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1f82 class-ID: 0300 Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 55 s-size: 887x499mm (34.9x19.6") s-diag: 1018mm (40.1") Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 77 size: 631x354mm (24.8x13.9") diag: 724mm (28.5") OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 510.47.03 direct render: Yes Audio: Device-1: Intel Comet Lake PCH cAVS vendor: ASRock driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403 Device-2: NVIDIA vendor: eVga.com. driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403 Sound Server-1: ALSA v: k5.16.4-zen1-1-zen running: yes Sound Server-2: PulseAudio v: 15.0 running: no Sound Server-3: PipeWire v: 0.3.44 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4d class-ID: 0200 IF: eno1 state: up speed: 100 Mbps duplex: full mac: Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel bus-ID: 02:00.0 chip-ID: 8086:2725 class-ID: 0280 IF: wlp2s0 state: down mac: Bluetooth: Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-7.3:7 chip-ID: 8087:0032 class-ID: e001 Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: Drives: Local Storage: total: 2.3 TiB used: 216.4 GiB (9.2%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3X0C-00SJG0 size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: rev: 10WD temp: 35.9 C scheme: GPT ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD100 size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: rev: 1A scheme: GPT ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10EURX-63UY4Y0 size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: rev: 1A01 scheme: GPT ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: PNY model: USB 2.0 FD size: 28.91 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: rev: PMAP scheme: MBR SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? Partition: ID-1: / raw-size: 431.1 GiB
[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.
[krita] [Bug 449011] New: qmic missing
https://bugs.kde.org/show_bug.cgi?id=449011 Bug ID: 449011 Summary: qmic missing Product: krita Version: 5.0.2 Platform: Mint (Ubuntu based) OS: Other Status: REPORTED Severity: normal Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: crazyjer...@gmail.com Target Milestone: --- The QMic plugin is missing from the krita repository (With the update eliminating the use of a separate appimage for the plugin, there isn't an obvious way to work around it with the binary release) STEPS TO REPRODUCE 1. 2. 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.
[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.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 John Miller changed: What|Removed |Added CC||neuromance...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448652] Overview Effect: Panels on top over search and doesn't show Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=448652 --- Comment #3 from john --- Cool!!! :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 --- Comment #9 from john --- (In reply to Nate Graham from comment #8) > Definitely sounds like you're using the Portal dialog rather than the > plasmazilla package, and I can reproduce it. ?! But... Is that default on neon??? Because I don't remember changing anything like that! How can I get the "plasmazilla"? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 --- Comment #7 from john --- Let me just add that i can't save to remote folders from Firefox either (but i guess you already knew that!) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 john changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from john --- > Is Firefox by any chance using the xdg-portal dialog? Is GTK_USE_PORTALS=1 > set in the environment? If you force GTK_USE_PORTALS to 0 and then run > Firefox, do you get a different (GTK) dialog? If so, then we're talking > about the xdg-portal dialog. > > I strongly suspect that we are talking about the xdg-portal dialog (since > normally Firefox uses the GTK dialog) but I'd like to be sure. OK, i've made some tests using the command "GTK_USE_PORTAL=1 /usr/lib/firefox/firefox -p default" and "GTK_USE_PORTAL=0 /usr/lib/firefox/firefox -p default" The GTK version does not show any remote folders, but judging by the Lubuntu's in the same network i believe it's a question of configuring the shared folders... The Qt version showed the the remote folders but did not allow uploads. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 john changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448652] Overview Effect: Panels on top over search and doesn't show Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=448652 john changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448652] Overview Effect: Panels on top over search and doesn't show Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=448652 --- Comment #1 from john --- Created attachment 145583 --> https://bugs.kde.org/attachment.cgi?id=145583=edit Overview Effect -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448652] New: Overview Effect: Panels on top over search and doesn't show Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=448652 Bug ID: 448652 Summary: Overview Effect: Panels on top over search and doesn't show Virtual Desktops Product: kwin Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: johnmaveric...@mail.com Target Milestone: --- SUMMARY If one has Panels on top they come up over the search field (as shown on the attached screenshot). Also, Virtual Desktops are not shown either (they don't show with panels on bottom as well) STEPS TO REPRODUCE 1. move/create a panel on top 2. activate the overview effect OBSERVED RESULT Panel overlaps Search field Virtual Desktops are not shown EXPECTED RESULT Search field should be fully visible Virtual Desktops should be seen SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-46-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 --- Comment #5 from john --- Uploaded Firefox Upload Dialog. About GwenView: I can open the remote files from File>Open with no problems The dialog is apparently the same from firefox (the GUI is the same) About the xdg-portal dialog: Where can i change that? I thought it was in Firefox's about:config, but i'm apparently wrong... need some help here -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 --- Comment #4 from john --- Created attachment 145581 --> https://bugs.kde.org/attachment.cgi?id=145581=edit Firefox Upload Dialog -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 john changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from john --- (In reply to Nate Graham from comment #1) Hi Nate. > 1. Can you provide a screenshot of what the upload dialog looks like? Is it > the GNOME dialog or the KDE Dialog? I though that you only needed screenshots because of the error. I'm away of any of the Linux machines so I'll only be able to provide the screenshot next Monday. I can advance however that the problem mentioned is in the KDE dialog (I currently work with 4 distinct systems: pure KDE neon, openSUSE Argon, Lubuntu and Windows 10. This problem described happens in neon. SUSE is one machine not in a network and lubuntu machines use GIO) > 2. Are you accessing the Windows share from its URL (e.g. smb://something) > or by a path to a local mount? I'm accessing the Windows share from its URL (e.g. smb://something) > 3. Does the same thing happen if you try to open the file from Gwenview? If I, in a remote image double-click it, it opens in Gwenview with no problem. Same thing happens in office documents. Now, if you mean going to File>open... I can't answer now. Only Monday when I'm back. (I believe I already tried that before, however, and that I was able to open the pictures - but I'm not sure. Next Monday I'll be able to reply with certain) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 448486] New: Unable to upload files from remote/network folders
https://bugs.kde.org/show_bug.cgi?id=448486 Bug ID: 448486 Summary: Unable to upload files from remote/network folders Product: frameworks-kio Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: johnmaveric...@mail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY It's not possible to upload files from remote/network folders to web services such as google images, gmail, outlook or any other web services. The only workaround is to copy/paste the files from the remote folder to a local folder and then upload them. STEPS TO REPRODUCE 1. Open Firefox (or any other browser) 2. go to images.google.com 3. try to upload an image from a MS Windows remote folder OBSERVED RESULT File does not upload - fails silently ( there is no error message - it's as if one canceled the action) EXPECTED RESULT user should be able to upload files from anywhere: either local or any remote folder with the same ease as we can on any other OS. SOFTWARE/OS VERSIONS Windows: 10 v21h2 and Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-46-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION maybe if the browser was using "kdialog --getopenurl" it would work... Relevant/maybe related Bugs: https://bugs.kde.org/show_bug.cgi?id=406323 https://bugs.kde.org/show_bug.cgi?id=213254 https://bugzilla.mozilla.org/show_bug.cgi?id=526293 https://bugzilla.mozilla.org/show_bug.cgi?id=682838 https://bugzilla.mozilla.org/show_bug.cgi?id=719952 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448244] New: Unable to symlink config for managing as dotfiles.
https://bugs.kde.org/show_bug.cgi?id=448244 Bug ID: 448244 Summary: Unable to symlink config for managing as dotfiles. Product: lattedock Version: 0.10.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: johnnyfl...@gmail.com Target Milestone: --- SUMMARY *** Hi there - This may not be a bug, but wanted to report anyway. I've got latte set up how I want and would like to manage the config as dotfiles so I can reconfigure easily after a reinstall. I'm currently using dotbot (https://github.com/anishathalye/dotbot) solution. This centralises all the config files and symlinks them over to the original locations - allowing for easier version control. Most work fine, however latte doesn't seem to like it. If i symlink ~/.config/lattedockrc ~/.config/latte/My Layout.layout.latte Then latte seems to open with all config set to default and the default layout (as it if couldn't read lattedockrc). If I copy the files back to the original location then all works fine. Is there a way to make latte compatible with config symlinked elsewhere - so that it can be managed under version control? Or maybe I'm doing something wrong. STEPS TO REPRODUCE 1. Fresh install of Manjaro 2. mkdir ~/.dotfiles 3. Setup dotbot https://github.com/anishathalye/dotbot in ~/.dotfiles 4. Create a sample layout ( in my instance My Layout). 5. Switch to that layout in latte settings 6. Copy ~/.config/lattedockrc to .dotfiles/config/lattedockrc 7. Copy ~/.config/latte/My Layout.layout.latte to ~/.dotfiles/config/latte/My Layout.layout.latte 8. Create file install.conf.yaml in ~/.dotfiles with following ``` - defaults: link: relink: true - create: - ~/.config/latte - link: ~/.config/lattedockrc: path: config/lattedockrc force: true ~/.config/latte/My Layout.layout.latte: path: config/latte/My Layout.layout.latte force: true ``` 9. run ~/.dotfiles/install OBSERVED RESULT Symlinks created, however on reboot it seems to go back to default settings (seems not to read lattedockrc file via symlink??). Any changes are reset next reboot. EXPECTED RESULT All settings remain as is with my custom layout. Any changes are saved in ~/.dotfiles/config/lattedockrc or layout file for version control. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro linux - 5.15.12 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446075] several crashes
https://bugs.kde.org/show_bug.cgi?id=446075 --- Comment #10 from John Clark --- This still looks like something is killing your X Server: Gdk-Message: 22:10:55.022: xsnow: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Exception in thread XInterface-thread: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3/dist-packages/autokey/interface.py", line 1206, in run self.recordDisplay.record_enable_context(self.ctx, self.__processEvent) File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 239, in enable_context EnableContext( File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 220, in __init__ rq.ReplyRequest.__init__(self, *args, **keys) File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1369, in __init__ self.reply() File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1381, in reply self._display.send_and_recv(request = self._serial) File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 610, in send_and_recv raise self.socket_error Xlib.error.ConnectionClosedError: Display connection closed by server XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 8763 requests (8763 known processed) with 0 events remaining. There is too much going on on this machine for me to be much more helpful than this. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #14 from John Bennett --- New install of Tumbleweed (20220106 + KDE Plasma V5.23.4) on Dell Optiplex 9020 1TB ssd boot drive/16gb RAM Hardware. Still VERY intermittent - mostly (95%) not working. Have tried different settings in both Screensaver and Power. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 John Bennett changed: What|Removed |Added CC||hornets...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440350] Screensaver never runs after logon.
https://bugs.kde.org/show_bug.cgi?id=440350 --- Comment #13 from John Bennett --- Have done a total reinstall of Tumbleweed (currently 20220106; KDE Plasma V5.23.4), with new user, and still intermittent at best. Mostly not working. Hardware is Dell Optiplex 9020, with 1TB SSD, 16GB RAM. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448139] New: started discover nd could not get to the location lower left of screen. A message came up to report a bug.
https://bugs.kde.org/show_bug.cgi?id=448139 Bug ID: 448139 Summary: started discover nd could not get to the location lower left of screen. A message came up to report a bug. Product: Discover Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ocrho...@comcast.net CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. unknown 2. 3. OBSERVED RESULT am restarting system after having terminated all other apps EXPECTED RESULT should have been able to search for updates SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.22.5 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION kernel: 5.15.12-100.fc34.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448098] Trying to drag tabs in Chrome to reorder them suddenly always produces a new window
https://bugs.kde.org/show_bug.cgi?id=448098 --- Comment #2 from John Smith --- Thanks, much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448104] New: System settings crashes on opening Power menu
https://bugs.kde.org/show_bug.cgi?id=448104
Bug ID: 448104
Summary: System settings crashes on opening Power menu
Product: systemsettings
Version: 5.23.4
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: hornets...@gmail.com
Target Milestone: ---
Application: systemsettings5 (5.23.4)
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Attempting to open Settings>System Settings>Power Management menu.
Immediately faults with "System Settings closed unexpectedly" message.
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fb212cfc506 in QComboBox::clear (this=0x556f74ade1b0) at
widgets/qcombobox.cpp:3049
#7 0x7fb1ff6f3714 in operator() (__closure=0x556f787011d0,
watcher=) at
/usr/src/debug/powerdevil5-5.23.4-1.2.x86_64/daemon/actions/bundled/powerprofileconfig.cpp:83
#8 0x7fb211f76393 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb0de9440,
r=0x7fb200011460, this=0x556f787011c0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9 doActivate (sender=0x556f783e5750, signal_index=3,
argv=0x7ffeb0de9440) at kernel/qobject.cpp:3886
#10 0x7fb211f6f85f in QMetaObject::activate (sender=,
m=m@entry=0x7fb210aa25e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeb0de9440)
at kernel/qobject.cpp:3946
#11 0x7fb210a8307f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#12 0x7fb211f6c33e in QObject::event (this=0x556f783e5750,
e=0x556f79d12af0) at kernel/qobject.cpp:1314
#13 0x7fb212bf1a7f in QApplicationPrivate::notify_helper (this=, receiver=0x556f783e5750, e=0x556f79d12af0) at
kernel/qapplication.cpp:3632
#14 0x7fb211f3fd2a in QCoreApplication::notifyInternal2
(receiver=0x556f783e5750, event=0x556f79d12af0) at
kernel/qcoreapplication.cpp:1064
#15 0x7fb211f42d77 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x556f74830480) at
kernel/qcoreapplication.cpp:1821
#16 0x7fb211f97b83 in postEventSourceDispatch (s=s@entry=0x556f749336c0) at
kernel/qeventdispatcher_glib.cpp:277
#17 0x7fb20fa92d9f in g_main_dispatch (context=0x7fb208005000) at
../glib/gmain.c:3381
#18 g_main_context_dispatch (context=0x7fb208005000) at ../glib/gmain.c:4099
#19 0x7fb20fa93128 in g_main_context_iterate
(context=context@entry=0x7fb208005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#20 0x7fb20fa931df in g_main_context_iteration (context=0x7fb208005000,
may_block=1) at ../glib/gmain.c:4240
#21 0x7fb211f97204 in QEventDispatcherGlib::processEvents
(this=0x556f7493cf90, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7fb211f3e72b in QEventLoop::exec (this=this@entry=0x7ffeb0de9830,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7fb211f46a10 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7fb21249319c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#25 0x7fb212bf19f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#26 0x556f73cb610b in main (argc=, argv=) at
/usr/src/debug/systemsettings5-5.23.4-1.2.x86_64/app/main.cpp:208
[Inferior 1 (process 26586) detached]
Possible duplicates by query: bug 447910, bug 447904, bug 447759, bug 447676,
bug 447282.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 448098] New: Trying to drag tabs in Chrome to reorder them suddenly always produces a new window
https://bugs.kde.org/show_bug.cgi?id=448098 Bug ID: 448098 Summary: Trying to drag tabs in Chrome to reorder them suddenly always produces a new window Product: kwin Version: 5.22.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nexus20072...@gmail.com Target Milestone: --- SUMMARY Since the last time Chrome updated, clicking and dragging tabs always creates a new window and they can't be dragged back into another Chrome window. Keyboard shortcuts of Shift+Ctrl+PgUp/PgDn do allow tabs to be merged back into a window, but not being able to reorder tabs is a workflow killer. Several people seem to have reported the same thing with the latest Chrome build (97.0.4692.71) and I'm not 100% sure this is a KWin issue but it seemed the logical place to report for Plasma as it's to do with window management and the issue reportedly doesn't exist using the same Chrome build under Xfce or Gnome. There's current discussion of this issue at https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/935713 STEPS TO REPRODUCE 1. Install latest Chrome. 2. Create several new tabs. 3. Try to drag a tab to reorder them. OBSERVED RESULT A new window is created rather than tabs being able to be reordered. EXPECTED RESULT A new window should only be created if the tab is dragged out of the window, and tabs should be able to be dragged into an existing Chrome window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: using Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Not sure what would be relevant but will try to answer questions. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447993] New: Feature request: A mode that allows the device to act like a microphone to the computer.
https://bugs.kde.org/show_bug.cgi?id=447993 Bug ID: 447993 Summary: Feature request: A mode that allows the device to act like a microphone to the computer. Product: kdeconnect Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: jxftw2...@gmail.com Target Milestone: --- SUMMARY I recently found and interesting proprietary application called "WO Mic" it allows for a phone to be used as a microphone on a computer. I thought this would be a great feature for kdeconnect. SOFTWARE/OS VERSIONS Ideally multi platform. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446075] several crashes
https://bugs.kde.org/show_bug.cgi?id=446075 John Clark changed: What|Removed |Added Ever confirmed|1 |0 CC||john.cl...@cantab.net Status|CONFIRMED |REPORTED --- Comment #3 from John Clark --- Hi, a quick scan of your logs shows that you have a LOT going on on this machine. Ultimately it's an X Server crash which I would guess is resource exhaustion. You have many thousand (234145!!) instances of this: 2021-12-30 13:31:15: Initialising aMule 2.3.2 compiled with wxGTK2 v3.0.4 and Boost 1.67 2021-12-30 13:31:15: Checking if there is an instance already running... !2021-12-30 13:31:15: There is an instance of aMule already running 2021-12-30 13:31:15: (lock file: /home/duns/.aMule/muleLock) 2021-12-30 13:31:15: Raising current running instance. eventually followed by a crash: klauncher: Exiting on signal 15 klauncher: Exiting on signal 1 XIO: fatal IO error 4 (Interrupted system call) on X server ":0" after 2072 requests (2072 known processed) with 0 events remaining. XIO: fatal IO error 0 (Success) on X server ":0" after 234145 requests (234122 known processed) with 0 events remaining. Exception in thread XInterface-thread: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3/dist-packages/autokey/interface.py", line 1206, in run self.recordDisplay.record_enable_context(self.ctx, self.__processEvent) File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 239, in enable_context EnableContext( File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 220, in __init__ rq.ReplyRequest.__init__(self, *args, **keys) File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1369, in __init__ self.reply() File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1381, in reply self._display.send_and_recv(request = self._serial) File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 610, in send_and_recv raise self.socket_error Xlib.error.ConnectionClosedError: Display connection closed by server after that everything goes wrong, as you might expect. May I suggest stopping aMule and seeing if that helps? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438448] EVERY Login Discover-Notifier tells me to restart
https://bugs.kde.org/show_bug.cgi?id=438448 John Schroeder changed: What|Removed |Added CC||jschr...@gmail.com --- Comment #17 from John Schroeder --- (In reply to notrealname from comment #12) > removing /var/lib/PackageKit/offline-update-action fixed it for me This fixed it for me as well on my Arch Linux system. I have not had the issue since removing /var/lib/PackageKit/offline-update-action. I have run updates since then and the file has not been recreated. Would this bug be able to be closed then? It suspect that the issue has been fixed in a recent build of Discover (or other software). The only lingering issue is that /var/lib/PackageKit/offline-update-action needs to be removed manually if the file was created at the time that this was an issue. However, it might be correct to leave up to the user to remove. -- 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.
[Akonadi] [Bug 434725] Crashed when starting Kontact being started
https://bugs.kde.org/show_bug.cgi?id=434725 --- Comment #3 from John --- Created attachment 145038 --> https://bugs.kde.org/attachment.cgi?id=145038=edit New crash information added by DrKonqi akonadiserver (5.14.2 (20.04.2)) using Qt 5.12.7 - What I was doing when the application crashed: This happened twice this morning: 1. I had just booted the machine and closed two windows (from a saved session) when I was informed that Akonadi server had crashed. I was busy with time-sensitive operations so could not report it then but I told it to restart the app. Things continued fine, until I noticed later that I could no longer access teh system menu (neither mouse to teh bottom of the screen nor pressing the Meta key). until then I had been able to, so something died some time after I successfully used the system menu. I did have a look at the journal and there seemed to be some unusual Qt errors (versus the usual noise pretty much every time I change window focus). I cannot show the entries in question because (as I just discovered) the journal default is not to save its logs. Wish I could be mroe helpful here. 2. When I got home and started up, I was informed just after logging in that the Akonadi server had died yet again. Since I had time, I am submitting this, as I really need to be able to use my system: at the moment I cannot get to the system menu. Keyboard shortcuts such as changing desktops or starting Konsole windows thankfully work, but it's a real problem to work properly. I really hope this will get sorted out quickly, as I need to use my laptop. -- Backtrace (Reduced): #4 0x7fabb0f7026c in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x14) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #6 QBasicAtomicInteger::load (this=0x14) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 [...] #8 QString::operator= (this=this@entry=0x7fab5c06cba8, other=...) at tools/qstring.cpp:2417 #9 0x55abeb5a0875 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55abecd44a30, request=0x7fab5c06cb90, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/server/storage/itemretrievalmanager.cpp:176 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434725] Crashed when starting Kontact being started
https://bugs.kde.org/show_bug.cgi?id=434725 John changed: What|Removed |Added CC||k...@yellowacorn.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447513] Crash caused from using 'Search' form in the Pattern section of a Fill Layer
https://bugs.kde.org/show_bug.cgi?id=447513 --- Comment #5 from John --- I did some additional experimentation and it looks like the issue is somehow connected to the data in the local config folder. After backing the data up, I did some selective folder deletes (keeping the brushes and custom palettes). So far, seems to clear up the sporadic crashing and search form crashes. So, old data from 4.x seemed to be the culprit. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447513] Crash caused from using 'Search' form in the Pattern section of a Fill Layer
https://bugs.kde.org/show_bug.cgi?id=447513 --- Comment #3 from John --- I am using the appimage. Observed also that the same crash occurs with the Search in the fill gradient window. Perhaps it is affecting searches in general -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 447372] The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them....
https://bugs.kde.org/show_bug.cgi?id=447372 John Riley changed: What|Removed |Added CC||rileyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436981] Crash of almost the entire KDE related software ,whilist reconnecting a screen connected by a thunderbolt dock
https://bugs.kde.org/show_bug.cgi?id=436981 --- Comment #4 from John Doe --- (In reply to Nicolas Fella from comment #1) > *** Bug 438838 has been marked as a duplicate of this bug. *** Actually now i think it might have been an issue related to a substandard physical connection 樂 once i have upgraded from samsung 226BW, connected with a dp-dvi cable, to a BenQ EW3270UE, connected with dp over usb-c this exact problem has ceased to persist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447513] Crash caused from using 'Search' form in the Pattern section of a Fill Layer
https://bugs.kde.org/show_bug.cgi?id=447513 --- Comment #1 from John --- Created attachment 144862 --> https://bugs.kde.org/attachment.cgi?id=144862=edit long backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447513] New: Crash caused from using 'Search' form in the Pattern section of a Fill Layer
https://bugs.kde.org/show_bug.cgi?id=447513 Bug ID: 447513 Summary: Crash caused from using 'Search' form in the Pattern section of a Fill Layer Product: krita Version: 5.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: crazyjer...@gmail.com Target Milestone: --- Created attachment 144861 --> https://bugs.kde.org/attachment.cgi?id=144861=edit backtrace from terminal Krita crashes while trying to filter available patterns with the Search form STEPS TO REPRODUCE 1. Create a Fill layer and choose Pattern 2. Click the Search field and type anything OBSERVED RESULT crash EXPECTED RESULT filter based on text 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.
[krita] [Bug 447484] New: Smudge engine does not work with grayscale images
https://bugs.kde.org/show_bug.cgi?id=447484 Bug ID: 447484 Summary: Smudge engine does not work with grayscale images Product: krita Version: 5.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: crazyjer...@gmail.com Target Milestone: --- Created attachment 144839 --> https://bugs.kde.org/attachment.cgi?id=144839=edit Video demonstrating bug Smudge engine paints hard black squares on a grayscale image surrounding the layer's alpha. STEPS TO REPRODUCE 1. create/convert image to grayscale using default color profile OR convert a layer's color profile to grayscale 2. paint with any brush that smudges on the grayscale image or layer. OBSERVED RESULT Big black squares surrounding the brush EXPECTED RESULT Smudging as seen in an RGB image 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.
[konversation] [Bug 447372] New: The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them....
https://bugs.kde.org/show_bug.cgi?id=447372
Bug ID: 447372
Summary: The listed users and repositories cannot be searched
either because the resources do not exist or you do
not have permission to view them
Product: konversation
Version: unspecified
Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konversation-de...@kde.org
Reporter: rileyi...@gmail.com
Target Milestone: ---
Created attachment 144778
--> https://bugs.kde.org/attachment.cgi?id=144778=edit
The entire copy and paste from the Mac Terminal.
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. brew install kde-mac/kde/konversation
2.
3.
OBSERVED RESULT
[8/124] cd /tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src &&
/usr/local/Cellar/cmake/3.22.1/bin/cmake -E cmake_autogen
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src/CMakeFiles/KF5XmlGui_autogen.dir/AutogenInfo.json
Release && /usr/local/Cellar/cmake/3.22.1/bin/cmake -E touch
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src/KF5XmlGui_autogen/timestamp
&& /usr/local/Cellar/cmake/3.22.1/bin/cmake -E cmake_transform_depfile Ninja
gccdepfile /tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/src
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/src/KF5XmlGui_autogen/deps
/tmp/kf5-kxmlgui-20211221-15691-1qfjmfv/kxmlgui-5.89.0/build/CMakeFiles/d/68716d242549687c6c47d988432c4be78542d92ac9037136b18426c52902e1a8.d
ninja: build stopped: subcommand failed.
If reporting this issue please do so to (not Homebrew/brew or Homebrew/core):
kde-mac/kde
/usr/local/Homebrew/Library/Homebrew/utils/github/api.rb:304:in `raise_error':
Validation Failed: [{"message"=>"The listed users and repositories cannot be
searched either because the resources do not exist or you do not have
permission to view them.", "resource"=>"Search", "field"=>"q",
"code"=>"invalid"}] (GitHub::API::ValidationFailedError)
from /usr/local/Homebrew/Library/Homebrew/utils/github/api.rb:234:in
`open_rest'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:166:in
`search'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:34:in
`search_issues'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:67:in
`issues_for_formula'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:491:in
`fetch_issues'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:487:in `issues'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:541:in `dump'
from /usr/local/Homebrew/Library/Homebrew/brew.rb:155:in `rescue in
'
from /usr/local/Homebrew/Library/Homebrew/brew.rb:143:in `'
/usr/local/Homebrew/Library/Homebrew/formula.rb:2307:in `block in system':
Failed executing: cmake --build build (BuildError)
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2243:in `open'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2243:in `system'
from
/usr/local/Homebrew/Library/Taps/kde-mac/homebrew-kde/Formula/kf5-kxmlgui.rb:25:in
`install'
from /usr/local/Homebrew/Library/Homebrew/build.rb:172:in `block (3
levels) in install'
from /usr/local/Homebrew/Library/Homebrew/utils.rb:588:in `with_env'
from /usr/local/Homebrew/Library/Homebrew/build.rb:134:in `block (2
levels) in install'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:1297:in `block in
brew'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2473:in `block (2
levels) in stage'
from /usr/local/Homebrew/Library/Homebrew/utils.rb:588:in `with_env'
from /usr/local/Homebrew/Library/Homebrew/formula.rb:2472:in `block in
stage'
from /usr/local/Homebrew/Library/Homebrew/resource.rb:126:in `block (2
levels) in unpack'
from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:115:in
`chdir'
from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:115:in
`chdir'
from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:102:in
`stage'
from /usr/local/Homebrew/Library/Homebrew/resource.rb:122:in `block in
unpack'
from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `block in
run'
from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `chdir'
from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `run'
from /usr/local/Homebrew/Library/Homebrew/resource.rb:208:in `mktemp'
from
[kwin] [Bug 446017] On Wayland, can't move window to another virtual desktops with Meta+F1/F2/F3 while dragging it
https://bugs.kde.org/show_bug.cgi?id=446017 John Doe changed: What|Removed |Added CC||sgale...@protonmail.ch Version|5.23.3 |5.23.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447283] Updating to Digikam 7.4 - just opens Digikam 7.3
https://bugs.kde.org/show_bug.cgi?id=447283 --- Comment #2 from John Dennison --- Hi Maik, Many thanks for the reply and comments. I hadn't uninstalled 7.3 before and I am sure it was the answer to my problem. It might be of interest to you that the other aspect of the problem for myself also involved F-Secure or Windows security blocking the full download. At the end of the download it kept warning that the file was unknown and might be hazardous, requiring the file to be 'kept', or otherwise being automatically erased. Though I had 'kept' before your advice the downloaded file hadn't installed v 7.4, but had either asked for a program that would open it, or opened the v 7.3 when it was still installed - the downloaded file didn't seem to be an .exe file or act like one. I'm not sure if I inadvertently did anything to affect this process when following your advice, as it did occur the first instance I tried to download and install after removing v 7.3, but then it all went fine. Not sure that my observations are of any interest, or just confusing. Many thanks for your advice and the great software, and apologies for any inconvenience caused.. Best wishes John Dennison Maik Qualmann wrote: https://bugs.kde.org/show_bug.cgi?id=447283 <https://bugs.kde.org/show_bug.cgi?id=447283> Maik Qualmann mailto:metzping...@gmail.com> > changed: What |Removed |Added CC| |metzping...@gmail.com <mailto:metzping...@gmail.com> --- Comment #1 from Maik Qualmann mailto:metzping...@gmail.com> > --- Did you uninstall digiKam-7.3.0 via Settings-> Apps beforehand? What is the name of the file you downloaded? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447283] New: Updating to Digikam 7.4 - just opens Digikam 7.3
https://bugs.kde.org/show_bug.cgi?id=447283 Bug ID: 447283 Summary: Updating to Digikam 7.4 - just opens Digikam 7.3 Product: digikam Version: 7.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Setup-FirstRun Assignee: digikam-bugs-n...@kde.org Reporter: john.denni...@blueyonder.co.uk Target Milestone: --- I am trying to update Digikam 7.3 to v 7.4. When I try to install the update all that happens is that the existing 7.3 version is opened. I'm using Windows 11 on a Dell G5. Have tried downloading from all UK servers with the same result. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446759] Implement Mixbox, a "Practical Pigment Mixing for Digital Painting"
https://bugs.kde.org/show_bug.cgi?id=446759 --- Comment #4 from John Kirk --- (In reply to Halla Rempt from comment #3) > We can always ask the authors to dual-license it. Also, my perpetual > reminder whenever stuff like this comes up: we had this years ago. If you > check the koffice 2.2 tarball, you'll find the color mixer plugin that > Emanele Tamponi implemented using the Kubelka-Munk equations. Could THAT be implement into the newer Krita versions then? How much work would that be? -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 446780] New: Losing a game should produce a new random grid
https://bugs.kde.org/show_bug.cgi?id=446780 Bug ID: 446780 Summary: Losing a game should produce a new random grid Product: kmines Version: 4.0.21081 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: johne...@waf.io CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY After losing a game, "Reset the Game" gives the exact same grid again. It is therefore trivial to make a high score by memorizing the grid or taking a screenshot. The grid should be randomized. STEPS TO REPRODUCE 1. Lose a game, then remember which cells have mines 2. Select "Yes" on the dialog "Reset the Game" 3. Click one of the previous cells where mines are located. The grid is exactly the same, and the game is immediately lost. OBSERVED RESULT After losing a game, there is never a new grid. To generate a new grid, one should switch to a game with a different difficulty level and then back to the previous difficulty. EXPECTED RESULT Randomize the grid. The method `void MineFieldItem::resetMines()` should probably call `MineFieldItem::generateField` (or a some other method that reads `random`). SOFTWARE/OS VERSIONS Linux Kubuntu Impish KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446759] New: Implement Mixbox, a "Practical Pigment Mixing for Digital Painting"
https://bugs.kde.org/show_bug.cgi?id=446759 Bug ID: 446759 Summary: Implement Mixbox, a "Practical Pigment Mixing for Digital Painting" Product: krita Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: jcaique...@gmail.com Target Milestone: --- Mixbox is a pigment mixing black-box. You pass RGB colors in and get the mixed RGB out. Internally, Mixbox treats the colors as if they were made of actual real-world pigments. It uses the Kubelka & Munk theory to predict the color of the resulting mixture. This way, Mixbox achieves that blue and yellow mix to green, the same way real pigments do. Source Code: https://github.com/scrtwpns/pigment-mixing The research paper: https://scrtwpns.com/mixbox.pdf Video demonstration: https://youtu.be/9egCAxhOHg4 Talk: https://youtu.be/_qa5iWdfNKg It has a non-commercial license, and according to their website "Being this simple plug-and-play module, Mixbox can be easily integrated into any painting software." So I trust that is easy to implement. (Forgive me if I didn't tag the correct component.) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445404] Crash during attempted folder import
https://bugs.kde.org/show_bug.cgi?id=445404 --- Comment #5 from John Pearson --- On Tuesday, December 7, 2021 4:54:35 PM EST you wrote: > https://bugs.kde.org/show_bug.cgi?id=445404 > > Johannes Zarl-Zierl changed: > >What|Removed |Added > > Latest Commit||4663fad989c029aba6dbf376911 >||f0532290f7323 > > Resolution|--- |FIXED > Status|CONFIRMED |RESOLVED > > --- Comment #4 from Johannes Zarl-Zierl --- > Thank you for the detailed response - this confirms that I didn't overlook > something. The fix is in master and therefore part of the next release. I did not feel it was more than me ending up with an unusual file[s]. I am glad I could be of some help. > As for your problem: depending on the details of your problem, you might get > some use out of the "kpa-merge" tool that can be found inside the contrib > directory of KPhotoAlbum. While the script is not officially supported and > we always recommend backing up your index.xml file before running any tools > on it, the script was written by long-time contributor Robert Krawitz and > can merge two index.xml files into one... 'kpa-merge' has not been a good search term; but thanks for the suggestion. kphotoalbum is fine tool. z -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445404] Crash during attempted folder import
https://bugs.kde.org/show_bug.cgi?id=445404 --- Comment #3 from John Pearson --- On Monday, December 6, 2021 7:01:17 PM EST you wrote: > https://bugs.kde.org/show_bug.cgi?id=445404 > > Johannes Zarl-Zierl changed: > >What|Removed |Added > > Ever confirmed|0 |1 > Status|REPORTED|CONFIRMED > CC||johan...@zarl-zierl.at > > --- Comment #1 from Johannes Zarl-Zierl --- > Hi John, > > Thanks for the crash report! > Upon inspection of the crash backtrace it seems like you deselected the > images from the import file and then started the import, leading to the > crash... Can you try if the crash also happens if you select any image > before starting the import? Actually, what happens is that I had forgotten to select images during export. So I have a folder with the images and a kim file that is mostly empty [I openned a terminal and used less to confirm that was the case.] kpa creates the destination folder and does not move images displaying a fault message. This seems consistent behavior. My work around consists of the following process: 1. System level copy of the folder created by export, and all the files there in. Drag and drop in Dolphin works; midnight commander is much more efficient. 2. Select Maintenance/Rescan add the images themselves to the database. 3. File/import any salvaged image information; it does not matter if I deselect the image names during the import dialog. If there is information, then it is added. If there is no information, there is no fault produced. I am in process of salvaging a database of many thousands of images. I upgraded my computer, Ubuntu 18.04 to Ubuntu 20.04, kpa going from 5.3 to 5.8. 20+ years of gathered family photos are what I am trying to salvage. I reinstalled Ubuntu 18.04 on the computer; the database works. Preserving the folder structure and the database seems to require 1.2K+ select and export operations, folder by folder, not all of which I perform flawlessly. I then boot the computer into Ubuntu 20.04, and import the folders one at a time. I could not find a better way. This has to be an edge case. The cause of the fault is forgetting to do a select all before the export. The procedure outlined above consistently overcomes the fault Thank you for the reply, John -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443940] Kate crashes on closing the application
https://bugs.kde.org/show_bug.cgi?id=443940 --- Comment #2 from John Apple II --- I'll upgrade and put Kate through it's paces to see how it performs - if it fails on this version, I'll open a new bug with the details. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446195] New: Plasmashell crashes after changing the wallpaper from slideshow to plain color
https://bugs.kde.org/show_bug.cgi?id=446195 Bug ID: 446195 Summary: Plasmashell crashes after changing the wallpaper from slideshow to plain color Product: plasmashell Version: 5.22.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: johne...@waf.io Target Milestone: 1.0 STEPS TO REPRODUCE 1. Right-click on the desktop, configure the wallpaper to a folder view to a slideshow (1 hour for example), apply and close the dialog 2. Right-click on the desktop, configure the wallpaper to a plain color (keep the folder view), apply and close the dialog 3. Right-click on the desktop: plasma crashes OBSERVED RESULT Crash in plasmashell EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.22.5 on Ubuntu 21.10 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140405159598464) at pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140405159598464) at pthread_kill.c:80 #2 __GI___pthread_kill (threadid=140405159598464, signo=signo@entry=6) at pthread_kill.c:91 #3 0x7fb2a3b30476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7fb2a3b167b7 in __GI_abort () at abort.c:79 #5 0x7fb2a3db3a31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x7fb2a3dbf4ec in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7fb2a3dbf557 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fb2a3dbf7f9 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7fb2a3fbcf85 in qBadAlloc() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb2a3fbf834 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb2a4ed9e80 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fb2a4ed9f81 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fb2a4f07769 in QWidget::insertAction(QAction*, QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fb2a4f078b6 in QWidget::addActions(QList) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fb29c526797 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #16 0x7fb29c5275de in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #17 0x7fb2a5c213c8 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7fb2a4ece6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb2a41e616a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb2a5c3dd56 in QQuickWindowPrivate::deliverMatchingPointsToItem(QQuickItem*, QQuickPointerEvent*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7fb2a5c3eef7 in QQuickWindowPrivate::deliverPressOrReleaseEvent(QQuickPointerEvent*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7fb2a5c3fced in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7fb2a5c40f6f in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7fb2a45d7515 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7fb2a4ece6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fb2a41e616a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb2a45cb257 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #28 0x7fb2a45a09bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #29 0x7fb29f12bb9e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #30 0x7fb2a26218bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fb2a2674f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7fb2a261f003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fb2a423f548 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fb2a41e4a9b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7fb2a41ed024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x560145d53e0c in ?? () #37 0x7fb2a3b17fd0 in __libc_start_call_main
[dolphin] [Bug 446008] when a URL based link is clicked on in dolphin it ravrowser even though Firefox is default. The same link if in an email opens in Firefox.
https://bugs.kde.org/show_bug.cgi?id=446008 --- Comment #1 from John Munn --- typo in summary - it says "...dolphin it ravrowser...: should say "..dolphin it opens in Brave Browser..." -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 446008] New: when a URL based link is clicked on in dolphin it ravrowser even though Firefox is default. The same link if in an email opens in Firefox.
https://bugs.kde.org/show_bug.cgi?id=446008 Bug ID: 446008 Summary: when a URL based link is clicked on in dolphin it ravrowser even though Firefox is default. The same link if in an email opens in Firefox. Product: dolphin Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ocrho...@comcast.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. set up dolphin with URL links and Brave as the default browser. 2. use awhile then load firefox and set as default 3. use the urls in dolphin OBSERVED RESULT persistent opening in Brave but not from other sources EXPECTED RESULT expected a change to the new browser SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.18-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Celeron® CPU N3450 @ 1.10GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 500Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION suspect the problem may be connected to n issue with Brave even though it has been uninstalled. I have also manually removed Brave Browser from the file associations and default apps in setups - not resolved -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 446007] New: dolphin frequently freezes for minutes at a time. This started after I upgraded to FC34. since 5.14.11-200 fc34.x86_64
https://bugs.kde.org/show_bug.cgi?id=446007 Bug ID: 446007 Summary: dolphin frequently freezes for minutes at a time. This started after I upgraded to FC34. since 5.14.11-200 fc34.x86_64 Product: dolphin Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: ocrho...@comcast.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. create a direcory with all URL objects 2. place it on your desktop 3. open it up and scroll. with a while and it may lock up ad quit responding OBSERVED RESULT becomes unresponsive EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.18-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Celeron® CPU N3450 @ 1.10GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 500 (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 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #14 from John Clark --- (In reply to Nicolas Fella from comment #13) > In Comment 2 the default device is > "alsa_input.usb-Sennheiser_Sennheiser_SC_1x5_USB_A002460204909793-00.analog- > stereo", which I understand is the USB microphone you are unplugging > > Once you are unplugging the mic there are two possible options for a new > default device: > alsa_input.pci-_00_1f.3-platform-skl_hda_dsp_generic. > HiFi__hw_sofhdadsp__source (Headphones Stereo Microphone) > and > alsa_input.pci-_00_1f.3-platform-skl_hda_dsp_generic. > HiFi__hw_sofhdadsp_6__source (Digital Microphone) > > the former is not available but the latter is. > > So the problem is that the former is picked as new default instead of the > latter? I beg your pardon, you are correct :-) I assumed that was my mic but you're right, it has picked a new default, just the wrong one. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #12 from John Clark --- (In reply to Nicolas Fella from comment #11) > Thanks > It looks like after the microphone is disconnected the default one does > change to a different one, but that one is inactive? Do I have that right? I think the default, as shown in the screenshot is just left as it was before: "Headphones Stereo Microphone", the "Digital Microphone" is the one built into the laptop and I think should be the new default but it hasn't been selected. In the screenshot the radio button is sat on the greyed out item and so commands like mute/unmute apply to that item even though its not present. This can be very confusing because things like Google Meet can select the internal microphone as its the only option and then you're not muted even though you've pressed the system mute button. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #10 from John Clark --- (In reply to John Clark from comment #9) > Created attachment 143873 [details] > "pactl list" whilst in broken state You can see mic2 is unavailable, it's currently not connected. This is the one that the Plasma settings panel shows as the default. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #9 from John Clark --- Created attachment 143873 --> https://bugs.kde.org/attachment.cgi?id=143873=edit "pactl list" whilst in broken state -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #7 from John Clark --- Created attachment 143872 --> https://bugs.kde.org/attachment.cgi?id=143872=edit Screenshot showing the default selection -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #6 from John Clark --- (In reply to Nicolas Fella from comment #5) > This works fine for me with both PulseAudio and PipeWire. Judging by your > command output the default device is changed (this is done by PA/PW, not > Plasma) Maybe this is because I've manually selected a new default from the audio applet in the when I have the headset attached? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 John Clark changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|RESOLVED|REPORTED --- Comment #4 from John Clark --- (In reply to Nicolas Fella from comment #1) > Are you using PulseAudio or PipeWire? > > Please attach the output of "pactl info" before and after removing the device I'm using PipeWire but I also have pipewire-pulse installed. I've attached the files as requested. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #3 from John Clark --- Created attachment 143868 --> https://bugs.kde.org/attachment.cgi?id=143868=edit After removing the headset, no other changes -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445943] Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 --- Comment #2 from John Clark --- Created attachment 143867 --> https://bugs.kde.org/attachment.cgi?id=143867=edit With a USB headset attached and selected as the default. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445955] New: paring keys dont match
https://bugs.kde.org/show_bug.cgi?id=445955 Bug ID: 445955 Summary: paring keys dont match Product: kdeconnect Version: 1.10 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: s...@forceway.com Target Milestone: --- SUMMARY When paring android phone with PC, the PC plasmoid app shows a key that has 2 extra digits: 32. The key on the phone does not have this. The keys do not match. STEPS TO REPRODUCE 1. Pair phone with PC 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kdeconnect-kde-21.08.3-1.1.x86_64 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Android: v1.18 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445943] New: Inactive audio devices may be left as default
https://bugs.kde.org/show_bug.cgi?id=445943 Bug ID: 445943 Summary: Inactive audio devices may be left as default Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: john.cl...@cantab.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY *** If you have a previously connected audio device and you set it as your default then upon disconnecting it it will be left as the default and the global mute and unmute controls no longer affect any of the devices left. *** STEPS TO REPRODUCE 1. Connect a USB microphone 2. Select it as your default microphone 3. Disconnect it 4. Toggle Microphone mute OBSERVED RESULT The microphone mute OSD is displayed but the built-in microphone (the only one left in the system) is not muted. EXPECTED RESULT A new default input device is selected and the mute operates correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux: 5.10.81-1-lts (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 443144] Marble always crashes on exit
https://bugs.kde.org/show_bug.cgi?id=443144 --- Comment #4 from John Zaitseff --- Created attachment 143811 --> https://bugs.kde.org/attachment.cgi?id=143811=edit New crash information added by DrKonqi marble (2.2.20 (2.3 development version)) using Qt 5.15.2 - What I was doing when the application crashed: Closing the application after viewing any map; was using OpenTopoMap at the time. Crashes every time I exit Marble. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139804725797888) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139804725797888) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139804725797888, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f26e6ede476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f26e6ec47b7 in __GI_abort () at abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 443144] Marble always crashes on exit
https://bugs.kde.org/show_bug.cgi?id=443144 John Zaitseff changed: What|Removed |Added CC||j.zaits...@zap.org.au -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 418635] Display of GPS Area Information does not respect EXIF specification
https://bugs.kde.org/show_bug.cgi?id=418635 John Clark changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #3 from John Clark --- Marking as NEEDSINFO until we can get an example where this doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 418635] Display of GPS Area Information does not respect EXIF specification
https://bugs.kde.org/show_bug.cgi?id=418635 John Clark changed: What|Removed |Added Assignee|gwenview-bugs-n...@kde.org |john.cl...@cantab.net CC||john.cl...@cantab.net --- Comment #2 from John Clark --- Created attachment 143703 --> https://bugs.kde.org/attachment.cgi?id=143703=edit Gwenview GPS Area Information I have just attempted this with an image of my own. I did not have any images with this data so I applied my own tags using exiv2: exiv2 -M"set Exif.GPSInfo.GPSAreaInformation Somewhere cool in space" ./test.jpg and then opened in in Gwenview 21.08.3 and the tag shows correctly. -- 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.
[kmymoney] [Bug 445458] New: Investment Cap Gains by Account (Customized) crashes with my dataset. Changing the date of one ledger entry fixes the crash.
https://bugs.kde.org/show_bug.cgi?id=445458 Bug ID: 445458 Summary: Investment Cap Gains by Account (Customized) crashes with my dataset. Changing the date of one ledger entry fixes the crash. Product: kmymoney Version: 5.1.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: patr...@lestrade.com Target Milestone: --- Created attachment 143529 --> https://bugs.kde.org/attachment.cgi?id=143529=edit Kmymoney file for client Walter White. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Load my file KM1.kmy 2. Go to Reports and choose Inv. Cap Gains by Account (Custom) (N.B. I did not create that custom report) 3. Crash. Restart 4. Go into ledger for "MethProfits". Change the date of the 737.85 ADDED Shares from 10/10/17 to 10/10/10 (mm/dd/yy) 5. Repeat step 3 above. This time it does not crash. OBSERVED RESULT Wife leaves me. etc EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu/Gnome ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445404] New: Crash during attempted folder import
https://bugs.kde.org/show_bug.cgi?id=445404 Bug ID: 445404 Summary: Crash during attempted folder import Product: kphotoalbum Version: 5.8.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: johnpearson...@gmail.com Target Milestone: --- Application: kphotoalbum (5.8.1) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I attempted to use the file import dialog to import a folder into a new data base with kphotoalbum. it did not work. So I copied the folder into the correct position. kphotoalbum found the images files and added them. I saved the data base. I then attempted to use the file import dialog to update the information, deselecting the image copy dialog. the result is the reported crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault [New LWP 69650] [New LWP 69651] [New LWP 69652] [New LWP 69653] [New LWP 69654] [New LWP 69655] [New LWP 69659] [New LWP 69660] [New LWP 69661] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f5196838aff in __GI___poll (fds=0x7ffe0902fd38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f5192733a40 (LWP 69649))] Thread 10 (Thread 0x7f5163bfb700 (LWP 69661)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55bd045b7a90) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55bd045b7a40, cond=0x55bd045b7a68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55bd045b7a68, mutex=0x55bd045b7a40) at pthread_cond_wait.c:647 #3 0x7f5196d375cb in QWaitConditionPrivate::wait (deadline=..., this=0x55bd045b7a40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x55bd045a2698, mutex=mutex@entry=0x55bd045a26a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x55bd039b8557 in ImageManager::AsyncLoader::next (this=0x55bd045a2670) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 0x55bd039b7c46 in ImageManager::ImageLoaderThread::run (this=0x55bd045a3340) at ./ImageManager/ImageLoaderThread.cpp:44 #7 0x7f5196d3145c in QThreadPrivate::start (arg=0x55bd045a3340) at thread/qthread_unix.cpp:329 #8 0x7f5195d53609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5196845293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f51657fd700 (LWP 69660)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55bd045b7a90) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55bd045b7a40, cond=0x55bd045b7a68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55bd045b7a68, mutex=0x55bd045b7a40) at pthread_cond_wait.c:647 #3 0x7f5196d375cb in QWaitConditionPrivate::wait (deadline=..., this=0x55bd045b7a40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x55bd045a2698, mutex=mutex@entry=0x55bd045a26a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x55bd039b8557 in ImageManager::AsyncLoader::next (this=0x55bd045a2670) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 0x55bd039b7c46 in ImageManager::ImageLoaderThread::run (this=0x55bd045c3070) at ./ImageManager/ImageLoaderThread.cpp:44 #7 0x7f5196d3145c in QThreadPrivate::start (arg=0x55bd045c3070) at thread/qthread_unix.cpp:329 #8 0x7f5195d53609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5196845293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f517ce9f700 (LWP 69659)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55bd045b7a94) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55bd045b7a40, cond=0x55bd045b7a68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55bd045b7a68, mutex=0x55bd045b7a40) at pthread_cond_wait.c:647 #3 0x7f5196d375cb in QWaitConditionPrivate::wait (deadline=..., this=0x55bd045b7a40) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x55bd045a2698, mutex=mutex@entry=0x55bd045a26a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x55bd039b8557 in ImageManager::AsyncLoader::next (this=0x55bd045a2670) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 0x55bd039b7c46 in
[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.
[plasmashell] [Bug 445100] New: Wake the screen when backspace is pressed
https://bugs.kde.org/show_bug.cgi?id=445100 Bug ID: 445100 Summary: Wake the screen when backspace is pressed Product: plasmashell Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: johne...@waf.io CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Wake the screen and show the password prompt when the backspace key is pressed STEPS TO REPRODUCE 1. lock the screen 2. press the backspace key 3. nothing appears (except confusion) OBSERVED RESULT The screen stays off and the password prompt does not appear EXPECTED RESULT The prompt for the entering the password should appear (it happens with the escape, shift or control keys). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.22.5 (Kubuntu Impish) (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I do not always lock my screen, and I usually have a terminal running. Typing the password directly can accidentally enter it in unwanted apps, so I press the backspace key instead (which works on many other systems and screen lockers). While the backspace is really the one that I miss, I believe that any other key should also activate the screen locker. -- 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.
[plasma-systemmonitor] [Bug 444585] New: bar chart display style does not show bars when many sensors are used
https://bugs.kde.org/show_bug.cgi?id=444585 Bug ID: 444585 Summary: bar chart display style does not show bars when many sensors are used Product: plasma-systemmonitor Version: 5.23.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: terragonj...@yahoo.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY This affects both the plasma system-monitor app and the plasma widget. I've got a 16C/32T machine so when I use the "Individual core usage" preset I should see 32 bars (duh). Instead no bars are displayed. That seems to be caused by the fact that bars now do not have a minimum width (whereas the widget as a whole seems to have a maximum width). So if you start from one core sensors (or any other sensor) and you keep adding up the other cores one by one you'll see that the bars look fine initially. But then, as you add cores, they get thinner and thinner until they get under one pixel width an then they become invisible. It used to work in 5.21. But I can't say anything about 5.22 since I use debian and we went from 5.21 to 5.23 directly. STEPS TO REPRODUCE 1. Simplest way is to use "Individual core usage" widget (or preset) with a machine with 16c/32t 2. Otherwise just start adding sensors (any sensor) to the widget until you get to about 20 and then you'll see non bars anymore. 3. OBSERVED RESULT With a high number of sensors the bars get under one pixel width and therefore they become invisible EXPECTED RESULT Bars with a minimum width even with a high number of sensors. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian unstable (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429858] Problem with creating mbox files
https://bugs.kde.org/show_bug.cgi?id=429858 John Andrew McInnes changed: What|Removed |Added CC||s...@forceway.com --- Comment #1 from John Andrew McInnes --- Same problem. I see 'akonadi_mbox_resource_1' in the root of my folder/account list. It doesn't seem to do anything. Not sure what it is for or why it is visible. There is also a proper entry for the mbox I added with the name that I gave it. That does work as it should. KMail Version 5.18.2 (21.08.2) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443995] New: dolphin frequently freezes for minutes at a time. This started after I upgraded to FC34. now 5.14.11-200 fc34.x86_64
https://bugs.kde.org/show_bug.cgi?id=443995 Bug ID: 443995 Summary: dolphin frequently freezes for minutes at a time. This started after I upgraded to FC34. now 5.14.11-200 fc34.x86_64 Product: dolphin Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ocrho...@comcast.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY THis all started shortly after upgrading from FC33 to FC34.The contents of any open folder do not seem to influebce the issue. Using ksysgard Isee thatit is using 225% of the total cpu load or 100% of one of the quad cores. It seems to be a race condition. system memory ue is not high. I've tried things like downgrading releae (of dolphin) - no improvement. then reinstalling the most recent release - it seemed to work for a bit, teh go back to teh freeze up. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Celeron® CPU N3450 @ 1.10GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 500 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443966] Move to trash not working
https://bugs.kde.org/show_bug.cgi?id=443966 --- Comment #2 from John Dennison --- Thanks for the advice Maik - working perfectly now -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443966] New: Move to trash not working
https://bugs.kde.org/show_bug.cgi?id=443966 Bug ID: 443966 Summary: Move to trash not working Product: digikam Version: 7.3.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Database-Albums Assignee: digikam-bugs-n...@kde.org Reporter: john.denni...@blueyonder.co.uk Target Milestone: --- Get message 'Could not move to trash' after confirming this is what I want. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443940] New: Kate crashes on closing the application
https://bugs.kde.org/show_bug.cgi?id=443940
Bug ID: 443940
Summary: Kate crashes on closing the application
Product: kate
Version: 21.08.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: jappl...@redhat.com
Target Milestone: ---
Application: kate (21.08.0)
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.14.11-200.fc34.x86_64 x86_64
Windowing System: X11
Drkonqi Version: 5.22.5
Distribution: "Fedora release 34 (Thirty Four)"
-- Information about the crash:
- This crash has happened multiple times, in either a case where:
- I have multiple tabs open and click the [x] button
- I have closed all but one empty tab and then click the [x] button
I have had Kate crash similarly with only Kate open on the desktop, or with all
of my standard applications open. It happens every time I have closed kate in
the past couple of weeks.
The crash can be reproduced every time.
-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
[KCrash Handler]
#4 0x564dd7131bbb in
qDeleteAll<__gnu_cxx::__normal_iterator > > >
(end=..., begin=0x564dd991ca40) at /usr/include/qt5/QtCore/qalgorithms.h:320
#5 qDeleteAll > > (c=std::vector of length 1, capacity 32
= {...}) at /usr/include/qt5/QtCore/qalgorithms.h:328
#6 KateMDI::MainWindow::~MainWindow (__vtt_parm=,
this=, this=, __vtt_parm=) at
/usr/src/debug/kate-21.08.0-1.fc34.x86_64/kate/katemdi.cpp:778
#7 KateMainWindow::~KateMainWindow (this=, this=) at /usr/src/debug/kate-21.08.0-1.fc34.x86_64/kate/katemainwindow.cpp:203
#8 0x564dd713204d in KateMainWindow::~KateMainWindow (this=, this=) at
/usr/src/debug/kate-21.08.0-1.fc34.x86_64/kate/katemainwindow.cpp:203
#9 0x7f05c7ddbd31 in QObject::event (this=0x564dd93ac070,
e=0x564ddc136220) at kernel/qobject.cpp:1301
#10 0x7f05c9538d2d in KXmlGuiWindow::event(QEvent*) () from
/lib64/libKF5XmlGui.so.5
#11 0x7f05c88be443 in QApplicationPrivate::notify_helper (this=, receiver=0x564dd93ac070, e=0x564ddc136220) at
kernel/qapplication.cpp:3632
#12 0x7f05c7db1798 in QCoreApplication::notifyInternal2
(receiver=0x564dd93ac070, event=0x564ddc136220) at
kernel/qcoreapplication.cpp:1064
#13 0x7f05c7db4d06 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x564dd8faf000) at
kernel/qcoreapplication.cpp:1821
#14 0x7f05c7e030d7 in postEventSourceDispatch (s=0x564dd912a6d0) at
kernel/qeventdispatcher_glib.cpp:277
#15 0x7f05c5ff64cf in g_main_dispatch (context=0x7f05b0005000) at
../glib/gmain.c:3337
#16 g_main_context_dispatch (context=0x7f05b0005000) at ../glib/gmain.c:4055
#17 0x7f05c604a4f8 in g_main_context_iterate.constprop.0
(context=context@entry=0x7f05b0005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131
#18 0x7f05c5ff3c03 in g_main_context_iteration (context=0x7f05b0005000,
may_block=1) at ../glib/gmain.c:4196
#19 0x7f05c7e02b78 in QEventDispatcherGlib::processEvents
(this=0x564dd912bd80, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x7f05c7db01a2 in QEventLoop::exec (this=this@entry=0x7fff7e6074c0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x7f05c7db86e4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x564dd712157e in main (argc=, argv=) at
/usr/src/debug/kate-21.08.0-1.fc34.x86_64/kate/main.cpp:699
[Inferior 1 (process 21853) detached]
The reporter indicates this bug may be a duplicate of or related to bug 442838,
bug 442632.
Possible duplicates by query: bug 443935, bug 443784, bug 443771, bug 443586,
bug 443435.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 374908] Dual monitors: when screen resumes, windows are rearranged on second monitor
https://bugs.kde.org/show_bug.cgi?id=374908 --- Comment #11 from John B --- As an alternative to waiting for this to be addressed in a more robust manner, would it be possible to just have kwin completely ignore the displays when it comes to this? In other words, don't rearrange the windows even if I do physically disconnect the display; just _never_ rearrange anything. Not windows, not Plasma widgets, not panels...nothing. I realize the gotcha to this is that if you do actually disconnect a monitor (or there's a hardware failure, etc.) then you're going to have to be brushed up on your kwin fu to be able to get them back, but the blunt reality of the situation for those of us with multiple DisplayPort monitors is thus: 1. Do we want a system that does what we want once every 3-5 years when we replace a monitor, or 2. ...do we want a system that does what we want 5-10 times per day when the displays' power save kicks in? Notes: 1. This behaviour should be optional. If nothing else, laptop users who (un)dock a lot may very well prefer the current behaviour. 2. The default setting of this option should be to have it turned off; first off because changing defaults violates the Principle of Least Surprise, but also because having to rearrange your windows 5-10 times per day is annoying but "permanently" losing an important window is _much worse_ for someone who doesn't know how to get it back. 3. Since we're not rearranging windows any more, we need to account for the edge case where you actually _do_ lose a display unexpectedly (let's say you have a hardware failure). This is fine (for people who have enabled this functionality) unless the display you lose is the primary, at which point the main panel that you need to re-home your windows is gone. I propose adding an item to the context menu that you get when you right-click on the desktop that says "Make this display the primary" that executes the same code that would normally execute if you went into the Control Center and fiddled the appropriate checkbox. This also brings the K menu back to a visible display, so that you can (for example) reconfigure the panel so that all applications show on all displays. YES YES YES I fully and completely understand that #3 is fiddly as all get out. The only reason I'm asking for any of this is because the status quo is EVEN WORSE. I am to the point where I'm about to buy physical adapters to proxy my DP GPU and DP monitors through HDMI or DVI so that the OS can't see the power state changes, even if it means having to change the resolution from 4K to 1080p to avoid spending a zillion dollars. :) Fun fact: I was looking around on the Internet trying to figure out how MS Windows handles this problem, 'cause I get how hard it is to figure out what the "right behaviour" should be, before we even talk about writing code (that's why I used the phrase "do what we want" above, instead :P). Turns out...it doesn't. I guess I've never seen an MSW machine with multiple DP displays, but there's reports out there in the wild from Win10 users having this same problem. So this isn't just a KDE issue or even a GNU/Linux issue, it's a legitimate new conceptual problem that the advent of DisplayPort (and other display protocols that the OS can actually detect a disconnection of) has brought to the table. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443685] When converting canon CR3 files to dng files in parallel digikam crashes. This worked in version 7.2.0 but not in 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443685 --- Comment #7 from John Beatty --- Hi Maik, Making sure the program doesn't use more memory than the system has is a good thing. I re-ran the test case while watching memory. The memory usage never topped 40% of 64GB or approximately 26GB used. Thanks, John B. On 10/15/21 2:06 AM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=443685 > > --- Comment #6 from Maik Qualmann --- > With a camera with 45 MP images and 16 cores, the memory will definitely not > be > sufficient. Either we limit the use of cores in general or we have to > dynamically adjust the running threads based on memory usage. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443685] When converting canon CR3 files to dng files in parallel digikam crashes. This worked in version 7.2.0 but not in 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443685 --- Comment #5 from John Beatty --- Hi Maik, Thanks for looking into this. I'm running a Ryzen 5950x with 16 cores and 32 threads. John B. On 10/14/21 1:50 AM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=443685 > > Maik Qualmann changed: > > What|Removed |Added > > CC||metzping...@gmail.com > > --- Comment #2 from Maik Qualmann --- > One more question, how many CPU cores and memory does your computer have? > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443685] When converting canon CR3 files to dng files in parallel digikam crashes. This worked in version 7.2.0 but not in 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443685 --- Comment #3 from John Beatty --- Hi Gilles, Thanks for looking into this. I'm trying to put together the requested information. 1 These were raws from the Canon R5. 2 Exiv 11.88 3 I'm not sure how to get a GDB backtrace of the crash 4) I've attached two consoles one where it was not running in parallel and worked. I stopped it after about 150 or so files converted. So it works in serial mode. I've also attached a console with it running under catchsegv in parallel and failing. It doesn't appear to get to far. On this run it only completed 1 dng. The file with the failure has segfault in the name (digikam.segfault.console). Just for a bit more context I ran digikam in parallel without catchsegv and the messages from digikam appear to be virtually identical so I don't think the catchsegv alters the output other than to display the backtrace info at the end of the console. Thanks again for being so prompt in looking into this problem, John B. On 10/13/21 11:44 PM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=443685 > > --- Comment #1 from caulier.gil...@gmail.com --- > I cannot reproduce the crash here with my CR3 test files. > > Can you precise : > > - which Canon camera you use. > - Which Exiv2 version you use (Look in Help/Components Info for details). > - capture a GDB backtrace of crash. > - capture console traces during dysfunction. > > See instructions here: https://www.digikam.org/contribute/ > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443685] New: When converting canon CR3 files to dng files in parallel digikam crashes. This worked in version 7.2.0 but not in 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443685 Bug ID: 443685 Summary: When converting canon CR3 files to dng files in parallel digikam crashes. This worked in version 7.2.0 but not in 7.3.0 Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: BatchQueueManager-RAWProcessing Assignee: digikam-bugs-n...@kde.org Reporter: hjohnbea...@gmail.com Target Milestone: --- SUMMARY I selected 634 CR3 files to convert and start the batch queue manager with use all cores enabled. The program produces about 0 to 9 dng files then crashes. On some test runs the program didn't complete any dng files but was working on temp files. STEPS TO REPRODUCE 1. In the albums select an album with some CR3 files. 2. In the batch queue manager queue the "Convert RAW to DNG" tool 3. Push the run button OBSERVED RESULT Digikam abends and vanishes from the screen. An inspection of the directory shows sometimes some dng files present. There are also some 20-56 BatchTool temp files present. Some of the temp files have data and others do not. Between the tests I removed any existing dng and temp files to keep a consistent methodology. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.37-generic ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443656] New: KDE Settings crash when adding custom shortcut *after* removing one
https://bugs.kde.org/show_bug.cgi?id=443656 Bug ID: 443656 Summary: KDE Settings crash when adding custom shortcut *after* removing one Product: systemsettings Version: 5.22.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: corcegajo...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.5) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-37-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: 1. Remove a custom shortcut in a group 2. Clicked Edit > New > Global Shortcut > Command/URL 3. Application crashed It happens regardless of the "Custom Shortcuts" page is opened standalone (i.e. from search), or directly on the System Settings GUI. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 18196] [New LWP 18197] [New LWP 18198] [New LWP 18199] [New LWP 18200] [New LWP 18201] [New LWP 18202] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f8d8b465aff in __GI___poll (fds=0x7ffc441026f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f8d86c9a9c0 (LWP 18195))] Thread 8 (Thread 0x7f8d69bcf700 (LWP 18202)): #0 0x7f8d895a44dd in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8d89556568 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8d89557329 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8d895574a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8d8ba335eb in QEventDispatcherGlib::processEvents (this=0x7f8d6b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8d8b9d787b in QEventLoop::exec (this=this@entry=0x7f8d69bcebc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f8d8b7f1292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f8d8a882549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f8d8b7f242c in QThreadPrivate::start (arg=0x563e8c6b6cf0) at thread/qthread_unix.cpp:329 #9 0x7f8d89f16609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f8d8b472293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f8d6affd700 (LWP 18201)): #0 0x7f8d8d17adca in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2 #1 0x7f8d8b7f18fa in get_thread_data () at thread/qthread_unix.cpp:207 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:207 #3 0x7f8d8ba33cb5 in postEventSourcePrepare (timeout=0x0, s=0x7f8d5c004bb0) at kernel/qeventdispatcher_glib.cpp:270 #4 postEventSourceCheck (source=0x7f8d5c004bb0) at kernel/qeventdispatcher_glib.cpp:270 #5 0x7f8d89556da1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f8d89557312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f8d895574a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f8d8ba335eb in QEventDispatcherGlib::processEvents (this=0x7f8d5c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #9 0x7f8d8b9d787b in QEventLoop::exec (this=this@entry=0x7f8d6affcbc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #10 0x7f8d8b7f1292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #11 0x7f8d8a882549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f8d8b7f242c in QThreadPrivate::start (arg=0x563e8c234990) at thread/qthread_unix.cpp:329 #13 0x7f8d89f16609 in start_thread (arg=) at pthread_create.c:477 #14 0x7f8d8b472293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f8d6b7fe700 (LWP 18200)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563e8c0f7498) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563e8c0f7448, cond=0x563e8c0f7470) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563e8c0f7470, mutex=0x563e8c0f7448) at pthread_cond_wait.c:638 #3 0x7f8d7e833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f8d7e833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f8d89f16609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f8d8b472293 in clone () at
[systemsettings] [Bug 428626] Auto screen rotation doesn't work anymore unless "only in tablet mode" is unchecked
https://bugs.kde.org/show_bug.cgi?id=428626 John Clark changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/libkscreen/commit/c21f2b ||52999f7127c08c03ace11901c4b ||356cc93 --- Comment #14 from John Clark --- Git commit c21f2b52999f7127c08c03ace11901c4b356cc93 by Johnathon Clark. Committed on 10/10/2021 at 15:36. Pushed by iasensio into branch 'master'. Fix autorotate when "only in tablet mode" is selected The setTabletModeAvailable and setTabletModeEngaged properties were not copied across in Config::apply. M +3-0src/config.cpp https://invent.kde.org/plasma/libkscreen/commit/c21f2b52999f7127c08c03ace11901c4b356cc93 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 435720] Simple Simon will not auto-drop
https://bugs.kde.org/show_bug.cgi?id=435720 John changed: What|Removed |Added CC||johnsarou...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443381] New: KDE System Settings crash when setting Color theme
https://bugs.kde.org/show_bug.cgi?id=443381 Bug ID: 443381 Summary: KDE System Settings crash when setting Color theme Product: systemsettings Version: 5.22.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: corcegajo...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.5) Qt Version: 5.15.3 Frameworks Version: 5.86.0 Operating System: Linux 5.11.0-37-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Was changing the Color theme to something I have installed. Settings crashed randomly. It did not happen again, though. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 6606] [New LWP 6607] [New LWP 6608] [New LWP 6609] [New LWP 6610] [New LWP 6611] [New LWP 6616] [New LWP 6617] [New LWP 6636] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe49ceb9aff in __GI___poll (fds=0x7ffd45dd6038, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fe4986f59c0 (LWP 6604))] Thread 10 (Thread 0x7fe45aa5f700 (LWP 6636)): #0 __GI___libc_read (nbytes=16, buf=0x7fe45aa5e9b0, fd=27) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=27, buf=0x7fe45aa5e9b0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fe49aff8b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe49afafebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe49afb0312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe49afb04a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fe49d4875eb in QEventDispatcherGlib::processEvents (this=0x7fe44c1d5b00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7fe49d42b87b in QEventLoop::exec (this=this@entry=0x7fe45aa5ebc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7fe49d245292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7fe49c2db549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fe49d24642c in QThreadPrivate::start (arg=0x7fe49000ad70) at thread/qthread_unix.cpp:329 #11 0x7fe49b96f609 in start_thread (arg=) at pthread_create.c:477 #12 0x7fe49cec6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fe45be68700 (LWP 6617)): #0 0x7fe49d485748 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fe454004920) at kernel/qtimerinfo_unix.cpp:91 #1 0x7fe49d485d29 in QTimerInfoList::timerWait (this=0x7fe454004920, tm=...) at kernel/qtimerinfo_unix.cpp:388 #2 0x7fe49d487346 in timerSourcePrepareHelper (timeout=0x7fe45be679f4, src=) at kernel/qeventdispatcher_glib.cpp:162 #3 timerSourcePrepare (source=, timeout=0x7fe45be679f4) at kernel/qeventdispatcher_glib.cpp:166 #4 0x7fe49afaf8ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe49afb029b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fe49afb04a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fe49d4875eb in QEventDispatcherGlib::processEvents (this=0x7fe454000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fe49d42b87b in QEventLoop::exec (this=this@entry=0x7fe45be67bc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #9 0x7fe49d245292 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #10 0x7fe49c2db549 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fe49d24642c in QThreadPrivate::start (arg=0x557675dcb170) at thread/qthread_unix.cpp:329 #12 0x7fe49b96f609 in start_thread (arg=) at pthread_create.c:477 #13 0x7fe49cec6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fe481046700 (LWP 6616)): #0 0x7fe49d2469c3 in QMutex::unlock (this=this@entry=0x55767598fbe0) at /usr/include/c++/9/bits/atomic_base.h:769 #1 0x7fe49d4874f2 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #2 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:248 #3 QThreadData::canWaitLocked (this=0x55767598fbb0) at ../../include/QtCore/5.15.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:272 #4 postEventSourcePrepare (s=0x7fe460004fe0, timeout=0x7fe4810459f4) at kernel/qeventdispatcher_glib.cpp:260 #5
