[krfb] [Bug 486713] New: Feature request: extern mediation of konections so i can reach someone over the Internet (Privat uses, help friends ...
https://bugs.kde.org/show_bug.cgi?id=486713 Bug ID: 486713 Summary: Feature request: extern mediation of konections so i can reach someone over the Internet (Privat uses, help friends ... Classification: Applications Product: krfb Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: philipp.pl...@mailbox.org Target Milestone: --- Hi, I have Feature Request, i have some people i help with their linux, they are normal users, they are mostly some houres to drive away. I used Anydesk for support, but anydesk is not supporting wayland, and it seems that they will not so fast in future, With the appearence of Plamsma6 and Wayland this solution is not working anymore. Can´t you create a kind of mediation solution so i can reach all of my freinds in future again, a little Server hostet e.g. under https://store.kde.org there doesn´t need to be much trafic just for mediation and Krfb then makes a point to point connection outside ... This would be so helpfull and solving a big amount of my problems right now and in future I would always prefer a KDE Solution over a proprietary... Thanks for the great job with KDE so far Philipp Plato *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486589] Dolphin crashes with segfault when space is pressed
https://bugs.kde.org/show_bug.cgi?id=486589 --- Comment #4 from Philipp Maierhöfer --- Reproduced this with neon-user-20240502-0718 live on VirtualBox. Insert the ISO image, start the machine, open Dolphin, press space --> crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486589] Dolphin crashes with segfault when space is pressed
https://bugs.kde.org/show_bug.cgi?id=486589 --- Comment #3 from Philipp Maierhöfer --- Created attachment 169226 --> https://bugs.kde.org/attachment.cgi?id=169226=edit valgrind -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486589] Dolphin crashes with segfault when space is pressed
https://bugs.kde.org/show_bug.cgi?id=486589 --- Comment #2 from Philipp Maierhöfer --- Created attachment 169225 --> https://bugs.kde.org/attachment.cgi?id=169225=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486589] New: Dolphin crashes with segfault when space is pressed
https://bugs.kde.org/show_bug.cgi?id=486589 Bug ID: 486589 Summary: Dolphin crashes with segfault when space is pressed Classification: Applications Product: dolphin Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: maiphi.pub...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open Dolphin. Do not select a file. 2. Press space. OBSERVED RESULT Dolphin crashes with a segmentation fault. Message in the console: "KCrash: Application 'dolphin' crashing... crashRecursionCounter = 2". EXPECTED RESULT Enter selection mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumblweed KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486197] New: Drag & drop fails e.g. for newly created files
https://bugs.kde.org/show_bug.cgi?id=486197 Bug ID: 486197 Summary: Drag & drop fails e.g. for newly created files Classification: Applications Product: dolphin Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: maiphi.pub...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In some cases, drag & drop of a file doesn't work. Instead, a selection rectangle appears when a file is clicked and dragged. This is 100% reproducible on newly created files in Dolphin. I think that it occured to me in other sitations as well, but this is the only case I could reproduce. Tested this on Wayland, but I think X11 is also affected. STEPS TO REPRODUCE 1. Open Dolphin. Right click on the main view to open the context menu. Select "Create New -> Text File" and press enter to create the file. 2. Left click and hold the new file and move the mouse. OBSERVED RESULT Instead of dragging the file, a selection rectangle opens. You have to release the left button and try again to make it work. EXPECTED RESULT The file should be dragged. No selection rectangle should show (btw. why is this a rectangle in in details view? The horizontal selector from KDE 5 was more convenient). SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486196] New: Remember folder panel state when switching between tabs or split windows
https://bugs.kde.org/show_bug.cgi?id=486196 Bug ID: 486196 Summary: Remember folder panel state when switching between tabs or split windows Classification: Applications Product: dolphin Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: maiphi.pub...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin doesn't remember the state of the folder panel per view (tab or split view). There are two problems with that: * Collapsing folders when switching tabs/views essentially foils the advantage and, in my opinion, the main use case of tabs/split views. * Performance: the issue is particularly pronounced if one of the locations is sftp:// over the internet, because every time you switch to the sftp tab/view, the directory structure is reloaded which often takes several seconds due to the slow ssh connection. STEPS TO REPRODUCE 1. Open Dolphin in your home directory. If the folder panel is not shown, turn it on (F7). 2. Expand at least one directory in the folder panel by pressing the ">" left to the folder name in the folder panel. But do not enter a subdirectory. 3. Open a second tab or split the view. Navigate to a location that has a different folder panel root than home. The home directory in the first tab and the root directory in the second tab will do for illustration (but to really see how annoying this is, open an sftp location over the internet). 4. Switch back to the first tab/view. OBSERVED RESULT The folder panel gets reloaded (in case of sftp slowly) and its root correctly switches back to home. But all expanded folders are collapsed, except the one that is currently selected. EXPECTED RESULT The folder panel should remember its state per tab and split view. Note that one could use the same state for tabs/views that have the same folder panel root (e.g. the home directory), but not for the root directory and sftp locations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE tumbleweed KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485886] New: Flatpak branch end of life, Discover won't let me upgrade
https://bugs.kde.org/show_bug.cgi?id=485886 Bug ID: 485886 Summary: Flatpak branch end of life, Discover won't let me upgrade Classification: Applications Product: Discover Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: philipp.kie...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Flatpak would not upgrade, despite showing as upgradable. Running `flatpak update` manually revealed that the branch was "end of life" STEPS TO REPRODUCE 1. Have the Flatpak "com.github.Eloston.UngoogledChromium" installed, version 123.0.6312.105 2. Check for updates in Discover -> Flatpak shows up, there is an update available. 3. Click on "Upgrade all" in Discover (unsure of the actual button label, since I use the German language: Button to apply upgrades, not the one to check if upgrades are available) OBSERVED RESULT The list of upgradable packages gets blank for a second, then the above-mentioned Flatpak reappears. No upgrade was performed. When running `flatpak update` in the command line, I get the following prompt: ``` Info: app com.github.Eloston.UngoogledChromium branch stable is end-of-life, in favor of io.github.ungoogled_software.ungoogled_chromium branch stable Replace? [Y/n]: ``` EXPECTED RESULT The Flatpak gets updated and does not reappear. Or at least some warning/error with instructions on what to do next. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-28-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 472793] merkuro-calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472793 Sebastian Philipp changed: What|Removed |Added CC||sebast...@spawnhost.de --- Comment #9 from Sebastian Philipp --- see this as well. #0 0x7f540ff55c7a QV4::Heap::InternalClass::changeVTableImpl(QV4::VTable const*) (libQt5Qml.so.5 0x155c7a) #1 0x7f541011f37b QV4::QQmlValueTypeWrapper::create(QV4::ExecutionEngine*, QObject*, int, QMetaObject const*, int) (libQt5Qml.so.5 0x31f37b) #2 0x7f540ffc4e75 loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (libQt5Qml.so.5 0x1c4e75) #3 0x7f540ffc59c3 QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (libQt5Qml.so.5 0x1c59c3) #4 0x7f5410124c77 QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) (libQt5Qml.so.5 0x324c77) #5 0x7f540ff4f585 QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) (libQt5Qml.so.5 0x14f585) #6 0x7f53d4449aa1 n/a (n/a 0x0) #7 0x7f540ffead50 QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (libQt5Qml.so.5 0x1ead50) #8 0x7f540ff7ad02 QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (libQt5Qml.so.5 0x17ad02) #9 0x7f5410111040 QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (libQt5Qml.so.5 0x311040) #10 0x7f54101177c7 QQmlBinding::evaluate(bool*) (libQt5Qml.so.5 0x3177c7) #11 0x7f541011bd7b QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (libQt5Qml.so.5 0x31bd7b) #12 0x7f5410119615 QQmlBinding::update(QFlags) (libQt5Qml.so.5 0x319615) #13 0x7f54100f4e17 QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (libQt5Qml.so.5 0x2f4e17) #14 0x7f540e6e8e20 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e8e20) #15 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #16 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #17 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #18 0x7f540f0f7b44 QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab44) #19 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #20 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #21 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #22 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #23 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #24 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #25 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #26 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #27 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #28 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #29 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #30 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #31 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #32 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #33 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #34 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #35 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #36 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #37 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #38 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #39 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #40 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #41 0x7f540f0f19a4 QQuickAction::checkedChanged(bool) (libQt5QuickTemplates2.so.5 0xa49a4) #42 0x7f540f0f7b0d QQuickAbstractButton::setChecked(bool) (libQt5QuickTemplates2.so.5 0xaab0d) #43 0x7f540e6e9151 void doActivate(QObject*, int, void**) (libQt5Core.so.5 0x2e9151) #44 0x7f540f0f19a4 QQuickAction::che
[plasmashell] [Bug 482816] On Wayland, real-fake-session-restored application not restored onto their virtual desktops
https://bugs.kde.org/show_bug.cgi?id=482816 --- Comment #4 from Philipp Verpoort --- After some further testing, I can confirm that in Wayland the size of Firefox windows is restored correctly, but neither their position nor the specific screen (in a multi-screen system) nor the virtual desktop is restored. All windows just pop up in the centre of the primary screen on the current virtual desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482816] On Wayland, real-fake-session-restored application not restored onto their virtual desktops
https://bugs.kde.org/show_bug.cgi?id=482816 Philipp Verpoort changed: What|Removed |Added CC||philipp.verpo...@secure.mai ||lbox.org --- Comment #3 from Philipp Verpoort --- I can confirm that I'm seeing the exact same behaviour. Windows are restored on the virtual desktops where they were before when using X11, but it's broken on Wayland. I tested this by logging out, switching from Wayland to X11 (in the bottom left corner of the login screen), and logging back in again. Notably, this has nothing to do with restoring the Plasma user session. Windows should restore correctly even when simply restarting (or closing/reopening) Firefox. Meanwhile, Chromium windows restore just fine on the correct virtual desktops in Wayland. So it's a Firefox-specific issue. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 479245] New: Offline upgrades: Offer option to shutdown instead of rebooting
https://bugs.kde.org/show_bug.cgi?id=479245 Bug ID: 479245 Summary: Offline upgrades: Offer option to shutdown instead of rebooting Classification: Applications Product: Discover Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: philipp.kie...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When "offline updates" is activated in Settings, Discover has a checkbox that allows the user to automatically reboot once the updates are finished in order to apply them cleanly. Would it be possible to choose between reboot and shutdown? I normally start updates whenever I am done using my computer. Now, I always have to wait for it to do the updates, reboot several times in order to apply them, and then shut down the machine? Is it possible to shift the process to the next boot, so that one can start the updates, automatically shutdown via Discover (instead of rebooting), and on the next boot the updates get applied? SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-14-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z170-Gaming K3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474624] Holding arrow key and then shift key does not engage text selection in any app on Wayland as it does on X11
https://bugs.kde.org/show_bug.cgi?id=474624 --- Comment #2 from Philipp Maierhöfer --- I find this very useful and it drives me crazy when it's not working. Here is one possible use case: You want to select a couple of lines starting with the one below the cursor. Press and hold the down arrow, then press shift during the key repetition delay. Saves one keypress. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 Philipp Richter changed: What|Removed |Added CC||richterphilipp.pops@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474626] New: Pointless error message when deleting folder from folder panel
https://bugs.kde.org/show_bug.cgi?id=474626 Bug ID: 474626 Summary: Pointless error message when deleting folder from folder panel Classification: Applications Product: dolphin Version: 23.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: maiphi.pub...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY An unnessesary and distracting error message is printed when the active folder is deleted using the folder panel. STEPS TO REPRODUCE 1. Show the folder panel (F7) if it's not already shown. 2. Left-click on a folder in the panel to enter it. 3. Then right-click on the same folder and select "delete". OBSERVED RESULT An error message is printed: "Current location changed, ‘/path/to/folder’ is no longer accessible." EXPECTED RESULT Don't print an error. It's expected behaviour that the folder is no more accessible after explicitly deleting it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbeweed 20230908 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Apart from the error message, the behaviour is as expected: the active folder is moving one step up in the hierarchy. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 474624] New: Text selection with shift+arrows half broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=474624 Bug ID: 474624 Summary: Text selection with shift+arrows half broken on Wayland Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: maiphi.pub...@gmx.net Target Milestone: --- SUMMARY Text selection with shift + arrow keys on Wayland doesn't work in any KDE application when the arrow key is pressed before the shift key. The other way around, i.e. first press and hold shift, then press an arrow key, selection works. STEPS TO REPRODUCE 1. Open an application that displays editable text (Kate, KWrite, Dolphin's location bar, ... this is everywhere) 2. Press and hold an arrow key, then press shift while the cursor is running through the text. OBSERVED RESULT No text ist selected. EXPECTED RESULT All text that the curser ran over while holding the shift should be selected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230908 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This is and has always been working fine on X11. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473839] Applications using KonsolePart crash when displaying it
https://bugs.kde.org/show_bug.cgi?id=473839
--- Comment #1 from Philipp A. ---
Yakuake traceback:
Application: Yakuake (yakuake), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f678837197b in QScopedPointer >::operator->() const (this=)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1151
#8 QAction::d_func() (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#9 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051
#10 0x7f675a4d4144 in Konsole::Screen::setReplMode(int)
(this=0x559703479400, mode=1) at
/usr/src/debug/konsole/konsole-23.08.0/src/Screen.cpp:2395
#11 0x7f675a4ef095 in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int)
(this=, tokenSize=, terminator=27) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:1071
#12 0x7f675a4e0290 in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) (this=this@entry=0x559703af8720,
newState=newState@entry=Konsole::Vt102Emulation::Escape, cc=cc@entry=27) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:434
#13 0x7f675a4e0473 in
Konsole::Vt102Emulation::receiveChars(QVector const&)
(this=0x559703af8720, chars=) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:698
#14 0x7f675a4babea in Konsole::Emulation::receiveData(char const*, int)
(this=0x559703af8720, text=0x559703b72708
"\033[?25l\033[1;1H\033[J\033[38;5;10m\033]133;A\033\\/home/phil\033]133;B\033\\\033[38;5;14m\343\200\211\342\200\214\033[38;5;5m\0337\033[1;271H2023-08-28
11:40:16\0338\033[0m\033[0m\0337\0338\033[6 q\033[?25h", length=132) at
/usr/src/debug/konsole/konsole-23.08.0/src/Emulation.cpp:233
#15 0x7f67876d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffb39bffa0, r=, this=0x55970357d1f0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x5597038856c0,
signal_index=17, argv=0x7fffb39bffa0) at kernel/qobject.cpp:3925
#17 0x7f675a4a893b in Konsole::Pty::receivedData(char const*, int)
(this=, _t1=, _t2=) at
/usr/src/debug/konsole/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_Pty.cpp:154
#18 0x7f675a4c07c9 in Konsole::Pty::dataReceived() (this=0x5597038856c0) at
/usr/src/debug/konsole/konsole-23.08.0/src/Pty.cpp:101
#19 0x7f67876d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffb39c0070, r=, this=0x55970357d0b0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x559703885740,
signal_index=3, argv=0x7fffb39c0070) at kernel/qobject.cpp:3925
#21 0x7f675af920c7 in KPtyDevicePrivate::_k_canRead() (this=0x5597037b7e40)
at /usr/src/debug/kpty/kpty-5.109.0/src/kptydevice.cpp:291
#22 0x7f675af92369 in KPtyDevice::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_c=, _a=0x7fffb39c0200,
_id=, _o=) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7fffb39c0200) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7f67876d17f3 in doActivate(QObject*, int, void**)
(sender=0x559703885920, signal_index=5, argv=0x7fffb39c0200) at
kernel/qobject.cpp:3937
#25 0x7f67876d2ea9 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x559703885920,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185
#26 0x7f67876d2f9b in QSocketNotifier::event(QEvent*) (this=0x559703885920,
e=) at kernel/qsocketnotifier.h:115
#27 0x7f678837893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x559703885920, e=0x7fffb39c0310) at
kernel/qapplication.cpp:3640
#28 0x7f678769c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x559703885920, event=0x7fffb39c0310) at
kernel/qcoreapplication.cpp:1064
#29 0x7f67876ea276 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x559703239f70) at kernel/qeventdispatcher_glib.cpp:107
#30 0x7f6785e81a31 in g_main_dispatch (context=0x7f677c000ee0) at
../glib/glib/gmain.c:3460
#31 g_main_context_dispatch (context=0x7f677c000ee0) at
../glib/glib/gmain.c:4200
#32 0x7f6785edecc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7f677c000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#33 0x7f6785e7f0e2 in g_main_context_iteration (context=0x7f677c000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#34 0x7f67876eb53f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55970323cc70, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#35 0x000
[konsole] [Bug 473839] New: Applications using KonsolePart crash when displaying it
https://bugs.kde.org/show_bug.cgi?id=473839
Bug ID: 473839
Summary: Applications using KonsolePart crash when displaying
it
Classification: Applications
Product: konsole
Version: 23.08.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: kpart
Assignee: konsole-de...@kde.org
Reporter: flying-sh...@web.de
Target Milestone: ---
SUMMARY
Applications hosting a KonsolePart crash with a segfault.
STEPS TO REPRODUCE
1. Make KonsolePart appear (e.g. open Dolphin, Yakuake or show the terminal
panel in Kate)
2. Observe segfault
OBSERVED RESULT
```
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fb26757197b in QScopedPointer >::operator->() const (this=)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1151
#8 QAction::d_func() (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#9 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051
#10 0x7fb24083d144 in Konsole::Screen::setReplMode(int)
(this=0x556a432a0190, mode=1) at
/usr/src/debug/konsole/konsole-23.08.0/src/Screen.cpp:2395
#11 0x7fb240858095 in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int)
(this=, tokenSize=, terminator=27) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:1071
#12 0x7fb240849290 in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) (this=this@entry=0x556a43763870,
newState=newState@entry=Konsole::Vt102Emulation::Escape, cc=cc@entry=27) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:434
#13 0x7fb240849473 in
Konsole::Vt102Emulation::receiveChars(QVector const&)
(this=0x556a43763870, chars=) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:698
#14 0x7fb240823bea in Konsole::Emulation::receiveData(char const*, int)
(this=0x556a43763870, text=0x556a43a5d3e8
"\033[?25l\033[6;1H\033[J\033[38;5;10m\033]133;A\033\\/home/phil\033]133;B\033\\\033[38;5;14m\343\200\211\342\200\214\033[38;5;5m\0337\033[6;174H2023-08-28
11:30:00\0338\033[0m\033[0m\0337\0338\033[6 q\033[?25h", length=132) at
/usr/src/debug/konsole/konsole-23.08.0/src/Emulation.cpp:233
#15 0x7fb2668d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffc01d6e4d0, r=, this=0x556a43309850, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x556a4317d950,
signal_index=17, argv=0x7ffc01d6e4d0) at kernel/qobject.cpp:3925
#17 0x7fb24081193b in Konsole::Pty::receivedData(char const*, int)
(this=, _t1=, _t2=) at
/usr/src/debug/konsole/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_Pty.cpp:154
#18 0x7fb2408297c9 in Konsole::Pty::dataReceived() (this=0x556a4317d950) at
/usr/src/debug/konsole/konsole-23.08.0/src/Pty.cpp:101
#19 0x7fb2668d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffc01d6e5a0, r=, this=0x556a432815e0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x556a4317db60,
signal_index=3, argv=0x7ffc01d6e5a0) at kernel/qobject.cpp:3925
#21 0x7fb24bedd0c7 in KPtyDevicePrivate::_k_canRead() (this=0x556a43277c30)
at /usr/src/debug/kpty/kpty-5.109.0/src/kptydevice.cpp:291
#22 0x7fb24bedd369 in KPtyDevice::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_c=, _a=0x7ffc01d6e730,
_id=, _o=) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7ffc01d6e730) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7fb2668d17f3 in doActivate(QObject*, int, void**)
(sender=0x556a4317dc20, signal_index=5, argv=0x7ffc01d6e730) at
kernel/qobject.cpp:3937
#25 0x7fb2668d2ea9 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x556a4317dc20,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185
#26 0x7fb2668d2f9b in QSocketNotifier::event(QEvent*) (this=0x556a4317dc20,
e=) at kernel/qsocketnotifier.h:115
#27 0x7fb26757893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x556a4317dc20, e=0x7ffc01d6e840) at
kernel/qapplication.cpp:3640
#28 0x7fb26689c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x556a4317dc20, event=0x7ffc01d6e840) at
kernel/qcoreapplication.cpp:1064
#29 0x7fb2668ea276 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x556a4276e730) at kernel/qeventdispatcher_glib.cpp:107
#30
[yakuake] [Bug 473836] New: Konsolepart crashes on start
https://bugs.kde.org/show_bug.cgi?id=473836
Bug ID: 473836
Summary: Konsolepart crashes on start
Classification: Applications
Product: yakuake
Version: 23.08.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: h...@kde.org
Reporter: flying-sh...@web.de
Target Milestone: ---
Application: yakuake (23.08.0)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.12-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Whenever I open an application that uses Konsolepart (i.e. not Konsole itself,
but Dolphin or Yakuake) it crashes on this line:
https://invent.kde.org/utilities/konsole/-/blob/25ad2a35a72ecb4e073786535f9bdf6cdc67fdf7/src/Screen.cpp#L2395
The crash can be reproduced every time.
-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f1035f7197b in QScopedPointer >::operator->() const (this=)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1151
#8 QAction::d_func() (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#9 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051
#10 0x7f10142d4144 in Konsole::Screen::setReplMode(int)
(this=0x55cfe34fc070, mode=1) at
/usr/src/debug/konsole/konsole-23.08.0/src/Screen.cpp:2395
#11 0x7f10142ef095 in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int)
(this=, tokenSize=, terminator=27) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:1071
#12 0x7f10142e0290 in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) (this=this@entry=0x55cfe3b5ed50,
newState=newState@entry=Konsole::Vt102Emulation::Escape, cc=cc@entry=27) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:434
#13 0x7f10142e0473 in
Konsole::Vt102Emulation::receiveChars(QVector const&)
(this=0x55cfe3b5ed50, chars=) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:698
#14 0x7f10142babea in Konsole::Emulation::receiveData(char const*, int)
(this=0x55cfe3b5ed50, text=0x55cfe3bd8d38
"\033[?25l\033[1;1H\033[J\033[38;5;10m\033]133;A\033\\/home/phil\033]133;B\033\\\033[38;5;14m\343\200\211\342\200\214\033[38;5;5m\0337\033[1;271H2023-08-28
09:03:58\0338\033[0m\033[0m\0337\0338\033[6 q\033[?25h", length=132) at
/usr/src/debug/konsole/konsole-23.08.0/src/Emulation.cpp:233
#15 0x7f10352d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcf1cf1010, r=, this=0x55cfe38df430, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x55cfe38df8e0,
signal_index=17, argv=0x7ffcf1cf1010) at kernel/qobject.cpp:3925
#17 0x7f10142a893b in Konsole::Pty::receivedData(char const*, int)
(this=, _t1=, _t2=) at
/usr/src/debug/konsole/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_Pty.cpp:154
#18 0x7f10142c07c9 in Konsole::Pty::dataReceived() (this=0x55cfe38df8e0) at
/usr/src/debug/konsole/konsole-23.08.0/src/Pty.cpp:101
#19 0x7f10352d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcf1cf10e0, r=, this=0x55cfe38df2f0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x55cfe38df940,
signal_index=3, argv=0x7ffcf1cf10e0) at kernel/qobject.cpp:3925
#21 0x7f102c0080c7 in KPtyDevicePrivate::_k_canRead() (this=0x55cfe36caf40)
at /usr/src/debug/kpty/kpty-5.109.0/src/kptydevice.cpp:291
#22 0x7f102c008369 in KPtyDevice::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_c=, _a=0x7ffcf1cf1270,
_id=, _o=) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7ffcf1cf1270) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7f10352d17f3 in doActivate(QObject*, int, void**)
(sender=0x55cfe38e05a0, signal_index=5, argv=0x7ffcf1cf1270) at
kernel/qobject.cpp:3937
#25 0x7f10352d2ea9 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x55cfe38e05a0,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185
#26 0x7f10352d2f9b in QSocketNotifier::event(QEvent*) (this=0x55cfe38e05a0,
e=) at kernel/qsocketnotifier.h:115
#27 0x7f1035f7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55cfe38e05a0, e=0x7ffcf1cf1380) at
kernel/qapplication.cpp:3640
#28 0x7f103529c6f8 in
[Discover] [Bug 472689] New: Discover fails when unattended-upgrade is running in the background
https://bugs.kde.org/show_bug.cgi?id=472689 Bug ID: 472689 Summary: Discover fails when unattended-upgrade is running in the background Classification: Applications Product: Discover Version: 5.24.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: philipp.k...@gmail.com CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Make sure you have updates to install (e.g. don't use your computer for a while). 2. Reboot. unattended-upgrades will start updating, but the user doesn't typically notice that. 3. Open Discover, click "Install updates". Any diligent user would do this after not using their computer for a while. 4. Enter password to confirm installation. OBSERVED RESULT Fails due to lack of installer lock, which is a hard-to-understand error message for (a) newbies or (b) people who don't know that unattended-upgrades is even enabled on their system. EXPECTED RESULT It doesn't fail. There's two concurrent processes trying to achieve basically the same thing: to install all available updates. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 POSSIBLE SOLUTIONS When encountering a lock error, discover could check if unattended-upgrades is running. If so, it could (a) display a message that other upgrades are in progress, and/or (b) wait for them to complete, and/or (c) resume its own updates once the background process is complete, and/or (d) in a "details" section show the log output of the background process (like `tail`) so that the user can verify that it isn't stuck and that it's worth waiting. This could be useful as there's no other kind of progress indicator in this case. If this isn't possible, the error message could point to the (canonical) log file location at least, so that the user knows where to look. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471914] New: gwenview crash jpg
https://bugs.kde.org/show_bug.cgi?id=471914 Bug ID: 471914 Summary: gwenview crash jpg Classification: Applications Product: gwenview Version: 23.04.2 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: philipp_foers...@yahoo.com Target Milestone: --- Application: gwenview (23.04.2) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: Gwenview crashes when opening a jpg file from my Sony camera. I get the following error message in Konsole: KCrash: Application 'gwenview' crashing... Corrupt JPEG data: premature end of data segment KCrash: Attempting to start /usr/libexec/drkonqi QFile::at: Cannot set file position 7323648 the files open just fine on other viewers, only gwenview crashes The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7f1065757dfd in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const () from /lib64/glibc-hwcaps/x86-64-v3/libexiv2.so.0.28.0 #5 0x7f1065831085 in ?? () from /lib64/glibc-hwcaps/x86-64-v3/libexiv2.so.0.28.0 #6 0x7f10657f0c3f in ?? () from /lib64/glibc-hwcaps/x86-64-v3/libexiv2.so.0.28.0 #7 0x7f106574fb81 in Exiv2::Exifdatum::write(std::basic_ostream >&, Exiv2::ExifData const*) const () from /lib64/glibc-hwcaps/x86-64-v3/libexiv2.so.0.28.0 #8 0x7f106663dfd8 in Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from /lib64/libgwenviewlib.so.5 #9 0x7f106660538c in Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib64/libgwenviewlib.so.5 #10 0x7f106660fda1 in ?? () from /lib64/libgwenviewlib.so.5 #11 0x7f10643257a2 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f106410d925 in QFutureWatcherBase::event(QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f1064fa519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f10642ed4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f10642f0af1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #16 0x7f1064346c83 in ?? () from /lib64/libQt5Core.so.5 #17 0x7f1061f168d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f1061f16ce8 in ?? () from /lib64/libglib-2.0.so.0 #19 0x7f1061f16d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f1064346496 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7f10642ebf8b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7f10642f4420 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #23 0x558d6830f413 in ?? () #24 0x7f1063a2abb0 in __libc_start_call_main () from /lib64/libc.so.6 #25 0x7f1063a2ac79 in __libc_start_main_impl () from /lib64/libc.so.6 #26 0x558d6830fb75 in ?? () [Inferior 1 (process 3117) detached] The reporter indicates this bug may be a duplicate of or related to bug 471167. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471147] webp files don't load, says "Failed to load image"
https://bugs.kde.org/show_bug.cgi?id=471147 --- Comment #5 from Philipp Keck --- Found the snap config here: https://invent.kde.org/packaging/snapcraft-kde-applications/-/blob/Neon/release/digikam/snapcraft.yaml Sadly running it locally requires LXD and thus a bunch of disk space and patience that I don't currently have. Could we solve this issue by adding something like `libkimageformat` (though that particular probably one doesn't exist, I made it up) to one of the packages sections in that config file? (And can we have the CI do the building, so it doesn't require a local build environment?) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471147] webp files don't load, says "Failed to load image"
https://bugs.kde.org/show_bug.cgi?id=471147 --- Comment #4 from Philipp Keck --- First of all, I can confirm that the AppImage doesn't have this issue. > Report the problem to Ubuntu, they should finally build a native digiKam > package. They already have, right? https://packages.ubuntu.com/jammy/digikam Just with jammy it's stuck at 7.5.0, which doesn't support webp yet. > Use our AppImage instead, just make it executable and start it. I'm a bit hesitant, because it wouldn't auto-update, as far as I understand. One of my reasons for using Linux instead of Windows is not having to update each and every application manually / separately. > The snap package does not appear to contain the KImageFormat plugin. Could that be changed? I can't find where the snap is built from. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471147] webp files don't load, says "Failed to load image"
https://bugs.kde.org/show_bug.cgi?id=471147
--- Comment #2 from Philipp Keck ---
I use the snap: https://snapcraft.io/digikam
This repeats for every one of my webp files when I open the directory:
```
digikam.metaengine: Check ExifTool availability: false
digikam.metaengine: ExifTool is not available to load metadata...
digikam.metaengine: Loading metadata with "Exiv2" backend from
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.general: Trying to get thumbnail from
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp" ( "image" )
digikam.general: Trying to get thumbnail with Exiv2 for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.general: Trying to get thumbnail with DImg preview for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.general: Trying to get thumbnail from Embedded preview with libraw for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.rawengine: Failed to load embedded RAW preview
digikam.general: Trying to get thumbnail from half preview with libraw for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.general: Trying to get thumbnail from Embedded preview with Exiv2 for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.dimg: "/media//2577a254-6362-4df1-988e-f7dc44320a90.webp" : Unknown
image format !!!
digikam.general: mimetype = "" ext = "WEBP"
digikam.general: Cannot create thumbnail for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
digikam.general: Thumbnail is null for
"/media//2577a254-6362-4df1-988e-f7dc44320a90.webp"
```
And when I open one of those files, it's this:
```
digikam.metaengine: Check ExifTool availability: false
digikam.metaengine: ExifTool is not available to load metadata...
digikam.metaengine: Loading metadata with "Exiv2" backend from
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Trying to get thumbnail from
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp" ( "image" )
digikam.general: Trying to get thumbnail with Exiv2 for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Trying to get thumbnail with DImg preview for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Trying to get thumbnail from Embedded preview with libraw for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.rawengine: Failed to load embedded RAW preview
digikam.general: Trying to get thumbnail from half preview with libraw for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Trying to get thumbnail from Embedded preview with Exiv2 for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.dimg: "/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp" : Unknown
image format !!!
digikam.general: mimetype = "" ext = "WEBP"
digikam.general: Cannot create thumbnail for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Thumbnail is null for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.metaengine: ExifToolProcess::command(): cannot process command with
ExifTool ("-json", "-G:0:1:2:4:6", "-l",
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp")
digikam.metaengine: ExifTool cannot be sent: "Load Metadata"
digikam.metaengine: Check ExifTool availability: false
digikam.metaengine: ExifTool is not available to load metadata...
digikam.metaengine: Loading metadata with "Exiv2" backend from
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Metadata loading with Exiv2 took 1 ms ( true )
digikam.general: Try to get preview from
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Preview quality: 0
digikam.metaengine: Check ExifTool availability: false
digikam.metaengine: ExifTool is not available to load metadata...
digikam.metaengine: Loading metadata with "Exiv2" backend from
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Try to load DImg preview from:
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.dimg: "/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp" : Unknown
image format !!!
digikam.general: Cannot extract preview for
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.webp"
digikam.general: Stacked View Mode : 1
digikam.general: FocusPointsGroup: no Point to load
digikam.metaengine: Check ExifTool availability: false
digikam.metaengine: ExifTool is not available to load metadata...
digikam.metaengine: Loading metadata with "Exiv2" backend from
"/media//9abd9ca2-09d8-4617-96cf-263979c5ebcc.
[digikam] [Bug 471147] New: webp files don't load, says "Failed to load image"
https://bugs.kde.org/show_bug.cgi?id=471147 Bug ID: 471147 Summary: webp files don't load, says "Failed to load image" Classification: Applications Product: digikam Version: 8.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: philipp.k...@gmail.com Target Milestone: --- Created attachment 159740 --> https://bugs.kde.org/attachment.cgi?id=159740=edit One of the files that fails to load. SUMMARY According to the release notes, 8.0.0 supports webP. But I get an error and don't see the images. STEPS TO REPRODUCE 1. View a folder that contains webp files (example attached). 2. Open one of those files. OBSERVED RESULT In the overview, only a green dummy thumbnail is shown. In the per-file view, the view remains empty (black) and at the top right it says "Failed to load image". EXPECTED RESULT Renders the image. Like nomacs, Xviewer, GIMP and Dolphin do just fine for the same file(s). SOFTWARE/OS VERSIONS Mint based on Ubuntu 22.04. KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408563] Provide option for day/night color theme switching
https://bugs.kde.org/show_bug.cgi?id=408563 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de --- Comment #19 from Philipp A. --- This is being worked on: https://invent.kde.org/plasma/plasma-workspace/-/issues/59 Until then, here is two more options to do it: - https://gitlab.com/WhyNotHugo/darkman - https://gitlab.com/LADlSLAV/yabotss (can be used with the former) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466587] New: Wrong German translation "Aktualisierung ausgewählt"
https://bugs.kde.org/show_bug.cgi?id=466587 Bug ID: 466587 Summary: Wrong German translation "Aktualisierung ausgewählt" Classification: Applications Product: Discover Version: 5.26.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: philipp.kie...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When updating only a part of the available updates, the button in the top right corner (to start the update process) displays the wrong string. STEPS TO REPRODUCE 1. Have multiple updates available 2. Deselect one of the updates OBSERVED RESULT Above mentioned string changes to "Aktualisierung ausgewählt", which *does indeed* translate to "Update selected" (I guess this is the original string), but in this case is a false friend. It should be "Ausgewählte aktualisiseren" or similar in my opinion. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 with Backports PPA KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444034] Plasmashell semi-freeze after and display bugs after a few hours or after sleep/hibernate
https://bugs.kde.org/show_bug.cgi?id=444034 Philipp Keck changed: What|Removed |Added CC||philipp.k...@gmail.com --- Comment #5 from Philipp Keck --- Same here regarding sluggishness/unresponsiveness after hibernate, actually for 10-30s. And even after that is over, sometimes it works again and other times it's just as sluggish when I try to use it again a few seconds later -- until I kquit& Though I haven't observed the random panel resizing. Operating System: Linux Mint 21.1 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-58-lowlatency (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6400 CPU @ 2.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 745/PCIe/SSE2 In https://bugs.kde.org/show_bug.cgi?id=451840, someone reported similar symptoms, though under Wayland (not X11 like here) and after suspend only, not hibernate (unlike here). Still I wonder if the clipboard history could be at fault somehow, perhaps an equivalent fix for X11 is needed as the one they did for Wayland in https://bugs.kde.org/show_bug.cgi?id=454379. I'll try to look for high CPU/RAM usage the next time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464961] New: Konsole crashes when switching from light to dark theme in system settings
https://bugs.kde.org/show_bug.cgi?id=464961 Bug ID: 464961 Summary: Konsole crashes when switching from light to dark theme in system settings Classification: Applications Product: konsole Version: 22.12.1 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: m...@philipp-wagner.com Target Milestone: --- Application: konsole (22.12.1) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.7-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: I had Konsole open when switching from Breeze in System Settings -> Global Design to Breeze Dämmerung (Dusk? Twilight? in the English translation). KDE switched over to the darker design, and Konsole crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7fe97b8fc2a9 in XAddExtension (dpy=dpy@entry=0x60002) at /usr/src/debug/libX11-1.8.1/src/InitExt.c:73 #5 0x7fe9774c0504 in _XcursorGetDisplayInfo (dpy=0x60002) at /usr/src/debug/libXcursor-1.2.1-1.4.x86_64/src/display.c:132 #6 0x7fe9774c1ac9 in XcursorGetTheme (dpy=) at /usr/src/debug/libXcursor-1.2.1-1.4.x86_64/src/display.c:353 #7 0x7fe977112f7c in updateCursorTheme (dpy=0x60002, theme=...) at qxcbcursor.cpp:524 #8 0x7fe9771130b4 in QXcbCursor::cursorThemePropertyChanged (screen=, name=..., property=..., handle=0x5569b87fd3b0) at qxcbcursor.cpp:539 #9 0x7fe9771170ff in QXcbXSettingsPropertyValue::updateValue (last_change_serial=, value=..., name=..., screen=0x5569b87cdaf0, this=) at qxcbxsettings.cpp:77 #10 QXcbXSettingsPropertyValue::updateValue (last_change_serial=, value=..., name=..., screen=0x5569b87cdaf0, this=) at qxcbxsettings.cpp:70 #11 QXcbXSettingsPrivate::populateSettings (this=this@entry=0x5569b87f4b30, xSettings=...) at qxcbxsettings.cpp:211 #12 0x7fe977116400 in QXcbXSettings::handlePropertyNotifyEvent (this=, event=) at qxcbxsettings.cpp:274 #13 0x7fe9770f2524 in QXcbConnection::handleXcbEvent (this=this@entry=0x5569b87cb5a0, event=event@entry=0x7fe96800ada0) at qxcbconnection.cpp:708 #14 0x7fe9770f34b6 in QXcbConnection::processXcbEvents (this=0x5569b87cb5a0, flags=...) at qxcbconnection.cpp:1065 #15 0x7fe977119143 in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:103 #16 0x7fe97b069a90 in g_main_dispatch (context=0x7fe970005010) at ../glib/gmain.c:3454 #17 g_main_context_dispatch (context=0x7fe970005010) at ../glib/gmain.c:4172 #18 0x7fe97b069e48 in g_main_context_iterate (context=context@entry=0x7fe970005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4248 #19 0x7fe97b069edc in g_main_context_iteration (context=0x7fe970005010, may_block=1) at ../glib/gmain.c:4313 #20 0x7fe97cf33b66 in QEventDispatcherGlib::processEvents (this=0x5569b890e0a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7fe97cedabab in QEventLoop::exec (this=this@entry=0x7fffce561200, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7fe97cee2d16 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x7fe97d36ed3c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870 #24 0x7fe97dba53c5 in QApplication::exec () at kernel/qapplication.cpp:2832 #25 0x5569b6cd0165 in main (argc=, argv=) at /usr/src/debug/konsole-22.12.1/src/main.cpp:252 [Inferior 1 (process 3655) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464775] Remote slewing and plate-solving target update problem
https://bugs.kde.org/show_bug.cgi?id=464775 Philipp Auersperg-Castell changed: What|Removed |Added CC||p...@bluedynamics.com Version|git |3.6.2 URL||https://invent.kde.org/educ ||ation/kstars/-/merge_reques ||ts/834 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464775] New: Remote slewing and plate-solving target update problem
https://bugs.kde.org/show_bug.cgi?id=464775 Bug ID: 464775 Summary: Remote slewing and plate-solving target update problem Classification: Applications Product: kstars Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: p...@bluedynamics.com Target Milestone: --- SUMMARY *** Remote slewing and plate-solving target update problem: when slewing with remote access(tested with kstars and stellarium as remote clients), there occurred 2 problems: - Name of target is not displayed in the Capture view. - target coords are not forwarded to Align, so plate solving gives not the delta from position to desired position but instead the delta between park position and slew position, so 'slew to target' does not work. *** This bug has been introduced in version 3.5.6. STEPS TO REPRODUCE 1. run kstars/ekos (3.6.x) and simulator telescope and ccd, GSC installed for plate solving simulation. - run ekos and hit 'start'. - telescope mount in park position. 2. unpark the mount. 3. on another machine start kstars and connect via Tools/Devices/Device Manager... 4. on client machine slew the telescope to M81 - either by selecting it in the map and rightclick and select in context menu 'Telescope Simulator/Slew'. - or by clicking ctlr-F and finding M81 and clicking "Details..." and then "Center in Telescope". 5. Telescope as expected points to M81. See logs at the end of this report! OBSERVED RESULT - In Ekos/Capture view the text box labeled 'Target:' is _not_ updated. - in the 'Align' tab when clicking 'Capture' with the 'Solver Action' set to 'sync': the solver finds the position but gives a wrong error like: "673084 arcsec. RA:541515 DE:-399754". EXPECTED RESULT - in the Capture view the 'Target' text box shows "M_81". - 'Capture' should gives an error in the range of <60 arcsec. when doing the above-mentioned steps from the local kstars map, everything works fine as described in EXPECTED RESULT. PROPOSED FIX I have provided a merge request that produces the expected result: https://invent.kde.org/education/kstars/-/merge_requests/834 . SOFTWARE/OS VERSIONS Tested on Ubuntu/amd64 and Raspberry arm64. This bug does not seem to be a platform-specific problem. ADDITIONAL INFORMATION Log with broken align: 2023-01-25T01:08:55 Mount is synced to solution coordinates. 2023-01-25T01:08:55 Syncing to RA (09h 57m 41s) DEC ( 68° 57' 26") 2023-01-25T01:08:55 Solution coordinates: RA (09h 57m 41s) DEC ( 68° 57' 26") Telescope Coordinates: RA (09h 57m 43s) DEC ( 68° 57' 15") Target Coordinates: RA (23h 56m 00s) DEC ( 180° 00' 00") 2023-01-25T01:08:55 WCS information updated. Images captured from this point forward shall have valid WCS. 2023-01-25T01:08:55 Effective telescope focal length is updated to 3 131,54 mm. 2023-01-25T01:08:55 Solver RA (148.94092) DEC (69.06839) Orientation (90.00727) Pixel Scale (0.24766) Parity (neg) 2023-01-25T01:08:55 Solver completed after 0.20 seconds. 2023-01-25T01:08:54 Image received. 2023-01-25T01:08:48 Capturing image... 2023-01-25T01:07:52 World Coordinate System (WCS) is enabled. Log with correct align: 2023-01-25T01:21:12 Mount is synced to solution coordinates. 2023-01-25T01:21:12 Syncing to RA (09h 57m 42s) DEC ( 68° 57' 26") 2023-01-25T01:21:12 Solution coordinates: RA (09h 57m 42s) DEC ( 68° 57' 26") Telescope Coordinates: RA (09h 57m 44s) DEC ( 68° 57' 15") Target Coordinates: RA (09h 57m 44s) DEC ( 68° 57' 15") 2023-01-25T01:21:12 WCS information updated. Images captured from this point forward shall have valid WCS. 2023-01-25T01:21:12 Effective telescope focal length is updated to 3 133,03 mm. 2023-01-25T01:21:12 Solver RA (148.94257) DEC (69.06839) Orientation (90.01308) Pixel Scale (0.24754) Parity (neg) 2023-01-25T01:21:12 Solver completed after 0.23 seconds. 2023-01-25T01:21:11 Image received. 2023-01-25T01:21:05 Capturing image... 2023-01-25T01:18:02 World Coordinate System (WCS) is enabled. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464066] New: User feedback Tooltip flashing
https://bugs.kde.org/show_bug.cgi?id=464066 Bug ID: 464066 Summary: User feedback Tooltip flashing Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Settings Assignee: plasma-b...@kde.org Reporter: philipp.kie...@gmail.com Target Milestone: --- SUMMARY When hovering over the question mark next to the slider which sets the level of feedback a user gives, the tooltip appears and disappears quickly in succession. See this screencap I made: https://youtu.be/NaO8YncZz2E STEPS TO REPRODUCE 1. Open the quick settings pane of System settings 2. Hover over the question mark button OBSERVED RESULT The tooltip appears flashes on and off EXPECTED RESULT The tooltip stays, so that the user can read it SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10, Kubuntu backports PPA enabled KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-28-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z170-Gaming K3 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 433084] KBibTeX crashes when opening .bib file
https://bugs.kde.org/show_bug.cgi?id=433084 --- Comment #20 from Philipp --- Created attachment 154680 --> https://bugs.kde.org/attachment.cgi?id=154680=edit New crash information added by DrKonqi kbibtex (0.9.90) using Qt 5.15.3 - What I was doing when the application crashed: Click on the kbibtex-Icon in the Application-Start-Menue. - Unusual behavior I noticed: Frame of kbibtex appears very briefly (about .5 seconds) on the screen but crashes immediately. - Custom settings of the application: None. All standard. -- Backtrace (Reduced): #4 0x7fefa9b7bd40 in FileModel::element(int) const () from /lib/x86_64-linux-gnu/libkbibtexdata.so.0 #5 0x7fefa9ea76e4 in SortFilterFileModel::filterAcceptsRow(int, QModelIndex const&) const () from /lib/x86_64-linux-gnu/libkbibtexgui.so.0 [...] #7 0x7fefa81e286d in QSortFilterProxyModel::setSourceModel(QAbstractItemModel*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fefa9ea8ac5 in SortFilterFileModel::setSourceModel(QAbstractItemModel*) () from /lib/x86_64-linux-gnu/libkbibtexgui.so.0 [...] #12 0x7fefa9aeeba7 in KParts::ReadOnlyPart::openUrl(QUrl const&) () from /lib/x86_64-linux-gnu/libKF5Parts.so.5 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 433084] KBibTeX crashes when opening .bib file
https://bugs.kde.org/show_bug.cgi?id=433084 Philipp changed: What|Removed |Added CC||lateinleh...@email.de -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 --- Comment #14 from Philipp A. --- Workaround: 1. run `cp /usr/share/applications/org.kde.kfontview.desktop ~/.local/share/applications/` 2. Change the `Exec` line to `Exec=QT_QPA_PLATFORM=xcb kfontview %U` -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 244945] kdesu should display the whole command that is being executed
https://bugs.kde.org/show_bug.cgi?id=244945 Philipp Wagner changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Philipp Wagner --- This issue is resolved now (and probably has been resolved for a while) in kdesu 5.25.4. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340551] Provide a link to the project page
https://bugs.kde.org/show_bug.cgi?id=340551 --- Comment #8 from Philipp A. --- This is still true, no links from fresh bugs to invent.kde.org -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 346074] Please fold drkonqui stacktraces
https://bugs.kde.org/show_bug.cgi?id=346074 Philipp A. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Philipp A. --- I think it’s formatted better now -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 340230] Icon mapping results in oxygen being used even if all toolkits’ icon theme is Flattr
https://bugs.kde.org/show_bug.cgi?id=340230 Philipp A. changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Philipp A. --- seems like it’s no longer a problem -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 437453] VPN protocol cannot be changed away from “pulse”
https://bugs.kde.org/show_bug.cgi?id=437453 Philipp A. changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Philipp A. --- Seems fixed, yes! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 408975] Starting the dashboard makes plasmashell spin up CPU cores
https://bugs.kde.org/show_bug.cgi?id=408975 Philipp A. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Philipp A. --- Seems like it was resolved -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Philipp Maierhöfer changed: What|Removed |Added CC||maiphi.pub...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #24 from Philipp Maierhöfer --- As is described there, this is a matter of highlighting. In Ark (I'm on 22.04.2), the entire line is clickable (and highlighted), but only the name is draggable, which is inconsistent in the described sense of space belonging to a specific object. Following my suggestion, only the Name column should be clickable & draggable. And to indicate that, only that column should be highlighted (rule: highlight the area that "belongs" to the item). Downside: we loose the visual accentuation of the rest of the row. Thanks to the alternating background colours in Dolphin's details view I'd find this acceptable (there is also the suggestion of different highlighting styles/colours). Of course in a perfect world all file listings in KDE applications would behave in the same way. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #22 from Philipp Maierhöfer --- The new behaviour caused a lot of frustration to me as a single clicker. But I'd like to suggest a compromise that avoids a configuration option and hopefully both sides can agree on. Let's start with some reasoning. In my opintion, a clickable area should either uniquely belong to an item in the folder, or to the folder that contains the item. * "belong to the item" means left click opens it, right click opens its context menu, dropping something on it means into it, click and hold drags the item, and hover opens the item's tooltip. * "belong to the folder" means left click unselects selected items, right click opens the context menu, dropping means into this folder, and click and hold activates the rubber band selection. Now we have an odd mixture: the entire row belongs to a list item if you click on it, but (apart from the name) it belongs to the folder if you use the rubber band, open the context menu or (with https://invent.kde.org/system/dolphin/-/merge_requests/401) if you drop something on it. This seems quite counterintuitive to me. So here's my suggestion: Treat the space within the "Name" column as if it belongs to the item with all consequences (see above), but the space within all other columns (Size/Modified/Owner/...) as if it belongs to the folder. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440082] Removable Media Tab Refuses to Load, Crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=440082 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de --- Comment #8 from Philipp A. --- I ran into this as well: A freeze because of a huge number of entries. I think the problem is that it creates config entries for everything it sees, but that’s what ~/.cache is for. Config entries should only be generated on user interaction. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 Philipp Maierhöfer changed: What|Removed |Added CC||maiphi.pub...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455625] Deleting copied file triggers Klipper::checkClipData -> Klipper::setClipboard -> repeat storm with memleak of QMimeData objects
https://bugs.kde.org/show_bug.cgi?id=455625 --- Comment #2 from Philipp Knechtges --- Looking at the supposedly solving fix in https://invent.kde.org/frameworks/kguiaddons/-/commit/04ddcecb5c91a79bce7443e2c43ed93450f435b1 , which was discussed in the bug 455625, it appreas to me that this probably only fixes the memleak. The issue of having an infinite loop in plasma_engine_clipboard.so should then still persist. Hence, I would suggest to reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455625] New: Deleting copied file triggers Klipper::checkClipData -> Klipper::setClipboard -> repeat storm with memleak of QMimeData objects
https://bugs.kde.org/show_bug.cgi?id=455625 Bug ID: 455625 Summary: Deleting copied file triggers Klipper::checkClipData -> Klipper::setClipboard -> repeat storm with memleak of QMimeData objects Product: plasmashell Version: 5.24.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: philipp-...@knechtges.com Target Milestone: 1.0 SUMMARY This bug report potentially reveals two issues: - An infinite loop in Klipper, if the clip data is an deleted file. - A memleak in Klipper::checkClipData or Klipper::setClipboard when dealing with QMimeData STEPS TO REPRODUCE (0. Optionally start plasmashell with environment variable QT_LOGGING_RULES="org.kde.klipper.debug=true" set) 1. Open Dolphin, create some temporary file. Let's call it "a.txt" 2. "Ctrl+C" this file "a.txt". 3. Now delete the "a.txt" file with "Shift+DEL". 4. Watch the memory consumption of plasmashell grow indefinitely. 5. "Ctrl+C" sth else and observe how the growth stops. OBSERVED RESULT 1. Watch memory consumption of plasmashell grow 2. Qt logging output will yield a loop of the following org.kde.klipper: Checking clip data org.kde.klipper: was empty. Retried, now still empty org.kde.klipper: Resetting clipboard (Prevent empty clipboard) org.kde.klipper: Setting clipboard to < "file:///home/asd/a.txt" > org.kde.klipper: Checking clip data org.kde.klipper: was empty. Retried, now still empty org.kde.klipper: Resetting clipboard (Prevent empty clipboard) org.kde.klipper: Setting clipboard to < "file:///home/asd/a.txt" > org.kde.klipper: Checking clip data org.kde.klipper: was empty. Retried, now still empty org.kde.klipper: Resetting clipboard (Prevent empty clipboard) org.kde.klipper: Setting clipboard to < "file:///home/asd/a.txt" > org.kde.klipper: Checking clip data org.kde.klipper: was empty. Retried, now still empty org.kde.klipper: Resetting clipboard (Prevent empty clipboard) org.kde.klipper: Setting clipboard to < "file:///home/asd/a.txt" > org.kde.klipper: Checking clip data org.kde.klipper: was empty. Retried, now still empty org.kde.klipper: Resetting clipboard (Prevent empty clipboard) org.kde.klipper: Setting clipboard to < "file:///home/asd/a.txt" > EXPECTED RESULT - no memleak in plasmashell SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Attaching to plasmashell with heaptrack reveals that the leaks come from QMimeData::QMimeData() and QMimeData::setData calls. Unfortunately, the rest of the heaptrack log is not so useful, since heaptrack mixes up symbols for .so files with dwarf version 6 debug info. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453305] KDE Connect Settings closed unexpectedly when using "Execute command" function in android app
https://bugs.kde.org/show_bug.cgi?id=453305 Philipp Kiemle changed: What|Removed |Added CC|philipp.kie...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453613] New: KDE Connect settings page closes when trying to open module settings
https://bugs.kde.org/show_bug.cgi?id=453613 Bug ID: 453613 Summary: KDE Connect settings page closes when trying to open module settings Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: philipp.kie...@gmail.com Target Milestone: --- Application: kdeconnect-settings (22.04.0) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.15.0-27-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: 1. Open Settings via the KDE Connect system tray icon 2. Click on the settings button for the module "Medium bei Anrufen anhalten" (with a "pause" symbol) 3. The whole KDE Connect window crashes This happens both when I am calling someone right now or not. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect-Einstellungen (kdeconnect-settings), signal: Segmentation fault [KCrash Handler] #4 0x7f313e463fbd in KSycocaEntry::property(QString const&) const () from /lib/x86_64-linux-gnu/libKF5Service.so.5 #5 0x7f311ef79518 in KdeConnectPluginKcm::KdeConnectPluginKcm(QWidget*, QList const&, QString const&) () from /lib/x86_64-linux-gnu/libkdeconnectpluginkcm.so.22 #6 0x7f311ef81a4d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kcms/kdeconnect_pausemusic_config.so #7 0x7f313fd71942 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x7f313fe504d9 in KCModuleLoader::loadModule(KPluginMetaData const&, QWidget*, QList const&) () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #9 0x7f313fe5317d in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #10 0x7f313fe537a8 in KCModuleProxy::realModule() const () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #11 0x7f313fe667cd in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #12 0x7f313fe66f8f in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #13 0x7f313ed02783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f313f8b2116 in QAbstractButton::clicked(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f313f8b239e in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f313f8b3fc4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f313f8b41e7 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f313f7ff4ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f313f7bc713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f313f7c4364 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f313eccae2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f313f7c2e47 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f313f818d40 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f313f81bfd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f313f7bc713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f313eccae2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f313f0b3307 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #28 0x7f313f088a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #29 0x7f3138e31d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #30 0x7f313cc6ad1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f313ccbf6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f313cc683c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f313ed240a8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f313ecc974b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f313ecd1ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x55c993117ab7 in ?? () #37 0x7f313e5e6d90 in __libc_start_call_main (main=main@entry=0x55c9931175f0, argc=argc@entry=1, argv=argv@entry=0x7ffee62689e8) at
[kdeplasma-addons] [Bug 383067] wayland: application dashboard appears on wrong screen
https://bugs.kde.org/show_bug.cgi?id=383067 --- Comment #10 from Philipp A. --- I think the current model is designed for laptops: Plugging in an external monitor there means I now use that one as primary screen until I unplug it. On my desktop however, my monitors always have the same role and physical position. My main monitor should keep the panels it has and plugging in my projector only means that I want to watch movies there and play games there, not that I want all my windows and panels to move there. I therefore want back the “there is no primary monitor” mode. Applications launch on the window where the mouse is, all panels and windows always stay where they are (until something’s unplugged, then they’re shunted somewhere accessible). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 383067] wayland: application dashboard appears on wrong screen
https://bugs.kde.org/show_bug.cgi?id=383067 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 452767] New: Visual bell notification does not have all variables interpolated
https://bugs.kde.org/show_bug.cgi?id=452767 Bug ID: 452767 Summary: Visual bell notification does not have all variables interpolated Product: konsole Version: 21.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: philipp.k...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Change Remote tab title format to sth like "%H : %w" 2. Log in to a remote machine and provoke a bell (might also work with local bells though, haven't tried that). OBSERVED RESULT Notification saying "Bell in 'mymachine : %w' (Session 'Profile 1')" So it looks like the placerholder / variable / parameter %w does not get replaced / interpolated correctly. EXPECTED RESULT Notification saying "Bell in 'mymachine : the_actual_command' (Session 'Profile 1')" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Some Debian-based thing. KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 431484] BTRFS snapshots
https://bugs.kde.org/show_bug.cgi?id=431484 --- Comment #5 from Philipp --- the tool is called snapper, it makes use of BTRFS' copy on write capabilities. It keeps snapshots as subfolders in the /.snapshot folder. Changed files are stored there, all other files are referenced as hardlinks in each snapshot. I think that counting all hardlinks as regular sized files makes filelight unusable. The displayed size of all files is way bigger than my hard drive for example. Of course this is not an easy situation because it's hard to say where the hardlinked file should be counted. Not counting it at all doesn't make sense either. That's why i suggested to ignore the /.snapshot folder, because it's the one folder where regular users get lots of hardlinks. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 437062] Glitch on hover over context menu of a window decoration on Wayland when using menu blur effect
https://bugs.kde.org/show_bug.cgi?id=437062 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452308] Thumbnails of wallpapers in "Configure Desktop and Wallpaper" change aspect ratio as window gets moved
https://bugs.kde.org/show_bug.cgi?id=452308 Philipp Verpoort changed: What|Removed |Added Summary|Desktop layout in wallpaper |Thumbnails of wallpapers in |config changes as window is |"Configure Desktop and |moved |Wallpaper" change aspect ||ratio as window gets moved -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452308] Desktop layout in wallpaper config changes as window is moved
https://bugs.kde.org/show_bug.cgi?id=452308 --- Comment #1 from Philipp Verpoort --- Created attachment 147989 --> https://bugs.kde.org/attachment.cgi?id=147989=edit Screenshot #2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452308] New: Desktop layout in wallpaper config changes as window is moved
https://bugs.kde.org/show_bug.cgi?id=452308 Bug ID: 452308 Summary: Desktop layout in wallpaper config changes as window is moved Product: plasmashell Version: 5.24.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: philipp.verpo...@secure.mailbox.org CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 147988 --> https://bugs.kde.org/attachment.cgi?id=147988=edit Screenshot #1 Apologies in advance in case I filed this bug in the wrong place, in which case I appreciate your help in correcting this. SUMMARY In KDE Plasma, the wallpaper of a screen can be modified by right-clicking on the empty desktop, selecting "Configure Desktop and Wallpaper" from the context menu, and then choosing a new wallpaper to use as a background image for that particular screen. Apparently, a new feature (as of 5.24.4?) seems to be that the layout of the thumbnails of all available wallpaper images is now determined by the size of the respective screen. The size of the screen is however not determined by the properties of the screen whose wallpaper is being edited but rather by the properties of the screen that the "Configure Desktop and Wallpaper" is placed on. This does not affect which screen gets edited though. Attached are two screenshots from the same window, where in the second screenshot, the size/layout of the thumbnails updated in that moment where the window was dragged across the border between the two screens such that the centre of the window is now on the new screen. Essentially, this bug occurs because the ratio/properties of the screen taken to display the thumbnails was not obtianed from the screen that is being edited but rather from the screen of the window. STEPS TO REPRODUCE 1. Have at least two monitors of dissimilar aspect ratios/resolutions. 2. Right-click on monitor 1. Select "Configure Desktop and Wallpaper" 3. Now drag the window over to monitor 2. OBSERVED RESULT After 2: Observe how the thumbnails have the correct aspect ratio corresponding to the screen whose wallpaper you are trying to edit (provided the window opens on monitor 1). After 3: Observe how the thumbnail aspect ratio changes to adopt the resolution of monitor 2. EXPECTED RESULT The aspect ratio of the thumbnails does not change. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 451130] Ugly buttons show up after checking for updates
https://bugs.kde.org/show_bug.cgi?id=451130 --- Comment #2 from Philipp Kiemle --- Thank you for your reply! Wouldn't this KDE Qt patch collection be part of the Backports PPA for Ubuntu though, similar to all other KDE related packages? I have the PPA enabled but still get this issue. Since this bug is only cosmetoc, I think I'll wait for Ubuntu 22.04 to come out, and if it is still present, report it. Have a nice day! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449981] Plasmashell crashes randomly in PrimaryOutputWatcher::primaryOutputNameChanged()
https://bugs.kde.org/show_bug.cgi?id=449981 --- Comment #16 from Philipp Maierhöfer --- The plasmashell crash when the screen wakes up from energy saving mode doesn't seem to happen anymore in 5.24.3. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 451130] New: Ugly buttons show up after checking for updates
https://bugs.kde.org/show_bug.cgi?id=451130 Bug ID: 451130 Summary: Ugly buttons show up after checking for updates Product: Discover Version: 5.24.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: philipp.kie...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 147275 --> https://bugs.kde.org/attachment.cgi?id=147275=edit Discover screenshot SUMMARY *** When Discover is done checking for updates, it sometimes shows weird buttons at the bottom (see attached screenshot). They seem to have the same functionality as the two buttons "Aktualisieren" and "Alle aktualisieren" in the top right of the window, as they have the same icons and their tooltips say so. I am using Kubuntu 21.10 with the Backports PPA enabled, so I should have the latest Plasma packages installed (apart from the packages you can see in the screnshot, of course ;) ) *** STEPS TO REPRODUCE 1. Wait for the Discover system tray icon to appear, informing me about pending updates 2. Click on it 3. Wait for Discover to compile the list of pending updates (which, as a sidenote, takes very long for me, is this normal? Longer than `apt update` and `flatpak update` combined, at least...) OBSERVED RESULT Now, Discover looks like in the attatched screenshot. EXPECTED RESULT Those misaligned buttons at the bottom should look nicer (or be gone completely, since their functionality is already covered by the buttons in the top right). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kbuntu 20.10, Backports PPA enabled KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel Version: 5.12.0-30-generic (64-bit) Graphics platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449981] Plasmashell crashes randomly in PrimaryOutputWatcher::primaryOutputNameChanged()
https://bugs.kde.org/show_bug.cgi?id=449981 --- Comment #12 from Philipp Maierhöfer --- The "duplicate" bug filed in https://bugs.kde.org/show_bug.cgi?id=450607 has not been fixed in Tumbleweed 20220227. I'm not saying that "WORKSFORSOME" is not correct in the sense that one possible trigger of the underlying bug may have been fixed. But I fear that setting the status to "WORKSFORSOME" reduces the priority even further. Given the fact that a core component of the DE is frequently crashing in everyday usage this might send the wrong signal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449981] Plasmashell crashes randomly in PrimaryOutputWatcher::primaryOutputNameChanged()
https://bugs.kde.org/show_bug.cgi?id=449981 --- Comment #8 from Philipp Maierhöfer --- (In reply to Nate Graham from comment #1) > So we're crashing trying to get a list of all screens? Could it be empty? Very likely in my case, where the crash always happens (i.e. really every time) when the screen (there's only one) wakes up from stand-by. Syslog shows me stuff like that: A bunch of messages from kscreen saying that the screen has been disconnected, e.g. > kscreen_backend_launcher[19076]: kscreen.xcb.helper: Connection: > "Disconnected" Several of these, 6x with screen -1 and a lot with screen 0: > plasmashell[929]: requesting unexisting screen -1 > plasmashell[929]: requesting unexisting screen 0 Then again kscreen reports about the disconnected screen and within a second notices that it has been connected again. After that plasmashell restarts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450607] New: plasmashell crashes when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=450607 Bug ID: 450607 Summary: plasmashell crashes when monitor wakes up Product: plasmashell Version: 5.24.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: maiphi.pub...@gmx.net Target Milestone: 1.0 Created attachment 146972 --> https://bugs.kde.org/attachment.cgi?id=146972=edit Backtrace SUMMARY Every time the screen wakes up from energy saving, plasmashell crashes and restarts. This happens both on Wayland and X11 (the attached backtrace is from X11). It started with Plasma 5.24.0 (and persists in 5.24.1). The PC is not suspended, just the screen (if the entire PC is suspended, not just the screen, waking up seems to work smoothly). STEPS TO REPRODUCE 1. In "System Settings -> Power Management -> Energy Saving", set "Screen Energy Saving -> Switch off after" to some finite value. 2. Wait until the screen is sent to energy saving mode, then move the mouse or press a key to wake it up. OBSERVED RESULT The panel is missing when the screen turns on and then reappears after ~1 second. Sometimes the KDE crash handler opens (most of the time it doesn't although the crash does happen). Use top or ps to see that the plasmashell process was restarted or check the syslog. EXPECTED RESULT Well, plasmashell shouldn't crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is not reproducible on all machines. But if so it happens every time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 Philipp Maierhöfer changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #11 from Philipp Maierhöfer --- This is still not fixed in 5.24.1. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 450095] New: Gwenview crashes after double right rotating and then moving to next image
https://bugs.kde.org/show_bug.cgi?id=450095 Bug ID: 450095 Summary: Gwenview crashes after double right rotating and then moving to next image Product: gwenview Version: 21.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: flying-sh...@web.de Target Milestone: --- Application: gwenview (21.12.2) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.8-zen1-1-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.24.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: See title: Gwenview crashes after double right rotating and then moving to next image The crash can be reproduced sometimes. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7f27442b56d8 in __memmove_avx_unaligned_erms () from /usr/lib/libc.so.6 #5 0x7f2744e350c3 in memcpy (__len=, __src=, __dest=, __dest=, __src=, __len=) at /usr/include/bits/string_fortified.h:29 #6 QImage::copy (this=0x5606a14b00f0, r=...) at image/qimage.cpp:1239 #7 0x7f27462dda1c in Gwenview::RasterImageItem::paint (this=0x5606a268ac90, painter=0x7ffc7e4059f0) at /usr/src/debug/gwenview-21.12.2/lib/documentview/rasterimageitem.cpp:106 #8 0x7f27457b3048 in QGraphicsScenePrivate::draw (this=this@entry=0x5606a05f9a60, item=item@entry=0x5606a268ac90, painter=painter@entry=0x7ffc7e4059f0, viewTransform=viewTransform@entry=0x0, transformPtr=, exposedRegion=exposedRegion@entry=0x5606a0ff6600, widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:4981 #9 0x7f27457b4040 in QGraphicsScenePrivate::drawSubtreeRecursive (this=this@entry=0x5606a05f9a60, item=0x5606a268ac90, painter=painter@entry=0x7ffc7e4059f0, viewTransform=viewTransform@entry=0x0, exposedRegion=exposedRegion@entry=0x5606a0ff6600, widget=widget@entry=0x5606a100cfc0, parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873 #10 0x7f27457b31ab in QGraphicsScenePrivate::draw (this=this@entry=0x5606a05f9a60, item=item@entry=0x5606a04804e0, painter=painter@entry=0x7ffc7e4059f0, viewTransform=viewTransform@entry=0x0, transformPtr=, exposedRegion=exposedRegion@entry=0x5606a0ff6600, widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:5013 #11 0x7f27457b4040 in QGraphicsScenePrivate::drawSubtreeRecursive (this=this@entry=0x5606a05f9a60, item=0x5606a04804e0, painter=painter@entry=0x7ffc7e4059f0, viewTransform=viewTransform@entry=0x0, exposedRegion=exposedRegion@entry=0x5606a0ff6600, widget=widget@entry=0x5606a100cfc0, parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873 #12 0x7f27457b31ab in QGraphicsScenePrivate::draw (this=0x5606a05f9a60, item=, painter=0x7ffc7e4059f0, viewTransform=0x0, transformPtr=, exposedRegion=0x5606a0ff6600, widget=, opacity=, effectTransform=, wasDirtyParentSceneTransform=, drawItem=) at graphicsview/qgraphicsscene.cpp:5013 #13 0x7f27457897a1 in QGraphicsItemEffectSourcePrivate::draw (this=0x5606a1368f50, painter=0x7ffc7e4059f0) at graphicsview/qgraphicsitem.cpp:11328 #14 0x7f274581a48c in QGraphicsEffectSource::draw (this=0x5606a26832c0, painter=0x7ffc7e4059f0) at effects/qgraphicseffect_p.h:90 #15 0x7f27457b3e3e in QGraphicsScenePrivate::drawSubtreeRecursive (this=0x5606a05f9a60, item=0x5606a137e360, painter=0x7ffc7e4059f0, viewTransform=, exposedRegion=0x5606a0ff6600, widget=0x5606a100cfc0, parentOpacity=, effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4867 #16 0x7f27457d77e4 in QGraphicsScenePrivate::drawItems (widget=, exposedRegion=0x5606a0ff6600, viewTransform=0x0, painter=0x7ffc7e4059f0, this=0x5606a05f9a60) at graphicsview/qgraphicsscene.cpp:4735 #17 QGraphicsView::paintEvent (this=, event=) at graphicsview/qgraphicsview.cpp:3561 #18 0x7f27454be71c in QWidget::event (this=0x5606a0ff6100, event=0x7ffc7e405db0) at kernel/qwidget.cpp:8801 #19 0x7f274556f0e3 in QFrame::event (this=0x5606a0ff6100, e=0x7ffc7e405db0) at widgets/qframe.cpp:550 #20 0x7f27447beeea in QCoreApplicationPrivate::sendThroughObjectEventFilters (event=, receiver=) at kernel/qcoreapplication.cpp:1190 #21 QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x5606a100cfc0, event=event@entry=0x7ffc7e405db0) at kernel/qcoreapplication.cpp:1179 #22 0x7f2745488195 in QApplicationPrivate::notify_helper (this=, receiver=0x5606a100cfc0, e=0x7ffc7e405db0) at kernel/qapplication.cpp:3626 #23 0x7f27447c016a in QCoreApplication::notifyInternal2 (receiver=0x5606a100cfc0,
[plasmashell] [Bug 449431] PlasmaUserFeedback crashes/freezes whole desktop
https://bugs.kde.org/show_bug.cgi?id=449431 Philipp A. changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|BACKTRACE |--- --- Comment #4 from Philipp A. --- Probably not a useful one, Arch doesn’t have debug symbols for KUserFeedback yet (The Plasma 5.24 release next week will have them) Anyway: #0 0x7f2b2c34cd22 raise (libc.so.6 + 0x3cd22) #1 0x7f2b2e652384 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7384) #2 0x7f2b2c34cda0 __restore_rt (libc.so.6 + 0x3cda0) #3 0x7f2b2e8a9278 _ZN13KUserFeedback16OpenGLInfoSource4dataEv (libKUserFeedbackCore.so.1 + 0x21278) #4 0x7f2b2e8b8ea6 n/a (libKUserFeedbackCore.so.1 + 0x30ea6) #5 0x7f2b2e8bac92 n/a (libKUserFeedbackCore.so.1 + 0x32c92) #6 0x7f2b2e8baed7 n/a (libKUserFeedbackCore.so.1 + 0x32ed7) #7 0x7f2b2c9b0d93 n/a (libQt5Core.so.5 + 0x2bcd93) #8 0x7f2b2c1dff88 n/a (libQt5Network.so.5 + 0xa2f88) #9 0x7f2b2c9a3e76 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2afe76) #10 0x7f2b2d5cb1a6 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1791a6) #11 0x7f2b2c98016a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28c16a) #12 0x7f2b2c980c69 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x28cc69) #13 0x7f2b2c9c7548 n/a (libQt5Core.so.5 + 0x2d3548) #14 0x7f2b2ad5bf13 g_main_context_dispatch (libglib-2.0.so.0 + 0x54f13) #15 0x7f2b2adb20d9 n/a (libglib-2.0.so.0 + 0xab0d9) #16 0x7f2b2ad59485 g_main_context_iteration (libglib-2.0.so.0 + 0x52485) #17 0x7f2b2c9cb44a _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d744a) #18 0x7f2b2c97844b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28444b) #19 0x7f2b2c983b97 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x28fb97) #20 0x55a7f482f51a n/a (plasmashell + 0x2051a) #21 0x7f2b2c337b25 __libc_start_main (libc.so.6 + 0x27b25) #22 0x55a7f482f8de n/a (plasmashell + 0x208de) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #9 from Philipp Maierhöfer --- Has this really been fixed? In neon-testing-20220201-1820 and neon-unstable-20220130-0332 the jumping window bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449431] PlasmaUserFeedback crashes/freezes whole desktop
https://bugs.kde.org/show_bug.cgi?id=449431 --- Comment #2 from Philipp A. --- There’s also more things to fix debugging here. (I’m on Arch Linux in a Wayland session too) 1. Dr. Konqui doesn’t come up for me at all on Arch Linux. IDK if this has to do with the newly introduced support for debugging symbols or is an attribute of this specific bug. 2. There‘s an extremely annoying interaction between KRunner, Plasma, and window focus here. I constantly lost focus trying to type in a terminal, and had to kill Plasma using the kill cursor from Ctrl+Alt+Esc before being able to do anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449431] PlasmaUserFeedback crashes/freezes whole desktop
https://bugs.kde.org/show_bug.cgi?id=449431 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Philipp A. --- Same for me -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438880] Image Sequence animation is ignored when rendering to video file
https://bugs.kde.org/show_bug.cgi?id=438880 --- Comment #5 from Tobias Philipp --- Bug ist still found in Kdenlive Version 21.12.1 No animation preview in Monitor and no animation export. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438880] Image Sequence animation is ignored when rendering to video file
https://bugs.kde.org/show_bug.cgi?id=438880 Tobias Philipp changed: What|Removed |Added CC||maill...@tobiasphilipp.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #7 from Philipp Maierhöfer --- Thanks, that was quick! The jumping mouse pointer only occurs on 5.23.5, but is fixed in 5.23.90 (to me it looked like the jumping pointer bug may have evolved into the jumping window bug, hence the historic information). Does it make sense to file a bug that has already been fixed in a newer version (if the old version is not LTS)? But if you say "just do it", I'll do it. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #5 from Philipp Maierhöfer --- Yes, on wayland the problem can't be reproduced. Only on X11. At least according to my tests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #2 from Philipp Maierhöfer --- X11. After a few more tests: the Wayland session seems not to be affected. I tested with Tumbleweed/Krypton+Wayland and the problem didn't occur. But on Neon I wasn't able to start the Wayland session at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] New: Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 Bug ID: 448961 Summary: Window jumps to differnet location when dragging it by the menu bar Product: kwin Version: 5.23.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: maiphi.pub...@gmx.net Target Milestone: --- SUMMARY For some non-KDE applications that can be dragged from the menu bar (or other window content), the window can suddenly jump to a different location when dragged. I observed this behaviour with VLC, SMPlayer and Libre Office on KDE Neon user and testing 20220118 and openSUSE Krypron from today (and a similar issue on Tumbleweed, see below). STEPS TO REPRODUCE 1. Play a video with VLC or SMPlayer (it is important to play a video, the bug may not occur otherwise). 2. Left-click and hold the menu bar (in case of SMPlayer the video region can be used as well). 3. Drag the window. OBSERVED RESULT The window suddenly jumps to a different location so that its top left corner is now under the pointer. It may also happen that the leftmost menu opens either together with the jump, or without. In openSUSE Tumbleweed (Plasma 5.23.5) the issue is a bit different: instead of the jumping window we have a jumping mouse pointer. The pointer suddenly jumps to the top left corner of the window, whereas the window itself stays where it is. EXPECTED RESULT The window should smoothly follow the mouse pointer when dragging. Neither the window nor the pointer should jump to a different location. REPRODUCIBILITY In principle the problem is always reproducible, but not always with the same applications on the same distribution, so please try all of the three mentioned above if you don't see the problem immediately. E.g. Libre Office 6 seems not to be affected on Neon in contrast to Libre Office 7 on the openSUSE systems. SOFTWARE/OS VERSIONS Linux: KDE Neon user or testing 20220118, openSUSE Krypron or Tumbleweed from 22.01.2022, KDE Plasma Version: 5.23.90 (5.23.5 in Tumbleweed) KDE Frameworks Version: 5.91.0 (5.90.0 in Tumbleweed) Qt Version: 5.15.2 ADDITIONAL INFORMATION The Problem with the jumping mouse pointer first occured mid-2021 if I remember correctly. The jumping window case only happens in the current testing version of KDE. Note that the problem doesn't show up if the window is dragged by the title bar. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 418800] Elisa does not show cover art for files with embedded album art
https://bugs.kde.org/show_bug.cgi?id=418800 Philipp A. changed: What|Removed |Added CC||flying-sh...@web.de --- Comment #23 from Philipp A. --- Huh. I had the same problem. Then I opened the files with EasyTAG, which by default deletes ID3v1 tags. I let it “fix” the files, which made Elisa no longer see the tracks at all. Then I configured EasyTag to write ID3v1 too, made it “fix” the files again, and now everything’s peachy. The only visible change is that now the track numbers don’t have leading zeros anymore. Could it be a caching issue? I also deleted a file whose name ended in -Cover.jpg because Elisa for some reason chose to display it instead of the embedded album art. So what could have happened is: 1. Elisa decides to use “Blahblah - Cover.jpg” for all files instead of the embedded covers (why?! Embedded art should be preferred, and why does “cover” somewhere in the file name trigger behavior?) 2. I delete the file. Speculation: Elisa doesn’t re-scan the files to find cover metadata, but simply doesn‘t display anything anymore (if this is true, also: why?! not finding the previous album art source should make Elisa re-discover album art) 3. I delete the ID3v1 tags. Elisa can’t extract metadata from the files anymore (why? kfilemetadata should work just fine in this case). Speculation: The cache gets invalidated, Elisa forgets the files 4. I re-add the ID3v1 tags. Speculation: Elisa re-finds the files and this time isn’t confused by image files that happen to have “cover” in their names. It finally successfully uses the embedded files. Can a dev please go over this and check the individual parts? There’s 2 bugs here if my speculations are all wrong, and 3 if one of them is correct. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442158] primary display in wayland
https://bugs.kde.org/show_bug.cgi?id=442158 --- Comment #17 from Philipp A. --- I have that on, but most games place themselves on the “primary screen”. That’s why I was happy that up until now on Wayland, all APIs for that returned the active screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442158] primary display in wayland
https://bugs.kde.org/show_bug.cgi?id=442158 --- Comment #15 from Philipp A. --- Yeah, that’s exactly what changing the “primary monitor” means for plasma currently. I want my panels to stay on the physical monitor I put them on and I only want fullscreen apps to launch on the projector. This is effortlessly provided by the previous Wayland behavior of “apps launch on the screen where the cursor is”, and impossible with the new behavior even with profiles. I therefore want an option to revert plasma’s behavior to what it did before 5.24. -- You are receiving this mail because: You are watching all bug changes.
[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.
