[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #27 from Norbert Preining --- Sorry again, with properly applied patch 369c3cbd7d843b6ce2901adf8b464158f84759a1 I cannot reproduce the failure :-( Sorry for the noise! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #26 from Norbert Preining --- Wait ... I blindly copied a test run to the PKGBUILD and it contained --dry-run ... let me rerun the test without the revert and see if it works Sorry for the confusion, now when I tried to add the other patch for reverting I found the --dry-run -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #23 from Norbert Preining --- (In reply to fanzhuyifan from comment #22) > Do you have any core-testing and extra-testing enabled, by the way? No, only default repositories (core,extra,multilib) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #21 from Norbert Preining --- (In reply to fanzhuyifan from comment #20) > I am on arch linux, using Qt 6.7 (with all the testing repos enabled > including kde-unstable). Hmmm, looking at https://archlinux.org/packages/?sort==KDE-Unstable it seems only Qt is updated there at the moment. I am a bit nervous going to a beta version of Qt since this is my work computer. Do you think this is purely depending on Qt updated to 6.7? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #19 from Norbert Preining --- Created attachment 166925 --> https://bugs.kde.org/attachment.cgi?id=166925=edit kwin x11 offset even with patch applied screencast -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #18 from Norbert Preining --- (In reply to fanzhuyifan from comment #15) > Could you share the steps with which you could still reproduce the problem? > A screencast would be ideal. I attach one > Are you still seeing this for all windows on X11? I tested konsole and system settings, both in screencast to be seen. That is based on Arch Linux kwin 6.0.1-3 with 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch applied. Build log shows: > ==> Making package: kwin 6.0.1-3.1 (Mon 11 Mar 2024 08:55:03 AM JST) > ==> Checking runtime dependencies... > ==> Checking buildtime dependencies... > ==> Retrieving sources... > -> Found kwin-6.0.1.tar.xz > -> Found kwin-6.0.1.tar.xz.sig > -> Found 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch > ==> Validating source files with sha256sums... > kwin-6.0.1.tar.xz ... Passed > kwin-6.0.1.tar.xz.sig ... Skipped > 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch ... Passed > ==> Verifying source file signatures with gpg... > kwin-6.0.1.tar.xz ... Passed > ==> Extracting sources... > -> Extracting kwin-6.0.1.tar.xz with bsdtar > ==> Starting build()... > checking file src/utils/xcbutils.h > checking file src/workspace.cpp > Hunk #1 succeeded at 3020 (offset -1 lines). > -- The C compiler identification is GNU 13.2.1 > ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #14 from Norbert Preining --- (In reply to fanzhuyifan from comment #8) > Git commit 369c3cbd7d843b6ce2901adf8b464158f84759a1 by Yifan Zhu. > Committed on 08/03/2024 at 19:34. > Pushed by fanzhuyifan into branch 'Plasma/6.0'. > > utils/xcbutils: Don't call toXNative with unsigned integer > > Instead use signed integers, to prevent the implicit cast from unsigned > integers to qreal. [..] > https://invent.kde.org/plasma/kwin/-/commit/ > 369c3cbd7d843b6ce2901adf8b464158f84759a1 I pulled this patch into a local build of kwin on Arch, but it did *NOT* fix the misbehaviour. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] Edge browser window receives events despite being shown in different position
https://bugs.kde.org/show_bug.cgi?id=482956 --- Comment #2 from Norbert Preining --- Created attachment 166780 --> https://bugs.kde.org/attachment.cgi?id=166780=edit Screencast showing the misbehaviour -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] Edge browser window receives events despite being shown in different position
https://bugs.kde.org/show_bug.cgi?id=482956 Norbert Preining changed: What|Removed |Added Summary|Cannot move Edge browser|Edge browser window |window out of the left |receives events despite |border |being shown in different ||position -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] Cannot move Edge browser window out of the left border
https://bugs.kde.org/show_bug.cgi?id=482956 --- Comment #1 from Norbert Preining --- I forgot to add an important information: That is an X11 session, not wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] New: Cannot move Edge browser window out of the left border
https://bugs.kde.org/show_bug.cgi?id=482956 Bug ID: 482956 Summary: Cannot move Edge browser window out of the left border Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY When I move the edge browser window out of the screen to the left, it is drawn as being out of it, but mouse actions are taken as if the windows has not moved out but got stuck with the window left border on the left border of the screen. Also mouse inputs to the window are misplaced as seen in the second part of the attached video. The moment I click the mouse, the window pops to its "assumed" (wrong) position. STEPS TO REPRODUCE 1. move edge browser window out of the left edge 2. click on the frame or somewhere around the position where there can be interaction 3. OBSERVED RESULT Window frame and window content reacts despite the window being in different position EXPECTED RESULT Not doing this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION nvidia graphic card -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #64 from Norbert Preining --- (In reply to David Edmundson from comment #61) > Can someone who can reproduce test a patch: > > change > ddca_get_display_info_list2(true, ); > > to > ddca_get_display_info_list2(false, ); Hi David, yes that worked, after installing ddcutil2 and rebuilding with this patch attached on my Arch machine, powerdevil did start properly ``` Jan 15 12:50:01 bulldog systemd[1786]: Starting Powerdevil... Jan 15 12:50:01 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Jan 15 12:50:01 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Jan 15 12:50:01 bulldog libddcutil[9507]: Initializing libddcutil. ddcutil version: 2.0.0, shared library: /usr/lib/libddcutil.so.5.0.0 Jan 15 12:50:01 bulldog libddcutil[9507]: Library initialization complete. Jan 15 12:50:03 bulldog systemd[1786]: Started Powerdevil. Jan 15 12:50:03 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: Handle button events action could not check for screen configuration Jan 15 12:50:03 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" ``` -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 --- Comment #20 from Norbert Preining --- (In reply to Harald Sitter from comment #11) > The unplugging and plugging back in should be fixed in master. There were > caching problems. Unfortunately it is not. I am running Arch Linux with the latest released KDE packages, and unplugging and replugging a mtp ebook reader does not help. The device contents is shown, but I cannot copy files to the device. I need to kill the kiod as always to get rw access to the device again. A typical example is Calibre (which I use a lot) which has a "Release" button for the device. Something similar should be included in Dolphin and "Removable Devices". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450777] (un)shading broken, window has a way too small size after unshading
https://bugs.kde.org/show_bug.cgi?id=450777 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #1 from Norbert Preining --- I cannot reproduce this on Arch with 5.24.2 running over X11. Are you using Wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #8 from Norbert Preining --- Like Thomas I can confirm that on Debian/unstable with my own OBS builds (frameworks 5.91, plasma 5.24.1), as well as with Arch builds, the strange misplaced clicks can be reproduced with e.g. ksnip in the same way as described above (right click ..) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #6 from Norbert Preining --- The "misplaced-mouse-click" is still present on Plasma 5.24.1 / Arch The Debian packages are built ATM. The context menu will need confirmation from a user of my Debian packages, I will inquire. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #5 from Norbert Preining --- I will retest with 5.24.1 and report back, will need 1-2 days to have the packages ready. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #2 from Norbert Preining --- One more comment concerning reproducibility with ksnip: Interestingly it only happens when I **right** click and select "Open Editor" When I just simply click on the tray icon of ksnip it also shows the editor, but then the misplaced click is not reproducible, while in the former case (right click) it is 100% reproducible. The same is the case with Steam, Right-click actions only trigger a misplaced click, not left-click actions on the tray. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #1 from Norbert Preining --- Additional comment concerning the "Misplaced click": No need for binary programs, I can reproduce this with ksnip: - right-click on ksnip tray icon, select "Open editor" - click on the Window decoration X to close it to the tray icon - click on any icon in the taskbar Observed result: the ksnip editor reappears Expected result: the application of the clicked icon appears -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] New: system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 Bug ID: 450287 Summary: system tray icon behavior partially broken from 5.23.90 to 5.24.0 Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: norb...@preining.info CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Since the update from 5.23.90 to 5.24 (both tried on Arch Linux and Debian unstable), the system tray icons behave strange in some ways: - minimizing some windows to tray icons, then click on *any* icon on the task bar pops up the context menu of the systray icon - some applications (known: anydesk) lost their systray icon context menu A similar bug was present in 5.22.90 and fixed for 5.23, but something seems to have creeped in again between 5.23.90 and 5.24.0 final release STEPS TO REPRODUCE Misplaced click 1. start steam, maximize it 2. click on the top bar X to minimize it to tray icon 3. click on the icon of any application in the task bar 4. the context menu of the steam tray icon pops up (far from the actual mouse pointer location!) (If needed, I can try to capture a screen shot of that) Lost context menu 1. Install anydesk 2. right/left click on the systray icon 3. no context menu is shown ADDITIONAL COMMENTS The same behavior appeared with both frameworks 5.90 and 5.91, so it seems not to depend on that. Also, the same behavior is shown on Arch Linux (packages made by Arch maintainers) as well as my own OBS builds of KDE/Plasma for Debian, so on two independent builds. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-zen1-0.1-zen-custom (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 62.8 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 447241] New: Terminal is striped immediately after dropping down yakuake terminal
https://bugs.kde.org/show_bug.cgi?id=447241 Bug ID: 447241 Summary: Terminal is striped immediately after dropping down yakuake terminal Product: yakuake Version: 21.12.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: norb...@preining.info Target Milestone: --- Created attachment 144687 --> https://bugs.kde.org/attachment.cgi?id=144687=edit Screenshot of the striped yakuake SUMMARY *** When dropping down yakuake and before the first refresh of the terminal, yakuake shows stripes on Intel graphics hardware. STEPS TO REPRODUCE 1. open yakuake (press F12) 2. stripes are shown (see attached screenshot) 3. do Ctrl-L, or open a curses program and the stripes are gone. This is repeatable every time yakuake is re-opened after it was hidden. OBSERVED RESULT stripes EXPECTED RESULT no stripes SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.10+futex+zstd+intel+wine+ (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445675] New: Rendering widescreen 16:9 format to DVD always adds black bars
https://bugs.kde.org/show_bug.cgi?id=445675 Bug ID: 445675 Summary: Rendering widescreen 16:9 format to DVD always adds black bars Product: kdenlive Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY It is not possible to render to widescreen DVD (NTSC) without adding black bars at top bottom, despite input data is 16:9. All renderings to DVD (VOB) result in 4:3 rendered video with black bars, which, when shown on a normal modern TV, results in wrong aspect ratio. STEPS TO REPRODUCE 1. create a project in some 16:9 format 2. render to SD/DVD OBSERVED RESULT output contains black bars at top bottom EXPECTED RESULT correctly encoded video that shows full screen (filling the full screen) of a 16:9 TV SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Changing the Project format to NTSC widescreen does not help, rendering to DVD again creates black bars. Changing the project to DVD, black bars are already added in the preview. What I currently do is: * render to 16:9 mp4 high quality * use videotrans' movie-to-dvd with the respective options -m ntsc -q high -a 16:9 -M * use dvdauthor to create the dvd structure using the previously created vob file * burn -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 444461] New: gwenview shows old file content when underlying file has changed
https://bugs.kde.org/show_bug.cgi?id=61 Bug ID: 61 Summary: gwenview shows old file content when underlying file has changed Product: gwenview Version: 21.08.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY When the underlying file is changed, gwenview does not update the displayed image, albeit the thumbnail changes. STEPS TO REPRODUCE 1. cd $(mktemp -d) 2. cp ~/photo1.jpg test.jpg 3. gwenview . & at this stage gwenview shows the thumbnail of test.jpg, and double-click on the thumbnail shows the content of photo1.jpg 4. Press ESC - return to directory view 5. cp ~/photo2.jpg test.jpg at this moment, the thumbnail is updated to show the content of photo2.jpg as thumbnail for test.jpg 6. double click on test.jpg this shows the content of photo1.jpg and not photo2.jpg OBSERVED RESULT old file content is shown EXPECTED RESULT new file content is shown SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442758] Some apps' tray icons don't have context menu anymore
https://bugs.kde.org/show_bug.cgi?id=442758 --- Comment #7 from Norbert Preining --- @David I can confirm that the proposed merge request fixes the issue, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442775] Extra margins introduced upon printing
https://bugs.kde.org/show_bug.cgi?id=442775 --- Comment #4 from Norbert Preining --- Thanks Nate, I can confirm here that by selecting "Force rasterizing" the correct page is produced. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442775] Extra margins introduced upon printing
https://bugs.kde.org/show_bug.cgi?id=442775 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #1 from Norbert Preining --- I can confirm this on Debian/unstable with okular 21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442758] New: some applications don't have context menu anymore
https://bugs.kde.org/show_bug.cgi?id=442758 Bug ID: 442758 Summary: some applications don't have context menu anymore Product: plasmashell Version: 5.22.90 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: norb...@preining.info CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Some applications, e.g., virt-manager, don't have right-click context menus anymore since upgrade from 5.22.5 to 5.22.90 STEPS TO REPRODUCE 1. start virt-manager 2. right click on the virt-manager icon OBSERVED RESULT no context menu is shown EXPECTED RESULT context menu with defined and running machines etc SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Debian GNU/Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 441957] kleopatra: Creates unsafe ~/.gnupg when not already present
https://bugs.kde.org/show_bug.cgi?id=441957 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #1 from Norbert Preining --- Same on Debian, and same with 20.12 - 21.04 - 21.08 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 438017] Drawer generates a thin line on its window edge that consumes clicks without triggering any action
https://bugs.kde.org/show_bug.cgi?id=438017 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #22 from Norbert Preining --- I can confirm the same behavior on Debian/unstable with Plasma 5.22.2, Okular 21.04.2, all native (no flatpak or other systems). I tried other viewers (mupdf, calibre ebook, atril) all of which worked without hiccup and much faster. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #6 from Norbert Preining --- Same here on Debian/sid with the packages I plan to upload to Debian. Also, several users confirmed the same behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 438497] Contact import / export does not work
https://bugs.kde.org/show_bug.cgi?id=438497 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #14 from Norbert Preining --- Sorry for the noise, my patch set was incomplete. I can confirm that the MR fixes the issue. THanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #11 from Norbert Preining --- For full details frameworks 5.82 konqueror 21.04.1 qt 5.15.2 plasma 5.21.90 Debian/sid+experimental -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #10 from Norbert Preining --- I tried the mentioned PR on Debian/experimental (21.04.1, frameworks 5.82) and it did *not* fix the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #2 from Norbert Preining --- Indeed, same here on Debian with Plasma 5.21.5, Frameworks 5.82, Gears 21.04 - kiod does not release a claimed USB MTP device and blocks all other devices (in particular Calibre in my case). Killing the kiod process that holds the lock (to be found with fuser /dev/libmtp...) resolves this problem, but is not optimal. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 405344] display does not stay in power save on lock screen
https://bugs.kde.org/show_bug.cgi?id=405344 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 436210] New: tray icon does not show up when started at system startup time
https://bugs.kde.org/show_bug.cgi?id=436210 Bug ID: 436210 Summary: tray icon does not show up when started at system startup time Product: elisa Version: 21.04.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: norb...@preining.info Target Milestone: --- SUMMARY When Elisa is started via the session manager, it does not show a tray icon and is not activatable at all: That means, calling it from the command line as well as from the kick off menu, both does not give any response. STEPS TO REPRODUCE 1. start elisa 2. reboot 3. log in 4. elisa is started and main window is shown 5. click on the close button of the window decoration 6. elisa disappears, no tray icon is shown, but elisa is still running OBSERVED RESULT no way to show elisa main window again: * no tray icon * starting from command line or menu results in no reaction EXPECTED RESULT main window of elisa is shown tray icon is shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable Plasma 5.21.4 Framworks 5.81.0 Qt: 5.15.2 ADDITIONAL INFORMATION I tried the patch from https://bugs.kde.org/show_bug.cgi?id=434560 which improves the situation slightly, but still doesn't make elisa show a tray icon on restart. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432660] QML application crashes when using Breeze style and KColorSchemeManager
https://bugs.kde.org/show_bug.cgi?id=432660 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #4 from Norbert Preining --- The same fix also helped with digikam 7.2.0-rc, where I saw crashes due to colorscheme switches, see https://bugs.kde.org/show_bug.cgi?id=432646 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #18 from Norbert Preining --- Hopefully last comment. Today the breeze git contained the following commit: commit 12e42f014338cce6a6d706a222a2f4af4bbb49b2 (HEAD -> Plasma/5.21, origin/Plasma/5.21) Author: David Redondo Date: Tue Feb 9 08:54:34 2021 + Clean up listener If the style is unloaded for example by an application dynamically switching styles, the listener was still around leading us to call into destroyed objects when the color scheme was changed. BUG:432660 (cherry picked from commit 5de36bd1381b1d755c8f2dd4b95b9758d3225b14) With this commit added to breeze, I can now change to Fusion and stay there and no crashes appear. So I would say, with today's breeze git update the issue can be closed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #17 from Norbert Preining --- Hi I can change the Widget Style to "Fusion" in the setup menu, and the layout changes - no error. Then I close digikam and restart, and it crashes again. Changing manually in digikamrc to Breeze makes it start again. 100% reproducible. So Fusion style should be here I guess, since there is a change in appearance when I select the FUsion widget style, but it fails on startup. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #15 from Norbert Preining --- Ok, I found the culprit. The following trivial change made digikam start up properly: [General Settings] Application Font=Noto Sans CJK JP Light,12,-1,5,25,0,0,0,0,0 -Application Style=fusion +Application Style=breeze Apply Sidebar Changes Directly=false I have no idea why there was "fusion" in there, guess I have selected it back then whenever. Anyway, this should *not* crash digikam ;-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #13 from Norbert Preining --- Ok, I created a new user and tried there - an there it is working. I will debug later on what is going on, but some file configuration file or so is kicking digikam into the off. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #11 from Norbert Preining --- I have now rebuild all of plasma to the current state in git, installed it, recompiled digikam rc on this system, installed it, and still get hit by the same problem. Then I checked the appimage, and that one works. Comparing the versions, I see that: appimage home compiled KDE Framewokrs5.78 5.78 Qt 5.14.2 5.15.2 So I suppose this is either a bug in Qt (5.15) or some incompatibility between digikam and Qt 5.15. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646
--- Comment #10 from Norbert Preining ---
I updated breeze from the state of today's git repo, branch "Plasma/521", but I
still get failures in this code in breeze:
if (ev->propertyName() == colorProperty) {
if (qApp && qApp->property(colorProperty).isValid()) {
auto path = qApp->property(colorProperty).toString();
manager->_config = KSharedConfig::openConfig(path);
} else {
--> manager->_config = KSharedConfig::openConfig();
}
manager->_watcher = KConfigWatcher::create(manager->_config);
The backtrace is now
#0 QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer
(this=0x7fffcdb0, __in_chrg=)
at /usr/include/c++/10/bits/atomic_base.h:333
#1 0x7fffcc1fd361 in
QExplicitlySharedDataPointer::operator= (other=...,
this=)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:226
#2 Breeze::AppListener::eventFilter (this=0x55e43760, watched=, event=)
at ./kstyle/breezetoolsareamanager.cpp:145
#3 0x757e1b46 in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x762a3198 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5 0x757e1f0a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7581715f in QObject::setProperty(char const*, QVariant const&) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x770b0742 in Digikam::ThemeManager::slotChangePalette (
this=0x775af690 )
at ./core/libs/widgets/mainview/thememanager.cpp:133
#8 0x770b0ab0 in Digikam::ThemeManager::setCurrentTheme (
this=0x775af690 , name=...)
at ./core/libs/widgets/mainview/thememanager.cpp:112
#9 0x770b1302 in Digikam::ThemeManager::populateThemeMenu (
this=0x775af690 )
at ./core/libs/widgets/mainview/thememanager.cpp:234
#10 0x77a78ed0 in Digikam::DigikamApp::populateThemes
(this=0x56758200) at ./core/app/main/digikamapp_setup.cpp:1024
#11 0x77a801da in Digikam::DigikamApp::setupActions
(this=this@entry=0x56758200) at ./core/app/main/digikamapp_setup.cpp:796
#12 0x77a6cfad in Digikam::DigikamApp::DigikamApp (this=0x56758200,
__in_chrg=, __vtt_parm=)
at ./core/app/main/digikamapp.cpp:151
#13 0x9e62 in main (argc=, argv=0x7fffd850) at
./core/app/main/main.cpp:355
I don't see anything else that needs updating here, all the other packages
involved, in particular the frameworks, are at the newest version (5.78 for
kconfig and kdelibs4support)
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #6 from Norbert Preining --- Maybe a Plasma 5.20.90 issue? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #5 from Norbert Preining --- Yes, the packages are compiled by me (like all of frameworks, plasma, etc). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #3 from Norbert Preining --- I agree with that, but beta2 didn't crash ;-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 --- Comment #1 from Norbert Preining --- Sorry, now I added debug symbols for the breeze stuff, I get the following backtrace:: Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=0x7fffcde0, __in_chrg=) at /usr/include/c++/10/bits/atomic_base.h:333 333 operator--() noexcept (gdb) bt #0 QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=0x7fffcde0, __in_chrg=) at /usr/include/c++/10/bits/atomic_base.h:333 #1 0x7fffcc1fd421 in QExplicitlySharedDataPointer::operator= (other=..., this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:226 #2 Breeze::AppListener::eventFilter (this=0x55e43e50, watched=, event=) at ./kstyle/breezetoolsareamanager.cpp:152 #3 0x757e1b46 in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x762a3198 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x757e1f0a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7581715f in QObject::setProperty(char const*, QVariant const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x770b0742 in Digikam::ThemeManager::slotChangePalette ( this=0x775af690 ) at ./core/libs/widgets/mainview/thememanager.cpp:133 #8 0x770b0ab0 in Digikam::ThemeManager::setCurrentTheme ( this=0x775af690 , name=...) at ./core/libs/widgets/mainview/thememanager.cpp:112 #9 0x770b1302 in Digikam::ThemeManager::populateThemeMenu ( this=0x775af690 ) at ./core/libs/widgets/mainview/thememanager.cpp:234 #10 0x77a78ed0 in Digikam::DigikamApp::populateThemes (this=0x56703640) at ./core/app/main/digikamapp_setup.cpp:1024 #11 0x77a801da in Digikam::DigikamApp::setupActions (this=this@entry=0x56703640) at ./core/app/main/digikamapp_setup.cpp:796 #12 0x77a6cfad in Digikam::DigikamApp::DigikamApp (this=0x56703640, __in_chrg=, __vtt_parm=) at ./core/app/main/digikamapp.cpp:151 #13 0x9e62 in main (argc=, argv=0x7fffd880) at ./core/app/main/main.cpp:355 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432646] New: digikam 7.2.0-rc crashes on startup (beta2 didn't)
https://bugs.kde.org/show_bug.cgi?id=432646 Bug ID: 432646 Summary: digikam 7.2.0-rc crashes on startup (beta2 didn't) Product: digikam Version: 7.2.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY Crashes on startup STEPS TO REPRODUCE 1. type digikam into the terminal 2. see it crash GDB backtrace (gdb) bt #0 0x7fffcc1b9528 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so #1 0x7fffcc1fd421 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so #2 0x757e1b46 in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x762a3198 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x757e1f0a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7581715f in QObject::setProperty(char const*, QVariant const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x770b0742 in Digikam::ThemeManager::slotChangePalette ( this=0x775af690 ) at ./core/libs/widgets/mainview/thememanager.cpp:133 #7 0x770b0ab0 in Digikam::ThemeManager::setCurrentTheme ( this=0x775af690 , name=...) at ./core/libs/widgets/mainview/thememanager.cpp:112 #8 0x770b1302 in Digikam::ThemeManager::populateThemeMenu ( this=0x775af690 ) at ./core/libs/widgets/mainview/thememanager.cpp:234 #9 0x77a78ed0 in Digikam::DigikamApp::populateThemes (this=0x56729630) at ./core/app/main/digikamapp_setup.cpp:1024 #10 0x77a801da in Digikam::DigikamApp::setupActions (this=this@entry=0x56729630) at ./core/app/main/digikamapp_setup.cpp:796 #11 0x77a6cfad in Digikam::DigikamApp::DigikamApp (this=0x56729630, __in_chrg=, __vtt_parm=) at ./core/app/main/digikamapp.cpp:151 #12 0x9e62 in main (argc=, argv=0x7fffd880) at ./core/app/main/main.cpp:355 SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.13 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 62.8 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432586] Dead zone in the top left corner - cannot activate kickoff
https://bugs.kde.org/show_bug.cgi?id=432586 --- Comment #4 from Norbert Preining --- Thanks, and sorry for the duplication! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432586] New: Dead zone in the top left corner - cannot activate kickoff
https://bugs.kde.org/show_bug.cgi?id=432586 Bug ID: 432586 Summary: Dead zone in the top left corner - cannot activate kickoff Product: plasmashell Version: 5.20.90 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: norb...@preining.info CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If the panel is on top, and has height less than 32px (?) there is a dead zone in the top-left (top edge and left edge) of a few (4?) pixel where the K button does not react to clicks STEPS TO REPRODUCE 1. switch the panel to the top edge 2. reduce the height to 30px 3. disable hotspot in top left corner 4. move the mouse to the top left and click OBSERVED RESULT THe kickoff is NOT activated EXPECTED RESULT The kickoff is activated SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.90 (available in About System) Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.13 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432203] No feedback when audio output is disabled via Icons-Only Task Manager Icon
https://bugs.kde.org/show_bug.cgi?id=432203 --- Comment #2 from Norbert Preining --- Hi Nate, thanks for answering, and suggesting the work-around. For now I will deactivate the indicator - two times talking against a wall of silenced video partners was enough - Fortunately company internal, so not a problem it was ;-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432204] Location of "Places" hinders favorite usage
https://bugs.kde.org/show_bug.cgi?id=432204 --- Comment #1 from Norbert Preining --- Created attachment 135236 --> https://bugs.kde.org/attachment.cgi?id=135236=edit Suggestion mock up -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432204] New: Location of "Places" hinders favorite usage
https://bugs.kde.org/show_bug.cgi?id=432204 Bug ID: 432204 Summary: Location of "Places" hinders favorite usage Product: plasmashell Version: 5.20.90 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: norb...@preining.info CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 135235 --> https://bugs.kde.org/attachment.cgi?id=135235=edit Current status - shadowed favorites SUMMARY If the kickoff menu button is in the lower left (default), activating the new kickoff and then moving diagonally to the grid of favorites often switched to the "Places" because the auto-activating button "Places" is in the mouse path from the kickoff start location to the favorites. In fact, most of the favorites are reachable only via the Places button when going in straight lines, see attached image 1. STEPS TO REPRODUCE 1. activate kickoff by clicking on the start button 2. move diagonally to one of your favorites 3. the mouse pointer moves over the places menu and activates it OBSERVED RESULT Places are activated EXPECTED RESULT Being able to select a favorite SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian/unstable (available in About System) KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The attached image 1 shows that the places button actually shadow about half of the favorites area (area between yellow lines marked with a big yellow X). The activation of the Places button is time dependent (I guess), so the outer corner might not activate it, but I have been hit by this behaviour already many times by now. I suggest (see attached image 2 for a very rough mock-up) (although this might not be possible fro 5.21) moving the Places button vertically on the side of the applications. This would have the following advantages and disadvantages: Advantages * orthogonalization of concern: - move right for logout/sleep/system stuff - move up for apps/places/future stuff - move diagonally for selection. This feels much more natural to me. * area of shadowed favorites greatly reduced (see yellow area in image 2) * open space for additional entries next to Places Disadvantage * again a different layout after the introduction of the new kickoff Thanks for the great KDE/Plasma! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432203] New: No feedback when audio output is disabled via Icons-Only Task Manager Icon
https://bugs.kde.org/show_bug.cgi?id=432203 Bug ID: 432203 Summary: No feedback when audio output is disabled via Icons-Only Task Manager Icon Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: norb...@preining.info CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY It is too easy to disable audio output by accidentally clicking on the loudspeaker part of the icon in the Icons-Only Task Manager, and there is no visual feedback that audio has been disabled. I have been hit by this already a few times during video conferences while giving presentations and switching between windows for sharing. STEPS TO REPRODUCE 1. Click on loudspeaker symbol in the icon 2. Stop hearing audio output OBSERVED RESULT Silence without warning EXPECTED RESULT visual feedback like a OSD coaster telling me that application foobar has been silenced. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian/unstable with KDE 5.20.90 (available in About System) KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431419] Screen locker KCM crashes on destruction in ScreenLockerKcm::~ScreenLockerKcm() after clicking on Appearance button and switching to another KCM
https://bugs.kde.org/show_bug.cgi?id=431419 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431626] The Knetattach dialog is no longer launched from the Dolphin (a required item is missing)
https://bugs.kde.org/show_bug.cgi?id=431626 Norbert Preining changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/commit/33270dd44 ||23eea329b8f20db17f8d70ab7b1 ||08da Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Norbert Preining --- Git commit 33270dd4423eea329b8f20db17f8d70ab7b108da by Norbert Preining. Committed on 18/01/2021 at 22:48. Pushed by ngraham into branch 'release/20.12'. Show button to open knetattach inline with URL nav on remove:// view This is a backport of b1cadeba939155282a9fadf7d7b025d6529c489e From b1cadeba939155282a9fadf7d7b025d6529c489e Mon Sep 17 00:00:00 2001 From: Nate Graham Date: Tue, 15 Dec 2020 23:03:00 -0700 Subject: [PATCH] Show button to open knetattach inline with URL nav on Remote:// view In conjunction with https://invent.kde.org/frameworks/kio/-/merge_requests/260, the net result is to hide the knetattach launcher in the view, and show it inline with Dolphin's URL navigator toolbar when viewing the remote:// view, just like how we add an "Empty Trash" button when viewing trash://. The backport ensures that even with frameworks << 5.78 only one network button is shown. M +61 -0src/dolphinnavigatorswidgetaction.cpp M +19 -1src/dolphinnavigatorswidgetaction.h https://invent.kde.org/system/dolphin/commit/33270dd4423eea329b8f20db17f8d70ab7b108da -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379474] KScreen wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 431580] mobilebroadbandsettings not responsive, CPU 100%
https://bugs.kde.org/show_bug.cgi?id=431580 --- Comment #1 from Norbert Preining --- I forgot to mention (but this is somehow implied), that plasma-nm was compiled with -DBUILD_MOBILE=true -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 431580] New: mobilebroadbandsettings not responsive, CPU 100%
https://bugs.kde.org/show_bug.cgi?id=431580 Bug ID: 431580 Summary: mobilebroadbandsettings not responsive, CPU 100% Product: plasma-nm Version: 5.20.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: norb...@preining.info Target Milestone: --- SUMMARY Selecting the "Mobile broadband" entry in the settings application, or starting it directly with systemsettings5 mobilebroadbandsettings results in 100% CPU on one core, and no output/display is generated. STEPS TO REPRODUCE 1. systemsettings5 mobilebroadbandsettings OBSERVED RESULT The same set of error messages is shown repeatedly (until interrupted): file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:591:5: QML ColumnView: possible QQuickItem::polish() loop file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:591:5: QML ColumnView: ColumnView called polish() inside updatePolish() of ColumnView Nothing is displayed EXPECTED RESULT Display of mobile settings, or a warning that this is not supported on the current device. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.7 OS Type: 64-bit ADDITIONAL INFORMATION I tried it on two computers, one laptop and one desktop, both not having a WWAN interface. I expected an empty display, or a comment no WWAN available, but nothing was displayed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422177] New Users kcm doesn't set user avatar as expected
https://bugs.kde.org/show_bug.cgi?id=422177 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Crash inKFileItemModel::removeItems() when using the tree view mode of the details view
https://bugs.kde.org/show_bug.cgi?id=422282 --- Comment #28 from Norbert Preining --- I can confirm that reverting ac234a9c55aed509b385ef03835a6d0f563e6a22 fixes the crashes for me! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Crash when using the tree view mode of the details view
https://bugs.kde.org/show_bug.cgi?id=422282 --- Comment #15 from Norbert Preining --- PS: that is Debian/unstable running with qt 5.14 (from Debian), frameworks and dolphin compiled by me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Crash when using the tree view mode of the details view
https://bugs.kde.org/show_bug.cgi?id=422282 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #14 from Norbert Preining --- Created attachment 132742 --> https://bugs.kde.org/attachment.cgi?id=132742=edit valgrind output of double free crash of dolphin I see a similar behavior (double free) with dolphin 20.08.2 on frameworks 5.75 when opening and closing a directory using the > sign in tree view, and the directory has lots of entries (in my case /usr/bin). The stack trace is 4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7fc544b00537 in __GI_abort () at abort.c:79 #6 0x7fc544b596c8 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fc544c67e31 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #7 0x7fc544b609ba in malloc_printerr (str=str@entry=0x7fc544c6a1a8 "double free or corruption (fasttop)") at malloc.c:5347 #8 0x7fc544b61cb5 in _int_free (av=0x7fc544c99b80 , p=0x55812010e160, have_lock=0) at malloc.c:4266 #9 0x7fc544a27959 in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #10 0x7fc544a33146 in KFileItemModel::setExpanded(int, bool) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 I did run it with valgrind dolphin 2>&1 | tee valgrind.log and attach the output. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 420074] DJVU thumbnailer crashes kdeinit
https://bugs.kde.org/show_bug.cgi?id=420074 --- Comment #9 from Norbert Preining --- Ok, I sent a merge request for this code. When it is merged, this bug can be closed, but for now it is still valid. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 420074] DJVU thumbnailer crashes kdeinit
https://bugs.kde.org/show_bug.cgi?id=420074 --- Comment #7 from Norbert Preining --- (In reply to Martin Mirchev from comment #6) > Sorry, making it a dependency would be a best option but I do not really > know how many people use Djvu these days so it may come as extra bloat > for some people. Well, the correct solution is to use _exit(1); instead of exit(1); because the normal exit(1) triggers the atexit registered functions to be executed, and that is not what we want (and crashed kdeinit5). I can confirm that with _exit(1) instead all works as expected - just that there are no thumbnails available, well, also this is expected. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 420074] DJVU thumbnailer crashes kdeinit
https://bugs.kde.org/show_bug.cgi?id=420074 --- Comment #5 from Norbert Preining --- (In reply to Martin Mirchev from comment #4) > Okay, so this means it can be added as general info for the tooltip right? Not sure what you mean with "tooltip", I see two options: - either make ddjvu binary a hard dependency via CMakeFile - fix the code that it does not crash (not call exit) if ddjvu is not available Both are possible solutions, but the current state is sub-optimal. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 420074] DJVU thumbnailer crashes kdeinit
https://bugs.kde.org/show_bug.cgi?id=420074 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #3 from Norbert Preining --- I just realized that this is simply because `ddjvu` the program is not available. This means that in the pid==0 case the execvp fails and drops down to the exit(1). On my system, where I had the same problem, a simple installation of djvulibre-bin package fixed the crashes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 --- Comment #30 from Norbert Preining --- No, with my 5.19.3 packages I cannot reproduce this anymore. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 --- Comment #6 from Norbert Preining --- One more comment: it seems to be a problem with kcm_translations! If I remove/rename the kcm_translations.so module, then systemsettings5 does NOT crash, shows a missing module warning in the Translation tab, but the others can be used. This reduces the culprit considerably I think. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 --- Comment #5 from Norbert Preining --- Created attachment 127041 --> https://bugs.kde.org/attachment.cgi?id=127041=edit kcrash save Debian/sid -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419008] Always crash in Regional Setting within System Settings
https://bugs.kde.org/show_bug.cgi?id=419008 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #4 from Norbert Preining --- Just to chime in, same here on home-compiled packages on Debian/sid. I am using en_US as locale, so it is not depending on that. I tried to start each kcm manually, which worked, but loading it from the systemsettings5 application failed. (Loop over all modules given by kcmshell5 --list and start the manually ... that is all fine!) Any help would be appreciated. I add the crash report I got. -- You are receiving this mail because: You are watching all bug changes.
