[okular] [Bug 482500] Installing Okular from snap breaks home directory
https://bugs.kde.org/show_bug.cgi?id=482500 --- Comment #7 from Nils --- This seems to be the cause. Has already been fixed upstream but the fix is not part of any snap build yet. https://github.com/sergio-costas/snapcraft-desktop-integration/blob/2b439f9/common/desktop-exports#L237 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482500] Installing Okular from snap breaks home directory
https://bugs.kde.org/show_bug.cgi?id=482500 Nils changed: What|Removed |Added CC||n.buech...@ubuntu.com --- Comment #6 from Nils --- Created attachment 168380 --> https://bugs.kde.org/attachment.cgi?id=168380=edit Video of the bug on a fresh Ubuntu 22.04 VM The bug only affects empty directories. The file in the Documents folder is still there after launching Okular. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 483880] Discover does not recognize plasma addons
https://bugs.kde.org/show_bug.cgi?id=483880 Nils changed: What|Removed |Added CC||nils.acrimont+kde@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399646] Brightness control adjusts the wrong backlight control (multiple GPUs)
https://bugs.kde.org/show_bug.cgi?id=399646 --- Comment #15 from Nils --- (In reply to Jakob Petsovits from comment #14) > (In reply to Nils from comment #13) > > Here is a log of some values of the sys providers concerned. The backlight > > value changes for acpi_video0 but amdgpu_bl1 is the one controlling the > > screen. > > Nils, what are the values for /sys/class/backlight/acpi_video0/type and > /sys/class/backlight/amdgpu_bl1/type on your system? If they're different, > PowerDevil currently would only pick the one(s) with the highest-ranked type. acpi_video0/type -> firmware amdgpu_bl2/type -> raw -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Nils changed: What|Removed |Added CC||nils.van-zuij...@mailo.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 468241] New: copying/moving file from SMB to USB storage fails occasionally
https://bugs.kde.org/show_bug.cgi?id=468241
Bug ID: 468241
Summary: copying/moving file from SMB to USB storage fails
occasionally
Classification: Frameworks and Libraries
Product: frameworks-kio
Version: 5.92.0
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kio-bugs-n...@kde.org
Reporter: k...@bugblatterbeast.de
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
Can't copy or move files from a SMB to an USB storage device. Issue is not
persistent but happens most of the time. Doesn't seem to make a difference
whether it's an USB stick or a smart device, but I'm mostly trying to copy to
smartphone or tablet so that's where I'm noticing it the most.
STEPS TO REPRODUCE (not always reproducible)
1. Navigate to SMB storage with dolphin ("smb://some_nas/some_folder/")
2. Select a file or folder and copy or cut it to the clipboard
3. Navigate to USB storage device ("mtp://some_device/disk/some_folder")
4. Paste file or folder from clipboard
OBSERVED RESULT
Status window: prepare copy/moving with bouncing progress bar
If you refresh dolphin during that time it shows empty directory
Error message: "Could not write file" (it seems to depend on the file size how
long it takes until the error message appears)
Dolphin needs to be refreshed and it takes very long
Mostly file is created on USB device (and then always less than 50 bytes
written)
Sometimes the connection is lost and sometimes it won't even recover until
reconnecting physically
EXPECTED RESULT
Status window: copying/moving with advancing progress bar
File copied/moved to USB device (dolphin refreshes automatically)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.04.2 LTS
(available in About System)
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
Copying the same files from SMB to local and then from local to USB always
worked for me.
Never noticed any problems copying/moving files from USB device to SMB or from
SMB to SMB.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 468148] The right click on the desktop should give same result that in dolphin and should use action .desktop file.
https://bugs.kde.org/show_bug.cgi?id=468148 --- Comment #2 from Nils Beaussé --- (In reply to Nate Graham from comment #1) > Yes, it's a good idea. But where should the code live? Dolphin and Plasma > are different products and have different release schedules. So all of the > code that's common to both of them would have to live in a library that both > can use, perhaps one of the KDE frameworks like KIO. I think it could be in a specific common lib. This is a common practice for big software to have some common files between projects. It could also be simple C++ files that are shared between project, not necessarily a compiled library. Imho, the modification is relatively simple for the menu, but can be extended to other things that are shared between the two. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468148] New: The right click on the desktop should give same result that in dolphin and should use action .desktop file.
https://bugs.kde.org/show_bug.cgi?id=468148 Bug ID: 468148 Summary: The right click on the desktop should give same result that in dolphin and should use action .desktop file. Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: nils_beau...@hotmail.com CC: notm...@gmail.com Target Milestone: 1.0 In plasma, the behaviour of the right click on the desktop is hardcoded in : https://invent.kde.org/plasma/plasma-workspace/-/tree/master/containmentactions To resemble and have certain functionalities of the dolphin counterpart coded here : https://invent.kde.org/system/dolphin/-/blob/master/src/dolphincontextmenu.cpp#L300 https://invent.kde.org/frameworks/kio/-/blob/master/src/widgets/kfileitemactions.cpp#L246 But the mimic is not perfect and lack feature. Most notably, the main feature missing is the absence of taken into account the .desktop files which describe specific action for the Dolphin menu and which are the generic way to modify this menu. For exemple, the open terminal is hardcoded (and not in the same way of Dolphin which open a terminal HERE). The functionality should be, in my opinion : - Same behaviour of the Dolphin counterpart menu in regard to the defined actions .desktop files. + the specifics of the desktop (add a panel etc.) Ideally, it could be a good idea to find a way to factorize the two part of the code in a way where all the « not desktop » part are coded in the same place as the dolphin part. Well, the two menus should be composed of a specific parts for dolphin and for the desktop and of a common part (copy, past, cancel, new, actions etc.). In addition to that point, it could be a good idea to defined a MIME type that apply specifically to the desktop in the .desktop file. Thanks for reading ;) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399646] Brightness control adjusts the wrong backlight control (multiple GPUs)
https://bugs.kde.org/show_bug.cgi?id=399646 Nils changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||nils.van-zuij...@mailo.com --- Comment #13 from Nils --- This is happening again in Plasma 5.27.1 Here are my hardware/software infos: Operating System: Manjaro Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.13-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 62.2 Gio of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Stellaris AMD Gen3 (CZN) Here is a log of some values of the sys providers concerned. The backlight value changes for acpi_video0 but amdgpu_bl1 is the one controlling the screen. $ pwd /sys/class/backlight $ ls acpi_video0 amdgpu_bl1 $ cat acpi_video0/device/enable 1 $ cat amdgpu_bl1/device/enable 1 $ cat acpi_video0/max_brightness 49 $ cat amdgpu_bl1/max_brightness 255 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462996] Windows do not stay on the virtual desktop they are on
https://bugs.kde.org/show_bug.cgi?id=462996 Nils changed: What|Removed |Added CC||nils.acrimont+kde@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376865] In-progress or half-finished animations included when capturing a screenshot without using the global keyboard shortcut or a delay
https://bugs.kde.org/show_bug.cgi?id=376865 Nils changed: What|Removed |Added CC||nils.acrimont+kde@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448460] discover 5.23.90 crashes with segfault on startup
https://bugs.kde.org/show_bug.cgi?id=448460 Nils changed: What|Removed |Added CC||nils.bittm...@googlemail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361022] Laptop goes to sleep when closing lid even with an external display connected
https://bugs.kde.org/show_bug.cgi?id=361022 Nils changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||nils.bittm...@googlemail.co ||m --- Comment #5 from Nils --- *** This bug has been marked as a duplicate of bug 438716 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Nils changed: What|Removed |Added CC||nitanovi...@gmail.com --- Comment #17 from Nils --- *** Bug 361022 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Nils changed: What|Removed |Added Version|5.22.3 |5.23.90 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Nils changed: What|Removed |Added CC||nils.bittm...@googlemail.co ||m --- Comment #16 from Nils --- Same issue here Thinkpad t460s on Fedora 35 connected via dock and HDMI the setting "Even when external monitor is connected " is disabled Operating System: Fedora 35 KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.15.16 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448945] Mouse Mark effect should allow marking shortcut configuration
https://bugs.kde.org/show_bug.cgi?id=448945 --- Comment #1 from Nils --- Created attachment 145745 --> https://bugs.kde.org/attachment.cgi?id=145745=edit Mouse Mark specific configuration, in french -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448945] New: Mouse Mark effect should allow marking shortcut configuration
https://bugs.kde.org/show_bug.cgi?id=448945 Bug ID: 448945 Summary: Mouse Mark effect should allow marking shortcut configuration Product: kwin Version: 5.23.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: nils.van-zuij...@mailo.com Target Milestone: --- SUMMARY The only configurable shortcuts for the mouse mark effect are the erasure ones, the writing shortcut should also be configurable in the same way. STEPS TO REPRODUCE 1. Activate the Mouse Mark effect in the desktop effects KCM 2. Open its specific configuration OBSERVED RESULT Color and width are configurable. Erasure shortcuts are configurable. The text "Draw with the mouse by holding Shift+Meta keys and moving the mouse." is shown, which implies that the drawing shortcut is fixed to Shift+Meta. EXPECTED RESULT Color and width are configurable. Erasure shortcuts are configurable. The drawing shortcut is configurable. SOFTWARE/OS VERSIONS Linux kernel version: 5.15.16-1-MANJARO KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Graphical platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 448185] SNCF physical ticket PDF417
https://bugs.kde.org/show_bug.cgi?id=448185 --- Comment #3 from Nils --- It would be nice to have a way to import such tickets via a photo or the barcode text read via other means. There is an article (in french) about them and other on https://zestedesavoir.com/articles/3625/anatomie-dun-titre-de-transport-du-billet-a-la-carte-a-puce/#1-le-billet-cartonne-classique They should be IATA-compatible, the norm they follow is available at https://www.era.europa.eu/sites/default/files/filesystem/tap/baseline_1.2.0_archive/era_technical_document_tap_b_6_v1.2.pdf The ZXing library implements PDF417 decoding from pictures, it could be used as an example, I don't know if libre C++ libraries exist: https://github.com/zxing/zxing -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 448185] SNCF physical ticket PDF417
https://bugs.kde.org/show_bug.cgi?id=448185 --- Comment #2 from Nils --- Created attachment 145284 --> https://bugs.kde.org/attachment.cgi?id=145284=edit tgv brest rennes TGV ticket for Brest-Rennes journey on train 8610 departing at 9h05 the 2022-01-03 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 448185] SNCF physical ticket PDF417
https://bugs.kde.org/show_bug.cgi?id=448185 --- Comment #1 from Nils --- Created attachment 145283 --> https://bugs.kde.org/attachment.cgi?id=145283=edit ter brest st-brieuc TER from Brest to St-Brieuc on 2021-12-31 for any TER on that journey -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 448185] New: SNCF physical ticket PDF417
https://bugs.kde.org/show_bug.cgi?id=448185 Bug ID: 448185 Summary: SNCF physical ticket PDF417 Product: KDE Itinerary Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: nils.van-zuij...@mailo.com Target Milestone: --- Created attachment 145282 --> https://bugs.kde.org/attachment.cgi?id=145282=edit whole ter ticket photo a physical ticket with a PDF417 barcode for a TER from St-Brieuc to Brest on 2022-01-01 for an under 26 years adult in 2nd class It is a one-way ticket for any TER on that route on that day. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 446798] New: Bug in group view names
https://bugs.kde.org/show_bug.cgi?id=446798 Bug ID: 446798 Summary: Bug in group view names Product: dolphin Version: 21.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bezardn...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 144439 --> https://bugs.kde.org/attachment.cgi?id=144439=edit weird text When enabling group view, there are some weird messages when it wants to display the month in which the file was created (see attachment) STEPS TO REPRODUCE 1. Set your system language to French (France) 2. Enable group view (as explained [here](https://userbase.kde.org/Dolphin/File_Management#View_as_Icons) but I directly made a shortcut in the toolbar) 3. Sort by creation date (newest first) 4. Have old files OBSERVED RESULT See attachment Sometimes it's written "amamamam", sometimes it's "pmpmpmpm" I guess it's just a wrong placeholder letter in some string... EXPECTED RESULT Text that makes sense SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.13.19-2-MANJARO (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405714] trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 --- Comment #6 from Nils --- (In reply to Friedrich W. H. Kossebau from comment #4) > (In reply to Nils from comment #1) > > Created attachment 143946 [details] > > Screenshot of the observed behaviour > > Hi Nils, what version of KOrganizer have you been using for that screenshot? I'm using version 5.18.3 (21.08.3), with French translations, from the Manjaro repository. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 405714] trivial appearance bug
https://bugs.kde.org/show_bug.cgi?id=405714 Nils changed: What|Removed |Added CC||nilsd...@gmail.com --- Comment #1 from Nils --- Created attachment 143946 --> https://bugs.kde.org/attachment.cgi?id=143946=edit Screenshot of the observed behaviour -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #11 from Nils Fenner --- Actually checking on the "dock" flag when cycling in "X11Client::belongsToDesktop" should work in both Plasma and LXQt (KDE independent) shouldn't it? (Does the Plasma panel set the "dock" attribute? If not, has it another attribute suitable?). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #10 from Nils Fenner --- @Vlad Setting the window modality in the demo application has no effect on both (desktop and/or normal) windows. And it makes sense! Had a look at that deprecated Qt::WA_GroupLeader flag. If you search for "groupLeader" in kwin gitlab you will find the code is disabled. Talking KWin X11Client here: In addition we have "lxqt-panel" (separate process). Noteworthy that it doesn't set "Qt::WA_X11NetWmWindowTypeDesktop" flag and instead "Qt::WA_X11NetWmWindowTypeDock". What we have: 1. pcmanfm -> the only place where the "desktop" flag is set (https://github.com/lxqt/pcmanfm-qt/blob/aa2dc974840521afcd65a2e160641c2eef99ca16/pcmanfm/desktopwindow.cpp#L89). 2. lxqt-panel -> set the "dock" flag (https://github.com/lxqt/lxqt-panel/blob/7c0478ef9c7fc8998f7a7e0c844a8921e038d04d/panel/lxqtpanel.cpp#L167) KWin filters all "clients" (regardless of the process!) and determines which "belong to the desktop". With wayland it seems to be handled well now by that "KeepAbove" + "belongsToSameApplication" magic. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044
--- Comment #9 from Nils Fenner ---
@Vlad From our IRC discussion:
All comes down to `BaseClient::bolongsToSameApplication()` (X11 client does not
query this!). By changing the code in
https://invent.kde.org/plasma/kwin/-/blob/master/src/layers.cpp#L736 it should
work:
```c++
bool X11Client::belongsToDesktop() const
{
const auto clients = group()->members();
return std::any_of(clients.constBegin(), clients.constEnd(),
[this](const AbstractClient *client) {
if (belongsToSameApplication(client, SameApplicationChecks())) {
return client->isDesktop();
}
return false;
}
);
}
```
Since my login doesn't work currently can you do that?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 Nils Fenner changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #7 from Nils Fenner --- Thanks for the feedbaack Vlad! We will discuss it and propose a fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #5 from Nils Fenner --- Actually this is rather simple to solve by enhancing the transient strategy. Would you accept a "collaboration" by LXQt on that issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #4 from Nils Fenner --- Here's a test application that cleanly reproduces that KWin behaviour: https://gitlab.com/antis81/kwindesktopwindow -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #3 from Nils Fenner --- Actually I was wrong with the assumption of the parented window. The pcmanfm-qt MainWindow is a QMainWindow and unparented! Presumingly KWin makes the false assumption here that an application can only have one top-level window (parent == nullptr)! This is independent of window attributes and definitely a KWin bug. LXQt cannot workaround that! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 --- Comment #2 from Nils Fenner --- The file manager Window has to be parented, because pcmanfm-qt runs as a single process. FYI: When pcmanfm-qt is used as a file manager, it just fires a dbus call and quits afterwards (explains why the process is short-lived). That means: When pcmanfm-qt receives the dbus call (I will send it for debugging) it creates a QMainWindow as child of the QApplication instance. Otherwise the LXQt session would create a mem-leak on quit (and likely also segfault). (LXQt can probably workaround that by using a smart-pointer instead of parenting the window.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 Nils Fenner changed: What|Removed |Added Version|unspecified |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442044] New: KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows.
https://bugs.kde.org/show_bug.cgi?id=442044 Bug ID: 442044 Summary: KWin does not respect the NET_WM_WINDOW_TYPE for sub-windows. Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: nilsfen...@web.de Target Milestone: --- When "show desktop" action is triggered (e.g. by Meta+D shortcut) pcmanfm-qt stays visible in LXQt session. STEPS TO REPRODUCE 1. Start LXQt session (implies: pcmanfm-qt --desktop) 2. Start pcmanfm-qt 3. Call "show desktop" action (e.g. Windows+D) OBSERVED RESULT pcmanfm-qt (file manager) stays visible on screen EXPECTED RESULT pcmanfm-qt (file manager) is hidden like a normal application SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.22.0 (available in About System) KDE Plasma Version: not relevant KDE Frameworks Version: not relevant Qt Version: 5.15.2 (LXQt Version: 0.17) ADDITIONAL INFORMATION When LXQt session starts the first pcmanfm-qt instance implies the flag __NET_WM_WINDOW_TYPE_DESKTOP (aka Qt::WA_X11NetWmWindowTypeDesktop). KWin correctly detects it as a desktop window and does not hide it when "show desktop" action is triggered. However pcmanfm-qt creates subsequent instances through a short-lived process resulting in a child window. KWin now takes the window flags from the parent (desktop window) and the (child) window always stays on screen. For reference see LXQt bug #1411 (https://github.com/lxqt/pcmanfm-qt/issues/1411) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441472] FTP files are considered as folders
https://bugs.kde.org/show_bug.cgi?id=441472 --- Comment #1 from Nils B. --- Created attachment 141002 --> https://bugs.kde.org/attachment.cgi?id=141002=edit missing attachment -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441472] New: FTP files are considered as folders
https://bugs.kde.org/show_bug.cgi?id=441472 Bug ID: 441472 Summary: FTP files are considered as folders Product: dolphin Version: 21.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bezardn...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When you double-click an FTP file, it does as if it was a folder, so when opening ftp:///a.txt , you get into a non-existing folder ftp:///a.txt in which you can see a.txt again, but now after a double-click it says that a.txt dosn't exist "550 Unknown error 187". When copying/pasting a.txt in a second dolphin Window (not tab) that is not ftp, let's say downloads, it creates a folder named a.txt and gives you an error message "unable to write in the file". STEPS TO REPRODUCE 1. Open an FTP connection 2. Create a file 3. Double-click on it OBSERVED RESULT see attachment EXPECTED RESULT opening a.txt with the default .txt editor (kate in my case) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux (x86_64) release 5.13.11-1-MANJARO KDE Plasma Version: 5.22.44 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439357] New: Package download size is always zero
https://bugs.kde.org/show_bug.cgi?id=439357 Bug ID: 439357 Summary: Package download size is always zero Product: Discover Version: 5.22.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: nils.acrimont+...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 139775 --> https://bugs.kde.org/attachment.cgi?id=139775=edit Package sizes are not computed SUMMARY When I launch Discover, I expect to be able to know what the size of the packages I will download, but it is not computed, instead it's always zero. STEPS TO REPRODUCE 1. Launch discover OBSERVED RESULT See screenshot attached. EXPECTED RESULT Getting the size of every packages. Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-arch1-2 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435207] New: Grouping by tags does not show the title over the first group when navigating back into the user home folder
https://bugs.kde.org/show_bug.cgi?id=435207 Bug ID: 435207 Summary: Grouping by tags does not show the title over the first group when navigating back into the user home folder Product: dolphin Version: 20.12.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: nilslindem...@tutanota.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY See title. STEPS TO REPRODUCE 1. Open Dolphin 2. Go to /home/ (it works in sub folders) 3. give some folders tags 4. Group by tags (the tags are now visible as group titles) 5. Navigate into a child folder 6. Navigate back OBSERVED RESULT The first group title is now gone in the home folder level, the others are still there. EXPECTED RESULT All group titles are visible in the home folder level. OS: Fedora KDE KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Observing this on Fedora KDE and on Kubuntu. When – after the group title has gone – I disable and then re-enable grouping, then the title will be there again. Comments and star ratings do not produce the error on Fedora, but if I remember right, they did on Kubuntu, which I had installed before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433666] Applet's "Clear history" action is sometimes inappropriately disabled
https://bugs.kde.org/show_bug.cgi?id=433666 --- Comment #2 from Nils --- Well, I must reformulate compared to the first comment: - clear your history - activate the "Do not disturb" mode - get new notifications - try to clear them With this scenario, I can reproduce the issue every time. So maybe there is other way to reproduce this issue, but this one is a good way to check if the issue is still there or not. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433642] Breeze Light color scheme in kdeglobals incomplete after Plasma 5.21 migration
https://bugs.kde.org/show_bug.cgi?id=433642 --- Comment #9 from Nils --- Hu sorry, I was thinking that it was now solved because it's consistent? I don't have the issue anymore. And because I didn't think initially that the header would then be grey I'm not sure that the problem wasn't the compositor. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433642] Breeze Light color scheme in kdeglobals incomplete after Plasma 5.21 migration
https://bugs.kde.org/show_bug.cgi?id=433642 Nils changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433665] Tooltip are unreadable and black
https://bugs.kde.org/show_bug.cgi?id=433665 Nils changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Nils --- It was whether the compositor or the breeze theme not applied correctly. It has been fixed through one of those two ways. So we can close this issue. Cf: https://bugs.kde.org/show_bug.cgi?id=433642 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433642] Inconsistent header with panel widgets
https://bugs.kde.org/show_bug.cgi?id=433642 --- Comment #6 from Nils --- Created attachment 136202 --> https://bugs.kde.org/attachment.cgi?id=136202=edit New grey header consistent with the others -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433642] Inconsistent header with panel widgets
https://bugs.kde.org/show_bug.cgi?id=433642 Nils changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Nils --- I was using Breeze Light in fact. I switched back and forth with Breeze. And now I have the same grey everywhere. A bit surprising but I suppose it's the new appearance. See attached file to confirm the issue is fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433666] New: I can't clear history when not disturbed mode is activated
https://bugs.kde.org/show_bug.cgi?id=433666 Bug ID: 433666 Summary: I can't clear history when not disturbed mode is activated Product: plasmashell Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: nils.acrimont+...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 136201 --> https://bugs.kde.org/attachment.cgi?id=136201=edit Can't click clean history SUMMARY Button authorizing cleaning of history is disabled once I have activated the "do not disturb" mode. STEPS TO REPRODUCE 1. Get some notifications in your history 2. Activate the "Do not disturb Mode" 3. Try to clean the history. OBSERVED RESULT You can't. EXPECTED RESULT You should be able to do so. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.11.1-arch1-1 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433665] New: Tooltip are unreadable and black
https://bugs.kde.org/show_bug.cgi?id=433665 Bug ID: 433665 Summary: Tooltip are unreadable and black Product: plasmashell Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: nils.acrimont+...@protonmail.com Target Milestone: 1.0 Created attachment 136200 --> https://bugs.kde.org/attachment.cgi?id=136200=edit Unreadable tooltip I can't read tooltips from the panel. See screenshot attached. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.11.1-arch1-1 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433642] Inconsistent header with panel widgets
https://bugs.kde.org/show_bug.cgi?id=433642 --- Comment #3 from Nils --- Created attachment 136199 --> https://bugs.kde.org/attachment.cgi?id=136199=edit compositor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433642] Inconsistent header with panel widgets
https://bugs.kde.org/show_bug.cgi?id=433642 Nils changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Nils --- Still broken even after turning on the compositing. It had crashed sometimes in the past and never launched again after that. Not the first time it happened to me. I would like very much to see the compositing restart when it crash and not just turn-off? Or maybe have a notification somewhere that it has been permanently disabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433642] New: Inconsistent header with panel widgets
https://bugs.kde.org/show_bug.cgi?id=433642 Bug ID: 433642 Summary: Inconsistent header with panel widgets Product: plasmashell Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: nils.acrimont+...@protonmail.com Target Milestone: 1.0 Created attachment 136183 --> https://bugs.kde.org/attachment.cgi?id=136183=edit Showing inconsistencies and weird tooltip SUMMARY Sometimes the header is grey, sometimes it has the same color than everything. Tooltip within those header seem broken too. See attached file for more information. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.11.1-arch1-1 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 431923] Keeping arrow keys pressed does nothing
https://bugs.kde.org/show_bug.cgi?id=431923 --- Comment #16 from Nils --- I can confirm here, the bug is not yet fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433147] New: No awareness of key maintained pressed down
https://bugs.kde.org/show_bug.cgi?id=433147 Bug ID: 433147 Summary: No awareness of key maintained pressed down Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nils.acrimont+...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I keep down a key like "Space", "Back Space", "Arrow Up", "Arrow down", ... whatever the key, it is not taken into account. I have to release the key and pressed it again if I want to see two "aa" for example in an input. And I want to erase the text I just type, it becomes really hard to do as I have to type backspace as many times as I want to erase characters. It happens on every software I can use so it does not depend of an application. It's global. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.10.16-arch1-1 KDE Plasma Version: 2.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427383] Plasma UI does not initially show up on external screen when using NVIDIA Optimus
https://bugs.kde.org/show_bug.cgi?id=427383 --- Comment #1 from Nils --- Just for information, it is still happening with the 5.21 release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430367] New: Panel shows a black border
https://bugs.kde.org/show_bug.cgi?id=430367 Bug ID: 430367 Summary: Panel shows a black border Product: plasmashell Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: nils.acrimont+...@protonmail.com Target Milestone: 1.0 Created attachment 134069 --> https://bugs.kde.org/attachment.cgi?id=134069=edit Black border on panel SUMMARY Since the last plasma packages upgrade, I get a black border on the outside border of the panel. It happens even with an empty/default panel. STEPS TO REPRODUCE 1. Login to your desktop session 2. Look existing panel showing a black border 3. Create a new panel and see that the same black border appears OBSERVED RESULT See screenshot attached. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux: 5.9.13-arch1-1 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Rebooting does not change anything. Restarting plasmashell does not change anything too. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426906] Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 --- Comment #3 from Nils --- Created attachment 133430 --> https://bugs.kde.org/attachment.cgi?id=133430=edit New crash information added by DrKonqi kontact (5.15.3 (20.08.3)) using Qt 5.15.1 - What I was doing when the application crashed: I was attempting to change the color of a CalDav Folder -- Backtrace (Reduced): #4 0x7fcdf770c4c5 in QColor::operator=(QColor const&) () at /usr/lib/libQt5Gui.so.5 #5 0x7fcd6535ad2c in EventViews::setResourceColor(Akonadi::Collection const&, QColor const&, QSharedPointer const&) () at /usr/lib/libKF5EventViews.so.5 #6 0x7fcd641fe783 in KOHelper::setResourceColor(Akonadi::Collection const&, QColor const&) () at /usr/lib/libkorganizerprivate.so.5 [...] #9 0x7fcdf7c05f63 in QAction::triggered(bool) () at /usr/lib/libQt5Widgets.so.5 #10 0x7fcdf7c08845 in QAction::activate(QAction::ActionEvent) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426906] Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 Nils changed: What|Removed |Added CC||nilsd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 427687] Show additional options for application doesn't expand anymore
https://bugs.kde.org/show_bug.cgi?id=427687 Nils changed: What|Removed |Added Version|5.19.90 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 427687] New: Show additional options for application doesn't expand anymore
https://bugs.kde.org/show_bug.cgi?id=427687 Bug ID: 427687 Summary: Show additional options for application doesn't expand anymore Product: plasma-pa Version: 5.19.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: nils.acrimont+...@protonmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132346 --> https://bugs.kde.org/attachment.cgi?id=132346=edit Menu doesn't show up SUMMARY When clicking on the "show additional options for XXX" in the applications part, nothing shows out. STEPS TO REPRODUCE 1. Launch a session and play some sound on some application 2. Try to switch for this specific application the device output 3. Can't do it OBSERVED RESULT Nothing shows off EXPECTED RESULT The select allowing us to choose a device output should appear SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.8.14-arch1-1 KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION See capture -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427383] New: Plasma don't show up (panel bar, wallpaper, menu when right clicking on wallpaper)
https://bugs.kde.org/show_bug.cgi?id=427383 Bug ID: 427383 Summary: Plasma don't show up (panel bar, wallpaper, menu when right clicking on wallpaper) Product: plasmashell Version: 5.19.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nils.acrimont+...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Plasma don't show up (panel bar, wallpaper, menu when right clicking on wallpaper, ... but krunner works) when starting on a external screen from a laptop with optimus manager set for Nvidia. STEPS TO REPRODUCE 1. Connect your laptop with HDMI to an external screen and switch (CMD+P) to external screen only 2. Install Optimus Manager, set as Intel for default and after launching your session switch to Nvidia 3. It closes your session, login then again OBSERVED RESULT You will not see your wallpaper, nor your panel until you type "plasmashell --replace" into your krunner EXPECTED RESULT You should not have to type "plasmashell --replace" SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.8.13-arch1-1 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION This bug does not occur when not using an external screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426894] Screen is black at start-up and right click does nothing on wallpaper
https://bugs.kde.org/show_bug.cgi?id=426894 --- Comment #7 from Nils --- (In reply to Nate Graham from comment #6) > Definitely reminds me of Bug 426496. Yes indeed. It's quite new and it feels related to the Qt upgrade. Probably a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426894] Screen is black at start-up and right click does nothing on wallpaper
https://bugs.kde.org/show_bug.cgi?id=426894 --- Comment #5 from Nils --- Could I provide something in order to know what's wrong with the desktop view? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426894] Screen is black at start-up and right click does nothing on wallpaper
https://bugs.kde.org/show_bug.cgi?id=426894 --- Comment #3 from Nils --- Typing `plasmashell --replace` in krunner works however? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426894] Screen is black at start-up and right click does nothing on wallpaper
https://bugs.kde.org/show_bug.cgi?id=426894 --- Comment #2 from Nils --- It output nothing and does nothing. The issue is still there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426894] New: Screen is black at start-up and right click does nothing on wallpaper
https://bugs.kde.org/show_bug.cgi?id=426894 Bug ID: 426894 Summary: Screen is black at start-up and right click does nothing on wallpaper Product: plasmashell Version: 5.19.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nils.acrimont+...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Every time I boot my laptop with an HDMI connection to my screen (set as principal AND the laptop screen is disabled), I got this issue where the wallpaper is black and if I try to right click on it, nothing happen. STEPS TO REPRODUCE 1. Boot your laptop with an external display set as main and laptop screen disabled 2. login OBSERVED RESULT Black screen, right click on wallpaper bring nothing EXPECTED RESULT Wallpaper is loaded, right click bring the popup options. SOFTWARE/OS VERSIONS Linux: 5.8.10-arch1-1 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION A way to solve this is to go to display configuration, set another resolution for the external monitor. It then load the wallpaper and the right click works again. I then choose the normal and expected resolution and I am all good to go. I can upload a GIF showing the issue if it helps? I can also put some warnings from journalctl if need be? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Bouncing when changing virtual desktop through touchpad or mouse wheel scroll (broken with Folder View, works with Desktop view)
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #22 from Nils Kneuper --- (In reply to Riccardo Robecchi from comment #21) > I had this bug as well, but it seems to be solved with the latest release > (5.19.4). Can anyone else confirm? Nope, not fixed for me. Still same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424598] Neither title nor image when using spotify
https://bugs.kde.org/show_bug.cgi?id=424598 --- Comment #6 from Nils --- Thanks. I suppose we could not use the solution provided in the referenced issue, I quote: A quick check on the WebApp showed that using the ID from that url and the prefix "https://i.scdn.co/image/; makes it work again. Though the client is more throughly checked." Anyway, I ended up installing this https://github.com/freundTech/SpotPRIS2 and now it works as long as I don't try to use spotify connect. Thanks for the quick feedback nevertheless! KDE is a top notch desktop environment! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424598] Neither title nor image when using spotify
https://bugs.kde.org/show_bug.cgi?id=424598 --- Comment #4 from Nils --- Here it is: ❯ qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.Metadata mpris:artUrl: https://open.spotify.com/image/ab67616d1e02db65cfec2e8e37303140c881 mpris:length: 185234000 mpris:trackid: spotify:track:1bXoENBZuBkZniaPhRVgNp xesam:album: The Elder Scrolls IV: Oblivion: Original Game Soundtrack xesam:albumArtist: xesam:artist: xesam:autoRating: 0 xesam:discNumber: 0 xesam:title: xesam:trackNumber: 0 xesam:url: https://open.spotify.com/track/1bXoENBZuBkZniaPhRVgNp -- You are receiving this mail because: You are watching all bug changes.
[kplayer] [Bug 424598] New: Neither title nor image when using spotify
https://bugs.kde.org/show_bug.cgi?id=424598 Bug ID: 424598 Summary: Neither title nor image when using spotify Product: kplayer Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ke...@heloo.net Reporter: nils.acrimont+...@protonmail.com Target Milestone: --- Created attachment 130359 --> https://bugs.kde.org/attachment.cgi?id=130359=edit Neither title nor image SUMMARY When using Spotify, I have no image nor title song. Just a base64 string and the default icon. The subtitle is displayed correctly STEPS TO REPRODUCE 1. Lauching Spotify 2. Clicking on media player OBSERVED RESULT See attached file. 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.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #18 from Nils Kneuper --- (In reply to Matt W from comment #15) > Broken for me in Fedora 32, plasma 5.18.5. > > Workaround: > > Right click desktop -> configure desktop -> Wallpaper -> layout -> desktop > (was folder view). > > I can scroll again. Yes, the issue is that switching with folder view is broken which was once working. Deactivating folder view would at least mean that it should be made clear to the users that the mouse wheel switching is not supported in that mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #17 from Nils Kneuper --- (In reply to Martin from comment #16) > (In reply to Nate Graham from comment #8) > > This is working for me in Plasma 5.19/git master. Can anyone using Neon Dev > > Unstable or the KDE unstable repo (or compiling stuff from source) verify? > > According to this comment, the issue should be fixed with plasma 5.19. > However, for me it still persists: > - OS FreeBSD 12.1 > - qt 5.14.2 > - plasma 5.19.1 > - frameworks 5.71.0 > > I am reopening this issue. Similar setup for me but on Archlinux ~AMD64 with the latest patchset: - Qt 5.15.0 - Plasma 5.19.1 - KDE Frameworks: 5.71.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420918] New: Switch workspaces with mousewheel broken
https://bugs.kde.org/show_bug.cgi?id=420918 Bug ID: 420918 Summary: Switch workspaces with mousewheel broken Product: plasmashell Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: crazy-ivano...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY With several virtual workspaces configured and the mouse wheel vertical scroll configured to allow switching between workspaces, it does not work if "folder view" is selected. Switching does work in "Desktop" mode. Switching via middle click does work as well. The same issue is described on this forum post: https://forum.endeavouros.com/t/switching-workspaces-with-mouse-wheel-stopped-working/4112 Speculation by JanKusanagi in the #kde IRC chan is that this is due to the folderview widget kidnapping the mouse wheel. The behavior of switching desktops via mousewheel changed some versions ago earlier this year (running archlinux ~amd64). A downgrade to an older package plasma-desktop back from the days when it was (most likely) still working did not help though. STEPS TO REPRODUCE 1. Configure >1 workspace, apply changes 2. Configure workspaces, change layout to "folder view" and ensure that vertical scrolling as well as middle click is set to "change workspace", apply changes 3. move the mouse to the desktop area and use the wheel to scroll vertically, afterwards use middle click OBSERVED RESULT Nothing happens when scrolling vertically, middle click opens the workspace selector as expected EXPECTED RESULT Switching workspaces or at least an information that this is not possible via wheel in folder view, middle click opens the workspace selector as expected SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.6.9-arch1-1, 64-bit (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Same issue as described in this forum post: https://forum.endeavouros.com/t/switching-workspaces-with-mouse-wheel-stopped-working/4112 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 420386] New: unknown error code 150 I/O problem
https://bugs.kde.org/show_bug.cgi?id=420386 Bug ID: 420386 Summary: unknown error code 150 I/O problem Product: gwenview Version: 19.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: gwenview-bugs-n...@kde.org Reporter: nils.wagenknecht.pri...@gmail.com Target Milestone: --- SUMMARY unknown error code 150 I/O problem send report to bugs.kde.org STEPS TO REPRODUCE 1. connect Apple IPAD idVendor=05ac, idProduct=12ab, bcdDevice= 7.12 Mfr=1, Product=2, SerialNumber=3 2. start application gwenview-import 3. OBSERVED RESULT error message EXPECTED RESULT download function available SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gentoo Linux 5.4.28-gentoo (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411996] Task switcher shows only large icon except when triggering from system settings
https://bugs.kde.org/show_bug.cgi?id=411996 Nils changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Nils --- Yes! That was the reason. I got a crash as showed in my other attachment. Confirming on the pop-up the activation and login again make it works! Thanks, plasma is awesome! Maybe having a notification for the user about an anomaly for the compositor would be great? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411996] Task switcher shows only large icon except when triggering from system settings
https://bugs.kde.org/show_bug.cgi?id=411996 --- Comment #2 from Nils --- Created attachment 122694 --> https://bugs.kde.org/attachment.cgi?id=122694=edit The status of my compositor I am not sure compositor is enabled... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411996] New: Task switcher shows only large icon except when triggering from system settings
https://bugs.kde.org/show_bug.cgi?id=411996 Bug ID: 411996 Summary: Task switcher shows only large icon except when triggering from system settings Product: systemsettings Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nils.acrimont+...@protonmail.com Target Milestone: --- Created attachment 122693 --> https://bugs.kde.org/attachment.cgi?id=122693=edit getting only icons instead of window thumbnail I tried without any success to have a nice task switcher showing windows thumbnail but for a reason I ignore I only got icons. Cf. attachment. However I have the right design from the task switcher from system settings -> windows management -> task switcher -> main -> Visualization -> Breeze preview. SOFTWARE/OS VERSIONS KDE Plasma Version:5.16.5 KDE Frameworks Version:5.62.0 Qt Version:5.13.1 Kernel Version:5.2.14-arch2-1-ARCH OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407617] New: Partition manager crash on clicking (probably faulty) drive.
https://bugs.kde.org/show_bug.cgi?id=407617 Bug ID: 407617 Summary: Partition manager crash on clicking (probably faulty) drive. Product: partitionmanager Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: niol...@hotmail.nl Target Milestone: --- Created attachment 120121 --> https://bugs.kde.org/attachment.cgi?id=120121=edit crash text file SUMMARY First there are some messages about (non-existing) partitions not being aligned properly. Probably caused by faulty usb: "Partition ‘/dev/sdc1’ is not properly aligned (first sector: 1948285285, modulo: 357)." "Partition ‘/dev/sdc1’ is not properly aligned (last sector: 3650263507, modulo: 468)." "Partition ‘/dev/sdc4’ is not properly aligned (last sector: 28049848, modulo: 441)." Then, as soon as i click that device in the partition manager gui, it crashes. The bug reporting window reports that the information might be useful. STEPS TO REPRODUCE 1. Insert probably faulty usb. 2. Click on it in the gui 3. OBSERVED RESULT The gui crashes EXPECTED RESULT the gui crashes SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.0.13-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.15 KDE Frameworks Version: 5.57 Qt Version: 5.12.3 ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 389962] Lock screen does not show Picture of the Day because image is not cached locally
https://bugs.kde.org/show_bug.cgi?id=389962 --- Comment #14 from Nils --- It would really be great to have this feature working. I don't ever see my desktop as I have a lot of things always opened. The only moment where I would enjoy to see something new is when I lock my computer. If this is related to the internet access, I suppose the images could be fetched in advance when the user has still not locked his session. The images would never change until he open up again his session and it's a new day. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 389962] Lock screen does not show Picture of the Day because image is not cached locally
https://bugs.kde.org/show_bug.cgi?id=389962 Nils changed: What|Removed |Added CC||nils.acrimont+kde@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #24 from Nils Rother --- Okay, thanks to your video I can now reproduce this issue. On my system it seems to occur when DPI scaling is enabled (using QT_SCALE_FACTOR=1.4 to test) and my left monitor is set to a lower resolution than my right monitor, which is similar to the configuration shown in your video. The whole overlayed rectangle selection interface seems to be shifted left or right, depending on which monitor is selected as the primary one. Note that this does NOT happen when my right monitor is set to a lower resolution than the left one or both are set to the same resolution. I don't know what configurations could cause issues if you have >2 monitors as I don't have the hardware to test that. I'm gonna peruse the code a bit, maybe I can figure out why this is happening... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 Nils Rother changed: What|Removed |Added CC||nilsrother...@gmail.com --- Comment #18 from Nils Rother --- I can only replicate this on the spectacle version version that ships with my distro (18.12.2), it seems to be working fine in the latest git version (19.03.70, commit bda92cd), could someone who was affected by this pull the latest source and try this again? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 346256] Konversation crashes every night
https://bugs.kde.org/show_bug.cgi?id=346256 --- Comment #3 from Nils Henrik Tvetene --- I am on Fedora 28 with konversation 1.7.5 now, and have not had this problem in a long time. Seems resolved to me :-) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397047] New: Last line of KWrite is not displayed entirely
https://bugs.kde.org/show_bug.cgi?id=397047 Bug ID: 397047 Summary: Last line of KWrite is not displayed entirely Product: kate Version: 18.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: nils.acrim...@gmail.com Target Milestone: --- Created attachment 114250 --> https://bugs.kde.org/attachment.cgi?id=114250=edit bottom part of letters are cut on the last line I have noticed something weird with Kwrite lastly, when I am writing on the last line of the editor, the letters with a low part like "q", or "g" are cut. See capture for reference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396595] New: Icons in system tray are wrapped by a black square
https://bugs.kde.org/show_bug.cgi?id=396595 Bug ID: 396595 Summary: Icons in system tray are wrapped by a black square Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: nils.acrim...@gmail.com Target Milestone: 1.0 Created attachment 113985 --> https://bugs.kde.org/attachment.cgi?id=113985=edit black square around skype & musixmatch Hello, Unlike this issue: https://bugs.kde.org/show_bug.cgi?id=184302 I got a visual for my icons, but they are wrapped with a black square instead of transparent square. See screenshot attached for more details. It happens only with proprietary software icons. And only at boot. When I exit and relaunch the application, it renders nicely without this black square. Thanks for your awesome work! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388036] Include support for autocrypt
https://bugs.kde.org/show_bug.cgi?id=388036 Nils Reuter <nils.reu...@gmx.net> changed: What|Removed |Added CC||nils.reu...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389406] Crash of Kactivitymanage after launching git gui
https://bugs.kde.org/show_bug.cgi?id=389406 --- Comment #2 from Nils <nils.acrim...@gmail.com> --- Neither I do. I will try to confirm that the issue is not happening anymore once I get my hands on 5.12 release. Thanks anyway! -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389406] New: Crash of Kactivitymanage after launching git gui
https://bugs.kde.org/show_bug.cgi?id=389406 Bug ID: 389406 Summary: Crash of Kactivitymanage after launching git gui Product: kactivitymanagerd Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: nils.acrim...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 110111 --> https://bugs.kde.org/attachment.cgi?id=110111=edit journalctl of crash Hello, I have noticed some stability issues recently on my daily usage of KDE. I am up to date with the last releases: - 4.14.15-1-ARCH #1 SMP PREEMPT Tue Jan 23 21:49:25 UTC 2018 x86_64 GNU/Linux - plasma-workspace 5.11.5-2 - plasma-desktop 5.11.5-1 - plasma-framework 5.42.0-1 - plasma-integration 5.11.5-1 The crash showed in the log happened twice after launching `git gui` from `konsole`. However it is not happening every time... just sometimes. I hope the traces provided can help explain it. If you need more information, do not hesitate to ask. Regards, -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 384734] Impossible to reply to the SMS once the phone is locked
https://bugs.kde.org/show_bug.cgi?id=384734 --- Comment #1 from Nils <nils.acrim...@gmail.com> --- This problem has been solved by the recent updates. I do not know which. However I now receive 2 notifications (one general and one about SMS with the reply feature) instead of one. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 384476] Ktorrent Crashes on shutdown
https://bugs.kde.org/show_bug.cgi?id=384476 Nils <n...@buechner.me> changed: What|Removed |Added CC||n...@buechner.me --- Comment #2 from Nils <n...@buechner.me> --- Same here on Kubuntu 17.10 Application: ktorrent (5.1.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.0-11-generic x86_64 Distribution: Ubuntu Artful Aardvark (development branch) -- Information about the crash: <Erklären Sie bitte ganz genau, was Sie machten, als das Programm abstürzte.> The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57440c1900 (LWP 24746))] Thread 16 (Thread 0x7f56c9ffb700 (LWP 24916)): #0 0x7f57380db047 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f57380dd59b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57380de05b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f57380de23c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f573ef1b41b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f573eec0dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f573ece03ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f573ece529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f573db4a7fc in start_thread (arg=0x7f56c9ffb700) at pthread_create.c:465 #9 0x7f573e07aa3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f56ca7fc700 (LWP 24915)): #0 0x7f573e06e831 in __GI___poll (fds=0x7f56b4002de0, nfds=1, timeout=98200) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f57380de129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57380de23c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f573ef1b41b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f573eec0dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f573ece03ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f573ece529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f573db4a7fc in start_thread (arg=0x7f56ca7fc700) at pthread_create.c:465 #8 0x7f573e07aa3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f56caffd700 (LWP 24914)): #0 0x7f573e06e831 in __GI___poll (fds=0x7f56c0002c80, nfds=1, timeout=98200) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f57380de129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57380de23c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f573ef1b41b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f573eec0dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f573ece03ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f573ece529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f573db4a7fc in start_thread (arg=0x7f56caffd700) at pthread_create.c:465 #8 0x7f573e07aa3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f5717fff700 (LWP 24913)): #0 0x7f573e069f2d in __GI___libc_read (fd=21, buf=0x7f5717ffea90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f5738122240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57380ddc0b in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f57380de0d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f57380de23c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f573ef1b41b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f573eec0dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f573ece03ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f573ece529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f573db4a7fc in start_thread (arg=0x7f5717fff700) at pthread_create.c:465 #10 0x7f573e07aa3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f56cb7fe700 (LWP 24912)): #0 0x7f5738122233 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f57380ddc0b in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57380de0
[kdeconnect] [Bug 384734] New: Impossible to reply to the SMS once the phone is locked
https://bugs.kde.org/show_bug.cgi?id=384734 Bug ID: 384734 Summary: Impossible to reply to the SMS once the phone is locked Product: kdeconnect Version: 1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: nils.acrim...@gmail.com Target Milestone: --- Hello, I have an issue and that whatever the computer or the phone. When my phone is unlocked and I receive SMS, it is seen as SMS notification and I can reply to it. However, as soon as I have my phone locked, all the SMS are notified through general notification and so I cannot reply to any of them. Furthermore, as we do not have access to the phone contact or the list of messages, the only way for me to reply is to use my phone. I have double checked the permissions and KDEConnect is all green. I originally talk about this on the forums here: https://forum.kde.org/viewtopic.php?f=18=141558 But curiously nobody confirmed the issue. I am not using any activities so this is not like the #369179. Regards, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381824] New: When undoing maximize windows, the windows does not take its original position
https://bugs.kde.org/show_bug.cgi?id=381824 Bug ID: 381824 Summary: When undoing maximize windows, the windows does not take its original position Product: kwin Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: nils.acrim...@gmail.com Target Milestone: --- Created attachment 106389 --> https://bugs.kde.org/attachment.cgi?id=106389=edit bad repositioning of windows when unmaximizing it Hello, I am using plasma as a wall of applications, with one big application in my right screen, and three in my left screen (browser, konsole, spotify). I often have to maximize one of the application in the left screen and I have set a shortcut (F11) in order to do so instead of fullscreen option because I want to keep my taskbar always visible. But when I am undoing the maximize thing by pressing F11 again, I got my application relocated elsewhere that were it was originally positioned. Thank you anyway for plasma which is awesome, -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches
https://bugs.kde.org/show_bug.cgi?id=354522 --- Comment #11 from Nils Kassube <kass...@gmx.net> --- Actually the patch was previously made for 1.2.2. Later I checked it with the current git source and made a new diff with the new line numbers. I have just tried the patch with the 1.1.2 source and it works directly. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches
https://bugs.kde.org/show_bug.cgi?id=354522 --- Comment #8 from Nils Kassube <kass...@gmx.net> --- The difference to the original patch is only an offset of several lines, so it should be easy to backport. If you are willing to compile from source, I could provide the necessary patch for 1.2.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377333] New: Crash of plasma when double clicking on the menu icon at the left top of the screen
https://bugs.kde.org/show_bug.cgi?id=377333 Bug ID: 377333 Summary: Crash of plasma when double clicking on the menu icon at the left top of the screen Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nils.acrim...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: I was looking at my empty desktop (layout: desktop with unlocked widgets) and I double clicked on the menu icon at the top left of the screen (with the three line). The task bar disappeared and reloaded by itself with the notification of the crash. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc83ef1800 (LWP 5524))] Thread 9 (Thread 0x7fdbb055f700 (LWP 10568)): #0 0x7fdc7d5a248d in poll () at /usr/lib/libc.so.6 #1 0x7fdc783c07a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdc783c08bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fdc7dec606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fdc7de6f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdc7dc91a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fdc80dcb025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fdc7dc966d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fdc7cb61454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fdc7d5ab7df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fdbc977c700 (LWP 5747)): #0 0x7fdc7d5a248d in poll () at /usr/lib/libc.so.6 #1 0x7fdc783c07a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fdc783c08bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fdc7dec606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fdc7de6f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdc7dc91a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fdc8197efd6 in () at /usr/lib/libQt5Quick.so.5 #7 0x7fdc7dc966d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fdc7cb61454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fdc7d5ab7df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fdc53de9700 (LWP 5723)): #0 0x7fdc7cb6710f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fdc83673234 in () at /usr/lib/libQt5Script.so.5 #2 0x7fdc83673279 in () at /usr/lib/libQt5Script.so.5 #3 0x7fdc7cb61454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fdc7d5ab7df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fdc5daeb700 (LWP 5722)): #0 0x7fdc78405e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fdc783bfc99 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fdc783c06cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7fdc783c08bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fdc7dec606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fdc7de6f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fdc7dc91a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fdc7dc966d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fdc7cb61454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fdc7d5ab7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fdc5f791700 (LWP 5721)): #0 0x7ffd84bf5939 in () #1 0x7ffd84bf5bc5 in clock_gettime () #2 0x7fdc7d5b86b6 in clock_gettime () at /usr/lib/libc.so.6 #3 0x7fdc7dec5201 in () at /usr/lib/libQt5Core.so.5 #4 0x7fdc7dec39c9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #5 0x7fdc7dec3f75 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #6 0x7fdc7dec563e in () at /usr/lib/libQt5Core.so.5 #7 0x7fdc783bfc8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #8 0x7fdc783c06cb in () at /usr/lib/libglib-2.0.so.0 #9 0x7fdc783c08bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #10 0x7fdc7dec606b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7fdc7de6f89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #12 0x7fdc7dc91a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #13 0x7fdc80dcb025 in () at /usr/lib/libQt5Qml.so.5 #14 0x7fdc7dc966d8 in () at /usr/lib/libQt5Core.so.5 #15
[kaffeine] [Bug 354522] repeated recordings get time-shifted by daylight-saving-time switches
https://bugs.kde.org/show_bug.cgi?id=354522 Nils Kassube <kass...@gmx.net> changed: What|Removed |Added CC||kass...@gmx.net --- Comment #3 from Nils Kassube <kass...@gmx.net> --- Created attachment 101858 --> https://bugs.kde.org/attachment.cgi?id=101858=edit fix dst switch problem I can confirm the problem with the git source of today. The attached patch fixes it for me. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 346450] Remove 1px margin [patch included]
https://bugs.kde.org/show_bug.cgi?id=346450 --- Comment #6 from Nils Luxton <nils.lux...@gmail.com> --- That would be great, thanks. I'm not concerned with it having a UI (personally) but understand if that is a 'blocker' to getting this in. My use case is in fact the opposite of the OP, namely, to be able to center and increase the margin. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 346450] Remove 1px margin [patch included]
https://bugs.kde.org/show_bug.cgi?id=346450 Nils Luxton <nils.lux...@gmail.com> changed: What|Removed |Added CC||nils.lux...@gmail.com --- Comment #4 from Nils Luxton <nils.lux...@gmail.com> --- Is there any proposal for when this might be merged? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 360396] kscreenlocker-greet ignores KB and Mouse after screen energy saving activates
https://bugs.kde.org/show_bug.cgi?id=360396 Nils <nils.acrim...@gmail.com> changed: What|Removed |Added CC||nils.acrim...@gmail.com --- Comment #26 from Nils <nils.acrim...@gmail.com> --- I also have this issue with plasma-desktop 5.7.3-1 on archlinux and extra/xf86-video-intel 1:2.99.917+688+g49daf5d-1 driver, same than Nick Shaforostoff. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362615] New: Audio settings causes plasmashell to segfault - no audio from bluetooth headphones
https://bugs.kde.org/show_bug.cgi?id=362615 Bug ID: 362615 Summary: Audio settings causes plasmashell to segfault - no audio from bluetooth headphones Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nils.lux...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Right-clicked on the audio settings applet and selected 'Audio Volume Settings...' - Unusual behavior I noticed: Plasma crashed This has been happening since the update from Kubuntu 15.10 -> Kubuntu 16.04 Bluetooth headset connected (Plantronics Backbeat Pro) and has been working for around a year or so. Since I upgraded OS (using upgrade path, not a fresh install) no audio comes through to the headphones and the second time I go into Volume Settings as mentioned above, plasma crashes. I attempted to mark this as a duplicate of #362432 in the bug reporting tool, but it wouldn't let me - I selected that it was a duplicate but it did not seem to actually mark it as a duplicate and told me I hadn't marked any as duplicates. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd0b6a9d8c0 (LWP 2063))] Thread 10 (Thread 0x7fd0a1dbf700 (LWP 2089)): #0 0x7fd0b11aee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd0b5273c62 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7fd0a1dbec00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 0x7fd0b5273c62 in _xcb_conn_wait (c=c@entry=0x23e2200, cond=cond@entry=0x23e2240, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7fd0b52758d7 in xcb_wait_for_event (c=0x23e2200) at ../../src/xcb_in.c:693 #4 0x7fd0a3f0d629 in QXcbEventReader::run() (this=0x23ec8c0) at qxcbconnection.cpp:1253 #5 0x7fd0b18a484e in QThreadPrivate::start(void*) (arg=0x23ec8c0) at thread/qthread_unix.cpp:331 #6 0x7fd0b09916fa in start_thread (arg=0x7fd0a1dbf700) at pthread_create.c:333 #7 0x7fd0b11bab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fd09b3ea700 (LWP 2101)): #0 0x7fd0b11aee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd0adf4431c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fd094003070, timeout=, context=0x7fd094000990) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:4135 #2 0x7fd0adf4431c in g_main_context_iterate (context=context@entry=0x7fd094000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3835 #3 0x7fd0adf4442c in g_main_context_iteration (context=0x7fd094000990, may_block=may_block@entry=1) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901 #4 0x7fd0b1adba9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fd0940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fd0b1a82dea in QEventLoop::exec(QFlags) (this=this@entry=0x7fd09b3e9ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fd0b189f8a4 in QThread::exec() (this=this@entry=0x24c5ec0) at thread/qthread.cpp:503 #7 0x7fd0b41473c5 in QQmlThreadPrivate::run() (this=0x24c5ec0) at qml/ftw/qqmlthread.cpp:141 #8 0x7fd0b18a484e in QThreadPrivate::start(void*) (arg=0x24c5ec0) at thread/qthread_unix.cpp:331 #9 0x7fd0b09916fa in start_thread (arg=0x7fd09b3ea700) at pthread_create.c:333 #10 0x7fd0b11bab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fd08ffcd700 (LWP 2113)): #0 0x7fd0b11aee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd0adf4431c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fd088002e70, timeout=, context=0x7fd088000990) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:4135 #2 0x7fd0adf4431c in g_main_context_iterate (context=context@entry=0x7fd088000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3835 #3 0x7fd0adf4442c in g_main_context_iteration (context=0x7fd088000990, may_block=may_block@entry=1) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901 #4 0x7fd0b1adba9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fd0880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fd0b1a82dea in QEventLoop::exec(QFlags)
[plasma4] [Bug 309214] Bouncing icon on mouse cursor occasionally remains stuck on after the application has launched
https://bugs.kde.org/show_bug.cgi?id=309214 Nils <nils.acrim...@gmail.com> changed: What|Removed |Added CC||nils.acrim...@gmail.com --- Comment #16 from Nils <nils.acrim...@gmail.com> --- I can confirm this issue. Easy for me to reproduce, I just have to click on an email link (in order to send an email) in Firefox while no email client has been configured. It then try to launch an application but it just does not know which application it has to launch, so it stay with the busy icon forever. -- You are receiving this mail because: You are watching all bug changes.
