[angelfish] [Bug 478783] Stop depending on QuickWebEngineDownloadRequest private header
https://bugs.kde.org/show_bug.cgi?id=478783 --- Comment #1 from Soren Stoutner --- I submitted an upstream bug report requesting that Qt make the needed parts of the API public. https://bugreports.qt.io/browse/QTBUG-120370 -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 478783] New: Stop depending on QuickWebEngineDownloadRequest private header
https://bugs.kde.org/show_bug.cgi?id=478783 Bug ID: 478783 Summary: Stop depending on QuickWebEngineDownloadRequest private header Classification: Applications Product: angelfish Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: so...@stoutner.com Target Milestone: --- Angelfish currently depends on a private header for QuickWebEngineDownloadRequest. This complicates efforts to maintain proper Qt WebEngine security support in Debian. See the following two Debian bugs for context: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059164 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057755 Qt 6 has a public version of this API: https://doc.qt.io/qt-6/qml-qtwebengine-webenginedownloadrequest.html But for some reason, Anglefish uses the private header instead of the public one, even though I can't see anything Anglefish is doing that can't be done with the public API. From https://invent.kde.org/network/angelfish/-/blob/master/lib/angelfishwebprofile.cpp?ref_type=heads #include If Anglefish does somehow need some functionality that is not included in the public API, the best course of action would probably be to request that Qt publicly expose that functionality. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 477443] Plain text emails truncated at 60 lines if HTML section is included
https://bugs.kde.org/show_bug.cgi?id=477443 --- Comment #1 from Soren Stoutner --- Created attachment 163432 --> https://bugs.kde.org/attachment.cgi?id=163432=edit Example email with truncated lines Attached is the source of an example email after it is sent. Perhaps it would be more accurate to say that it truncates before line 60. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 477443] Plain text emails truncated at 60 lines if HTML section is included
https://bugs.kde.org/show_bug.cgi?id=477443 Soren Stoutner changed: What|Removed |Added Summary|Plain text emails truncated |Plain text emails truncated |at 60 lines |at 60 lines if HTML section ||is included -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 477443] New: Plain text emails truncated at 60 lines
https://bugs.kde.org/show_bug.cgi?id=477443 Bug ID: 477443 Summary: Plain text emails truncated at 60 lines Classification: Applications Product: kmail2 Version: 5.22.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: so...@stoutner.com Target Milestone: --- When composing an email in both plain text and HTML, the plain text is truncated at 60 lines when the email is sent. The HTML contains the entire message. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 460777] Add support for OpenVPN TLS-Crypt v2 to NetworkManager
https://bugs.kde.org/show_bug.cgi?id=460777 Soren Stoutner changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Soren Stoutner --- This has been fixed in 5.27.5 (or perhaps earlier). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 470848] Add a view_redisplay_merge MergeLocal entry to ui_standards.rc
https://bugs.kde.org/show_bug.cgi?id=470848 --- Comment #1 from Soren Stoutner --- https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/169 addresses this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 470848] New: Add a view_redisplay_merge MergeLocal entry to ui_standards.rc
https://bugs.kde.org/show_bug.cgi?id=470848 Bug ID: 470848 Summary: Add a view_redisplay_merge MergeLocal entry to ui_standards.rc Classification: Frameworks and Libraries Product: frameworks-kxmlgui Version: 5.106.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: so...@stoutner.com Target Milestone: --- Would you consider adding immediately after in ui_standards.rc? The resulting block would look as follows. View I am building a browser based on KDE Frameworks and need to add a menu entry that reloads the page while bypassing the cache. I would prefer to have this entry immediately below "view_redisplay" without having a separator in between. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 451869] KAboutData does not correctly indicate that later versions of the license can be used
https://bugs.kde.org/show_bug.cgi?id=451869 Soren Stoutner changed: What|Removed |Added Version|5.90.0 |5.106.0 CC||so...@stoutner.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 451895] KXmlGui ignores Action attributes set in XML
https://bugs.kde.org/show_bug.cgi?id=451895 Soren Stoutner changed: What|Removed |Added CC||so...@stoutner.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 465094] New: Falkon should search for dictionaries in `QTWEBENGINE_DICTIONARIES_PATH`
https://bugs.kde.org/show_bug.cgi?id=465094 Bug ID: 465094 Summary: Falkon should search for dictionaries in `QTWEBENGINE_DICTIONARIES_PATH` Classification: Applications Product: Falkon Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: so...@stoutner.com Target Milestone: --- This should mirror the logic in Qt WebEngine as can see seen on line 235 of https://sources.debian.org/src/qtwebengine-opensource-src/5.15.12%2Bdfsg-2/src/core/web_engine_library_info.cpp/. Debian has recently added .bdic dictionaries and populates the `QTWEBENGINE_DICTIONARIES_PATH` to point to /usr/share/hunspell-bdic. There is more information at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020387 and https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/12. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 460777] Add support for OpenVPN TLS-Crypt v2 to NetworkManager
https://bugs.kde.org/show_bug.cgi?id=460777 --- Comment #2 from Soren Stoutner --- Some additional information about TLS Crypt v2: https://openvpn.net/vpn-server-resources/tls-control-channel-security-in-openvpn-access-server/ -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 460777] Add support for OpenVPN TLS-Crypt v2 to NetworkManager
https://bugs.kde.org/show_bug.cgi?id=460777 Soren Stoutner changed: What|Removed |Added CC||kdebugzi...@perfugium.net --- Comment #1 from Soren Stoutner --- *** Bug 395596 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] Qt version of network manager GUI does not support TLS Crypt v2
https://bugs.kde.org/show_bug.cgi?id=395596 Soren Stoutner changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #16 from Soren Stoutner --- Actually, it looks like this bug report contains a mix of at least three different root causes. As such, it would make the most sense to close it and mark it as a duplicate of the one issue that is still remaining. *** This bug has been marked as a duplicate of bug 460777 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] Qt version of network manager GUI does not support TLS Crypt v2
https://bugs.kde.org/show_bug.cgi?id=395596 Soren Stoutner changed: What|Removed |Added Summary|[OpenVPN] qt version of |[OpenVPN] Qt version of |network manager gui does|network manager GUI does |not work with openvpn >=|not support TLS Crypt v2 |2.4 configuration | -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] qt version of network manager gui does not work with openvpn >= 2.4 configuration
https://bugs.kde.org/show_bug.cgi?id=395596 Soren Stoutner changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #15 from Soren Stoutner --- Then it is appropriate to mark https://bugs.kde.org/show_bug.cgi?id=416643 as fixed, but to keep this open until the GUI is also updated to handle TLS Crypt v2. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] qt version of network manager gui does not work with openvpn >= 2.4 configuration
https://bugs.kde.org/show_bug.cgi?id=395596 --- Comment #13 from Soren Stoutner --- Does this also fix the GUI so that, if a user creates an OpenVPN connection using the GUI instead of importing the settings it also works with TLS-Crypt v2? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460778] Desktop widgets rearranged on every reboot
https://bugs.kde.org/show_bug.cgi?id=460778 Soren Stoutner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|DUPLICATE |FIXED --- Comment #4 from Soren Stoutner --- This is fixed for me with the current packages in Debian testing. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 447102] Konqueror seems to auto-start every boot
https://bugs.kde.org/show_bug.cgi?id=447102 --- Comment #9 from Soren Stoutner --- Thank you for the detailed explanation. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 447102] Konqueror seems to auto-start every boot
https://bugs.kde.org/show_bug.cgi?id=447102 --- Comment #6 from Soren Stoutner --- I just did a bit of testing with the following results (testing was done with a Debian testing installation, which is currently running KDE Plasma 5.26.0 and Konqueror 21.12.3). Konqueror does not open on every login when the following is true: Preload an instance after desktop startup: false Always try to have one preloaded instance: false Preload an instance after desktop startup: true Always try to have one preloaded instance: false Preload an instance after desktop startup: true Always try to have one preloaded instance: true Konqueror opens on every login when the following is true: Preload an instance after desktop startup: false Always try to have one preloaded instance: true In addition, there must be a running Konqueor instance when the user logged off (and KDE must be set to restore the last session). However--and this is the kicker that makes this feel like a bug--Konqueror does not need to have a visible window when the user logged off for this to be triggered because closing all of Konqueror's windows does not actually close Konqueror. So, my understanding of how this has happened. 1) The defaults for Konqueror are set to `Preload an instance after desktop startup: false` and `Always try to have one preloaded instance: true`. 2) A user is curious and opens Konqueror. They then close it, but by default it continues to run in the background. 3) Konqueror then opens up every time they log in going forward. They close it every time and it pops back up on the next login. They can't figure out why this is happening. If the user manually kills the Konqueror instance before logging off it won't pop up again the next time. Or, if a user unchecks `Always try to have one preloaded instance`, they can also get rid of this behavior. Either way, it seems that this represents unintentional behavior. I would assume that the default should be for `Always try to have one preloaded instance` to be false, as that is probably what the majority of users desire. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 447102] Konqueror seems to auto-start every boot
https://bugs.kde.org/show_bug.cgi?id=447102 Soren Stoutner changed: What|Removed |Added Status|RESOLVED|REOPENED CC||so...@stoutner.com Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #3 from Soren Stoutner --- In my opinion this should not be the default. Having Konqueror preload every time KDE boots is not the desired behavior for the majority of users. It is even worse that doing so causes Konqueror to display a window on the screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 Soren Stoutner changed: What|Removed |Added CC||so...@stoutner.com --- Comment #10 from Soren Stoutner --- *** Bug 460778 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460778] Desktop widgets rearranged on every reboot
https://bugs.kde.org/show_bug.cgi?id=460778 Soren Stoutner changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE --- Comment #2 from Soren Stoutner --- I am on X11, so this does seem like a duplicate of https://bugs.kde.org/show_bug.cgi?id=458038 I apologize for not finding it when I searched before filing the bug report. *** This bug has been marked as a duplicate of bug 458038 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460778] New: Desktop widgets rearranged on every reboot
https://bugs.kde.org/show_bug.cgi?id=460778 Bug ID: 460778 Summary: Desktop widgets rearranged on every reboot Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: so...@stoutner.com CC: notm...@gmail.com Target Milestone: 1.0 I have a destkop with 7 folder views, three icons, and two panels (right and bottom). Every time I log in about half the folder views are in a slightly different location (sometimes slightly resized as well) and all of the icons have move slightly. Those that are effected are the ones that are closest to the panels on the bottom and the right. The two folder views closest to the upper left corner of the screen never move or change size. My guess is that the folder views and icons are being laid out on the screen before the panels have been displayed and then their position and size is being moved once the panels start taking up space (both of them are thicker than the KDE default so they change the available real estate to a significant degree). Some of the folder views and icons are placed fairly close to the panels, but none of them overlap, so there shouldn't be any need to move or resize them. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 460777] New: Add support for OpenVPN TLS-Crypt v2 to NetworkManager
https://bugs.kde.org/show_bug.cgi?id=460777 Bug ID: 460777 Summary: Add support for OpenVPN TLS-Crypt v2 to NetworkManager Classification: Plasma Product: plasma-nm Version: 5.26.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: so...@stoutner.com Target Milestone: --- Plasma's NetworkManager currently supports TLS-Crypt (v1) in OpenVPN but not TLS-Crypt v2. Below is a link to the patch that added support for GNOME's NetworkManager in case it is helpful: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/33/diffs?commit_id=717a1d41be0b039778b4eb85bca57f9356bb87aa -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] qt version of network manager gui does not work with openvpn >= 2.4 configuration
https://bugs.kde.org/show_bug.cgi?id=395596 Soren Stoutner changed: What|Removed |Added CC||so...@stoutner.com --- Comment #11 from Soren Stoutner --- Based on the tls-crypt error, this sound like it is the same problem described in https://bugs.kde.org/show_bug.cgi?id=416643 Basically, the tls-crypt entry is not being properly imported. But if it is imported through another mechanism or set directly then it does work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 451895] KXmlGui ignores Action attributes set in XML
https://bugs.kde.org/show_bug.cgi?id=451895 --- Comment #1 from Soren Stoutner --- As a followup piece of information, setting attributes like "icon" work correctly for Menus. So, this appears to just be a problem with Actions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 451895] New: KXmlGui ignores Action attributes set in XML
https://bugs.kde.org/show_bug.cgi?id=451895 Bug ID: 451895 Summary: KXmlGui ignores Action attributes set in XML Product: frameworks-kxmlgui Version: 5.90.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: so...@smallbusinesstech.net Target Milestone: --- KXmlGui ignores Action attributes enumerated at https://invent.kde.org/frameworks/kxmlgui/-/blob/master/src/kxmlgui.xsd beyond "name". For example, setting "text", "icon", or "group" in the ui.rc file are ignored. Creating the Action and setting the "name" in the XML file and then setting the "text", "icon", or "group" attributes programaticaly in C++ works as expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 414218] KConfigDialog wraps pages in QScrollArea; KPageDialog does not
https://bugs.kde.org/show_bug.cgi?id=414218 Soren Stoutner changed: What|Removed |Added CC||so...@smallbusinesstech.net --- Comment #1 from Soren Stoutner --- I would like to note that this behavior is particularly annoying in instances where the size of the information displayed in KConfigDialog changes programmatically in response to user interaction. A standard QDialog window will auto resize (if possible) to display the contents if screen room is available. Even if `KConfigDialog::setSizePolicy(QSizePolicy::Expanding, QSizePolicy::Expanding)` is explicitly set, the QScrollArea prevents this from functioning correctly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 451869] New: KAboutData does not correctly indicate that later versions of the license can be used
https://bugs.kde.org/show_bug.cgi?id=451869 Bug ID: 451869 Summary: KAboutData does not correctly indicate that later versions of the license can be used Product: frameworks-kcoreaddons Version: 5.90.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: mp...@kde.org Reporter: so...@smallbusinesstech.net CC: kdelibs-b...@kde.org Target Milestone: --- `KAboutData::setLicense()` has an overloaded constructor that allows specifying `KAboutLicense::OrLaterVersions`. However, specifying this does nothing, and the interface is the same as if it is not specified. For example, `setLicense(KAboutLicense::GPL_V3)` display the following text in the About dialog: "License: GNU General Public License Version 3" `setLicense(KAboutLicense::GPL_V3, KAboutLicense::OrLaterVersion)` displays the same text, where it should display something like: "License: GNU General Public License Version 3 or later version" Similarly, clicking on the license to display the full text shows the same thing for both, where the second should specify that a later version of the license may be used. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423655] cannot display all of very large SVG images
https://bugs.kde.org/show_bug.cgi?id=423655 --- Comment #3 from Soren Harward --- More details: Setting QT_AUTO_SCREEN_SCALE_FACTOR=0 shows the entire SVG, but the scaling of the image is messed up. What gwenview thinks is 100% is more like 50%. 12pt text in image is 6pt high on screen. Setting QT_AUTO_SCREEN_SCALE_FACTOR=1 results in the behavior explained above: the scaling of the image is correct (12pt looks like 12pt), but I can only scroll the middle quarter of the image. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423655] cannot display all of very large SVG images
https://bugs.kde.org/show_bug.cgi?id=423655 --- Comment #2 from Soren Harward --- possibly also relevant: I have a hidpi display: 24", 3840×2160, 185dpi -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423655] cannot display all of very large SVG images
https://bugs.kde.org/show_bug.cgi?id=423655 --- Comment #1 from Soren Harward --- Created attachment 129762 --> https://bugs.kde.org/attachment.cgi?id=129762=edit very large SVG image -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423655] New: cannot display all of very large SVG images
https://bugs.kde.org/show_bug.cgi?id=423655 Bug ID: 423655 Summary: cannot display all of very large SVG images Product: gwenview Version: 20.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: stharw...@gmail.com Target Milestone: --- SUMMARY When displaying a SVG that is much larger than screen size, Gwenview does not display all of the image. Maybe only a quarter of it? STEPS TO REPRODUCE Load a SVG that is much larger than screen resolution; I'll attach a 6000×6000 demo file. OBSERVED RESULT Gwenview displays only part of the image. Zooming in and out scales the image properly, but only a part of it is displayed. Scrolling/panning stops at the wrong place. EXPECTED RESULT Full image should be displayed, with proper zooming and panning. SOFTWARE/OS VERSIONS Linux: recent Gentoo KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I'm using LXQT as my desktop environment, with kwin_x11 as the window manager. I'm not running a full KDE/plasma environment. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383025] F12 does not open the window anymore after upgrade to Fedura26, when shotwell foto manager is open.
https://bugs.kde.org/show_bug.cgi?id=383025 --- Comment #2 from Soren <ma...@posteo.de> --- Also, it is not working when the Terminal is activated. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383214] New: F12 does not open the window anymore
https://bugs.kde.org/show_bug.cgi?id=383214 Bug ID: 383214 Summary: F12 does not open the window anymore Product: yakuake Version: 3.0.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: ma...@posteo.de Target Milestone: --- F12 stopped working after upgrade to Fedora 26. Yakuake does not open when the button is pressed. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383025] F12 does not open the window anymore after upgrade to Fedura26, when shotwell foto manager is open.
https://bugs.kde.org/show_bug.cgi?id=383025 Soren <ma...@posteo.de> changed: What|Removed |Added Summary|F12 does not open the |F12 does not open the |window anymore after|window anymore after |upgrade to Fedura26 |upgrade to Fedura26, when ||shotwell foto manager is ||open. --- Comment #1 from Soren <ma...@posteo.de> --- Noticed, that it opens when chrome is active, however when Shotwell is active the yakuake window does not open. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383025] New: F12 does not open the window anymore after upgrade to Fedura26
https://bugs.kde.org/show_bug.cgi?id=383025 Bug ID: 383025 Summary: F12 does not open the window anymore after upgrade to Fedura26 Product: yakuake Version: 3.0.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: ma...@posteo.de Target Milestone: --- Pressing F12 does not open the yakuake window anymore after upgrade to Fedora26 from Fedora 24. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 382454] amarock automatic playlist generator tagmatch does not work
https://bugs.kde.org/show_bug.cgi?id=382454 Soren Harward <stharw...@gmail.com> changed: What|Removed |Added Assignee|amarok-bugs-d...@kde.org|stharw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 382454] amarock automatic playlist generator tagmatch does not work
https://bugs.kde.org/show_bug.cgi?id=382454 Soren Harward <stharw...@gmail.com> changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |UNCONFIRMED --- Comment #5 from Soren Harward <stharw...@gmail.com> --- Cannot reproduce with either 2.8.90, or latest git (0340ec23f4df0250). Even the "classiques.xml" file from comment #0 works when imported into Amarok. If you're using 2.8.0, there was a bug I fixed in May 2015 (0b7492e709d9c8c37) that fixed a problem with zero-length playlists being returned. Upgrade and see if you still have the problem. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 382456] Amarok APG: crashes if checkpoint is unassigned in CheckpointConstraint
https://bugs.kde.org/show_bug.cgi?id=382456 Soren Harward <stharw...@gmail.com> changed: What|Removed |Added Summary|amarock APL model with |Amarok APG: crashes if |incomplete checkpoint |checkpoint is unassigned in |crashes amarok |CheckpointConstraint -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 382456] amarock APL model with incomplete checkpoint crashes amarok
https://bugs.kde.org/show_bug.cgi?id=382456 Soren Harward <stharw...@gmail.com> changed: What|Removed |Added Assignee|amarok-bugs-d...@kde.org|stharw...@gmail.com Ever confirmed|0 |1 Version|2.8.0 |2.8.90 (2.9 beta) Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 Soren Harward <stharw...@gmail.com> changed: What|Removed |Added CC||stharw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps
https://bugs.kde.org/show_bug.cgi?id=340267 --- Comment #53 from Soren Harward <stharw...@gmail.com> --- (In reply to Christoph Feck from comment #50) > Can you please test with Qt 5.6.1 ? Still getting crashes in plasmashell with qt-5.6.1 and plasma-5.6.5, though less frequently. Now it seems to happen only when the displays are turned off for an extended period of time; I'll do some more testing and see if I can figure out exactly how long "an extended period of time" actually is. krunner and kwin_x11 also crashed frequently before qt-5.6.1 and plasma-5.6.5, and haven't done so since. The xrandr command I listed in comment #41 doesn't cause plasmashell to crash anymore, but when I run it the panel moves back and forth between monitors unpredictably, even when I set one of the outputs as "--primary" in xrandr, and even when widgets are locked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps
https://bugs.kde.org/show_bug.cgi?id=340267 --- Comment #43 from Soren Harward <stharw...@gmail.com> --- (In reply to Xapient from comment #42) > could this be an intel driver issue after all? No. I'm using the amdgpu drivers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps
https://bugs.kde.org/show_bug.cgi?id=340267 Soren Harward <stharw...@gmail.com> changed: What|Removed |Added CC||stharw...@gmail.com Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #41 from Soren Harward <stharw...@gmail.com> --- Still crashing with plasmashell 5.6.3 and Qt 5.6.0. Running the following crashes plasmashell every single time: $ xrandr --output DisplayPort-2 --off --output DisplayPort-3 --off && sleep 0.2 && xrandr --output DisplayPort-2 --preferred --output DisplayPort-3 --preferred --right-of DisplayPort-2 If I bring up krunner using +, krunner immediately crashes (this didn't happen before 5.6.3), which makes restarting plasmashell is even more difficult :( Upstream seems to think the underlying Qt bug is fixed ( https://bugreports.qt.io/browse/QTBUG-42985 ), so it looks like this is something that needs to be addressed in KDE-land. -- You are receiving this mail because: You are watching all bug changes.