[systemsettings] [Bug 486895] Command Bar opens behind some KCMs
https://bugs.kde.org/show_bug.cgi?id=486895 --- Comment #4 from Tore Havn --- Created attachment 169385 --> https://bugs.kde.org/attachment.cgi?id=169385=edit Command bar opens in front of KDE Connect settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486895] Command Bar opens behind some KCMs
https://bugs.kde.org/show_bug.cgi?id=486895 --- Comment #3 from Tore Havn --- Created attachment 169384 --> https://bugs.kde.org/attachment.cgi?id=169384=edit Command bar opens up behind Sound settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486895] Command Bar opens behind some KCMs
https://bugs.kde.org/show_bug.cgi?id=486895 --- Comment #2 from Tore Havn --- Created attachment 169383 --> https://bugs.kde.org/attachment.cgi?id=169383=edit Command bar opens in front of Keyboard settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486895] Command Bar opens behind some KCMs
https://bugs.kde.org/show_bug.cgi?id=486895 --- Comment #1 from Tore Havn --- Created attachment 169382 --> https://bugs.kde.org/attachment.cgi?id=169382=edit Command bar opens up behind Mouse & Touchpad settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486895] Command Bar opens behind some KCMs
https://bugs.kde.org/show_bug.cgi?id=486895 Tore Havn changed: What|Removed |Added Summary|Command Bar opens behind|Command Bar opens behind |KCMs|some KCMs -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486895] New: Command Bar opens behind KCMs
https://bugs.kde.org/show_bug.cgi?id=486895 Bug ID: 486895 Summary: Command Bar opens behind KCMs Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: v...@veqz.net Target Milestone: --- Created attachment 169381 --> https://bugs.kde.org/attachment.cgi?id=169381=edit Command bar opens up behind Quick Settings The command bar in System Settings opens up behind _some of_ the KCMs. See attachments. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486736] New: Show Plasma Widgets in general search results
https://bugs.kde.org/show_bug.cgi?id=486736 Bug ID: 486736 Summary: Show Plasma Widgets in general search results Classification: Applications Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: v...@veqz.net CC: aleix...@kde.org Target Milestone: --- It's currently not possible to search for widgets without first going to the «Plasma Widgets» page, which is rather unfortunate as many users – me included – don't know that and end up not finding a widget we're looking to install. I strongly suggest that we instead mark the different types of things with an emblem or something to show what it is, and include obvious filters in the search result (which can default to applications as I understand that's the most popular use case). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477957] Application launcher shouldn't try to center on its button when the panel acts like a dock
https://bugs.kde.org/show_bug.cgi?id=477957 Tore Havn changed: What|Removed |Added CC||v...@veqz.net --- Comment #5 from Tore Havn --- I can also confirm that this is a problem. Would prefer it to be left aligned with the launch button. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 481454] New: Audio device selection in hamburger menu on application titlebar
https://bugs.kde.org/show_bug.cgi?id=481454 Bug ID: 481454 Summary: Audio device selection in hamburger menu on application titlebar Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: v...@veqz.net CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Users can select different audio devices for different applications, so, for instance, it is possible to listen to music on the computer speakers while playing a game or having a conversation on the headset. However, this functionality is not very discoverable or accessible. At best the user has to go to the Volume controller in the Systray, go to Applications, and use the hamburger menu next to the application to select an audio device. I propose that it should be possible to find this hamburger menu (with a different icon) on the application title bars so users can quickly discover and switch between audio devices. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 477507] Places Icon for Snap folder
https://bugs.kde.org/show_bug.cgi?id=477507 --- Comment #3 from Tore Havn --- Ah, thanks. That's a useful little thing to know. :) Still think the folder should have its own special icon, though. It is a special type of folder, after all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471265] Window rule to zoom/scale a window
https://bugs.kde.org/show_bug.cgi?id=471265 --- Comment #5 from Tore Havn --- Sorry for the late reply. Unfortunately I could still ~~reproduce~~ not avoid the problem after the redesign. Now I've gotten a new computer and am just using a single screen, so the problem doesn't bother me anymore. I'm still thinking it could be a good feature though, so I hope we can keep it open until someone has time to deal with it – or I get enough time to do it myself. :) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 477507] Places Icon for Snap folder
https://bugs.kde.org/show_bug.cgi?id=477507 --- Comment #1 from Tore Havn --- I should add that ideally I'd prefer the folder to be hidden, or at least more out of the way. C'est la vie... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 477507] New: Places Icon for Snap folder
https://bugs.kde.org/show_bug.cgi?id=477507 Bug ID: 477507 Summary: Places Icon for Snap folder Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: v...@veqz.net CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 163470 --> https://bugs.kde.org/attachment.cgi?id=163470=edit Snap logo as snap folder icon When using snap packages the user gets a «snap» folder in their Home directory. This looks like any other folder, but I think it would be useful if it was visually distinct, since it is where Snap applications are located. Have attached an example of how I've customised it on my machine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471265] Window rule to zoom/scale a window
https://bugs.kde.org/show_bug.cgi?id=471265 --- Comment #3 from Tore Havn --- Created attachment 159832 --> https://bugs.kde.org/attachment.cgi?id=159832=edit Screenshot showing tiny Stream client on 4K screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471265] Window rule to zoom/scale a window
https://bugs.kde.org/show_bug.cgi?id=471265 Tore Havn changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #2 from Tore Havn --- Reopening as I didn't explain the problem correctly. This is on a 43" 4K monitor, so a 100% scaling works perfectly well for everything else. It is only the Steam client that is too small – but this is a noted problem for many other users of the Steam client regardless of the screen setup. I've also attached a screenshot to illustrate. Everything on the screen is legible (if the monitor was smaller, I would have to increase the global scaling) except for the Steam client, where the text is barely decipherable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471265] New: Window rule to zoom/scale a window
https://bugs.kde.org/show_bug.cgi?id=471265 Bug ID: 471265 Summary: Window rule to zoom/scale a window Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net CC: isma...@gmail.com Target Milestone: --- Basically just what the title says. This occurred to me when trying to use the Steam Client on a 4K screen with no scaling. The app has no way of zooming, and it is extremely tiny! The simplest solution would be to just apply the magnifying effect, but just on the window contents. Though admittedly, the quality of the look of the Steam Client is pretty bad since it's already been drawn ridiculously tiny. Would it perhaps be possible to make the Steam Client draw to what it believes is a smaller resolution? And, of course, being able to zoom/scale a window the other way would also be good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Tore Havn changed: What|Removed |Added CC||v...@veqz.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438008] Option to transform minimized windows into thumbnails of in place of icons when using the "Do not group" setting
https://bugs.kde.org/show_bug.cgi?id=438008 Tore Havn changed: What|Removed |Added CC||v...@veqz.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461732] Updates broke system with incompatible Qt libraries
https://bugs.kde.org/show_bug.cgi?id=461732 --- Comment #2 from Tore Havn --- Nah, don't feel bad. It was an annoying hour or so, but it did work out. I mostly just filed the bug in case it could help with pointing out some unrecognized problem. I know it can be rather hard to do anything about. The contents of /var/log/apt/: eipp.log.xz history.log history.log.1.gz term.log term.log.1.gz If these could be of any interest just let me know and I can upload them. Otherwise, don't worry about it. :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461732] New: Updates broke system with incompatible Qt libraries
https://bugs.kde.org/show_bug.cgi?id=461732 Bug ID: 461732 Summary: Updates broke system with incompatible Qt libraries Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: v...@veqz.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Unfortunately I am not quite sure how it went down, but I have tried to somehow list the steps. STEPS TO REPRODUCE 1. Run updates in Discover as normal, but do not reboot after updates are installed. 2. Keep using the system as normal, install new packages, use applications, maybe do more updates – this step is hazy, at best. 3. Finally, install Kolourpaint and notice that the application refuses to launch! 4. Notice that no applications will launch! Running applications still works without issue. 5. Reboot. OBSERVED RESULT 1. System boots up to a blank screen, with just the mouse point present and working. 2. Logging into terminal and checking journalctl shows mostly normal messages, but also: sddm-greeter[1595]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" sddm-greeter[1595]: Reading from "/usr/share/xsessions/plasma.desktop" dbus-daemon[1597]: [session uid=117 pid=1597] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' systemd[1587]: Started sandboxed app permission store. sddm-greeter[1595]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf" dbus-daemon[1597]: [session uid=117 pid=1597] Successfully activated service 'org.freedesktop.portal.Documents' systemd[1587]: Started flatpak document portal service. sddm-greeter[1595]: Connected to the daemon. sddm[1558]: Message received from greeter: Connect sddm-greeter[1595]: Cannot mix incompatible Qt library (5.15.6) with this library (5.15.7) dbus-daemon[1597]: [session uid=117 pid=1597] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.2' (uid=117 pid=1599 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") systemd[1587]: Starting Portal service (GTK/GNOME implementation)... sddm-helper[1585]: [PAM] Closing session xdg-desktop-por[1618]: cannot open display: sddm-helper[1585]: pam_unix(sddm-greeter:session): session closed for user sddm systemd[1587]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE systemd[1587]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. systemd[1587]: Failed to start Portal service (GTK/GNOME implementation). sddm-helper[1585]: [PAM] Ended. sddm[1558]: Auth: sddm-helper exited with 6 systemd[1]: session-7.scope: Deactivated successfully. sddm[1558]: Greeter stopped. The Wifi also did not work. Eventually I connected with an ethernet cable, ran `pkcon update` got a long list of packages to update, rebooted, and finally got back into SDDM and Plasma. EXPECTED RESULT System should have kept working as normal. SOFTWARE/OS VERSIONS These are the current versions after the latest updates. The earlier versions when it failed was between one or two weeks old. Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9370 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460250] New: Search results should include settings for active widgets
https://bugs.kde.org/show_bug.cgi?id=460250 Bug ID: 460250 Summary: Search results should include settings for active widgets Classification: Plasma Product: krunner Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: v...@veqz.net CC: alexander.loh...@gmx.de Target Milestone: --- When searching (through krunner or any other location) the results of the search should also return settings for any active widgets. For instance, searching for "battery" while having the Battery and Brightness widget in the Systray, does not return an option for the settings page of the widget, so users may not discover that it is possible to enable battery percentage on the widget - especially since it does return "Energy Saving" and "Advanced Power Settings", where this option is not available. Might need to somehow account for multiple active instances of a widget though... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 430815] New: Custom shortcuts do not handle file paths with spaces
https://bugs.kde.org/show_bug.cgi?id=430815 Bug ID: 430815 Summary: Custom shortcuts do not handle file paths with spaces Product: frameworks-kglobalaccel Version: 5.77.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: v...@veqz.net Target Milestone: --- The CommandURL actions for custom shortcuts do not handle file paths with spaces. The file chooser works well and a script with spaces in the filename can be stored for the shortcut. Unfortunately, the path is not stored in a way that can handle spaces in the file path. The following are excerpts from the ~/.config/khotkeysrc: This works: [Data_4Actions0] CommandURL=/home/username/this_is_a_script Type=COMMAND_URL This does not work: [Data_4Actions0] CommandURL=/home/username/this is a script Type=COMMAND_URL -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426294] New: Desktop background is desaturated on startup under Wayland
https://bugs.kde.org/show_bug.cgi?id=426294 Bug ID: 426294 Summary: Desktop background is desaturated on startup under Wayland Product: kwin Version: 5.19.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start and log in on Wayland. OBSERVED RESULT Desktop background is or immediately gets desaturated, showing a black-and-white background. EXPECTED RESULT Desktop background should not be desaturated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon Stable KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION >From what I understand this is caused by a Kwin feature to desaturate unresponsive windows. Seems it's extra aggressive towards the desktop background in the beginning. As soon as one interacts with the desktop (right click on it), it returns to normal. -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 414971] ksystemlog cannot start from the menu
https://bugs.kde.org/show_bug.cgi?id=414971 Tore Havn changed: What|Removed |Added CC||v...@veqz.net --- Comment #4 from Tore Havn --- I can confirm this issue. Still happens on neon with Plasma 5.19.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 Tore Havn changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #10 from Tore Havn --- Seems that things work after I cleared the cache. There's still differences in scaling (especially with Latte dock), but it seems that this problem itself is not real. Setting status to Resolved Fixed to make it clear that this is properly resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 401740] Kate Scheme names are untranslatable
https://bugs.kde.org/show_bug.cgi?id=401740 Tore Havn changed: What|Removed |Added CC||v...@veqz.net --- Comment #2 from Tore Havn --- But is this something we really want to translate? These are all proper nouns, are they not? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405895] symbol viewer
https://bugs.kde.org/show_bug.cgi?id=405895 --- Comment #7 from Tore Havn --- (In reply to Lothar from comment #4) > If anyone likes, give this a chance > https://github.com/loh-tar/KatePlugin-IndexView Thanks. I'll look more on this when I'm a bit more experienced, and see if it's something I can include. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405895] symbol viewer
https://bugs.kde.org/show_bug.cgi?id=405895 Tore Havn changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||kate/commit/c68a443e73c7db5 ||bde7de1e20fcff3513a1ed3ba Resolution|--- |FIXED --- Comment #5 from Tore Havn --- Git commit c68a443e73c7db5bde7de1e20fcff3513a1ed3ba by Tore Melangen Havn. Committed on 12/09/2019 at 16:25. Pushed by torehavn into branch 'symbolviewer-sorting'. Added a line to set default sort order for the Symbolviewer. M +2-0addons/symbolviewer/plugin_katesymbolviewer.cpp https://invent.kde.org/kde/kate/commit/c68a443e73c7db5bde7de1e20fcff3513a1ed3ba -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405895] symbol viewer
https://bugs.kde.org/show_bug.cgi?id=405895 Tore Havn changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kat |kate/commit/c68a443e73c7db5 |e/c68a443e73c7db5bde7de1e20 |bde7de1e20fcff3513a1ed3ba |fcff3513a1ed3ba --- Comment #6 from Tore Havn --- Git commit c68a443e73c7db5bde7de1e20fcff3513a1ed3ba by Tore Melangen Havn. Committed on 12/09/2019 at 16:25. Pushed by scmsync into branch 'symbolviewer-sorting'. Added a line to set default sort order for the Symbolviewer. M +2-0addons/symbolviewer/plugin_katesymbolviewer.cpp https://commits.kde.org/kate/c68a443e73c7db5bde7de1e20fcff3513a1ed3ba -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400486] Display keyboard shortcut for switching Input modes
https://bugs.kde.org/show_bug.cgi?id=400486 --- Comment #7 from Tore Havn --- Andreas Hartmann: Sorry, the bug itself was somewhat complicated for a junior job. Simply changing the menus weren't straightforward, but we just managed to fix it now. Hope you find some other worthwhile bugs to fix. :) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406732] Some digits of the clock are invisible on the screenlocker
https://bugs.kde.org/show_bug.cgi?id=406732 --- Comment #8 from Tore Havn --- I only ever saw it once, and I have no clue how to reproduce, I'm afraid. I assume it's okay, but one never knows... I'm okay with closing this one, and rather open a new one later if the problem reappears. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 408585] New: Open menus block global keyboard shortcuts like volume up/down, play/pause, etc.
https://bugs.kde.org/show_bug.cgi?id=408585 Bug ID: 408585 Summary: Open menus block global keyboard shortcuts like volume up/down, play/pause, etc. Product: frameworks-kxmlgui Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: v...@veqz.net Target Milestone: --- While a menu in an application is open, the keyboard keys to control volume, media playback, are blocked. Easily reproducible by opening the Edit or View menus in any application, and trying to use the keyboard media keys. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 408584] New: Menu entries with submenu entries do not display keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=408584
Bug ID: 408584
Summary: Menu entries with submenu entries do not display
keyboard shortcut
Product: frameworks-kxmlgui
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: v...@veqz.net
Target Milestone: ---
Created attachment 120801
--> https://bugs.kde.org/attachment.cgi?id=120801=edit
Kate showing its Input Modes menu entry, without a keyboard shortcut
I've noticed that the menu entries doesn't show their keyboard shortcuts if
they have submenu entries.
Attached is a screenshot of a menu entry in Kate that I've been looking at.
The code for this entry is found in «kateview.cpp», lines 694-698:
a = ac->addAction(QStringLiteral("switch_next_input_mode"));
a->setText(i18n("Switch to Next Input Mode"));
ac->setDefaultShortcut(a, QKeySequence(Qt::CTRL + Qt::SHIFT + Qt::Key_V));
a->setWhatsThis(i18n("Switch to the next input mode."));
connect(a, SIGNAL(triggered(bool)), SLOT(cycleInputMode()));
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 397987] Add application/vnd.apple.pkpass icon
https://bugs.kde.org/show_bug.cgi?id=397987 Tore Havn changed: What|Removed |Added CC||v...@veqz.net --- Comment #2 from Tore Havn --- Eh. Just rotate the plane icon 90 degrees clockwise, and it should be fine. :P -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 --- Comment #5 from Tore Havn --- However, after looking more on this, I suspect that the root cause here is a difference in how the display scaling works between Xorg and Wayland. I forgot to include this in the first post, but I have a 13" laptop with 4K display, so I run Plasma with 2x scaling. Looking at the last two screenshots, it should be obvious that their scale is different (which I can't explain). However, notice how it seems that the horizontal padding around the Favourite icons seems to be attempting being the same real size in the two screenshots, while the vertical padding is larger under Xorg. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 --- Comment #4 from Tore Havn --- Created attachment 120114 --> https://bugs.kde.org/attachment.cgi?id=120114=edit Kicker under Xorg, with a different theme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 --- Comment #3 from Tore Havn --- Created attachment 120113 --> https://bugs.kde.org/attachment.cgi?id=120113=edit Kicker under Wayland, with a different theme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 --- Comment #2 from Tore Havn --- I have never tried to play around much with themes, but while using Wayland I went and downloaded the «Honeycrisp KDE» (called «OSX Absurdity» when installed) theme. After applying it I took a screenshot again, logged out and logged in using Xorg, and took a new screenshot. I've uploaded the two images here. (The difference in icons could be because I also switched to regular Breeze inbetween.) While it is not uniform, it does look like in general, the Xorg versions have less padding than the Wayland versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] New: Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 Bug ID: 407569 Summary: Extra padding in Plasmashell when switching from Xorg to Wayland Product: plasmashell Version: 5.15.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: v...@veqz.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120088 --> https://bugs.kde.org/attachment.cgi?id=120088=edit Combined two screenshots of Kicker: the inserted/rightmost is in Xorg, and the leftmost is afterwards in Wayland SUMMARY Wanting to test out Wayland more, I logged out of Plasma under Xorg and logged in to Plasma under Wayland. Once there, the padding is much larger than expected. See the attachment, where I have combined two screenshots of Kicker. The inserted/rightmost is in Xorg, and the leftmost is afterwards in Wayland. STEPS TO REPRODUCE 1. Having logged in to Plasma under Xorg 2. Logging out and loggin in to Plasma under Wayland OBSERVED RESULT The padding in Plasmashell is larger than expected. EXPECTED RESULT The padding should have been similar under Wayland as under Xorg. SOFTWARE/OS VERSIONS KDE neon User Edition KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58 Qt Version: 5.12.0 ADDITIONAL INFORMATION I tried to report this earlier with https://bugs.kde.org/show_bug.cgi?id=398636, and David Edmundson found a workaround. This is still a problem however, and shouldn't happen. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405895] symbol viewer
https://bugs.kde.org/show_bug.cgi?id=405895 Tore Havn changed: What|Removed |Added CC||v...@veqz.net --- Comment #2 from Tore Havn --- I've been looking at this for a bit, and while there shouldn't be any big technical issues with this, there is a question about the design. At the moment, only the changes to the settings on the Symbol Viewer Configuration Page are saved. There is a checkbox to «Always sort symbols», but no setting for the sort direction. In the Symbol Viewer it is possible to turn on and off sorting, and to set the direction. Changing the settings here have no impact on the configured settings however, and are never stored. Should we: A) Change the configuration page to add a sort direction option? B) Change the settings behaviour for Symbol Viewer, so that the changes made in the Symbol Viewer itself are stored? -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 406965] New: Permanent clipboard items
https://bugs.kde.org/show_bug.cgi?id=406965 Bug ID: 406965 Summary: Permanent clipboard items Product: klipper Version: unspecified Platform: unspecified OS: unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: v...@veqz.net Target Milestone: --- Taken from https://old.reddit.com/r/kde/comments/bht119/permanent_clipboard_object/ Request for new feature which would allow us to have permanent items in the clipboard. This could be useful for items that are pasted often, but might end up falling out of the clipboard from time to time. Personally, I could envision a simple «Pin» action for each item, next to the other actions there. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406890] New: Digital clock on Lock screen missing digit
https://bugs.kde.org/show_bug.cgi?id=406890 Bug ID: 406890 Summary: Digital clock on Lock screen missing digit Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: v...@veqz.net CC: bhus...@gmail.com Target Milestone: --- Created attachment 119629 --> https://bugs.kde.org/attachment.cgi?id=119629=edit Mobile phone photo of lock screen at 16:37. SUMMARY After putting the computer in standby last night, I activated it today, and was greeted by a buggy lock screen. The time of the attached screenshot is 16:37, but the digit 6 is missing. Never seen this before, and the lock screen is fine again when testing now. Linux/KDE neon 5.15 User Edition KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-48-generic OpenGL Version: 3.0 Mesa 18.2.8 Running on Xorg, not Wayland. The machine is a Dell XPS 13" 2018 Developer's Edition, and has an Intel UHD 620 graphics chip. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400860] Add «Show All Entries» toggle for Places to the Panels submenu
https://bugs.kde.org/show_bug.cgi?id=400860 --- Comment #2 from Tore Havn --- Okay, this went rather fast! :) https://phabricator.kde.org/D16767 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400860] New: Add «Show All Entries» toggle for Places to the Panels submenu
https://bugs.kde.org/show_bug.cgi?id=400860 Bug ID: 400860 Summary: Add «Show All Entries» toggle for Places to the Panels submenu Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Created attachment 116186 --> https://bugs.kde.org/attachment.cgi?id=116186=edit Mockup of the suggested feature There should be an option to toggle the «Show All Entries» in the Panels submenu in Dolphin. This will make it more discoverable, and be easier to find and unhide items which were accidentally hidden. Attached an image of what I'm envisioning. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398636] Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 Tore Havn changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Tore Havn --- The padding sorted itself at some point, but I haven't figured out how yet. The missing menus where a global menu widget hidden on a disconnected screen. I recommend we close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400486] New: Display keyboard shortcut for switching Input modes
https://bugs.kde.org/show_bug.cgi?id=400486 Bug ID: 400486 Summary: Display keyboard shortcut for switching Input modes Product: kate Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- I just learned that Ctrl+Shift+V switches between Normal and Vi input modes. It would be very useful to display this keyboard shortcut in Kate's menu, just like Ctrl+Shift+B is diplayed for the «Block Selection Mode». -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398642] The menu bar is gone from Kate under Wayland
https://bugs.kde.org/show_bug.cgi?id=398642 --- Comment #2 from Tore Havn --- I should take this one back. It's not a problem with Kate, but some problem with Kwin or frameworks, I think. The menus are gone from all Qt applications, as far as I can tell. Reporting this in another bug. This one can probably be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398636] Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 --- Comment #3 from Tore Havn --- Okay, I'm gonna add another comment, cause the fix made a bit of a problem with it all: In Plasma under X11 I no longer have any menus, and where before I had extra padding, now it seems I lack padding... I have tried to clear the cache again and rebooting into X11, but it doesn't seem to fix anything. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398642] The menu bar is gone from Kate under Wayland
https://bugs.kde.org/show_bug.cgi?id=398642 --- Comment #1 from Tore Havn --- I need to add another development: It turns out the menu bar is also gone in Kate now when I'm back in X11... Also, I'm using Kate with Vi-mode, if that helps any. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398636] Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 --- Comment #2 from Tore Havn --- Yes, yes it did! I'm really surprised you figured it out so fast. :) Was this a known problem? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398642] New: The menu bar is gone from Kate under Wayland
https://bugs.kde.org/show_bug.cgi?id=398642 Bug ID: 398642 Summary: The menu bar is gone from Kate under Wayland Product: kate Version: 18.08.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Created attachment 114967 --> https://bugs.kde.org/attachment.cgi?id=114967=edit Kate without the menu bar Kate seems to be working properly, but the menu bar and thus the menu seems to be missing. I can't bring it back with Ctrl+M, and katerc says "Show Menu Bar=true". The same issue is affecting KWrite. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398636] New: Extra padding on items under Wayland
https://bugs.kde.org/show_bug.cgi?id=398636 Bug ID: 398636 Summary: Extra padding on items under Wayland Product: kwin Version: 5.13.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Created attachment 114965 --> https://bugs.kde.org/attachment.cgi?id=114965=edit Application Menu under Wayland (with 2x scaling) There's extra padding on certain items under Wayland. I've attached a picture of the Application Menu, which looks quite differently from how it does under X11. Should be noted that I run 2x scaling, if that might matter. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398634] New: Keyboard repeat setting not respected under Wayland
https://bugs.kde.org/show_bug.cgi?id=398634 Bug ID: 398634 Summary: Keyboard repeat setting not respected under Wayland Product: kwin Version: 5.13.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- Nothing much to it. I have the keyboard repeat rate set to 200ms in Plasma when running X11. Booted into Wayland now to try it out, and noticed that the keyboard repeat setting -- both delay and rate -- doesn't have any effect. No matter the values set to it, it still runs on the defaults. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 396764] KTextEditor does not accept soft-hyphen as input
https://bugs.kde.org/show_bug.cgi?id=396764 --- Comment #1 from Tore Havn --- I should of course specify that the soft-hyphen character is U+00AD. (See https://unicode-table.com/en/00AD/) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 396764] New: KTextEditor does not accept soft-hyphen as input
https://bugs.kde.org/show_bug.cgi?id=396764 Bug ID: 396764 Summary: KTextEditor does not accept soft-hyphen as input Product: frameworks-ktexteditor Version: 5.48.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- I've recently added soft-hyphen as a key on my keyboard layout, and found that Kate does not accept it as input. Hitting the key has no effect in Kate. I tried the same in LibreOffice Writer and in KWrite. LibreOffice Writer handles it as expected, and creates a zero-width character in the text, which turns to a hyphen when the word it is in encounters a line break. KWrite does not react, same as in Kate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391350] Shortcuts: Alt and Shift modifiers is not handled correctly
https://bugs.kde.org/show_bug.cgi?id=391350 --- Comment #1 from Tore Havn <v...@veqz.net> --- Added Thomas Lübking to this, as it seems from the other bug reports that he may have a better idea of what's going on. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391350] Shortcuts: Alt and Shift modifiers is not handled correctly
https://bugs.kde.org/show_bug.cgi?id=391350 Tore Havn <v...@veqz.net> changed: What|Removed |Added CC||thomas.luebk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391350] New: Shortcuts: Alt and Shift modifiers is not handled correctly
https://bugs.kde.org/show_bug.cgi?id=391350
Bug ID: 391350
Summary: Shortcuts: Alt and Shift modifiers is not handled
correctly
Product: kwin
Version: 5.12.2
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: input
Assignee: kwin-bugs-n...@kde.org
Reporter: v...@veqz.net
Target Milestone: ---
It seems the Alt+Shift modifiers do not work correctly together when using the
Tab key to walk through windows. I intiially assumed it was a hardware bug
(recently got a new laptop), but I have finally been able to get some details
of what is happening.
1.
I also have Alt+Shift set to walk through keyboard layouts. Alt+Shift+Tab is
never triggered because KWin has already triggered on Alt+Shift being pressed.
Disabling Alt+Shift to walk through keyboard layouts made Alt+Shift+Tab
function again.
The correct behaviour should be that Alt+Shift should only be triggerd when
those keys are released, and while just being pressed and held should function
as modifiers waiting for the next key to be pressed.
2.
A similar thing happens when cycling through tabs in applications.
2.1 Firefox
Ctrl+Tab will cycle through tabs, and works as it should. Ctrl+Shift+Tab
however, does not work. Holding Ctrl+Shift and hiting Tab appears to do
nothing. Continuing to hold Ctrl+Shift and hiting Tab again will bring the
focus to the address bar.
To correctly reverse cycle through tabs in Firefox, it is necessary to hold
Ctrl and hit Tab, to start the tab cycling process. By continuing to hold Ctrl
and now also holding Shift, it is possible to hit Tab to reverse cycle through
the tab list.
2.2 Kate
Holding Ctrl and hiting Tab will cycle through the open documents, as it
should. Holding Ctrl+Shift and hiting Tab, however, will start by cycling one
document forward, and then function as reverse cycling through documents.
3.
While experimenting with KWin's shortcut settings in System Settings, I noticed
a funny behaviour when trying to set a custom keyboard shortcut:
First pressing and holding Alt, and then pressing and holding Shift, will
display the shortcut as "Alt+Shift+...". A key combo like Alt+Shift+Tab can
then be set by hiting Tab.
However, by first pressing and holding Shift, and then pressing and holding
Alt, will display the shortcut as "Meta+Shift+..."! By hiting Tab it will
change to Alt+Shift+Tab again and work as before.
I don't know what is happening there, but I suspect there might be some bug in
the code which modifies Alt to appear as Meta. I'm including this here in case
it is related to the Alt+Shift bug. Utilising the Meta key in a combination
seems to make all three appear ("Meta+Alt+Shift+...").
4.
After looking through the bug tracker, I found several open, unconfirmed bugs
which I suspect are other symptoms of this bug:
- Alt + Shfit + shortcut bug (2018)
https://bugs.kde.org/show_bug.cgi?id=391056
* kwin takes control over shortcut input and does not allow for "unshifting"
(2016) https://bugs.kde.org/show_bug.cgi?id=359206
- Keyboard layout switching ignores settings, sometimes it does not work at
all. (2016) https://bugs.kde.org/show_bug.cgi?id=370734
- Custom Alt+` shortcut brings up task switcher, but does not walk through
applications (2016) https://bugs.kde.org/show_bug.cgi?id=359141
- inconsistent behavior with alt+7 (2016)
https://bugs.kde.org/show_bug.cgi?id=365255
- Impossible to use AltGr as modifier (2016)
https://bugs.kde.org/show_bug.cgi?id=359146
- Remapping Num Lock with xmodmap breaks all Alt+* key shortcuts in KDE! O_OOO
(2015-2016) https://bugs.kde.org/show_bug.cgi?id=345816
- Shortcuts bound to F keys ignore state of ISO_Level3_Shift (2015)
https://bugs.kde.org/show_bug.cgi?id=357127
- Keyboard input shortcut keys do not work (2015)
https://bugs.kde.org/show_bug.cgi?id=348456
- Broken canvas input shortcut naming when pressing keys used to switch
keyboard layouts (2014-2017, Confirmed)
https://bugs.kde.org/show_bug.cgi?id=333431
- when connecting to a remote host, some modifier key (shift, or alt) is
permanently pressed (2014-2016) https://bugs.kde.org/show_bug.cgi?id=329951
- Ambigous shortcut detected with pressing Ctrl+Shift+w (2013-2017, Confirmed)
https://bugs.kde.org/show_bug.cgi?id=319172
- Keyboard shortcuts doesn't work if non-english keyboard layout is set before
english one (2012-2018, Confirmed) https://bugs.kde.org/show_bug.cgi?id=309193
- custom shortcuts: send keyboard input does not work for keys requiring AltGr
(2012-2018) https://bugs.kde.org/show_bug.cgi?id=295633
- Walk Through Windows (Reverse) does not work (2012-2017, Kde4+5)
https://bugs.kde.org/show_bug.cgi?id=294249
- Unsupported Key message when adding a custom Alt+Shift+ shortcut
(2012-2013) https://bugs.kde.org/show_bug.cgi?id=294245
- Alt-Tab menu cannot use Alt-Shift-Tab for going back through
[systemsettings] [Bug 389617] Main window too narrow by default
https://bugs.kde.org/show_bug.cgi?id=389617 Tore Havn <v...@veqz.net> changed: What|Removed |Added CC||v...@veqz.net --- Comment #1 from Tore Havn <v...@veqz.net> --- Isn't the KCM supposed to be designed for (and should thus open as) 1024 px x 768 px anyway? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385836] Scrolling in sidebar ignores "Mouse wheel scroll speed" - Always scrolls 3 lines
https://bugs.kde.org/show_bug.cgi?id=385836 Tore Havn <v...@veqz.net> changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385836] New: Scrolling in sidebar ignores "Mouse wheel scroll speed" - Always scrolls 3 lines
https://bugs.kde.org/show_bug.cgi?id=385836 Bug ID: 385836 Summary: Scrolling in sidebar ignores "Mouse wheel scroll speed" - Always scrolls 3 lines Product: systemsettings Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: v...@veqz.net Target Milestone: --- When scrolling in the sidebar it seems that it will scroll three entires at a time, regardless of what the "Mouse wheel scroll speed" is set to. I've tried making it both less and more than 3, but no difference. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 355456] Duplicate items show up when adding Google calendar as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=355456 --- Comment #2 from Tore Havn <v...@veqz.net> --- I've dropped Google in favour of Kolab, so I can't test this anymore. However, I do not have this problem with my curreny setup, with version 5.5.3 on KDE neon User Edition, and a synced Kolab resource. :-) -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 381066] Konversation crashes with a segmentation fault
https://bugs.kde.org/show_bug.cgi?id=381066 Tore Havn <v...@veqz.net> changed: What|Removed |Added CC||v...@veqz.net --- Comment #1 from Tore Havn <v...@veqz.net> --- Same problem happens for me. Application: Konversation 1.7.2 Qt version: 5.7.1 Frameworks version: 5.35.0 Kernel version: 4.4.0-79-generic x86_64 Distribution: KDE neon 5.10 Description: This has actually been happening for a few months, but I had mostly decided to blame my filesystem (btrfs), which was experiencing problems in general. Those have been fixed, and the problem persists. I have configured it to automatically connect to multiple servers and channels at startup (5 servers and ~20 channels). I usually leave my computer on during the night, and every morning Konversation has segfaulted. Restarting it would only help for about an hour or so before segfaulting again. I recently emptied all my old irc logs and this seems to have made Konversation last a few hours more, but this morning it had once again segfaulted. The program is usually segfaults while it is minimized or I'm sleeping, so no user action is taken to make it happen. There's no pattern in usage before it segfaults, as far as I can tell. -- Backtrace (drkonqi): -- Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6856bff8c0 (LWP 4719))] Thread 4 (Thread 0x7f6850cca700 (LWP 4723)): #0 0x7f685d197a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f685d152929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f685d1532bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f685d15349c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6862a8675b in QEventDispatcherGlib::processEvents (this=0x7f68480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f6862a310ba in QEventLoop::exec (this=this@entry=0x7f6850cc9d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f6862860f64 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f6862865b48 in QThreadPrivate::start (arg=0x2c52f20) at thread/qthread_unix.cpp:368 #8 0x7f68607a46ba in start_thread (arg=0x7f6850cca700) at pthread_create.c:333 #9 0x7f6861e6982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f68520e2700 (LWP 4722)): #0 0x7f6861e5db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f685d15338c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f685d15349c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6862a8675b in QEventDispatcherGlib::processEvents (this=0x7f68440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6862a310ba in QEventLoop::exec (this=this@entry=0x7f68520e1cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f6862860f64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f6862c94735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f6862865b48 in QThreadPrivate::start (arg=0x7f6862d08d60) at thread/qthread_unix.cpp:368 #8 0x7f68607a46ba in start_thread (arg=0x7f68520e2700) at pthread_create.c:333 #9 0x7f6861e6982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f68542a5700 (LWP 4721)): #0 0x7f6861e5db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f685f22fc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f685f2318d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f68567fdd79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f6862865b48 in QThreadPrivate::start (arg=0x2be13e0) at thread/qthread_unix.cpp:368 #5 0x7f68607a46ba in start_thread (arg=0x7f68542a5700) at pthread_create.c:333 #6 0x7f6861e6982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6856bff8c0 (LWP 4719)): [KCrash Handler] #6 0x7f68628ec19f in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:99 #9 QtPrivate::RefCount::ref (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::operator= (this=this@entry=0x7ffd70b1a270, other=...) at tools/qstring.cpp:1814 #11 0x005124af in InputFilter::parseClientCommand (this=this@entry=0x3124810, prefix=..., command=..., parameterList=..., messageTags=...) at /workspace/build/s
[Breeze] [Bug 376312] New: Confusing Akregator and Wifi icons in systray
https://bugs.kde.org/show_bug.cgi?id=376312 Bug ID: 376312 Summary: Confusing Akregator and Wifi icons in systray Product: Breeze Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: v...@veqz.net CC: kain...@gmail.com Target Milestone: --- This isn't a big thing, but I've noticed that I constantly click on the Akregator icon when I intend to click on the Wifi icon in the systray. Perhaps one of them should be modified a bit so they are less interchangable? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 369008] Kate crashes when doing lookoup
https://bugs.kde.org/show_bug.cgi?id=369008 Tore Havn <tore.h...@gmail.com> changed: What|Removed |Added CC||tore.h...@gmail.com --- Comment #1 from Tore Havn <tore.h...@gmail.com> --- I am noticing the same behaviour. Trying to do Lookup segfaults Kate. I'm on Frameworks 5.27. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 371675] New: The import functionality for new syntax highlighting files disqualifies all files
https://bugs.kde.org/show_bug.cgi?id=371675 Bug ID: 371675 Summary: The import functionality for new syntax highlighting files disqualifies all files Product: kate Version: 16.04 Platform: Neon Packages URL: https://forum.kde.org/viewtopic.php?f=225=136892 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: tore.h...@gmail.com When trying to import a new xml file (or as .kateklcolor) into Kate, the program just throws up a "File is not a single highlighting color file" message. I have validated the file I'm trying to upload, and it seems to be correct. I have also tried just using an xml from ~/.local/share/katepart5/syntax/ and both incremented the version number of changing the "name" attribute, but the same error is thrown in all cases. The url is to a post in the KDE forums where I asked for help and showed the files I was trying to import. Reproducible: Always Steps to Reproduce: 1. Start Kate and go to Settings -> Configure Kate... -> Fonts & Colors -> Highlighting Text Styles. 2. Click 'Import...' and select a valid xml or katehlcolor file. Actual Results: A message box appears stating "File is not a single highlighting color file". Expected Results: A new or updated version of a highlighting style should become available in Kate. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 353567] KAddress Book custom fields don't work properly (url data type)
https://bugs.kde.org/show_bug.cgi?id=353567 Tore Havn <tore.h...@gmail.com> changed: What|Removed |Added CC||tore.h...@gmail.com --- Comment #2 from Tore Havn <tore.h...@gmail.com> --- I have the same (similar?) problem, I think. I'm running KAddressbook v5.1.3 on Kubuntu 16.04. My use case has been to try and make a global custom date field. However, I am constantly running into lots of little bugs surrounding custom fields. Reproducible: Always Steps to reproduce: 1. Create a new user, give it a name and create a new Custom Field, setting the Type to Date and not checking the 'use for all contacts'. This seems to work, and I input a date and close the contact view. 2. Edit the contact and add one more date field. Still seems to work fine. 3. Make a new contact and give it a name. Everything is still fine with the first user. 4. Edit the first contact and make a Custom Field of type Date and check 'use for all contacts', put in a date and save the contact. In the view pane something looks strange with the new date field (it is formated differently than the first two). Go back to the contact and the Custom Fields tab. Select the third custom field and click Edit. In the Edit Custom Field box, the Title has now been set to the Title of the first custom field, and the Type to Text. 5. Make a new contact, give it a name and save it. When checking the first contact now, both the first and third custom fields have their Title's set to the Custom Fields' ID, and their Types have been set to Text. The 'use for all contacts' field has also been unchecked for both. 6. Furthermore, and Custom Field for all contacts has its Type set to Text when trying to edit it from another contact. Finally, I've tried to export my contacts and putting them all in one file. When looking at the vcf-file, I can see the Custom Fields, but all the values are formated as if they are Text fields, and there is no information about the Type of the fields. -- You are receiving this mail because: You are watching all bug changes.
