[kwin] [Bug 487750] Kwin never notifies the systemd watchdog and gets killed
https://bugs.kde.org/show_bug.cgi?id=487750 --- Comment #4 from Jonas Rakebrandt --- Created attachment 170063 --> https://bugs.kde.org/attachment.cgi?id=170063=edit Systemd journal log This could be a relevant part of the systemd journal - especially the "Cannot find unit for notify message of PID 9192, ignoring." (9192 being kwin_wayland_wrapper) part. Looks like Kwin is sending the notifies properly but systemd can't associate the process with plasma-kwin_wayland.service (?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487750] Kwin never notifies the systemd watchdog and gets killed
https://bugs.kde.org/show_bug.cgi?id=487750 --- Comment #3 from Jonas Rakebrandt --- Created attachment 169994 --> https://bugs.kde.org/attachment.cgi?id=169994=edit CMake Log Here's the CMake log, it can definitely find libsystemd and libsystemd is also linked to the final kwin_wayland binary (in ldd output) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487750] Kwin never notifies the systemd watchdog and gets killed
https://bugs.kde.org/show_bug.cgi?id=487750 --- Comment #1 from Jonas Rakebrandt --- Tested with Kwin commit: 0e9b0fd4046908d609e243d57af896e2ce590359 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487750] New: Kwin never notifies the systemd watchdog and gets killed
https://bugs.kde.org/show_bug.cgi?id=487750 Bug ID: 487750 Summary: Kwin never notifies the systemd watchdog and gets killed Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: xar...@protonmail.com Target Milestone: --- SUMMARY This may very well just be some mis-configuration on my system but Kwin never sends anything to the systemd unit watchdog. This then results in systemd killing Kwin after the configured watchdog timeout (15s). Only tested on Wayland because I don't have an X-server installed at the moment. STEPS TO REPRODUCE 1. Log into a Plasma (Wayland) Session 2. Wait 15 seconds OBSERVED RESULT Kwin gets killed by systemd, shown in the journal afterwards. (If you are quick you can see `systemctl --user status plasma-kwin_wayland.service` never reaching the "active" state) EXPECTED RESULT Kwin should notify systemd as intended. My current workaround is reverting plasma-kwin_wayland.service to the old [Service] ExecStart=/usr/bin/kwin_wayland_wrapper --xwayland BusName=org.kde.KWinWrapper Slice=session.slice SOFTWARE/OS VERSIONS Operating System: Gentoo 2.15 KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-linux-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 62.0 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486134] Crash when opening an IFF data (?) file
https://bugs.kde.org/show_bug.cgi?id=486134 Jonas Baecker changed: What|Removed |Added Attachment #168909|text/x-basic|application/octet-stream mime type|| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486134] Crash when opening an IFF data (?) file
https://bugs.kde.org/show_bug.cgi?id=486134 --- Comment #1 from Jonas Baecker --- Created attachment 168909 --> https://bugs.kde.org/attachment.cgi?id=168909=edit An example of a file that's causing the crash -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486134] New: Crash when opening an IFF data (?) file
https://bugs.kde.org/show_bug.cgi?id=486134 Bug ID: 486134 Summary: Crash when opening an IFF data (?) file Classification: Applications Product: kate Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: vlu2at...@mozmail.com Target Milestone: --- Created attachment 168908 --> https://bugs.kde.org/attachment.cgi?id=168908=edit Process 8633 (kate) of user 1000 dumped core. SUMMARY Kate will crash immediately when opening the file. Note that this file is not actually meant to be readable by Kate, but Dolphin identified it as a text file for me so I tried opening it. The "file" command identifies the file as an IFF file, it's from an old video game "Urban Assault". All the *.BAS files that come with this game seem to cause a crash, I have uploaded one that has a small filesize for testing. STEPS TO REPRODUCE 1. Try opening the file "xc.BAS" 2. Kate should crash OBSERVED RESULT Kate crashing. EXPECTED RESULT Kate not crashing and perhaps showing a warning that the file is not a text file. SOFTWARE/OS VERSIONS Linux: 6.8.6 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 479612] Massive memory leak when looking at a file
https://bugs.kde.org/show_bug.cgi?id=479612 --- Comment #15 from Jonas Baecker --- (In reply to Albert Astals Cid from comment #14) > We believe this has been as fixed as it can be. > > Please upgrade to the newer versions (still unreleased) and tell us if you > (ideally KDE Frameworks 6 >= 6.1 and KDE Gear >= 24.05) and tell us if you > still have the problem. I recently upgraded to Plasma 6 and can confirm that it is indeed fixed for me now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482788] Panel alignment changes when moving custom-width centre
https://bugs.kde.org/show_bug.cgi?id=482788 --- Comment #2 from Jonas Verhofsté --- Created attachment 166654 --> https://bugs.kde.org/attachment.cgi?id=166654=edit The same panel, but its centre moved to the left -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482788] Panel alignment changes when moving custom-width centre
https://bugs.kde.org/show_bug.cgi?id=482788 --- Comment #1 from Jonas Verhofsté --- Created attachment 166653 --> https://bugs.kde.org/attachment.cgi?id=166653=edit A centred, small-width panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482788] New: Panel alignment changes when moving custom-width centre
https://bugs.kde.org/show_bug.cgi?id=482788 Bug ID: 482788 Summary: Panel alignment changes when moving custom-width centre Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jo...@verhofste.tech CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When moving the centre of a custom-width panel, it's configured Alignment changes to "Left" or "Right", depending which side you move it to. In plasma 5 it was possible to have the centre of your panel not in the centre of your screen. STEPS TO REPRODUCE 1. Create a new panel 2. Set Alignment to Centre 3. Set Width to Custom 4. Ensure the max width of the panel is smaller than the max width of the screen 5. Try to move the centre of the panel itself OBSERVED RESULT The Alignment of the panel changes, and with it also it's bounding box (max and min arrows). EXPECTED RESULT The Alignment should stay "Centre" and the panel centre itself should move, creating an off-centre centred panel. SOFTWARE/OS VERSIONS Linux: Arch Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Happens on both Wayland and X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482781] Multiple panels on the same position stack instead of overlap
https://bugs.kde.org/show_bug.cgi?id=482781 Jonas Verhofsté changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Jonas Verhofsté --- Ah, this is a duplicate. *** This bug has been marked as a duplicate of bug 477939 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477939] Center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 Jonas Verhofsté changed: What|Removed |Added CC||plcasimiro2...@gmail.com --- Comment #13 from Jonas Verhofsté --- *** Bug 482781 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482781] Multiple panels on the same position stack instead of overlap
https://bugs.kde.org/show_bug.cgi?id=482781 --- Comment #2 from Jonas Verhofsté --- I.e: on X11 the behaviour is as expected and like it was on plasma 5 (where this worked on both X11 and Wayland): the multiple panels overlap. On my end the stacking only happens on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482781] Multiple panels on the same position stack instead of overlap
https://bugs.kde.org/show_bug.cgi?id=482781 Jonas Verhofsté changed: What|Removed |Added CC||jo...@verhofste.tech --- Comment #1 from Jonas Verhofsté --- I can reproduce this on Wayland, but not on X11. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 479612] Massive memory leak when looking at a file
https://bugs.kde.org/show_bug.cgi?id=479612 --- Comment #9 from Jonas Baecker --- (In reply to Nicolas Fella from comment #4) > Analyzing in heaptrack suggests the file is loaded as a TGA file. Not sure > that makes sense Yeah, it's not really a TGA file. Actually, quite a few of these MIX archives are detected as TGA files for me in Dolphin, though only one of them used a lot of memory. This false detection happens with all the old Command & Conquer games that use MIX files. The games are freeware and can be downloaded from here for testing: https://cnc-comm.com/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479679] plasmashell exits with -1 on right mouse click with layershellqt: Cannot attach popup of unknown type
https://bugs.kde.org/show_bug.cgi?id=479679 Jonas Rakebrandt changed: What|Removed |Added CC||xar...@protonmail.com --- Comment #10 from Jonas Rakebrandt --- (In reply to Bernard from comment #3) > I'm having this issue on gentoo too but with kde's master branch Same here. Plasmashell crashes on right click. I'm on a clang(+libcxx) system. Might be interesting to hear what the others experiencing this issue are using. Just to see if it might be a clang vs. gcc issue or if it happens with either toolchain. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 479612] Massive memory leak when looking at a file
https://bugs.kde.org/show_bug.cgi?id=479612 --- Comment #6 from Jonas Baecker --- (In reply to Albert Astals Cid from comment #5) > I'm not sure there's an actual bug, the header of the file describes an > image of 41039 * 63040 in size, and thus lots of memory is needed to load it > to memory. > > You'd have to send us the actual file to confirm if it's a TGA file or not > and if not if we could bail earlier. Here's the whole file https://files.catbox.moe/fwoeqz.gz I'm using a third party filehost here as the file is too big to be attached. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479612] Massive memory leak when looking at a file
https://bugs.kde.org/show_bug.cgi?id=479612 --- Comment #1 from Jonas Baecker --- Created attachment 164813 --> https://bugs.kde.org/attachment.cgi?id=164813=edit Head of the offending file. It seems that running the file through the head command gives a file that has the same effect. Unzip and it should make Dolphin consume all of your RAM. The file is a mix file, an archive format of sorts, from a game "Tiberian Sun". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479612] New: Massive memory leak when looking at a file
https://bugs.kde.org/show_bug.cgi?id=479612 Bug ID: 479612 Summary: Massive memory leak when looking at a file Classification: Applications Product: dolphin Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: vlu2at...@mozmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY A file from an old Windows video game makes Dolphin use all my RAM. It's a problem that has persisted across a couple of months of updates. I can't tell when exactly it started, or if it has always been there, as I haven't looked at these files in a very long time. I can provide the offending file for analysis, but it's 8,9MiB large so it does not fit the attachment. STEPS TO REPRODUCE 1. Have the file visible in Dolphin 2. Wait a couple of seconds OBSERVED RESULT All of my 32GB of RAM consumed in just a few seconds. EXPECTED RESULT No excessive RAM usage. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.6 / 5.27.10 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479185] plasmashell upstream crashes on launch
https://bugs.kde.org/show_bug.cgi?id=479185 Jonas Rakebrandt changed: What|Removed |Added CC||xar...@protonmail.com --- Comment #8 from Jonas Rakebrandt --- (In reply to Timur Mangliev from comment #7) > Plasmashell launches but when I attempt to RMB on anything or hover over > some icons, it crashes and/or exits abnormally I think I'm experiencing the same issue (also on Gentoo using upstream master build). Plasmashell crashes when opening "right click" context menus (right click anywhere, left click some systray icons e.g. steam, using the keyboard's "context menu button" on the desktop, etc.) with the messages: > layershellqt: Cannot attach popup of unknown type > xdg_wm_base@3: error 3: no xdg_popup parent surface has been specified > The Wayland connection experienced a fatal error: Protocol error -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 476797] New: Tokodon crashes on closing
https://bugs.kde.org/show_bug.cgi?id=476797 Bug ID: 476797 Summary: Tokodon crashes on closing Classification: Applications Product: Tokodon Version: 23.08.2 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gross.jo...@gmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Application: tokodon (23.08.2) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: probably because of bizmuth ... seems like some position value is off The crash can be reproduced sometimes. -- Backtrace: Application: Tokodon (tokodon), signal: Segmentation fault [KCrash Handler] #4 0x7fd7c66f0281 in QCoreApplication::postEvent(QObject*, QEvent*, int) (receiver=0x5614ee69c0e0, event=0x5614eba91780, priority=) at kernel/qcoreapplication.cpp:1600 #5 0x7fd7c6716c41 in QObject::deleteLater() (this=) at kernel/qobject.cpp:2340 #6 0x7fd7c8b32384 in QQuickAnimatedImage::~QQuickAnimatedImage() (this=this@entry=0x5614eddbbfd0, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.11+kde30/src/quick/items/qquickanimatedimage.cpp:151 #7 0x7fd7c8c079a5 in QQmlPrivate::QQmlElement::~QQmlElement() (this=0x5614eddbbfd0, __in_chrg=) at ../../include/QtQml/../../../src/qml/qml/qqmlprivate.h:144 #8 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x5614eddbbfd0, __in_chrg=) at ../../include/QtQml/../../../src/qml/qml/qqmlprivate.h:144 #9 0x7fd7c6716aee in QObjectPrivate::deleteChildren() (this=this@entry=0x5614ed6b6050) at kernel/qobject.cpp:2137 #10 0x7fd7c6722de4 in QObject::~QObject() (this=this@entry=0x5614ec86f9d0, __in_chrg=) at kernel/qobject.cpp:1115 #11 0x7fd7c8a86602 in QQuickItem::~QQuickItem() (this=this@entry=0x5614ec86f9d0, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.11+kde30/src/quick/items/qquickitem.cpp:2389 #12 0x7fd7c8c07c45 in QQmlPrivate::QQmlElement::~QQmlElement() (this=0x5614ec86f9d0, __in_chrg=) at ../../include/QtQml/../../../src/qml/qml/qqmlprivate.h:144 #13 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x5614ec86f9d0, __in_chrg=) at ../../include/QtQml/../../../src/qml/qml/qqmlprivate.h:144 #14 0x7fd7c6716aee in QObjectPrivate::deleteChildren() (this=this@entry=0x5614eb6ca910) at kernel/qobject.cpp:2137 #15 0x7fd7c6722de4 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:1115 #16 0x5614eb11b93f in main(int, char**) (argc=, argv=) at /usr/src/debug/tokodon-23.08.2/src/main.cpp:260 [Inferior 1 (process 21729) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475554] Crash when importing a clip which was recorded in portrait mode
https://bugs.kde.org/show_bug.cgi?id=475554 --- Comment #4 from Jonas Schäfer --- Thanks for the reply & taking care of upstreaming the report! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475554] Crash when importing a clip which was recorded in portrait mode
https://bugs.kde.org/show_bug.cgi?id=475554 Jonas Schäfer changed: What|Removed |Added Summary|Crash when importing a clip |Crash when importing a clip |which was recorded in |which was recorded in |landscape mode |portrait mode -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475554] Crash when importing a clip which was recorded in landscape mode
https://bugs.kde.org/show_bug.cgi?id=475554 --- Comment #1 from Jonas Schäfer --- Created attachment 162270 --> https://bugs.kde.org/attachment.cgi?id=162270=edit video reproducing the crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475554] New: Crash when importing a clip which was recorded in landscape mode
https://bugs.kde.org/show_bug.cgi?id=475554 Bug ID: 475554 Summary: Crash when importing a clip which was recorded in landscape mode Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jo...@wielicki.name Target Milestone: --- Created attachment 162269 --> https://bugs.kde.org/attachment.cgi?id=162269=edit thread apply all bt full SUMMARY kdenlive crashes when importing a clip recorded in portrait format (i.e. height > width). That is the most concise I can describe it, because other clips from the same source import fine. STEPS TO REPRODUCE 1. Start kdenlive with a blank project 2. Add the out.mkv clip OBSERVED RESULT kdenlive freezes briefly and then crashes. EXPECTED RESULT kdenlive imports the clip and shows a preview of it in the project bin. SOFTWARE/OS VERSIONS Using flatpak: ID: org.kde.kdenlive Ref: app/org.kde.kdenlive/x86_64/stable Arch: x86_64 Branch: stable Version: 23.08.1 License: GPL-3.0-only Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 262.5 MB Runtime: org.kde.Platform/x86_64/5.15-22.08 Sdk: org.kde.Sdk/x86_64/5.15-22.08 Commit: cccf66901d249eb2486e87636e3685579bd33830a2420d21d7b258f868ae7f51 Parent: 322f25539b0d54540ce2bedb52ce6be7ed77aced7165d2734af55be7baca3285 Subject: Update urllib3-2.0.5-py3-none-any.whl to 2.0.6 (fa9743d2) Date: 2023-10-02 20:36:20 + ADDITIONAL INFORMATION - clip plays fine with ffplay (ffplay version 6.0-7+b1 Copyright (c) 2003-2023 the FFmpeg developers) from debian/testing - clip plays fine with melt (melt 7.18.0) from debian/testing - the issue is also reproduced with 23.08.0 from debian/testing -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 475505] New: Ending portal does not stop screen cast
https://bugs.kde.org/show_bug.cgi?id=475505 Bug ID: 475505 Summary: Ending portal does not stop screen cast Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j.eym...@gmx.net CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY *** When sharing the screen in a Plasma Wayland session using TeamViewer, the screen cast continues to get transmitted even after the user has stopped the portal session. This can have potential security implications as the user is wrongly assuming that the session was stopped. *** STEPS TO REPRODUCE 1. Install recent TeamViewer version on a system running KDE Plasma (tested with Fedora 38 and KDE Plasma 5.27.8) 2. Connect to the system when running a Wayland session 3. In the status bar of KDE Plasma, click the screen icon indicating an active remote desktop portal session and click "End" OBSERVED RESULT * Remote input gets stopped properly, but screen cast is still being updated on the remote side EXPECTED RESULT * Screen cast should not get updated anymore SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38, KDE neon testing KDE Plasma Version: 5.27.8 ADDITIONAL INFORMATION * TeamViewer should also close the connection due to the stopped signal. This is a known issue at TeamViewer (however, this would then hide above problem) * I found this merge request which might be related, but I think it was only merged to master, i.e. not the 5.27 branch: https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/215 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 128434] Preview tooltip for hyperlinks to other pages
https://bugs.kde.org/show_bug.cgi?id=128434 Jonas changed: What|Removed |Added CC||jonas...@gmail.com --- Comment #9 from Jonas --- This would be really great to have! I've been using okular for years, but just learned about this feature in evince. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472312] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=472312 Bug ID: 472312 Summary: plasma crash Classification: I don't know Product: kde Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jonasmz@gmail.com Target Milestone: --- Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: plasma crash when i try delete an aplication panel The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 2466 (plasmashell) UID: 1000 (jonasmz) GID: 1000 (jonasmz) Signal: 11 (SEGV) Timestamp: Mon 2023-07-17 01:31:08 -03 (48s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (jonasmz) Boot ID: 1b503569cc9a4ed4abcf5e86a8e5509f Machine ID: 4fbbfb5ed0a04100979b8ed8662549a6 Hostname: debian-lap Storage: /var/lib/systemd/coredump/core.plasmashell.1000.1b503569cc9a4ed4abcf5e86a8e5509f.2466.168956826800.zst (present) Size on Disk: 26.6M Message: Process 2466 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 2466: #0 0x7f0c5f0aebb4 pthread_sigmask (libc.so.6 + 0x8fbb4) #1 0x7f0c5f05b179 sigprocmask (libc.so.6 + 0x3c179) #2 0x7f0c616e5e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f0c616e6b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f0c5f05af90 n/a (libc.so.6 + 0x3bf90) #5 0x7f0c60c70c92 _ZN8QQmlData17isSignalConnectedEP24QAbstractDeclarativeDataPK7QObjecti (libQt5Qml.so.5 + 0x270c92) #6 0x7f0c5f4e8a6c n/a (libQt5Core.so.5 + 0x2e8a6c) #7 0x7f0c5f44c0bd _ZN18QAbstractItemModel19modelAboutToBeResetENS_14QPrivateSignalE (libQt5Core.so.5 + 0x24c0bd) #8 0x55859dac425c n/a (plasmashell + 0x7625c) #9 0x55859da7b433 n/a (plasmashell + 0x2d433) #10 0x7f0c60cc6c93 n/a (libQt5Qml.so.5 + 0x2c6c93) #11 0x7f0c60ba3521 n/a (libQt5Qml.so.5 + 0x1a3521) #12 0x7f0c60ba53e0 _ZNK3QV413QObjectMethod12callInternalEPKNS_5ValueES3_i (libQt5Qml.so.5 + 0x1a53e0) #13 0x7f0c60bc1cb6 n/a (libQt5Qml.so.5 + 0x1c1cb6) #14 0x7f0c60bc53df n/a (libQt5Qml.so.5 + 0x1c53df) #15 0x7f0c60b57c2e _ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5 + 0x157c2e) #16 0x7f0c60ce144d _ZN24QQmlJavaScriptExpression8evaluateEPN3QV48CallDataEPb (libQt5Qml.so.5 + 0x2e144d) #17 0x7f0c60c92baf _ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt5Qml.so.5 + 0x292baf) #18 0x7f0c60c942f8 n/a (libQt5Qml.so.5 + 0x2942f8) #19 0x7f0c60cc677f _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 0x2c677f) #20 0x7f0c5f4e8a8d n/a (libQt5Core.so.5 + 0x2e8a8d) #21 0x7f0c5f4e8f4f n/a (libQt5Core.so.5 + 0x2e8f4f) #22 0x7f0c5a1f5221 _ZN27QQuickAbstractButtonPrivate13handleReleaseERK7QPointF (libQt5QuickTemplates2.so.5 + 0x8a221) #23 0x7f0c5a214251 _ZN13QQuickControl17mouseReleaseEventEP11QMouseEvent (libQt5QuickTemplates2.so.5 + 0xa9251) #24 0x7f0c612550e8 _ZN10QQuickItem5eventEP6QEvent (libQt5Quick.so.5 + 0x2550e8) #25 0x7f0c60362fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #26 0x7f0c5f4b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #27 0x7f0c612729da _ZN19QQuickWindowPrivate17deliverMouseEventEP23QQuickPointerMouseEvent (libQt5Quick.so.5 + 0x2729da) #28 0x7f0c612740dd _ZN19QQuickWindowPrivate19deliverPointerEventEP18QQuickPointerEvent (libQt5Quick.so.5 + 0x2740dd) #29 0x7f0c5f9493f5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1493f5) #30
[plasmashell] [Bug 471030] New: The panel does not auto-hide when a different keyboard layout is selected
https://bugs.kde.org/show_bug.cgi?id=471030 Bug ID: 471030 Summary: The panel does not auto-hide when a different keyboard layout is selected Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: gertemu...@gufum.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 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. Windows can cover enabled 2. Multiple keyboard layouts in different languages installed 3. A window in full screen 4. Changing the keyboard layout by clicking on the abbreviation on the panel OBSERVED RESULT The panel does not auto hide until the window is resized EXPECTED RESULT The panel should auto-hide when somewhere else or after some time SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396 --- Comment #26 from Jonas Arndt --- (In reply to Nate Graham from comment #23) > People who are affected by this issue, please test again with Plasma 5.27.5 > once it's released on May 9th, a little over two weeks from now. Thanks! I haven't tested much anything since back when I reported the bug. I am on Debian Bookworm and plasma 5.27.2-1 now. For some reason it all works now. I don't anymore need to have a login script with xrandr. It works on Xorg and Wayland. The middle landscape oriented screen is the default screen now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464985] Struts of panels affect windows on other screens with no panels, causing stickiness when dragging close to a screen edge
https://bugs.kde.org/show_bug.cgi?id=464985 --- Comment #9 from Jonas Rakebrandt --- Created attachment 158812 --> https://bugs.kde.org/attachment.cgi?id=158812=edit kwin patch Did some digging through kwin's code myself to try finding the issue and the changes in the attached diff are my best bet so far. As far as I can tell this doesn't cause any other issues but fixes this issue. Kind of feels like a hack though. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469067] When moving your mouse between items that display a tooltip, the tooltip box becomes deformed
https://bugs.kde.org/show_bug.cgi?id=469067 Jonas Kvinge changed: What|Removed |Added CC||jo...@jkvinge.net -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 468671] New: Problem starting lesson
https://bugs.kde.org/show_bug.cgi?id=468671 Bug ID: 468671 Summary: Problem starting lesson Classification: Applications Product: ktouch Version: 22.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: jonasjf...@gmail.com Target Milestone: --- Created attachment 158204 --> https://bugs.kde.org/attachment.cgi?id=158204=edit Screenshot SUMMARY problem starting lesson OBSERVED RESULT When starting the lesson, the application is stuck on the title of the lesson, until the first one is completed and enter is pressed. EXPECTED RESULT The correct thing would be for the title to disappear as soon as you start typing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.25.5 Kubuntu 22.10 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464985] Windows with server side decoration get stuck when dragging to top screen edge
https://bugs.kde.org/show_bug.cgi?id=464985 --- Comment #7 from Jonas Rakebrandt --- Another video showing this: https://youtu.be/9uAjvfUVa44 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464985] Windows with server side decoration get stuck when dragging to top screen edge
https://bugs.kde.org/show_bug.cgi?id=464985 --- Comment #6 from Jonas Rakebrandt --- Just updated to 5.27.0 and the issue still exists. However I think I found some more info: 1) This only happens with multiple monitors. 2) When dragging a window that "got stuck" horizontally along the height where it gets stuck it perfectly aligns with other top located panels. This leads me to the conclusion that windows snap to panels of other screens. Is it possible that the panels "snap regions" somehow extend across screen boundaries? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396 --- Comment #9 from Jonas Arndt --- (In reply to David Edmundson from comment #8) > > Currently I have an xrandr script I use to set them right: > > Currently as in, you're using this as a workaround for the Kscreen bug, or > you always used to have an xrandr on startup? No I just use xrandr as a work-around for this problem. I suspect my upgrade systemsettings:amd64 (4:5.26.5-1, 4:5.26.90-1) on February 2nd caused this issue -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396 --- Comment #7 from Jonas Arndt --- All the commands were run when the wrong screen (the left one) was primary. Currently I have an xrandr script I use to set them right: xrandr --output eDP-1 --off --output DP-1 --mode 1920x1080 --pos 0x0 --rotate right --output DP-2 --off --output DP-3 --off --output DP-3-1 --off --output DP-3-2 --primary --mode 1920x1080 --pos 1080x420 --rotate normal --output DP-3-3 --mode 1920x1080 --pos 3000x0 --rotate left -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396
--- Comment #6 from Jonas Arndt ---
(In reply to Marco Martin from comment #3)
> can you also paste the output of the command kscreen-console ?
>
> I'm curious if all the edids are found correctly, as is a known problem of
> erratic behavior when there are screens with invalid or duplicated edid
> (especially on displayport)
Here you go
jonas@uberpenguinwan:~$ kscreen-console
START: Requesting Config
Received config. Took 16 milliseconds
Screen:
maxSize: QSize(16384, 16384)
minSize: QSize(320, 200)
currentSize: QSize(4080, 1920)
-
Id: 65
Name: "eDP-1"
Type: "Panel (Laptop)"
Connected: true
Enabled: false
Priority: 0
Rotation: KScreen::Output::None
Pos: QPoint(0,0)
MMSize: QSize(344, 194)
FollowPreferredMode: false
Scale: 1
Clones: None
Mode: ""
Preferred Mode: "73"
Preferred modes: ("73")
Modes:
"100""" QSize(1280, 720) 59.7447
"101""" QSize(1024, 768) 60.0373
"102""" QSize(1024, 768) 60.0038
"103""" QSize(960, 720) 60
"104""" QSize(928, 696) 60.0507
"105""" QSize(896, 672) 60.0144
"106""" QSize(1024, 576) 59.9534
"107""" QSize(1024, 576) 59.9593
"108""" QSize(1024, 576) 59.8992
"109""" QSize(1024, 576) 59.8195
"110""" QSize(960, 600) 59.9327
"111""" QSize(960, 600) 59.9988
"112""" QSize(960, 540) 59.9628
"113""" QSize(960, 540) 59.9879
"114""" QSize(960, 540) 59.629
"115""" QSize(960, 540) 59.8182
"116""" QSize(800, 600) 60
"117""" QSize(800, 600) 60.3165
"118""" QSize(800, 600) 56.25
"119""" QSize(840, 525) 60.0094
"120""" QSize(840, 525) 59.8833
"121""" QSize(864, 486) 59.9153
"122""" QSize(864, 486) 59.5703
"123""" QSize(700, 525) 59.9756
"124""" QSize(800, 450) 59.946
"125""" QSize(800, 450) 59.8248
"126""" QSize(640, 512) 60.0197
"127""" QSize(700, 450) 59.9641
"128""" QSize(700, 450) 59.8798
"129""" QSize(640, 480) 60
"130""" QSize(640, 480) 59.9405
"131""" QSize(720, 405) 59.5062
"132""" QSize(720, 405) 58.9879
"133""" QSize(684, 384) 59.882
"134""" QSize(684, 384) 59.8532
"135""" QSize(640, 400) 59.8824
"136""" QSize(640, 400) 59.9824
"137""" QSize(640, 360) 59.8551
"138""" QSize(640, 360) 59.8255
"139""" QSize(640, 360) 59.8404
"140""" QSize(640, 360) 59.3249
"141""" QSize(512, 384) 60.0038
"142""" QSize(512, 288) 59.9994
"143""" QSize(512, 288) 59.9206
"144""" QSize(480, 270) 59.629
"145""" QSize(480, 270) 59.8182
"146""" QSize(400, 300) 60.3165
"147""" QSize(400, 300) 56.3401
"148""" QSize(432, 243) 59.9153
"149""" QSize(432, 243) 59.5703
"150""" QSize(320, 240) 60.0525
"151""" QSize(360, 202) 59.5062
"152""" QSize(360, 202) 59.129
"153""" QSize(320, 180) 59.8404
"154""" QSize(320, 180) 59.3249
"73""" QSize(1920, 1080) 60.0028
"74""" QSize(1920, 1080) 59.9685
"75""" QSize(1920, 1080)
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396 --- Comment #5 from Jonas Arndt --- (In reply to Marco Martin from comment #2) > X11 or wayland? I am running X11 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465396] Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma with three-screen arrangement (leftmost and rightmost are rotated)
https://bugs.kde.org/show_bug.cgi?id=465396 --- Comment #4 from Jonas Arndt --- Here is the output of kscreen-doctor -o Output: 65 eDP-1 disabled connected priority 0 Panel Modes: 73:1920x1080@60! 74:1920x1080@60 75:1920x1080@60 76:1920x1080@60 77:1920x1080@48 78:1680x1050@60 79:1680x1050@60 80:1400x1050@60 81:1600x900@60 82:1600x900@60 83:1600x900@60 84:1600x900@60 85:1280x1024@60 86:1400x900@60 87:1400x900@60 88:1280x960@60 89:1440x810@60 90:1440x810@60 91:1368x768@60 92:1368x768@60 93:1280x800@60 94:1280x800@60 95:1280x800@60 96:1280x800@60 97:1280x720@60 98:1280x720@60 99:1280x720@60 100:1280x720@60 101:1024x768@60 102:1024x768@60 103:960x720@60 104:928x696@60 105:896x672@60 106:1024x576@60 107:1024x576@60 108:1024x576@60 109:1024x576@60 110:960x600@60 111:960x600@60 112:960x540@60 113:960x540@60 114:960x540@60 115:960x540@60 116:800x600@60 117:800x600@60 118:800x600@56 119:840x525@60 120:840x525@60 121:864x486@60 122:864x486@60 123:700x525@60 124:800x450@60 125:800x450@60 126:640x512@60 127:700x450@60 128:700x450@60 129:640x480@60 130:640x480@60 131:720x405@60 132:720x405@59 133:684x384@60 134:684x384@60 135:640x400@60 136:640x400@60 137:640x360@60 138:640x360@60 139:640x360@60 140:640x360@59 141:512x384@60 142:512x288@60 143:512x288@60 144:480x270@60 145:480x270@60 146:400x300@60 147:400x300@56 148:432x243@60 149:432x243@60 150:320x240@60 151:360x202@60 152:360x202@59 153:320x180@60 154:320x180@59 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 66 DP-1 enabled connected priority 2 DisplayPort Modes: 79:1680x1050@60 85:1280x1024@60 88:1280x960@60 102:1024x768@60 117:800x600@60 118:800x600@56 130:640x480@60 155:1920x1080@60*! 156:1920x1080@50 157:1920x1080@60 158:1920x1080@60 159:1920x1080@60 160:1920x1080@50 161:1920x1080@60 162:1600x1200@60 163:1280x1024@75 164:1440x900@60 165:1366x768@60 166:1152x864@75 167:1280x720@60 168:1280x720@50 169:1280x720@60 170:1024x768@75 171:1024x768@70 172:832x624@75 173:800x600@72 174:800x600@75 175:720x576@50 176:720x480@60 177:720x480@60 178:640x480@75 179:640x480@73 180:640x480@67 181:640x480@60 182:720x400@70 Geometry: 0,0 1080x1920 Scale: 1 Rotation: 8 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 67 DP-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 68 DP-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 69 DP-3-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 70 DP-3-2 enabled connected priority 1 DisplayPort Modes: 79:1680x1050@60 85:1280x1024@60 88:1280x960@60 96:1280x800@60 102:1024x768@60 117:800x600@60 118:800x600@56 130:640x480@60 155:1920x1080@60*! 156:1920x1080@50 157:1920x1080@60 163:1280x1024@75 167:1280x720@60 168:1280x720@50 169:1280x720@60 170:1024x768@75 171:1024x768@70 172:832x624@75 173:800x600@72 174:800x600@75 175:720x576@50 176:720x480@60 177:720x480@60 178:640x480@75 179:640x480@73 181:640x480@60 182:720x400@70 183:1920x1080@75 184:1600x900@60 185:1366x768@60 Geometry: 1080,420 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 71 DP-3-3 enabled connected priority 3 DisplayPort Modes: 79:1680x1050@60 85:1280x1024@60 96:1280x800@60 102:1024x768@60 117:800x600@60 130:640x480@60 155:1920x1080@60*! 156:1920x1080@50 157:1920x1080@60 164:1440x900@60 167:1280x720@60 168:1280x720@50 169:1280x720@60 175:720x576@50 176:720x480@60 177:720x480@60 181:640x480@60 182:720x400@70 184:1600x900@60 Geometry: 3000,0 1080x1920 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465396] New: Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=465396 Bug ID: 465396 Summary: Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma Classification: Applications Product: systemsettings Version: 5.26.90 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: jar...@duck.com CC: plasma-b...@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. Start computer 2. Log into Plasma 3. OBSERVED RESULT Running on Debian Bookworm. I have three screens. The left and the right are portrait oriented and the middle one is landscape oriented and the default screen. After an apt upgrade the system forgets that the middle screen is the default one. The list of screen priorities is correct, but the system still decides to make my very left screen default (the one with panels on). This happens every time I log in. Note that the positions are fine. It is just the issue that it forgets which one is the main screen. To fix it I have to change the screen priorities list, save, change back, save. EXPECTED RESULT I expect that the system will look at the screen priorities and make the screen with the highest priority the default screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.90 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have also logged a bug with Debian's maintainer on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030552 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 447053] Editing Google event causes incorrect year
https://bugs.kde.org/show_bug.cgi?id=447053 --- Comment #2 from Jonas --- Thanks Claudio :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464985] Windows with server side decoration get stuck when dragging to top screen edge
https://bugs.kde.org/show_bug.cgi?id=464985 --- Comment #3 from Jonas Rakebrandt --- As far as I can tell the panel doesn't affect this issue in any way. It can be floating, non-floating, completely gone - the windows get stuck at the same height. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464985] Windows with server side decoration get stuck when dragging to top screen edge
https://bugs.kde.org/show_bug.cgi?id=464985 --- Comment #1 from Jonas Rakebrandt --- A video showing what was described: https://youtu.be/lFZyV1ud-ro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464985] New: Windows with server side decoration get stuck when dragging to top screen edge
https://bugs.kde.org/show_bug.cgi?id=464985 Bug ID: 464985 Summary: Windows with server side decoration get stuck when dragging to top screen edge Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: xar...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** When dragging windows with server side decoration to the top edge of the screen they get stuck (the window stops moving up as if it already reached the edge). They get stuck earlier when scaling is involved. Client side decorated windows are not affected. It happens consistently after un-minimizing. Maximizing and un-maximizing sometimes temporarily "fixes" it. The window snaps back to the cursor when it either reaches the screen edge or a panel located at the top screen edge. STEPS TO REPRODUCE 1. Minimize and un-minimize a non-maximized server side decorated window 2. Drag the window to the top screen edge OBSERVED RESULT The window gets stuck and stops following the cursor EXPECTED RESULT The window continues moving with the cursor SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-x86_64-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463619] Unable to change desktop resolution beyond natively supported resolutions on Wayland
https://bugs.kde.org/show_bug.cgi?id=463619 Jonas Pedersen changed: What|Removed |Added CC||jo...@jope.eu --- Comment #1 from Jonas Pedersen --- I am facing exact same issue. Also on Manjaro. It is actually a bit of a showstopper for me as I am often connecting an external display during meetings and using the "unify outputs" option. This results in my laptop screen and the external screen is not running the same resolution and then it is more less unusable for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463759] If 'Star' tab is selected, volume adjusted via Media Player applet is not properly updated in the OSD
https://bugs.kde.org/show_bug.cgi?id=463759 Jonas Kvinge changed: What|Removed |Added CC||jo...@jkvinge.net -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463313] tokodon crashed
https://bugs.kde.org/show_bug.cgi?id=463313 --- Comment #2 from Jonas --- Created attachment 154797 --> https://bugs.kde.org/attachment.cgi?id=154797=edit New crash information added by DrKonqi tokodon (22.11.2) using Qt 5.15.7 Clicking on user icon makes application crash. Also settings page is empty -- Backtrace (Reduced): #6 0x7ff6f270a4b9 in QV4::QQmlTypeWrapper::lookupSingletonProperty(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) () from /lib64/libQt5Qml.so.5 #7 0x7ff6f270be2c in QV4::QQmlTypeWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5 [...] #10 0x7ff6f25701de in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #11 0x7ff6f26f89fd in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #12 0x7ff6f26aa02f in QQmlBoundSignalExpression::evaluate(void**) () from /lib64/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463313] tokodon crashed
https://bugs.kde.org/show_bug.cgi?id=463313 Jonas changed: What|Removed |Added CC||jonas.smolians...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 189159] bad error message in "log and messages" view
https://bugs.kde.org/show_bug.cgi?id=189159 Jonas changed: What|Removed |Added Platform|Compiled Sources|Kubuntu Version|unspecified |2.9.93 CC||jonas...@gmail.com Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Jonas --- The problem persists in kile 2.9.93 on ubuntu 22.04 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461349] Most "special" keys broken in konsole with Neo 2 keyboard layout
https://bugs.kde.org/show_bug.cgi?id=461349 --- Comment #1 from Jonas Schäfer --- Possible downstream report at Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022972 (It's not confirmed yet that the original reporter also used Neo 2) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461349] New: Most "special" keys broken in konsole with Neo 2 keyboard layout
https://bugs.kde.org/show_bug.cgi?id=461349 Bug ID: 461349 Summary: Most "special" keys broken in konsole with Neo 2 keyboard layout Classification: Applications Product: konsole Version: 22.08.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: jo...@wielicki.name Target Milestone: --- SUMMARY When using the Neo2 keyboard layout (setxkbmap de neo, see https://neo-layout.org/ for a visual reference if you attempt to reproduce this), Konsole seems to assume that some unspecified modifier is pressed all the time, causing it to emit incorrect CSI sequences for keys. STEPS TO REPRODUCE 1. Start konsole 2. setxkbmap de neo 3. Press any arrow key OBSERVED RESULT Arrow keys are mapped to their letters (Up -> A, Down -> B, …). EXPECTED RESULT Arrow keys navigate the shell history or input buffer. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian/testing (available in About System) KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION This can be tracked down to the aforementioned modifier situation by looking into Edit Current Profile -> Keyboard -> Default (XFree 4) -> Edit… and using the input field for testing. The rules which match differ based on which keyboard layout is used: Layout Rule Escape Sequence de neo Up-Shift+Ansi+AnyModifier\E[1;1A us Up-Shift+Ansi-AppCursorKeys-AnyModifier \E[A This makes me believe that something in konsole, or its dependencies, assumes that there's some modifier continuously pressed while using the neo2 layout. As this happens even right after switching layouts, I presume that this is no lingering state. I also suspect that this may not affect just konsole; I also noticed that some other applications shortcuts have stopped working correctly (e.g. the password prompt of kontact/kmail does not react to the Enter key anymore, I have to click Ok explicitly) and it may be related. If this is true, I'd like to know where to file this and how to help to debug this further. Is this Qt? Is this some KDE library? How can I help? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460135] digikam should use ISO date format, or at least the system setting
https://bugs.kde.org/show_bug.cgi?id=460135 --- Comment #5 from Jonas Stein --- I confirm, that my example screenshot was a special case. Because this format is exactly the raw data from exif. You can delete the "Date with Colons in Metadata" screenshot, if it confuses. I created screenshots for more general description of the problem. Please reopen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460135] digikam should use ISO date format, or at least the system setting
https://bugs.kde.org/show_bug.cgi?id=460135 --- Comment #4 from Jonas Stein --- Created attachment 152651 --> https://bugs.kde.org/attachment.cgi?id=152651=edit Dateformat in File Properties -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460135] digikam should use ISO date format, or at least the system setting
https://bugs.kde.org/show_bug.cgi?id=460135 --- Comment #3 from Jonas Stein --- Created attachment 152650 --> https://bugs.kde.org/attachment.cgi?id=152650=edit Dateformat in Album -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460135] New: digikam should use ISO date format, or at least the system setting
https://bugs.kde.org/show_bug.cgi?id=460135 Bug ID: 460135 Summary: digikam should use ISO date format, or at least the system setting Classification: Applications Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Usability-Ergonomy Assignee: digikam-bugs-n...@kde.org Reporter: k...@mail.jonasstein.de Target Milestone: --- Created attachment 152649 --> https://bugs.kde.org/attachment.cgi?id=152649=edit Date with Colons in Metadata SUMMARY The date format in Digikam should be * the same date format in all places * at least ISO date https://en.wikipedia.org/wiki/ISO_8601 * use the users locales settings (like TIME_STYLE=long-iso) STEPS TO REPRODUCE open Digikam and look at all different places where a date is printed. Screenshot attached. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux KDE Frameworks Version 5.98.0 Qt Version 5.15.5 (built against 5.15.5) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459232] Panel crashes when hovering over Task Manager entries with tooltips enabled
https://bugs.kde.org/show_bug.cgi?id=459232 --- Comment #7 from Jonas Rakebrandt --- Yes, this fixes it! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459232] Panel crashes when hovering over Task Manager entries with tooltips enabled
https://bugs.kde.org/show_bug.cgi?id=459232 --- Comment #3 from Jonas Rakebrandt --- Created attachment 152164 --> https://bugs.kde.org/attachment.cgi?id=152164=edit Backtrace with GDB I compiled most of the related packages with debug symbols and created a backtrace which lead me to the file `libtaskmanager/declarative/screencastingrequest.cpp` from `plasma-workspace`. Something seems to be broken for me in the `ScreencastingRequest::setUuid` function, specifically the `d->m_stream->deleteLater();` bit. Surprisingly everything seems work again after I just remove either that entire line. I don't really know if that is a safe thing to do though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459232] Panel crashes when hovering over Task Manager entries with tooltips enabled
https://bugs.kde.org/show_bug.cgi?id=459232 --- Comment #2 from Jonas Rakebrandt --- For me the issue actually occurs with both task manager styles and as previously said disabling tooltips makes them work again. Though if you say there's no issue for you it might just be a problem with how I compiled plasmashell on my system. I'll try to look further into it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459232] New: Panel crashes when hovering over Task Manager entries with tooltips enabled
https://bugs.kde.org/show_bug.cgi?id=459232 Bug ID: 459232 Summary: Panel crashes when hovering over Task Manager entries with tooltips enabled Classification: Unclassified Product: plasmashell Version: 5.25.90 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: xar...@protonmail.com Target Milestone: 1.0 SUMMARY The Plasma panel crashes when hovering over Task Manager entries with tooltips enabled. STEPS TO REPRODUCE 1. Create a panel with Task Manager 2. Hover the cursor over a Task Manager entry OBSERVED RESULT On Hover the Task Manager entry changes color as expected, then freezes in this state and then crashes the entire panel. EXPECTED RESULT Hovering over an entry should not crash the panel and display the tooltip if enabled. SOFTWARE/OS VERSIONS OS: Gentoo Linux Kernel: 5.19.8-xanmod1-x86_64 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 Graphics Platform: Wayland ADDITIONAL INFORMATION Disabling tooltips makes hovering over entries work as expected which makes me believe there's something going wrong in the tooltip/thumbnail generation. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 373428] Separator for split terminals not visible unless the background is black
https://bugs.kde.org/show_bug.cgi?id=373428 Jonas changed: What|Removed |Added CC||jonas...@gmail.com --- Comment #1 from Jonas --- I would also very much like to be able to configure the color of the divider. For me it's a dark grey and quite difficult to see between black terminals. I tried changing themes and restarting but that didn't seem to change it. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 456025] No remote keyboard input - implementation of RemoteDesktopPortal::NotifyKeyboardKeysym is missing/empty
https://bugs.kde.org/show_bug.cgi?id=456025 Jonas Eymann changed: What|Removed |Added CC||j.eym...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 456025] New: No remote keyboard input - implementation of RemoteDesktopPortal::NotifyKeyboardKeysym is missing/empty
https://bugs.kde.org/show_bug.cgi?id=456025
Bug ID: 456025
Summary: No remote keyboard input - implementation of
RemoteDesktopPortal::NotifyKeyboardKeysym is
missing/empty
Product: xdg-desktop-portal-kde
Version: git-master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: j.eym...@gmx.net
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
Target Milestone: ---
SUMMARY
***
After investigating, fixing and testing [an issue about the
RemoteDesktopPortalDialog not
appearing|https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/114],
I found out that RemoteDesktopPortal::NotifyKeyboardKeysym is currently not
implemented.
As a result, keyboard input is not possible in connections to a KDE Plasma
system using TeamViewer (which has support for sharing Wayland sessions,
[currently still
experimental|https://community.teamviewer.com/English/discussion/122410/teamviewer-support-on-wayland-experimental-state]).
***
STEPS TO REPRODUCE
1. Install current TeamViewer on a system running KDE Plasma ([a version which
includes above mentioned
fix|https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/114])
2. Connect to the system when running a Wayland session, allow mouse and
keyboard input
3. Attempt keyboard input from remote system
OBSERVED RESULT
Remote keyboard input is not possible
EXPECTED RESULT
Remote keyboard input should be possible
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro, KDE neon
(available in About System)
KDE Plasma Version: 5.24.5, 5.25.0
ADDITIONAL INFORMATION
Current implementation in
[remotedesktop.cpp|https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/blob/master/src/remotedesktop.cpp]
looks like this:
void RemoteDesktopPortal::NotifyKeyboardKeysym(const QDBusObjectPath
_handle, const QVariantMap , int keysym, uint state)
{
Q_UNUSED(session_handle)
Q_UNUSED(options)
Q_UNUSED(keysym)
Q_UNUSED(state)
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 455270] Line around auto-hide floating panel after making it visible over a fullscreen window
https://bugs.kde.org/show_bug.cgi?id=455270 Jonas Rakebrandt changed: What|Removed |Added CC||xar...@protonmail.com --- Comment #2 from Jonas Rakebrandt --- I have the same issue but with "Always Visible" instead of "Auto Hide". It seems like the line is a shadow that is being created when the panel has "grown" because of a maximized window and it doesn't get removed again after the panel shrinks. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-xanmod1-x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454410] New: No subwoofer sound and side channels are playing on the rear channels
https://bugs.kde.org/show_bug.cgi?id=454410 Bug ID: 454410 Summary: No subwoofer sound and side channels are playing on the rear channels Product: systemsettings Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jonas.ja...@gmail.com Target Milestone: --- SUMMARY *** No subwoofer sound and side channels are playing on the rear channels *** STEPS TO REPRODUCE 1. Use Sony STRDH790.CEK 7.2 Channel Dolby Atmos/DTS: X 4K HDR AV Receiver (or probably any 7.1 receiver) 2. In Kubuntu audio settings select "Digital Surround 7.1 (HDMI) Output" 3. Test audio channels OBSERVED RESULT No subwoofer sound Side channels are playing on rear channels EXPECTED RESULT Subwoofer sound Side channels play on side speakers SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447822] New: Menu entry in Settings should be "Manage Resource Libraries" instead of "Manage Resources Libraries".
https://bugs.kde.org/show_bug.cgi?id=447822 Bug ID: 447822 Summary: Menu entry in Settings should be "Manage Resource Libraries" instead of "Manage Resources Libraries". Product: krita Version: 5.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: jonas_ehrh...@yahoo.de Target Milestone: --- SUMMARY *** When opening the "Settings" menu bar entry, the second entry is calles "Manage Resources Libraries". I think it should be "Manage Resource Libraries", which is also the title of the window which opens after clicking the entry. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: Xubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 Jonas changed: What|Removed |Added CC||jonas...@gmail.com --- Comment #69 from Jonas --- I'm also affected by this, in my case it's because I'm synchronizing files via cloud storage between different computers, and sometimes an update from another machine only comes through after I opened an old version (at least I think that's what happens). The effect is also that I end up with annotations that I can't save (not even via "save as"), which is very annoying. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 447053] New: Editing Google event causes incorrect year
https://bugs.kde.org/show_bug.cgi?id=447053 Bug ID: 447053 Summary: Editing Google event causes incorrect year Product: kalendar Version: 0.3.1 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: k...@iwr.sh CC: c...@carlschwan.eu Target Milestone: --- SUMMARY After editing the date of a "Google Groupware" event, the year is incorrectly affected. Saving something like "17.12.21" as the date results in the event being set to occur in the year 1921. Furthermore, defining a date in the DD.MM. format results in the following error: "Invalid dates provided" STEPS TO REPRODUCE 1. Create a "Google Groupware" calendar source 2. Edit an existing event of the Google calendar 3. Change the date, eg. from "16.12.21" to "17.12.21" 4. Click Save OBSERVED RESULT - Year of event is 1921. EXPECTED RESULT - Year of event should be 2021. - It should also allow users to set the date in the DD.MM. format. SOFTWARE/OS VERSIONS Linux: 5.14.21-2 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446868] [x11] - 30bit color depth makes dock invisible with broken transparency
https://bugs.kde.org/show_bug.cgi?id=446868 --- Comment #6 from Jonas --- Created attachment 144480 --> https://bugs.kde.org/attachment.cgi?id=144480=edit full desktop capture after the patch; 2 screens (1080p, 1440p) The top and bottom latte panels are correctly shown in this image, now. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446868] [x11] - 30bit color depth makes dock invisible with broken transparency
https://bugs.kde.org/show_bug.cgi?id=446868 --- Comment #5 from Jonas --- Created attachment 144479 --> https://bugs.kde.org/attachment.cgi?id=144479=edit full desktop capture before the patch; 2 screens (1080p, 1440p) Neither of the menus are rendered -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446868] Dock not visible and transparency broken with X11set to 30bit color depth
https://bugs.kde.org/show_bug.cgi?id=446868 --- Comment #1 from Jonas --- This is my first time reporting a bug here so I am not completely familiar in how things are done. I have written a patch to solve this bug, but I am not sure how to link git and this bug tracker together. On top of that, I think that my patch needs improvement. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446868] Dock not visible and transparency broken with X11set to 30bit color depth
https://bugs.kde.org/show_bug.cgi?id=446868 Jonas changed: What|Removed |Added CC||m...@inty.dev -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446868] New: Dock not visible and transparency broken with X11set to 30bit color depth
https://bugs.kde.org/show_bug.cgi?id=446868 Bug ID: 446868 Summary: Dock not visible and transparency broken with X11set to 30bit color depth Product: lattedock Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: m...@inty.dev Target Milestone: --- Created attachment 144474 --> https://bugs.kde.org/attachment.cgi?id=144474=edit Blurred rectangle where dock should be STEPS TO REPRODUCE 1. create /etc/X11/xorg.conf.d/30-screensetup.conf Section "Screen" Identifier"Default Screen" Monitor"Configured Monitor" Device "Configured Video Device" DefaultDepth30 EndSection 2. Restart session or display manager sudo systemctl restart display-manager OBSERVED RESULT The lattedock gets loaded, but you can only see a blurred rectangle where it usually (see attached image) EXPECTED RESULT Dock loading normally with transparency SOFTWARE/OS VERSIONS Linux/KDE Plasma: 21.12 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION lattedock --version reports as 0.10.75 I couldn't find that in the version box above. -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 445301] New: blue text not well readable in dark mode.
https://bugs.kde.org/show_bug.cgi?id=445301 Bug ID: 445301 Summary: blue text not well readable in dark mode. Product: KSystemLog Version: 21.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: nicolas.ternis...@gmail.com Reporter: jonas...@gmail.com Target Milestone: --- Created attachment 143430 --> https://bugs.kde.org/attachment.cgi?id=143430=edit screenshot displaying badly readable text on dark background I'm using kubuntu 21.10 with the breeze dark theme, and the blue text in the log view is very hard to read on my screen. see attached screenshot. would it be possible to either use a shade of blue that is well visible on both light and dark background, or have different color themes depending on light vs dark mode? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444747] New: automatically remove newlines from filenames when renaming
https://bugs.kde.org/show_bug.cgi?id=444747 Bug ID: 444747 Summary: automatically remove newlines from filenames when renaming Product: dolphin Version: 21.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jonas...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- I often download pdfs and then rename them in dolphin with the title of the document that I either copied from a website or from the document itself. When doing this I regularly end up with unwanted linebreaks in the filename, for two reasons: * when selecting a line of text by double clicking in the browser and then copying with ctrl+c, the string that ends up in the clipboard is usually terminated with a newline * when copying the title out of the pdf itself, it is often broken in two lines if the title is too long for one line I don't want to have linebreaks in a filename in any situation, and can't think of a use case where they're desirable. Therefore I suggest that dolphin automatically eats all linebreaks that are inserted when renaming files via F2. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443544] New: Two actions want to use the same shortcut: Open Command Bar and Add Images
https://bugs.kde.org/show_bug.cgi?id=443544 Bug ID: 443544 Summary: Two actions want to use the same shortcut: Open Command Bar and Add Images Product: digikam Version: 7.1.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: j.andra...@gmail.com Target Milestone: --- When opening digikam, I get the following pop-up error: There are two actions (Open Command Bar, Add Images...) that want to use the same shortcut (Ctrl+Alt+I). This is most probably a bug. Please report it in bugs.kde.org I have not changed myself these shortcuts, so I am assuming this is a mismatch in the configuration when digikam was upgraded from one version to another. Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 digiKam 7.1.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442180] Unable to define Custom Oauth2 Settings
https://bugs.kde.org/show_bug.cgi?id=442180 --- Comment #3 from Jonas Andradas --- Hi Iyán, thank you for your comments. I have tried changing this using qdbus as per your suggestions. I have managed to change both the oAuthAppId and oAuth2ReturnURI with qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_10 /Settings org.kde.Akonadi.Ews.Settings.oAuth2AppId "d3590ed6-52b3-4102-aeff-aad2292ab01c" qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_10 /Settings org.kde.Akonadi.Ews.Settings.setOAuth2ReturnUri urn:ietf:wg:oauth:2.0:oob These settings are changed fine, but when I try to authenticate, I am taken through the journey just as before, so still not able to use Kmail here :( When access is not allowed because the device is not "configured properly", this is what I get from EWS in the error: App name: App id: ---- IP address: Device identifier: Not available Device platform: Android Device state: Unregistered So, despite setting the Custom UserAgent to Microsoft Office 2016, and the OAuth2 App id to Outlook's, it seems that, for some reason, these are not being properly sent to EWS, or at least not in the way the server expects them. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442180] Unable to define Custom Oauth2 Settings
https://bugs.kde.org/show_bug.cgi?id=442180 Jonas Andradas changed: What|Removed |Added CC||j.andra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442180] Unable to define Custom Oauth2 Settings
https://bugs.kde.org/show_bug.cgi?id=442180 --- Comment #1 from Jonas Andradas --- Sorry, forgot to add the URL to Chriss' blog [1] from where I got the Oauth2AppId setting name: [1] https://micreabog.wordpress.com/2017/10/05/akonadi-ews-resource-now-part-of-kde-pim/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442180] New: Unable to define Custom Oauth2 Settings
https://bugs.kde.org/show_bug.cgi?id=442180 Bug ID: 442180 Summary: Unable to define Custom Oauth2 Settings Product: Akonadi Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: j.andra...@gmail.com CC: kri...@op.pl Target Milestone: --- In order for the EWS in my organization to work properly from Linux a set of custom Oauth2 settings need to be defined/overriden from the defaults. It was possible to have this working from Evolution (using evolution-ews) when the following settings were defined to specific values: * OAB URL: in the form of https://outlook.office365.com/OAB//oab.xml * Tenant * Application ID (for example using Outlook's "d3590ed6-52b3-4102-aeff-aad2292ab01c" * Redirect URI: urn:ietf:wg:oauth:2.0:oob I do not see a way to setup these settings from KMail UI, but have read that I could modify the settings in ~/.config/akonadi_ews_resource_Xrc (X being 0 or above, depending on the configuration). I have modified this settings, adding an `Oauth2AppId` option, based on Chriss' blog entry [1], and tried to guess the names for the other settings, but to no avail. An example of how my configuration file is can be found below: ``` AuthMode=oauth2 AutoDiscovery=false BaseUrl=https://outlook.office365.com/EWS/Exchange.asmx OABUrl=https://outlook.office365.com/OAB//oab.xml OAuth2AppId=d3590ed6-52b3-4102-aeff-aad2292ab01c Oauth2Tenant= Oauth2RedirectUri=urn:ietf:wg:oauth:2.0:oob ``` SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 11 (sid) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438999] New: QVariant assignment (-Wclazy-qt6-deprecated-api-fixes)
https://bugs.kde.org/show_bug.cgi?id=438999 Bug ID: 438999 Summary: QVariant assignment (-Wclazy-qt6-deprecated-api-fixes) Product: clazy Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jo...@jkvinge.net CC: smart...@kde.org Target Milestone: --- SUMMARY QVariant assignment (-Wclazy-qt6-deprecated-api-fixes) STEPS TO REPRODUCE The following code gives warning: QVariant variant; QString string; variant = string; OBSERVED RESULT warning: operator does not exist in Qt6. Using QVariant::compare() instead [-Wclazy-qt6-deprecated-api-fixes] EXPECTED RESULT No warning. Is this a bug? I'm compiling with Qt dev branch and it does compile and work. Changing it setValue instead does not produce the warning: variant.setValue(string); SOFTWARE/OS VERSIONS Qt Version: Latest dev branch clazy version: 1.9 clang version: 12.0.0 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 438998] New: QProcess::startDetached gives qt6-deprecated-api-fixes warning
https://bugs.kde.org/show_bug.cgi?id=438998 Bug ID: 438998 Summary: QProcess::startDetached gives qt6-deprecated-api-fixes warning Product: clazy Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jo...@jkvinge.net CC: smart...@kde.org Target Milestone: --- SUMMARY There is no QProcess::startDetachedCommand() function in Qt 6 as of today, using the Qt 6 dev branch. OBSERVED RESULT jonas@jonas:~/Projects/strawberry/build> clazy-standalone -checks=qt6-deprecated-api-fixes -p compile_commands.json ../strawberry/src/core/utilities.cpp /home/jonas/Projects/strawberry/strawberry/src/core/utilities.cpp:393:10: warning: call function QProcess::startDetached(). Use function QProcess::startDetachedCommand() instead [-Wclazy-qt6-deprecated-api-fixes] proc.startDetached(command, QStringList() << command_params << "--select" << url.toLocalFile()); ^ startDetachedCommand 1 warning generated. EXPECTED RESULT No warning -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438290] New: option "C.UTF-8" should be available instead of / in addition to locale "C"
https://bugs.kde.org/show_bug.cgi?id=438290 Bug ID: 438290 Summary: option "C.UTF-8" should be available instead of / in addition to locale "C" Product: systemsettings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_formats Assignee: se...@kde.org Reporter: jonas...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- In the drop-down menus in the "Formats" dialog, the first option that I see is labeled "Default (C)", and selecting it results in my terminal not treating unicode correctly anymore. I know that there's a unicode version of the C-locale called C-UTF-8. I think it would be good to include it instead of or in addition to the old-school C locale. I'm using Kubuntu 20.04. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438280] default locale should be C.UTF-8, not C
https://bugs.kde.org/show_bug.cgi?id=438280 --- Comment #2 from Jonas --- OK but what about C.UTF-8 being an option in the dropdown menu? For me, the first entry in the menu is "Default (C)", and "C.UTF-8" is not in the menu as far as I can see. Maybe I wasn't very clear, but the feature that I would like to see at least, is to have "C.UTF-8" available in the menu additionally (if not as a replacement of "C"). I don't think the suggestion of having the option of "C.UTF-8" in the dropdown is a duplicate of the bug you linked. If you want I can add a new bug report that's more clear. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438280] New: default locale should be C.UTF-8, not C
https://bugs.kde.org/show_bug.cgi?id=438280 Bug ID: 438280 Summary: default locale should be C.UTF-8, not C Product: systemsettings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_formats Assignee: se...@kde.org Reporter: jonas...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- As title says. In any case, C.UTF-8 should be an option. Why should I have to have to select from a list of nation-states just to get reasonable defaults? I'm using kubuntu 20.04. I can't tell you which KDE version since it's not shown in the "About KDE" dialog anymore (why?) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 394403] Width column list resize every time to restart
https://bugs.kde.org/show_bug.cgi?id=394403 Jonas Eberle changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||flightvis...@googlemail.com --- Comment #4 from Jonas Eberle --- I can confirm (kontact 5.13.3) It does not happen always, but approx. every 3rd start of kontact. A workaround to restore the layout is to: * right-click on table header * Select "Adapt Column Width" (This is not persistent, though) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435473] New: grub-theme-breeze fails to install on KDE Neon with ZFS on root
https://bugs.kde.org/show_bug.cgi?id=435473 Bug ID: 435473 Summary: grub-theme-breeze fails to install on KDE Neon with ZFS on root Product: Breeze Version: 5.21.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: GRUB Assignee: plasma-de...@kde.org Reporter: kdeb...@l3m.ch CC: sit...@kde.org Target Milestone: --- SUMMARY Error message: Preparing to unpack .../grub-theme-breeze_5.21.4-0xneon+20.04+focal+release+build24_amd64.deb ... Unpacking grub-theme-breeze (5.21.4-0xneon+20.04+focal+release+build24) over (5.21.3-0xneon+20.04+focal+build23) ... dpkg: error processing archive /var/cache/apt/archives/grub-theme-breeze_5.21.4-0xneon+20.04+focal+release+build24_amd64.deb (--unpack): unable to make backup link of './boot/grub/themes/breeze/progress_bar2_c.png' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/grub-theme-breeze_5.21.4-0xneon+20.04+focal+release+build24_amd64.deb ZSys is adding automatic system snapshot to GRUB menu E: Sub-process /usr/bin/dpkg returned an error code (1) STEPS TO REPRODUCE 1. Have KDE neon on ZFS filesystem with grub-theme-breeze in a version older than 5.21.4 2. apt update && apt dist-upgrade OBSERVED RESULT Package fails to install. EXPECTED RESULT Package can be installed without error. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.21 User Edition KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It's possible to manually copy the images from an extracted package to the target folder, but installing the package fails. Likely also related to this: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1873008 Related entries from /etc/fstab: # /boot/efi was on /dev/nvme0n1p3 during installation UUID=(some uuid) /boot/efi vfatumask=0022,fmask=0022,dmask=0022 0 1 /boot/efi/grub /boot/grub nonedefaults,bind 0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 188764] Ambiguous shortcuts in all actions when starting Kate with split views
https://bugs.kde.org/show_bug.cgi?id=188764 Jonas changed: What|Removed |Added CC|fire...@firefly.nu | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430243] New: fulltext search for Å doesn't work
https://bugs.kde.org/show_bug.cgi?id=430243 Bug ID: 430243 Summary: fulltext search for Å doesn't work Product: okular Version: 1.9.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: jonas...@gmail.com Target Milestone: --- SUMMARY fulltext search for "Å" with okular in https://arxiv.org/pdf/1301.2134.pdf yields no results, even though I got the character out of this document by selecting and copying. Searching for the same character in the same document in evince or qpdfview works as expected. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 429791] New: okular can only open files in user directory
https://bugs.kde.org/show_bug.cgi?id=429791 Bug ID: 429791 Summary: okular can only open files in user directory Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: jonas...@gmail.com CC: neon-b...@kde.org Target Milestone: --- SUMMARY Using kubuntu 20.04. I installed the okular snap since it's a newer version than the deb. However, it can't open files outside my home directory, e.g. files in /usr/share/doc. Specifically I get the error message `Could not open file:///usr/share/doc...` in a dialogue window when trying to do `okular /absolute/path`, and `Could not open file:///var/lib/snapd/void/filename.pdf` when doing `okular relative/path`. `snap info okular` gave me a url that sent me to this form, so I hope it's the right place to report the bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 186531] [JJ] Trim Margin doesn't work if paper color was set
https://bugs.kde.org/show_bug.cgi?id=186531 Jonas changed: What|Removed |Added CC||jonas...@gmail.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #26 from Jonas --- (A variation of) the problem still exists for me (Kubuntu 20.04, okular 1.9.3). More precisely, trim margins stops working if I set a background color, and then disable the background color feature again. After setting the background color, okularpartrc contains a block like this: [Document] ChangeColors=true PaperColor=202,254,78 RenderMode=Paper With background color set, trim margins is still working. After disabling the background color again, this block changes to [Document] PaperColor=202,254,78 RenderMode=Paper and trim margin stops working after restarting okular. Deleting the block (or just the PaperColor line) solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334019] Okular should warn if closing with multiple tabs opened
https://bugs.kde.org/show_bug.cgi?id=334019 Jonas changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||jonas...@gmail.com --- Comment #16 from Jonas --- I think there should also be an option in settings. Otherwise, how do I get the confirmation dialog back once I have clicked "Don't ask me again"? (For now, could anybody tell me what to add/delete in which config file to get the dialog back?) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425251] After cancelled upgrade I don't know how to restart the upgrade
https://bugs.kde.org/show_bug.cgi?id=425251 Jonas Eberle changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Jonas Eberle --- Thank you very much Colin, That's exactly the information I missed on https://community.kde.org/Neon/FocalUpgrades as for me logging in/out doesn't bring up the notification again. - do you know who I could talk to to suggest including it there? On that note (but another topic) it might also be important to have better public information about what `pkcon update` really does. If it is just a wrapper around the OS's update mechanisms without any additional logic it would spread a lot less uncertainty. As package management in neon is suggested to be done with `pkcon`, I didn't want to just start the Ubuntu updater in fear it could do harm. In forums and on reddit people suggest `do-release-upgrade --allow-third-party` but nobody yet seemed to have the original command that KDE runs - thank you! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425251] New: After cancelled upgrade I don't know how to restart the upgrade
https://bugs.kde.org/show_bug.cgi?id=425251 Bug ID: 425251 Summary: After cancelled upgrade I don't know how to restart the upgrade Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: flightvis...@googlemail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- STEPS TO REPRODUCE I just started the upgrade to Focal but it had to be cancelled due to insufficient disk space. So now I cleaned up some space. OBSERVED RESULT I followed https://community.kde.org/Neon/FocalUpgrades again but after logout/login I do not get the upgrade notifier. Do you know how I can restart the upgrade? EXPECTED RESULT Either: 1) Upgrade notification is shown or 2) Upgrade notes https://community.kde.org/Neon/FocalUpgrades should mention the console command to initiate an upgrade. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 --- Comment #21 from Jonas Schäfer --- Hi Martin, I followed the idea to upgrade to 5.14, and everything has improved a lot back to the previous level! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 Jonas Wielicki changed: What|Removed |Added CC||jo...@wielicki.name --- Comment #17 from Jonas Wielicki --- I would like to confirm the imap resource problem being similar, but I don’t know which specific perf invocation produces output like the one shown above. The symptoms seem very similar and I can see it spinning on an fd like the maildir resource here in strace. If you could hand me the perf command lines, I’d try to confirm and if it matches, post here or create a new bugreport if it doesn’t match. (I never used perf before, came up with perf report -g but that didn’t look structurally similar; but maybe I’m missing something else.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423522] New: Sensor Widget Bar Style hides legend
https://bugs.kde.org/show_bug.cgi?id=423522 Bug ID: 423522 Summary: Sensor Widget Bar Style hides legend Product: plasmashell Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: jonasple...@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The "Bar Chart" Display style of the new sensors widgets (which are a awesome addition) auto-hides the legends of the associated sensors. The Legend cannot be unhidden. Same happens when creating new sensor widget with "Bar" Display style. STEPS TO REPRODUCE 1. Create New Sensors Widget 2. Add some sensor 3. Switch to "Bar Chart" Display Style OBSERVED RESULT - No Legends of sesors EXPECTED RESULT - Legends should be there - Legends should be hidable by button SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux 5.4.48-1-lts (available in About System) KDE Plasma Version: plasma 5.19.2 KDE Frameworks Version: plasma-framework 5.71.0-2 Qt Version: 5.15.0-3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 Jonas changed: What|Removed |Added CC||jonasple...@gmx.de --- Comment #5 from Jonas --- For me too in 5.19.2 Memory Sensors and fans as well as ethernet up/down and usage of Drives are not affected in my setup. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421399] Different setting of continuous view mode per windows does not work correctly
https://bugs.kde.org/show_bug.cgi?id=421399 --- Comment #5 from Jonas Schürmann --- I created a screencast of the page lockup and attached it to this issue. -- You are receiving this mail because: You are watching all bug changes.
