[kwin] [Bug 445259] Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=445259 --- Comment #7 from Philipp Reichmuth --- In my case, after updating to Plasma 5.23.4 I now get the same behaviour as in comment 4. When starting Chromium from the command line with `chromium --enable-features=UseOzonePlatform --ozone-platform=wayland`, the browser window opens normally (same with Brave and Edge) After maximizing Chromium, closing the maximized window and starting it again with the same command line command, the window no longer comes up, while the command is running. It this state is not visible in the KWin debug console. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #6 from Philipp Reichmuth --- Where do I find this command? Currently I get the following: # drm_info Wenn 'drm_info' kein Tippfehler ist, können Sie command-not-found benutzen, um das Paket zu finden, das den Befehl enthält, z. B.: cnf drm_info # cnf drm_info drm_info: Befehl nicht gefunden -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 446104] QtWebengine-based views broken in master - affects Kmail + Akregator + more in wayland session
https://bugs.kde.org/show_bug.cgi?id=446104 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #2 from Philipp Reichmuth --- I'm seeing this in Qutebrowser and Falkon and what fixes it is setting QT_WEBENGINE_DISABLE_WAYLAND_WORKAROUND=1 (the variablecomes from an OpenSUSE patch: https://build.opensuse.org/package/view_file/KDE:Qt:5.15/libqt5-qtwebengine/disable-gpu-when-using-nouveau-boo-1005323.diff?expand=1) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 Philipp Reichmuth changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Philipp Reichmuth --- It's back. Last thing I did was to put the laptop to sleep by closing the lid. Before suspend, the external screen was set to 3840x2160. Upon wakeup, it came up at 2560x1440 and nothing I I would change in the display settings KCM would actually set the monitor to anything else but 2560x1440. It's as if KWin refused to change the physical resolution. I could change scaling settings and they would get applied to 2560x1440, no matter what resolution I actually selected. Windows came up as if the size was still 3840x2160 (i.e. with the outer controls outside the screen margins). I managed to restore it to normal was to unplug the monitor's power cable. This led to a crash in Plasmashell (bug 438839) and Akonadi (bug 445249), but when Plasmashell came up again on the external monitor it was at 3840x2160. System information: Operating System: openSUSE Tumbleweed 20211202 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.5-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #51 from Philipp Reichmuth --- I'm in favour of reopening, I don't think this has been fixed. I am still observing this in Plasma 5.23.4. I power down my external HDMI monitor, Plasmashell goes down, taking all applications with it. In addition (probably as a consequence of Plasmashell going down) Akonadi segfaults. This is on OpenSUSE TW, Plasma 5.34.4, Frameworks 5.88, Qt 5.15.2, libqt5-qtwayland 5.15.2+kde34-1.2. -- 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 Philipp Reichmuth changed: What|Removed |Added CC|philipp.reichm...@gmail.com | -- 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 Philipp Reichmuth changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #16 from Philipp Reichmuth --- (In reply to linadmin from comment #15) > However, I disagree that this is an upstream issue. When the developer of > Gwenview decides to use some unstable library with version numbers 0.xx he > holds the obligation to check from time to time [...] Plenty of software is at 0.x without being unstable, or at >= 1.x without being stable. Exiv2 is 13 years old and pretty stable. All of KDE uses exiv2. There has been talk of making it a KDE project. Of course it has bugs. The best way to get them fixed is to report them in the right place. The bug reports states that a particular field is displayed as a bunch of integers. This is not happening any more, so the bug as reported has been resolved upstream and is gone. If there is some other undesirable behaviour now, this should IMHO be reported separately. -- 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 --- Comment #14 from Philipp Reichmuth --- (In reply to linadmin from comment #13) > (In reply to Philipp Reichmuth from comment #12) > > I think bashing developers is counterproductive. I think it's more probable > > that they didn't have test cases that were generated by whatever process you > > use to put GPS tags in your files. Where do those tags come from? I notice > > that the lengths of several fields are off. > > I do know that bashing may be counterproductive, but my many years of > waiting without success proved that positive feedback does not help either. A bug tracker is not a good place for venting and deliberately bashing developers is destructive, no matter how unhappy we are. I think this was probably an upstream issue that was fixed upstream unnoticed while you were waiting. If you still have access to your old system, and you want to be sure whether the bug was fixed in Gwenview or exiv2, you can verify this: go back to the old version where you see the Gwenview behaviour in the original bug report, check the exiv2 version installed there, and read out the broken 266-byte GPSAreaInformation tag on the command line. (In reply to linadmin from comment #11) > However, I do not see why it should display the additional information that > the GPSAreaInformation is in such and such character coding. It does not > show that on City and City2 which also can be Unicode and which have already > worked as expected in older versions. I conclude that the Gwenview project > management it too lousy to believe: They _somehow_ worked at the bug > without looking how it has been done on other fields. (In reply to linadmin from comment #13) > There is the EXIF standards documentation and Gwenview must first of all > adhere to this paper. [...] As fas as I can see Gwenview uses exiv2 for handling metadata. On my system the metadata is displayed exactly as exiv2 also shows it. So you might be holding the developers accountable for something with which they have nothing to do. According to the exiv2 manpage, the character specification applies to the tags Exif.Photo.UserComment, Exif.GPSInfo.GPSProcessingMethod and Exif.GPSInfo.GPSAreaInformation. It does not mention that this applies to tags from the manufacturer MakerNote such as Exif.Panasonic.City and I wouldn't expect it to, as they are not part of the standard. Either way I think we are talking about an upstream issue. -- 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 --- Comment #12 from Philipp Reichmuth --- (In reply to linadmin from comment #11) > (In reply to Philipp Reichmuth from comment #10) > > Created attachment 144076 [details] > > Screenshot of the GPSAreaInformation tag in Gwenview 21.08.3 > > > > Here's how Gwenview displays the tag on my system, it looks OK. > > Maybe the issue is with a particular combination of libraries and tags? > > Thousand thanks for your efforts. Indeed your version does display it in a > different way from my slightly older version. > I therefore installed Debian Bullseye which has Gwenview 20.12.3 and the > display indeed looks as you showed it. > > However, I do not see why it should display the additional information that > the GPSAreaInformation is in such and such character coding. It does not > show that on City and City2 which also can be Unicode and which have already > worked as expected in older versions. It shows exactly what you have in your file, as reported by libexiv2: # exiv2 -g City P1020755A.JPG Exif.Panasonic.City Undefined 72 Mecklenburgische Seenplatte Exif.Panasonic.City2 Undefined 72 Neubrandenburg # exiv2 -g GPS P1020755A.JPG Exif.Image.GPSTagLong1 15800 Exif.GPSInfo.GPSVersionIDByte4 2.3.0.0 Exif.GPSInfo.GPSLatitudeRef Ascii 2 Norden Exif.GPSInfo.GPSLatitude Rational3 53deg 32' 51" Exif.GPSInfo.GPSLongitudeRef Ascii 2 Osten Exif.GPSInfo.GPSLongitudeRational3 13deg 15' 13" Exif.GPSInfo.GPSTimeStampRational3 16:09:34 Exif.GPSInfo.GPSStatus Ascii 2 Messung wird durchgeführt Exif.GPSInfo.GPSMeasureMode Ascii 2 Zweidimensionale Messung Exif.GPSInfo.GPSDOP Rational1 9/10 Exif.GPSInfo.GPSMapDatum Ascii 10 WGS-84 Exif.GPSInfo.GPSProcessingMethod Undefined 14 charset=Ascii GPS Exif.GPSInfo.GPSAreaInformation Undefined 266 charset=Unicode Dampferanlegestelle Exif.GPSInfo.GPSDateStampAscii 11 2019:07:14 > I conclude that the Gwenview project management it too lousy to believe: > They _somehow_ worked at the bug without looking how it has been done on > other fields. I think bashing developers is counterproductive. I think it's more probable that they didn't have test cases that were generated by whatever process you use to put GPS tags in your files. Where do those tags come from? I notice that the lengths of several fields are off. Maybe that process has something to do with the behaviour we're seeing here. For example, there are digital cameras that zero-pad the EXIF strings to a fixed length, but I'm not sure whether Panasonic is one of them. -- 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 --- Comment #10 from Philipp Reichmuth --- Created attachment 144076 --> https://bugs.kde.org/attachment.cgi?id=144076=edit Screenshot of the GPSAreaInformation tag in Gwenview 21.08.3 Here's how Gwenview displays the tag on my system, it looks OK. Maybe the issue is with a particular combination of libraries and tags? -- 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 --- Comment #9 from Philipp Reichmuth --- (In reply to linadmin from comment #6) > Please find enclosed jpg-image with embedded GPS info which is erroneously > displayed as shown in enclosed screenshot gwenview-erroneous-display.png For me Gwenview displays the GPS Area Information in that file just fine. I can post a screenshot if you want. This is with Gwenview 21.08.3 on OpenSUSE Tumbleweed. (In reply to linadmin from comment #8) > (In reply to John Clark from comment #2) > > Created attachment 143703 [details] > > Gwenview GPS Area Information > > 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. > > For me that exiv2 command does not work at all? > Maybe that with correct parameters it does set the text in a different was? It looks like it. Check out the length of the GPSAreaInformation field (266 vs. 46, 27 without the charset tag). # exiv2 -g GPSAreaInformation P1020755A.JPG Exif.GPSInfo.GPSAreaInformation Undefined 266 charset=Unicode Dampferanlegestelle # cp P1020755A.JPG exif-gps-area-information-test.jpg # exiv2 -M"set Exif.GPSInfo.GPSAreaInformation charset=Unicode Dampferanlegestelle" ./exif-gps-area-information-test.jpg # exiv2 -g GPSAreaInformation ./exif-gps-area-information-test.jpg Exif.GPSInfo.GPSAreaInformation Undefined 46 charset=Unicode Dampferanlegestelle -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441417] Monitor layout and dimensions don't match resolution when using scaling
https://bugs.kde.org/show_bug.cgi?id=441417 --- Comment #8 from Philipp Reichmuth --- (In reply to Nate Graham from comment #2) > *** Bug 445757 has been marked as a duplicate of this bug. *** I'm not sure that bug 445757 is actually a duplicate. This bug seems to be about logical sizes being calculated wrong, while bug 445757 is about the confusing display of resolutions in the pager applet in principle - the physical resolution is not shown, so users see the logical size and think that it's the physical resolution and that their display is not used at its full capability. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445757] Confusing display of resolution of scaled screens in Wayland
https://bugs.kde.org/show_bug.cgi?id=445757 Philipp Reichmuth changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #2 from Philipp Reichmuth --- This is IMHO not a duplicate of bug 441417. Bug 441417 is about the displayed logical sizes being calculated incorrectly. This, however, is about how the resolution should be shown in addition to the logical size. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 --- Comment #8 from Philipp Reichmuth --- I guess. I've refiled it there -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 Philipp Reichmuth changed: What|Removed |Added CC||kwin-bugs-n...@kde.org Platform|Other |openSUSE RPMs Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Component|wayland-generic |window decoration Product|kwin|Breeze Version|5.23.2 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 --- Comment #6 from Philipp Reichmuth --- It populates that from the app_id, probably, just calling it "class"? Then it's a matter of applying it to window decorations the same way as to window rules. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 Philipp Reichmuth changed: What|Removed |Added Version|5.23.2 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #9 from Philipp Reichmuth --- Created attachment 143785 --> https://bugs.kde.org/attachment.cgi?id=143785=edit Backdrop with oversized Yakuake window after booting into KWin Wayland 5.23.3 Another example - opening Yakuake after a fresh reboot into KWin 5.23.3 under Wayland. The Yakuake window extends across both screens, roughly the same as the backdrop of the left screen. There are clearly some scaling/positioning issues here. The left screen is my 2560x1440 laptop screen @ 200%, the right screen is an external 4K monitor running at 3840x2160 @ 200%. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #8 from Philipp Reichmuth --- Created attachment 143784 --> https://bugs.kde.org/attachment.cgi?id=143784=edit Backdrop after booting into KWin Wayland 5.23.3 I'm seeing it again. Now the wallpaper of the left screen extends into the right screen. Looks like there are some other positioning issues (KRunner opens in a strange position that is rougly in the middle of the wallpaper of the left screen) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445757] New: Confusing display of resolution of scaled screens in Wayland
https://bugs.kde.org/show_bug.cgi?id=445757 Bug ID: 445757 Summary: Confusing display of resolution of scaled screens in Wayland Product: KScreen Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY The Display Settings KCM will show the resolution of the screen in the scaled coordinate system of the Wayland compositor. This means that it will show a value that does not correspond to the physical resolution of the monitor, but with the screen scale factor applied. This can be confusing to new users, because they are used to think in terms of monitor resolutions, not screen coordinates. It would be preferable to show both the resolution of the scaled coordinate system, as well as the physical resolution of the monitor in the same place. STEPS TO REPRODUCE 1. On Wayland, open the Display Settings KCM and set scaling for a display to a value other than 100%. 2. Look at the resolution shown inside the screen icon in the top panel. OBSERVED RESULT E.g. for a 4K/3840x2160 screen at 200% scaling, the screen icon will show "(1920x1080)", even though the physical resolution is still 3840x2160. The KCM will show the physical resolution 3840x2160 in the dropdown box under "Resolution", but it is confusing to new users - it was to me. EXPECTED RESULT The screen icon should show a more descriptive text that includes the scale factor, e.g.: 1920x1080 (3840x2160 @ 200%) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 2026 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-3-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Every now and then there are discussions where new users are asking questions related to this, e.g. https://www.reddit.com/r/kde/comments/qxil1r/scaling_4k_monitor_without_loss_of_resolution/. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #3 from Philipp Reichmuth --- Similar scaling issues were reported in bug 445680. -- 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 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #1 from Philipp Reichmuth --- Can you provide a sample file? I wanted to see if I can reproduce this and went through a bunch of my own photos, as well as sample JPEGs from places like https://github.com/ianare/exif-samples/tree/master/jpg/gps, and didn't find any that have this particular tag. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #7 from Philipp Reichmuth --- I now have the situation where after a reboot, the wallpaper on screen 1 loads just fine, while the same wallpaper on screen 2 "jumps" repeatedly from the properly scaled version to a 200% scaled version and back :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444904] Unrecoverable plasma shell crash on dragging firefox tab in wayland.
https://bugs.kde.org/show_bug.cgi?id=444904 --- Comment #8 from Philipp Reichmuth --- (In reply to Shubham Arora from comment #7) > Try enabling gfx.webrender.all as well. Make sure Fission is enabled and web > gpu from about:preferences#experimental . So I've enabled gfx.webrender.all, fission.autostart and dom.webgpu.enabled, restarted Firefox and dragged about 20 tabs from different websites to my desktop without a crash. This is on OpenSUSE Tumbleweed with the MozillaFirefox package 93.0-80.3 from the home:trmdi:Tumbleweed repo (because it has the global menu patch), with KDE Wayland 5.23.2. I'm not saying that this issue doesn't happen, only that I can't reproduce it yet. If/when it happens, I will post again here. Either way it should not bring down Plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 445434] New: Gwenview crash when clicking "crop" button
https://bugs.kde.org/show_bug.cgi?id=445434
Bug ID: 445434
Summary: Gwenview crash when clicking "crop" button
Product: gwenview
Version: 21.08.3
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: philipp.reichm...@gmail.com
Target Milestone: ---
Application: gwenview (21.08.3)
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-2-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Opened an image, selected the Crop tool from the toolbar on the left.
Gwenview reproducibly crashes for me when cropping any image.
The crash can be reproduced every time.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 QScreen::geometry (this=0x0) at kernel/qscreen.cpp:413
#7 0x7f0f0f3319b5 in Gwenview::CropWidgetPrivate::initRatioComboBox
(this=0x56366c4e9eb0) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/cropwidget.cpp:203
#8 Gwenview::CropWidget::CropWidget (this=, parent=, imageView=, cropTool=, this=, parent=, imageView=, cropTool=) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/cropwidget.cpp:396
#9 0x7f0f0f332f70 in Gwenview::CropToolPrivate::setupWidget
(this=0x56366c4ff7d0) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/croptool.cpp:203
#10 Gwenview::CropTool::CropTool (this=, view=,
this=, view=) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/lib/crop/croptool.cpp:234
#11 0x56366aab02cc in Gwenview::ImageOpsContextManagerItem::crop
(this=0x56366c28b670) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/app/imageopscontextmanageritem.cpp:264
#12 Gwenview::ImageOpsContextManagerItem::qt_static_metacall
(_o=0x56366c28b670, _id=, _a=, _c=) at
/usr/src/debug/gwenview5-21.08.3-1.1.x86_64/build/app/gwenview_autogen/EWIEGA46WW/moc_imageopscontextmanageritem.cpp:115
#13 0x7f0f0d713078 in doActivate (sender=0x56366c19ddc0,
signal_index=4, argv=0x7fff03a218d0) at kernel/qobject.cpp:3898
#14 0x7f0f0d70c50f in QMetaObject::activate
(sender=sender@entry=0x56366c19ddc0, m=m@entry=0x7f0f0ea0c0a0,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff03a218d0)
at kernel/qobject.cpp:3946
#15 0x7f0f0e4ed182 in QAction::triggered (this=this@entry=0x56366c19ddc0,
_t1=) at .moc/moc_qaction.cpp:376
#16 0x7f0f0e4efdb4 in QAction::activate (this=0x56366c19ddc0,
event=) at kernel/qaction.cpp:1161
#17 0x7f0f0e5e8a0a in QAbstractButtonPrivate::click (this=0x563672befd90)
at widgets/qabstractbutton.cpp:398
#18 0x7f0f0e5e8b63 in QAbstractButton::mouseReleaseEvent
(this=0x563672bee010, e=0x7fff03a21e70) at widgets/qabstractbutton.cpp:1044
#19 0x7f0f0e6e139a in QToolButton::mouseReleaseEvent (this=,
e=) at widgets/qtoolbutton.cpp:622
#20 0x7f0f0e53576e in QWidget::event (this=0x563672bee010,
event=0x7fff03a21e70) at kernel/qwidget.cpp:9020
#21 0x7f0f0e4f3a7f in QApplicationPrivate::notify_helper
(this=this@entry=0x56366bccdb30, receiver=receiver@entry=0x563672bee010,
e=e@entry=0x7fff03a21e70) at kernel/qapplication.cpp:3632
#22 0x7f0f0e4fb584 in QApplication::notify (this=0x7fff03a21b90,
receiver=0x563672bee010, e=0x7fff03a21e70) at kernel/qapplication.cpp:3076
#23 0x7f0f0d6dc9fa in QCoreApplication::notifyInternal2
(receiver=0x563672bee010, event=0x7fff03a21e70) at
kernel/qcoreapplication.cpp:1064
#24 0x7f0f0e4fa093 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x563672bee010, event=event@entry=0x7fff03a21e70,
alienWidget=alienWidget@entry=0x563672bee010, nativeWidget=0x56366bd33120,
buttonDown=, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#25 0x7f0f0e54e83c in QWidgetWindow::handleMouseEvent (this=0x56366c2d6e40,
event=0x7fff03a22140) at kernel/qwidgetwindow.cpp:683
#26 0x7f0f0e551c55 in QWidgetWindow::event (this=0x56366c2d6e40,
event=0x7fff03a22140) at kernel/qwidgetwindow.cpp:300
#27 0x7f0f0e4f3a7f in QApplicationPrivate::notify_helper (this=, receiver=0x56366c2d6e40, e=0x7fff03a22140) at
kernel/qapplication.cpp:3632
#28 0x7f0f0d6dc9fa in QCoreApplication::notifyInternal2
(receiver=0x56366c2d6e40, event=0x7fff03a22140) at
kernel/qcoreapplication.cpp:1064
#29 0x7f0f0dda15c7 in QGuiApplicationPrivate::processMouseEvent
(e=0x56366c50b3c0) at kernel/qguiapplication.cpp:2282
#30 0x7f0f0dd7778c in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:1169
#31 0x7f0f0b906a80 in userEventSourceDispatch
(source=source@entry=0x56366bd07fe0) at qeventdispatcher_glib.cpp:74
#32
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 Philipp Reichmuth changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Philipp Reichmuth --- After some time the issue went away, so I'm setting this to WORKSFORME for the time being. Will report in more detail if/when it comes back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444904] Unrecoverable plasma shell crash on dragging firefox tab in wayland.
https://bugs.kde.org/show_bug.cgi?id=444904 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #6 from Philipp Reichmuth --- As described, it works for me - i.e. I can drag a tab from Firefox 93 to the desktop to create a new window, and Plasma 5.23.2 doesn't crash. However, when I set "layers.acceleration.force-enabled" to "true", dragging a tab to the desktop will no longer create a new window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435220] Cannot paste text copied from firefox outside firefox in wayland session
https://bugs.kde.org/show_bug.cgi?id=435220 Philipp Reichmuth changed: What|Removed |Added Version|5.21.5 |5.23.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #12 from Philipp Reichmuth --- Bug 435220 might be a duplicate of this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435220] Cannot paste text copied from firefox outside firefox in wayland session
https://bugs.kde.org/show_bug.cgi?id=435220 Philipp Reichmuth changed: What|Removed |Added Version Fixed In|5.22| Status|REPORTED|CONFIRMED CC||philipp.reichm...@gmail.com Ever confirmed|0 |1 --- Comment #9 from Philipp Reichmuth --- For what it's worth, I have this problem now with Plasma 5.23.2. I select text in Firefox 93, hit Ctrl+C and it doesn't appear in Klipper. Some time ago it worked, so the issue seems to be transient, but it's definitely still there. Other issues noticeable at the moment: - Firefox does not show the global menu - I see several Firefox processes in `ps ax | grep firefox` , but `killall firefox` says "process not found": ``` > ps ax | grep firefox 7065 ?Sl40:40 /usr/lib64/firefox/firefox -contentproc -childID 8 -isForBrowser -prefsLen 6484 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 19148 ?Sl90:52 /usr/lib64/firefox/firefox 19231 ?Sl 0:10 /usr/lib64/firefox/firefox -contentproc -parentBuildID 20210927210923 -prefsLen 1 -prefMapSize 256017 -appdir /usr/lib64/firefox/browser 19148 true socket 19319 ?Sl 1:00 /usr/lib64/firefox/firefox -contentproc -childID 2 -isForBrowser -prefsLen 5348 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 19377 ?Sl 1:29 /usr/lib64/firefox/firefox -contentproc -childID 3 -isForBrowser -prefsLen 5983 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 19861 ?Sl 0:09 /usr/lib64/firefox/firefox -contentproc -childID 103 -isForBrowser -prefsLen 11209 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 19904 ?Sl 1:20 /usr/lib64/firefox/firefox -contentproc -childID 104 -isForBrowser -prefsLen 11209 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 20051 ?Sl 0:29 /usr/lib64/firefox/firefox -contentproc -childID 105 -isForBrowser -prefsLen 11209 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 20088 ?Sl 0:31 /usr/lib64/firefox/firefox -contentproc -childID 106 -isForBrowser -prefsLen 11209 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 29548 ?Sl 6:25 /usr/lib64/firefox/firefox -contentproc -childID 74 -isForBrowser -prefsLen 11250 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 29816 pts/2S+ 0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox firefox 31137 ?Sl 5:45 /usr/lib64/firefox/firefox -contentproc -childID 88 -isForBrowser -prefsLen 11264 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab 32271 ?Sl27:11 /usr/lib64/firefox/firefox -contentproc -childID 99 -isForBrowser -prefsLen 11241 -prefMapSize 256017 -jsInit 286204 -parentBuildID 20210927210923 -appdir /usr/lib64/firefox/browser 19148 true tab > killall firefox firefox: no process found ``` This is with Firefox 93.0-80.3 and Plasma 5.23.2 on OpenSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #40 from Philipp Reichmuth --- I'm seeing crashes in Akonadi whenever I switch off my external screen or unplug the dock it's attached to (bug 445249). Could this be related? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445249] Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=445249 --- Comment #4 from Philipp Reichmuth --- This also happens if I leave the dock plugged in and switch off my external screen. Could be related to bug 438839 or bug 444801, but it's not Plasmashell that crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #1 from Philipp Reichmuth --- I now get the crash reported under bug 445249 reproducibly whenever I unplug and replug my dock. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445249] Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=445249 --- Comment #3 from Philipp Reichmuth --- This happens reproducibly, every time I unplug my Thunderbolt dock I get this Akonadi crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 Philipp Reichmuth changed: What|Removed |Added Product|Breeze |kwin Version|5.14.4 |5.23.2 Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Component|window decoration |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445259] New: Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=445259 Bug ID: 445259 Summary: Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland Product: kwin Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY Chromium-based browsers are unable to bring up their browser windows on Wayland (tested with Chromium, Brave and Edge). The browser processes are running, but no browser window appears. This started happening since yesterday, with no changes to the system configuration or packages. The problem persists after a logout and reboot. As it started happening on three separate browsers, and the package versions for all three browsers are unchanged, and Brave and Edge are self-contained, I believe there could be an issue related to the compositor. STEPS TO REPRODUCE 1. Launch browser with `--enable-features=UseOzonePlatform --ozone-platform=wayland`: chromium --enable-features=UseOzonePlatform --ozone-platform=wayland (substitute `brave-browser` or `microsoft-edge-dev` for `chromium`) OBSERVED RESULT The browser processes come up as they do on X11, but no browser window appears. When I hit Ctrl+C in the command line, they are terminated. EXPECTED RESULT The browser window should come up as it does on X11. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Chromium: 95.0.4638.69-1.1 (OpenSUSE RPM) Brave: 1.31.88-1 (OpenSUSE RPM) Edge: 97.0.1069.0-1 (OpenSUSE RPM) ADDITIONAL INFORMATION Command line output: chromium --enable-features=UseOzonePlatform --ozone-platform=wayland [6687:6687:1110/092447.136492:ERROR:browser_main_loop.cc(269)] Gdk: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed [6687:6687:1110/092447.246910:ERROR:cursor_loader.cc(115)] Failed to load a platform cursor of type kNull [6732:6732:1110/092447.576224:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is egl, ANGLE is [6732:6732:1110/092447.580413:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [6687:6742:1110/092747.721888:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends. [6687:6742:1110/092747.721905:ERROR:chrome_browser_main_extra_parts_metrics.cc(233)] crbug.com/1216328: Checking Bluetooth availability ended. [6687:6742:1110/092747.721909:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends. [6687:6742:1110/092747.821040:ERROR:chrome_browser_main_extra_parts_metrics.cc(240)] crbug.com/1216328: Checking default browser status ended. Output from `ps ax`: > ps ax | grep chrom 6687 pts/2Sl+0:02 /usr/lib64/chromium/chrome --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-crashpad 6695 ?Sl 0:00 /usr/lib64/chromium/chrome_crashpad_handler --monitor-self --monitor-self-annotation=ptype=crashpad-handler --database=/home/username/.config/chromium/Crash Reports --annotation=channel=stable --annotation=lsb-release=openSUSE Tumbleweed --annotation=plat=Linux --annotation=prod=Chrome_Linux --annotation=ver=95.0.4638.69 --initial-client-fd=229 --shared-client-connection 6698 pts/2S+ 0:00 /usr/lib64/chromium/chrome --type=zygote --no-zygote-sandbox --enable-crashpad --crashpad-handler-pid=0 --enable-crash-reporter=,stable --change-stack-guard-on-fork=enable --enable-crashpad 6700 ?S 0:00 /usr/lib64/chromium/chrome_crashpad_handler --no-periodic-tasks --monitor-self-annotation=ptype=crashpad-handler --database=/home/username/.config/chromium/Crash Reports --annotation=channel=stable --annotation=lsb-release=openSUSE Tumbleweed --annotation=plat=Linux --annotation=prod=Chrome_Linux --annotation=ver=95.0.4638.69 --initial-client-fd=4 --shared-client-connection 6702 pts/2S+ 0:00 /usr/lib64/chromium/chrome --type=zygote --enable-crashpad --crashpad-handler-pid=0 --enable-crash-reporter=,stable --change-stack-guard-on-fork=enable --enable-crashpad 6704 pts/2S+ 0:00 /usr/lib64/chromium/chrome --type=zygote --enable-crashpad --crashpad-handler-pid=0 --enable-crash-reporter=,stable --change-stack-guard-on-fork=enable --enable-crashpad 6732 pts/2Sl+0:00 /usr/lib64/chromium/chrome --type=gpu-process --field-trial-handle=1093270205260396699,6503610067434351146,131072 --enable-features=UseOzonePlatform
[Akonadi] [Bug 445249] Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=445249 --- Comment #2 from Philipp Reichmuth --- Sorry, bug 445253. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445249] Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=445249 --- Comment #1 from Philipp Reichmuth --- The screen resolution issue I reported separately as bug 445353. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445253] New: Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 Bug ID: 445253 Summary: Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots) Product: kwin Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY I have a 3840x2160 screen attached to a Thunderbolt dock. However, since waking up from suspend this morning, KWin fails to set any more than 2560x1440, even though I see a 3840x2160 option in System settings. I can select 3840x2160 and apply the setting, and System settings will show that the resolution is 3840x2160, but the monitor actually goes to 2560x1440 as seen from the monitor's HUD. The next time I open the Display settings KCM, it will again show the monitor at 2560x1440. KWin has supported 3840x2160 until this morning, and I made no changes to the configuration. The laptop was on suspend. I would be happy if I had a way to get to yesterday's state before suspending the notebook to the night. But now it will not go to this resolution even after several reboots, unplugging and replugging the Thunderbolt dock, and power cycling the dock and monitor. STEPS TO REPRODUCE 1. Boot up system 2. Log into KDE Wayland session (the monitor HUD shows it correctly running at 3840x2160 in SDDM) 3. KWin comes up with the monitor in 2560x1440. 4. Open System Settings, set resolution to 3840x2160, click Apply. OBSERVED RESULT The monitor goes to 2560x1440, even though the Display settings KCM shows it at 3840x2160. If I open a different KCM in System settings and then go back to Display settings, the monitor is shown at 2560x1440 again. EXPECTED RESULT The monitor should go to 3840x2160. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Upon unplugging and replugging the Thunderbolt dock, I once got the crash reported under #445249. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445249] New: Akonadi crash after unplugging Thunderbolt dock with attached monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=445249
Bug ID: 445249
Summary: Akonadi crash after unplugging Thunderbolt dock with
attached monitor on Wayland
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: philipp.reichm...@gmail.com
Target Milestone: ---
Application: akonadiserver (5.18.3 (21.08.3))
Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Unplugged my Thunderbolt dock, which has a monitor attached via DisplayPort, in
order to fix an issue where the monitor would not go to the resolution I
selected in System Settings.
- Unusual behavior I noticed:
The Wayland session was behaving strangely prior to unplugging.
The monitor is capable of 3840x2160 resolution and has supported this
resolution in KWin Wayland in the past. I can see and select this resolution in
System Settings.
Since this morning (with no user changes to my KDE configuration or packages),
the monitor comes up with 2560x1440. I can set it to 3840x2160 in System
Settings. However, when I apply the settings, the monitor will go to 2560x1440
anyway (as confirmed by the monitor's HUD), and when I enter System Settings
again, I see it again at 2560x1440.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 std::default_delete::operator() (__ptr=0x111,
this=) at /usr/include/c++/11/bits/unique_ptr.h:79
#7 std::unique_ptr >::~unique_ptr
(this=, this=) at
/usr/include/c++/11/bits/unique_ptr.h:361
#8 __gnu_cxx::new_allocator >
>::destroy > > (__p=,
this=) at /usr/include/c++/11/ext/new_allocator.h:168
#9
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at /usr/include/c++/11/bits/alloc_traits.h:531
#10 std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {get() = {}}, this=) at /usr/include/c++/11/bits/vector.tcc:177
#11 std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {get() = {}}, this=) at /usr/include/c++/11/bits/stl_vector.h:1431
#12 Akonadi::Server::AkonadiServer::connectionDisconnected (this=) at
/usr/src/debug/akonadi-server-21.08.3-1.1.x86_64/src/server/akonadi.cpp:234
#13 0x7fd6f95f8fee in QObject::event (this=0x7ffe83590c90,
e=0x7fd6a4005970) at kernel/qobject.cpp:1314
#14 0x7fd6f95cc9cf in doNotify (event=0x7fd6a4005970,
receiver=0x7ffe83590c90) at kernel/qcoreapplication.cpp:1154
#15 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1140
#16 QCoreApplication::notifyInternal2 (receiver=0x7ffe83590c90,
event=0x7fd6a4005970) at kernel/qcoreapplication.cpp:1064
#17 0x7fd6f95cfa47 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55eb0afff980) at
kernel/qcoreapplication.cpp:1821
#18 0x7fd6f9624853 in postEventSourceDispatch (s=s@entry=0x55eb0b03da30) at
kernel/qeventdispatcher_glib.cpp:277
#19 0x7fd6f7852d4f in g_main_dispatch (context=0x55eb0b03d4d0) at
../glib/gmain.c:3381
#20 g_main_context_dispatch (context=0x55eb0b03d4d0) at ../glib/gmain.c:4099
#21 0x7fd6f78530d8 in g_main_context_iterate
(context=context@entry=0x55eb0b03d4d0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#22 0x7fd6f785318f in g_main_context_iteration (context=0x55eb0b03d4d0,
may_block=1) at ../glib/gmain.c:4240
#23 0x7fd6f9623ed4 in QEventDispatcherGlib::processEvents
(this=0x55eb0b03cbf0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7fd6f95cb3fb in QEventLoop::exec (this=this@entry=0x7ffe83590ad0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#25 0x7fd6f95d36e0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#26 0x55eb08ff7559 in AkApplicationBase::exec (this=0x7ffe83590c60) at
/usr/src/debug/akonadi-server-21.08.3-1.1.x86_64/src/shared/akapplication.cpp:107
#27 main (argc=, argv=) at
/usr/src/debug/akonadi-server-21.08.3-1.1.x86_64/src/server/main.cpp:65
[Inferior 1 (process 3075) detached]
The reporter indicates this bug may be a duplicate of or related to bug 442147.
Possible duplicates by query: bug 444916, bug 444909, bug 444534, bug 46,
bug 21.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 445217] Configuration file mess under $XDG_CONFIG_HOME
https://bugs.kde.org/show_bug.cgi?id=445217 --- Comment #4 from Philipp Reichmuth --- The reason for this bug report was not that I tried to edit the configuration manually, but that I tried to back up my KDE configuration and the files are all over the place. I appreciate that there is a technical reasons behind it. But for a user who knows nothing about the architecture of Akonad,i this is not very intuitive and can be confusing. Akonadi is not the only app that does this, but it's a particularly obvious one because it makes its own config subdirectory, but then puts several files outside of it. I prefer how Falkon or KDE Connect do it - one subdirectory under $XDG_CONFIG_HOME with all config data underneath it (and ideally persistent stateful data should then go separately under $XDG_STATE_HOME). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445217] Configuration file mess under $XDG_CONFIG_HOME
https://bugs.kde.org/show_bug.cgi?id=445217 --- Comment #2 from Philipp Reichmuth --- There may be a rationale to it, but as a user I find it rather confusing to have seven Akonadi config files under ~/.config, and then another subdirectory called akonadi with another 30 files. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 445217] New: Configuration file mess under $XDG_CONFIG_HOME
https://bugs.kde.org/show_bug.cgi?id=445217 Bug ID: 445217 Summary: Configuration file mess under $XDG_CONFIG_HOME Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY Akonadi components put their config files in different places - some under $XDG_CONFIG_HOME, others under $XDG_CONFIG_HOME, and some seem to put them in both places. While this technically does not contradict the XDG spec, this is inconsistent, difficult to use., and contributes to the mess in ~/.config that is a deterrent to many novice users. STEPS TO REPRODUCE 1. Install Akonadi, work with it for a while 2. Check content of ~/.config OBSERVED RESULT There are some configuration files in a directory ~/.config/akonadi, and other configuration files directly under ~/./config, which is both inconsistent and unwieldy On my system: > cd ~/.config > ls -1 akonadi* akonadi_akonotes_resource_0rc akonadi_contacts_resource_2rc akonadi-firstrunrc akonadi_ical_resource_0rc akonadi_indexing_agentrc akonadi_maildir_resource_0rc akonadi-migrationrc akonadi: agent_config_akonadi_akonotes_resource_0 agent_config_akonadi_akonotes_resource_0_changes.dat agent_config_akonadi_archivemail_agent_changes.dat agent_config_akonadi_birthdays_resource agent_config_akonadi_birthdays_resource_changes.dat agent_config_akonadi_contacts_resource_0 agent_config_akonadi_contacts_resource_0_changes.dat agent_config_akonadi_contacts_resource_1 agent_config_akonadi_contacts_resource_1_changes.dat agent_config_akonadi_contacts_resource_2 agent_config_akonadi_contacts_resource_2_changes.dat agent_config_akonadi_followupreminder_agent_changes.dat agent_config_akonadi_ical_resource_0 agent_config_akonadi_ical_resource_0_changes.dat agent_config_akonadi_indexing_agent agent_config_akonadi_indexing_agent_changes.dat agent_config_akonadi_maildir_resource_0 agent_config_akonadi_maildir_resource_0_changes.dat agent_config_akonadi_maildispatcher_agent_changes.dat agent_config_akonadi_mailfilter_agent_changes.dat agent_config_akonadi_mailmerge_agent_changes.dat agent_config_akonadi_migration_agent_changes.dat agent_config_akonadi_newmailnotifier_agent_changes.dat agent_config_akonadi_notes_agent_changes.dat agent_config_akonadi_sendlater_agent_changes.dat agent_config_akonadi_unifiedmailbox_agent agent_config_akonadi_unifiedmailbox_agent_changes.dat agentsrc akonadiconnectionrc akonadiserverrc EXPECTED RESULT If we have a directory ~/.config/akonadi, all Akonadi coomponents should put their config files in there. SOFTWARE/OS VERSIONS Akonadi components 21.08.3 Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 393223] DisplayPort detection issues after standby/resume
https://bugs.kde.org/show_bug.cgi?id=393223 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #1 from Philipp Reichmuth --- I also have this issue when my monitor goes to Deep Sleep, upon wakeup the login screen appears on only one screen and my windows are a jumbled mess. This is with KDE 5.23.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 --- Comment #4 from Philipp Reichmuth --- It seems unlikely that this will ever work though, because window class is an X11 property. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #3 from Philipp Reichmuth --- Can reproduce still with Kate 21.08.3 Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 433530] Unable to take second screenshot under Wayland
https://bugs.kde.org/show_bug.cgi?id=433530 Philipp Reichmuth changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Philipp Reichmuth --- Seems to be resolved now, as of 21.08.3 the problem no longer appears. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #6 from Philipp Reichmuth --- It seems to be only the wallpaper as far as I can see. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433418] Wayland session hangs for several seconds with frozen mouse pointer before startup screen
https://bugs.kde.org/show_bug.cgi?id=433418 Philipp Reichmuth changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #4 from Philipp Reichmuth --- Oh and sorry for missing this: SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211105 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #3 from Philipp Reichmuth --- Created attachment 143336 --> https://bugs.kde.org/attachment.cgi?id=143336=edit Backdrop after changing - note how it is scaled right away, and Spectacle now sees the scaling -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #2 from Philipp Reichmuth --- Created attachment 143335 --> https://bugs.kde.org/attachment.cgi?id=143335=edit Initial backdrop after relogin, screenshot - note how Spectacle does not see the scaling as it is on the screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 --- Comment #1 from Philipp Reichmuth --- Created attachment 143334 --> https://bugs.kde.org/attachment.cgi?id=143334=edit Initial backdrop after re-login - note how the wallpaper on the right screen has the scaling factor (200%) applied -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445160] New: Wallpaper scaling issues on multimonitor Wayland setup
https://bugs.kde.org/show_bug.cgi?id=445160 Bug ID: 445160 Summary: Wallpaper scaling issues on multimonitor Wayland setup Product: plasmashell Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 14 --> https://bugs.kde.org/attachment.cgi?id=14=edit Initial backdrop (National Geographic POTD) SUMMARY When I reboot or relogin after changing the desktop wallpaper, the wallpaper on one of the monitors now appears scaled according to system scaling factor. I don't always see this in Spectacle (but sometimes I do). I can reset this by changing the scaling factor for the affected display, then the wallpaper appears as it should, until the next login. I see it with Picture of the day as well as static wallpapers. STEPS TO REPRODUCE 1. Set a scale factor and a desktop wallpaper. 2. Logout or login again - the wallpaper on one screen is now scaled. 3. Change the scale factor on that monitor - the wallpaper now appears as it should. 4. Logout or login again - it's scaled again OBSERVED RESULT The wallpaper looks scaled after a login. EXPECTED RESULT The wallpaper should appear the same after each login. 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.
[yakuake] [Bug 445158] New: Yakuake does not open on the screen where the mouse pointer is
https://bugs.kde.org/show_bug.cgi?id=445158 Bug ID: 445158 Summary: Yakuake does not open on the screen where the mouse pointer is Product: yakuake Version: 21.08.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- SUMMARY On Wayland, Yakuake always opens on a particular screen. I would prefer it to open on the screen with the mouse pointer, just like KRunner does in X11. STEPS TO REPRODUCE 1. With multiple monitors, invoke Yakuake. 2. Move the mouse pointer to another monitor and invoke Yakuake again. OBSERVED RESULT Yakuake always opens on a particular screen - in my case my notebook's screen, which happens to be the leftmost screen. EXPECTED RESULT Yakuake should open on the screen where the mouse pointer is, like KRunner does on X11. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211105 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Some people might prefer it to open always on a particular screen, so "follow the mouse" could be a configuration option. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 445157] New: KRunner always opens on a particular screen in Wayland (unlike X11, where it opens where the mouse is)
https://bugs.kde.org/show_bug.cgi?id=445157 Bug ID: 445157 Summary: KRunner always opens on a particular screen in Wayland (unlike X11, where it opens where the mouse is) Product: krunner Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY On Wayland, KRunner always opens on a particular screen, when in X11 it opens on the screen with the mouse pointer. STEPS TO REPRODUCE 1. In the Wayland session, with multiple monitors, invoke KRunner. 2. Move the mouse pointer to another monitor and invoke KRunner again. OBSERVED RESULT KRunner always opens on a particular screen - in my case my notebook's screen, which happens to be the leftmost screen. EXPECTED RESULT KRunner should open on the screen where the mouse pointer is, like it does on X11. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211105 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445156] New: No frame drawn around window titlebar
https://bugs.kde.org/show_bug.cgi?id=445156 Bug ID: 445156 Summary: No frame drawn around window titlebar Product: kwin Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com Target Milestone: --- Created attachment 143330 --> https://bugs.kde.org/attachment.cgi?id=143330=edit Window title bars don't have frames when the rest of the window does SUMMARY Window title bars don't have frames round them when the rest of the window does. (See screenshot.) STEPS TO REPRODUCE 1. In System Settings > Appearance > Window decorations, activate the Breeze theme and set frame width to "Normal" 2. Configure colours for the active frame, e.g. by doing ` kwriteconfig5 --file ~/.config/kdeglobals --group WM --key frame 215,121,33 && kwriteconfig5 --file ~/.config/kdeglobals --group WM --key inactiveFrame 60,56,54`, logging out and logging in 3. Open a window, or check appearance in Settings > Appearance > Window decorations. OBSERVED RESULT You see a frame around the left, bottom and right part of the window, but not around the title bar. EXPECTED RESULT The whole window should have a frame around it. Frames should either override title bar decorations, or the decorations should account for them SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211105 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This might be a result of having title bars with rounded corners. This happens on Wayland as well as on X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444602] LyX menu stops opening after a while
https://bugs.kde.org/show_bug.cgi?id=444602 Philipp Reichmuth changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444602] New: LyX menu stops opening after a while
https://bugs.kde.org/show_bug.cgi?id=444602 Bug ID: 444602 Summary: LyX menu stops opening after a while Product: plasmashell Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: philipp.reichm...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I use the Global Menu applet and am seeing problems with LyX (version 2.3.6.1), which is a document processing program that uses Qt for its UI. Upon launching LyX, the menu works fine. However, after working in LyX for a while, the menu stops working, submenus cease to appear. STEPS TO REPRODUCE 1. Start LyX. 2. Work in LyX for a while, opening/closing menus and so on. OBSERVED RESULT After a while, menus stop opening: the top-level menu item in the manu bar is highlighted, but no submenu opens. EXPECTED RESULT Submenus should open every time. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211027 KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 LyX version 2.3.6.1 from the OpenSUSE repositories. ADDITIONAL INFORMATION I've reported this on the LyX bugtracker: https://lyx.org/trac/ticket/12415 The developer there says that LyX is generating the menus on the fly when you enter the top-level menu, it's their way of adjusting the changing menu contents. The developer uses global menus with Unity and says it took them a while to get right back at the time (4-5 years ago). It may be an issue between the way KDE displays the menu and the way LyX generates them, but for me it's a bit hard to track down. There were some issues with this with KDE in the past (#399975); this issue is different because it only appears after a while. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430465] Add Crop option in annotation tool
https://bugs.kde.org/show_bug.cgi?id=430465 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #4 from Philipp Reichmuth --- Please, please add this. I'm trying to work around this by using rectangular region, but it doesn't work as well, and you get side effects (like the application in question reacts to the mouse pointer and e.g. controls pop up in YouTube) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 430620] Discover shows apps/packages as recommended that I have already installed
https://bugs.kde.org/show_bug.cgi?id=430620 Philipp Reichmuth changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 430620] Discover shows apps/packages as recommended that I have already installed
https://bugs.kde.org/show_bug.cgi?id=430620 --- Comment #10 from Philipp Reichmuth --- Done, filed as bug 436564 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 436564] New: Discover: DE Translation of "Featured" apps as "Recommended" apps leads to confusion
https://bugs.kde.org/show_bug.cgi?id=436564
Bug ID: 436564
Summary: Discover: DE Translation of "Featured" apps as
"Recommended" apps leads to confusion
Product: i18n
Version: 20.12.3
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: de
Assignee: kde-i18n...@kde.org
Reporter: philipp.reichm...@gmail.com
Target Milestone: ---
SUMMARY
In the German UI of Discover, "Featured" apps are translated as "Empfehlung"
("Recommendation"). This makes it seem like they are recommended to me
specifically. As a result, when I open Discover, I find it confusing when it
recommends me to install apps that I have already installed.
STEPS TO REPRODUCE
1. Open Discover
2. The featured apps pane opens by default.
OBSERVED RESULT
The list of featured apps is presented as a list of apps that Discover
recommends me for installation. These recommended apps include apps that I have
already installed, so recommending them to me makes no sense.
EXPECTED RESULT
Instead of "Empfehlung", I would expect something that does not carry the
connotation of having been recommended for me specifically. Suggestions -
"Ausgewählte Apps", "Besondere Apps", "Empfehlung des KDE-Teams"
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210427
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.11.16-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® UHD Graphics 620
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 430620] Discover shows apps/packages as recommended that I have already installed
https://bugs.kde.org/show_bug.cgi?id=430620
--- Comment #8 from Philipp Reichmuth ---
Maybe the issue is just with the German translation, which translates
"Featured" as "Empfohlen" ("Recommended"). A featured app and a recommended app
are not the same thing, the translation carries the connotation that it's
recommended for me specifically. You can feature something even when it's
already there, while recommending it doesn't make sense.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 Philipp Reichmuth changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 --- Comment #4 from Philipp Reichmuth --- No, still happens with 21.04: 1) Open Dolphin 2) Hit F3. There are now two panes showing the same location. 3) Click in the right pane 4) Navigate somewhere else in the right pane 5) Hit F3 again. The right pane (which has the focus) disappears, the left pane (with the original location) remains. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 Philipp Reichmuth changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 --- Comment #72 from Philipp Reichmuth --- I am running kio-extras 21.04.0 on OpenSUSE TW and I still have the problem, so I believe it has not been fixed. I have a few directories upon which it reproducibly crashes when I navigate to the directory in the fileselector from Qutebrowser. These directories have in common that they contain subdirectories with image files in them. However, if I begin individually removing files and subdirectories, it's no longer reproducible - e.g. I have a configuration where it crashes, I remove a subdirectory and it no longer crashes, I copy the subdirectory in again and it still doesn't crash. I don't know enough about how the thumbnailer works to come up with a reliable strategy to produce a minimal configuration. I can send a zip file of such a directory, however as it's rather large and contains sensitive files I would rather not post it online. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436116] New: Segmentation fault in kdeinit5 when opening file selector
https://bugs.kde.org/show_bug.cgi?id=436116 Bug ID: 436116 Summary: Segmentation fault in kdeinit5 when opening file selector Product: frameworks-kinit Version: 5.81.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: philipp.reichm...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Periodically, when opening the file selector from a KDE or Qt applications, kdeinit5 segfaults STEPS TO REPRODUCE 1. Open a Qt application (e.g. Qutebrowser) OBSERVED RESULT Repeated crashes in kdeinit5 until either you select a different folder in the file selector, or the file selector closes EXPECTED RESULT kdeinit5 should not crash. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210422 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.15-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 ADDITIONAL INFORMATION Application: kdeinit5 (kdeinit5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f225a16acc0 (LWP 8257))] [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:269 #7 0x7f2258356f81 in memcpy (__len=49152, __src=, __dest=0x7f2255487000) at /usr/include/bits/string_fortified.h:29 #8 ThumbnailProtocol::get (this=0x7ffedb062d60, url=...) at /usr/src/debug/kio-extras5-20.12.3-1.3.x86_64/thumbnail/thumbnail.cpp:315 #9 0x7f2257ffeee6 in KIO::SlaveBase::dispatch (this=0x7ffedb062d60, command=67, data=...) at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:1215 #10 0x7f2257ff68c6 in KIO::SlaveBase::dispatchLoop (this=0x7ffedb062d60) at /usr/src/debug/kio-5.81.0-1.2.x86_64/src/core/slavebase.cpp:336 #11 0x7f22583537b6 in kdemain (argc=, argv=0x5563ace62e70) at /usr/src/debug/kio-extras5-20.12.3-1.3.x86_64/thumbnail/thumbnail.cpp:138 #12 0x5563ab8e0c07 in launch (argc=argc@entry=4, _name=_name@entry=0x5563ace62da8 "/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so", args=, args@entry=0x5563ace62dd4 "thumbnail", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=envs@entry=0x5563ace62e50 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x5563ab8e3175 "0") at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:692 #13 0x5563ab8e23a8 in handle_launcher_request (sock=7, who=) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1130 #14 0x5563ab8e2a36 in handle_requests (waitForPid=waitForPid@entry=0) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1323 #15 0x5563ab8dd623 in main (argc=2, argv=) at /usr/src/debug/kinit-5.81.0-1.2.x86_64/src/kdeinit/kinit.cpp:1761 [Inferior 1 (process 8257) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435917] New: Show desktop preview (w/windows) in Activity Switcher
https://bugs.kde.org/show_bug.cgi?id=435917 Bug ID: 435917 Summary: Show desktop preview (w/windows) in Activity Switcher Product: plasmashell Version: 5.21.4 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Activity Switcher Assignee: ivan.cu...@kde.org Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The Activity Switcher currently shows only the desktop background of each Activity. However, I use desktop backgrounds that change (Slideshow and Picture of the Day), so they are not instantly recognizable. I would prefer if I could see a preview of the desktop as it is, with all active windows. STEPS TO REPRODUCE 1. Press Meta-Q to bring up the activity switcher. OBSERVED RESULT The Activity switcher shows an empty desktop background for each activity. EXPECTED RESULT The Activity Switcher should show the whole currently-active desktop with all windows. For users who prefer to see the desktop background, there should be a configuration option, e.g. "Show windows in activity switcher" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210417 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.12-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397662] Activity Switcher not cycles through more than two activities on Wayland with Meta+Tab shortcut
https://bugs.kde.org/show_bug.cgi?id=397662 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #4 from Philipp Reichmuth --- I can confirm the same behaviour in the Task Switcher on Plasma 5.21.4, Frameworks 5.81.0 on X11 on OpenSUSE.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 271686] Keyboard shortcut to move windows to activities
https://bugs.kde.org/show_bug.cgi?id=271686 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #10 from Philipp Reichmuth --- Yesterday and today I spent a lot of time looking for such a keyboard shortcut. Now on the one hand I'm relieved that it wasn't my fault for not finding one, and disappointed that there is none for such a basic operation, since 2014 :( Is there a workaround, maybe with a DBus command that could be scripted? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 --- Comment #2 from Philipp Reichmuth --- OK, will try. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435806] Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 Philipp Reichmuth changed: What|Removed |Added Platform|Other |openSUSE RPMs Version|unspecified |20.12.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435806] New: Hitting F3 in split view always closes right pane, even when it has the focus
https://bugs.kde.org/show_bug.cgi?id=435806 Bug ID: 435806 Summary: Hitting F3 in split view always closes right pane, even when it has the focus Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split view Assignee: dolphin-bugs-n...@kde.org Reporter: philipp.reichm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When closing the split view by hitting F3, Dolphin always closes the right pane and leaves the left pane in place - even when the right pane is the one that has the focus. STEPS TO REPRODUCE 1. Open Dolphin in split view. 2. Click into right pane by clicking into it. 3. Hit F3 to close split view. OBSERVED RESULT Dolphin always closes the right pane, even when it has the focus. EXPECTED RESULT Dolphin should close the inactive pane, the pane that has the focus should stay open. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210408 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.11-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 ADDITIONAL INFORMATION Maybe the behaviour should be configurable, as some users may have gotten used to the behaviour that the right pane closes and the left pane remains. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433418] Wayland session hangs for several seconds with frozen mouse pointer before startup screen
https://bugs.kde.org/show_bug.cgi?id=433418 Philipp Reichmuth changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] Plasmashell blurry after changing display scaling in Wayland session
https://bugs.kde.org/show_bug.cgi?id=433416 --- Comment #6 from Philipp Reichmuth --- Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] Plasmashell blurry after changing display scaling in Wayland session
https://bugs.kde.org/show_bug.cgi?id=433416 Philipp Reichmuth changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432165] On Wayland, I can't take a screenshot by pressing printscreen key while Spectacle is open
https://bugs.kde.org/show_bug.cgi?id=432165 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #1 from Philipp Reichmuth --- Happens to me too (bug 433530), but even when Spectacle is closed or when I `kill -9` the spectacle process. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 433530] New: Unable to take second screenshot under Wayland
https://bugs.kde.org/show_bug.cgi?id=433530 Bug ID: 433530 Summary: Unable to take second screenshot under Wayland Product: Spectacle Version: 20.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: philipp.reichm...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When trying to take a screenshot for the second time, even when Spectacle is closed, Spectacle reports "No screenshot can be taken. Please report this error here". STEPS TO REPRODUCE 1. Use the Spectacle keyboard shortcut to take a (full screen) screenshot 2. Save the screen shot 3. Close Spectacle, or kill the Spectacle process 4. Use the Spectacle keyboard shortcut to take another (full screen) screenshot OBSERVED RESULT A notification box appears in the Spectacle window, telling me that no screenshot could be taken. This happens regardless of whether I select full screen or rectangular area. EXPECTED RESULT A screenshot should be taken. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433418] Wayland session hangs for several seconds with frozen mouse pointer before startup screen
https://bugs.kde.org/show_bug.cgi?id=433418 --- Comment #3 from Philipp Reichmuth --- The time spent hanging seems to be variable; just now the mouse cursor was frozen for 25 seconds before the splash screen came up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] Plasmashell blurry after changing display scaling in Wayland session
https://bugs.kde.org/show_bug.cgi?id=433416 --- Comment #4 from Philipp Reichmuth --- Created attachment 136108 --> https://bugs.kde.org/attachment.cgi?id=136108=edit KDE Plasma 5.21 screenshot after clearing Plasma cache: crisp Firefox and Plasma panel, blurry Yakuake -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] Plasmashell blurry after changing display scaling in Wayland session
https://bugs.kde.org/show_bug.cgi?id=433416 --- Comment #3 from Philipp Reichmuth --- Thank you. Clearing the Plasma cache does solve the problem for the Plasma panel. However, if any other KDE applications were open before changing the display scaling, they are still blurry. This happened to me with Yakuake, but also with Plasma notifications. I'm attaching a screenshot taken right after clearing the cache and restarting Plasma - it shows the Yakuake window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433418] Wayland session hangs for several seconds with frozen mouse pointer before startup screen
https://bugs.kde.org/show_bug.cgi?id=433418 --- Comment #2 from Philipp Reichmuth --- No, I have the splash screen enabled and am not using systemd startup (yet). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433420] Under Wayland, submenus in "single button" global menu open in regular window with window decorations, application loses focus
https://bugs.kde.org/show_bug.cgi?id=433420 Philipp Reichmuth changed: What|Removed |Added Attachment #136030|Plasma 5.21 global menu |Plasma 5.21 global menu description|under Wayland: in Single|under Wayland: in Single |Button mode, for Kate, |Button mode, for Kate, |showing an unrelated Plasma |showing submenu opened with |menu instead of the "File" |window decorations, and |menu|Kate lost focus to Plasma -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433420] Under Wayland, submenus in "single button" global menu open in regular window with window decorations, application loses focus
https://bugs.kde.org/show_bug.cgi?id=433420 --- Comment #1 from Philipp Reichmuth --- Update: in fact it is the correct menu (so no unrelated Plasma window), it just opens in a regular window, switching focus to Plasma and causing the application to lose focus. Description updated accordingly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433420] Under Wayland, submenus in "single button" global menu open in regular window with window decorations, application loses focus
https://bugs.kde.org/show_bug.cgi?id=433420 Philipp Reichmuth changed: What|Removed |Added Summary|Under Wayland, submenus in |Under Wayland, submenus in |"single button" global menu |"single button" global menu |open unrelated Plasma menus |open in regular window with |instead |window decorations, ||application loses focus -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433420] New: Under Wayland, submenus in "single button" global menu open unrelated Plasma menus instead
https://bugs.kde.org/show_bug.cgi?id=433420 Bug ID: 433420 Summary: Under Wayland, submenus in "single button" global menu open unrelated Plasma menus instead Product: plasmashell Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: philipp.reichm...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 136030 --> https://bugs.kde.org/attachment.cgi?id=136030=edit Plasma 5.21 global menu under Wayland: in Single Button mode, for Kate, showing an unrelated Plasma menu instead of the "File" menu SUMMARY In the Wayland session, When the Global Menu applet is configured to show a single button instead of the whole menu, the top-level menu will open fine, but opening any submenu will cause the application to lose focus and open a regular window, with decorations, showing an unrelated Plasma menu. STEPS TO REPRODUCE 1. Put Global Menu applet in panel, configure to show a single button instead of the whole menu 2. Open a KDE application (e.g. Kate or Dolphin) 3. Click on global menu button, the menu opens 4. Hover mouse over any entry that opens a submenu OBSERVED RESULT The application loses focus, in place of the regular submenu a window with regular window decorations and an unrelated Plasma menu appears (see screenshot) EXPECTED RESULT The regular submenu should open as usual. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 ADDITIONAL INFORMATION When Global Menu is configured to show the full menu instead of a single button, all submenus work just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] Plasmashell blurry after changing display scaling in Wayland session
https://bugs.kde.org/show_bug.cgi?id=433416 Philipp Reichmuth changed: What|Removed |Added Summary|Plasmashell blurry under|Plasmashell blurry after |Wayland with 200% display |changing display scaling in |scaling |Wayland session -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] Plasmashell blurry under Wayland with 200% display scaling
https://bugs.kde.org/show_bug.cgi?id=433416 --- Comment #1 from Philipp Reichmuth --- Update: this is gone after a logout. It happens again whenever I change the display scaling, until the next login. So a more accurate description would be: "After changing the display scaling in the Wayland session, Plasma and applets are rendered blurry until the next login." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433419] New: Need to select "Log out" twice to actually log out
https://bugs.kde.org/show_bug.cgi?id=433419 Bug ID: 433419 Summary: Need to select "Log out" twice to actually log out Product: plasmashell Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After upgrading to Plasma 5.21 and the new appliation launcher, I need to log out twice in order to actually log out. STEPS TO REPRODUCE 1. Open Application Launcher. 2. Select Shut down. 3. From the shut down screen, select Log Out. 4. Nothing happens. I'm back in the Plasma session 5. Open Application Launcher again. 6. Select Shut down again. 7. From the shut down screen, select Log Out again. 8. The logout routine starts and I am logged out. OBSERVED RESULT The system lets me log out only on the second try. EXPECTED RESULT I should be logged out right away. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433418] New: Wayland session hangs for several seconds with frozen mouse pointer before startup screen
https://bugs.kde.org/show_bug.cgi?id=433418 Bug ID: 433418 Summary: Wayland session hangs for several seconds with frozen mouse pointer before startup screen Product: plasmashell Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When logging into the Full Wayland session, the mouse pointer hangs frozen for several seconds before the startup screen appears. STEPS TO REPRODUCE 1. Log into Full Wayland session from SDDM. OBSERVED RESULT The screen goes dark, the mouse pointer appears and hangs frozen for 5-10 seconds. Then the mouse pointer unfreezes and the startup screen appears. EXPECTED RESULT The startup screen should appear right away; the mouse pointer should never freeze. SOFTWARE/OS VERSIONS Computer: Lenovo Thinkpad X1Y3 Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433416] New: Plasmashell blurry under Wayland with 200% display scaling
https://bugs.kde.org/show_bug.cgi?id=433416 Bug ID: 433416 Summary: Plasmashell blurry under Wayland with 200% display scaling Product: plasmashell Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 136029 --> https://bugs.kde.org/attachment.cgi?id=136029=edit KDE Plasma 5.21 screenshot: crisp Firefox and KCalc windows, blurry Plasma panel and launcher SUMMARY On a HiDPI display under Plasma Wayland 5.21 with 200% display scaling, the panel, launcher etc. are rendered blurry, while KDE and Qt applications, regular Wayland applications and window decorations are not. STEPS TO REPRODUCE 1. Set display scaling to 200%. 2. Launch a few Qt applications. 3. Look at the panel or open the application launcher. OBSERVED RESULT The panel and launcher are blurry, the application windows are not. (See screenshot.) EXPECTED RESULT The panel and launcher should be crisp. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 ADDITIONAL INFORMATION Note that this is not bug 412089, the window decorations are crisp. I encountered this after running into bug 432099 (having to set the display scaling once again in Wayland after setting it in X11). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432099] If I set the same display scale factor to both X11 and Wayland sessions, display scaling is not applied to Wayland one
https://bugs.kde.org/show_bug.cgi?id=432099 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #2 from Philipp Reichmuth --- Can confirm with 5.21. Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432577] New: Feature request: Play sound when USB device is attached
https://bugs.kde.org/show_bug.cgi?id=432577 Bug ID: 432577 Summary: Feature request: Play sound when USB device is attached Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: philipp.reichm...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY KDE does not play a sound when a new USB device is connected. New users coming from Windows or Gnome are used to notification sounds upon USB connection/disconnection. These users may find it irritating that there is no sound and no way to configure it. Having a notification sound can also help with identifying USB connection/disconnection issues. STEPS TO REPRODUCE 1. Plug in a USB device 2. Nothing happens OBSERVED RESULT Nothing happens. EXPECTED RESULT It would be nice to hear a sound when a USB device is connected A second step would be a KNotification popup indicating the device. There are regularly users switching from GNOME or Windows and asking for this: - https://forum.kde.org/viewtopic.php?f=17=161442 - https://unix.stackexchange.com/questions/434600/how-enabled-sound-notifications-when-insert-an-usb-flash-drive-into-an-usb-port - https://askubuntu.com/questions/1192960/kubuntu-18-04-and-new-device-notification-sound - https://reddit.com/r/kdeneon/comments/h91v9z/enable_sound_when_a_usb_drive_is_inserted_kde_neon/ - https://www.reddit.com/r/kde/comments/gdjz0c/is_it_possible_to_have_an_audio_notification_when/ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 430620] Discover shows apps/packages as recommended that I have already installed
https://bugs.kde.org/show_bug.cgi?id=430620 --- Comment #2 from Philipp Reichmuth --- What I find confusing about it is why is Discover recommending that I install program X? After all I already have it installed. The remove button doesn't help, I don't want to remove it either. Already-installed software should just never appear in the recommended list at all. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 430844] Laptop on battery, continues to think charger is connected, will run battery to 0% and crash
https://bugs.kde.org/show_bug.cgi?id=430844 Philipp Reichmuth changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 430844] Laptop on battery, continues to think charger is connected, will run battery to 0% and crash
https://bugs.kde.org/show_bug.cgi?id=430844 --- Comment #4 from Philipp Reichmuth --- Fixed by kernel update. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391781] Add support for SIXEL in Konsole
https://bugs.kde.org/show_bug.cgi?id=391781 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #5 from Philipp Reichmuth --- I like this, because unlike many image extensions, this is based on an actual industry standard, it's supported by DEC VTs as well as several Unix terminal emulators (xterm, mlterm, active work in VTE) and there are quite a few applications now that use it. I would tend to agree with the point in the VTE discussion that it's better to think of a general way to implement images and use Sixel and Sixel-enabled appliations as the test case, rather than supporting Sixel specifically. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 430844] Laptop on battery, continues to think charger is connected, will run battery to 0% and crash
https://bugs.kde.org/show_bug.cgi?id=430844 --- Comment #3 from Philipp Reichmuth --- Could be related to a combination of upower and kernel bugs: https://gitlab.freedesktop.org/upower/upower/-/issues/126 -- You are receiving this mail because: You are watching all bug changes.
