[kwin] [Bug 480171] With 225% scale on a 4k screen, right-side-tiled windows and full-screen video/image content are not fully adjacent to right screen edge
https://bugs.kde.org/show_bug.cgi?id=480171 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #31 from Xwang --- Created attachment 170061 --> https://bugs.kde.org/attachment.cgi?id=170061&action=edit Issue visible on internal monitor of dell latitude 9330 As you can see from the attached images, I feel I'm facing the same (or at least similar issue), but I'm not sure because the internal screen is 2560x1600, it uses 160% scale and the panel is 64px. So dividing the sizes by 1.6, the pixel number is integer both for the whole screen, and the panel and Konsole areas. Once I remove the height of the panel, the Konsole window measures (2560x1536) which divided by 1.6 gives an integer 1600x960 once the scaling is applied. The panel itself measures (2560x64) which give a scaled dimension of 1600x40 once scaling is applied. So I do not understand why I still see the issue. Is there anything else I should consider? My system is the following: Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488246] New: maliit does not change layout when I change keyboard layout in the plasma environment
https://bugs.kde.org/show_bug.cgi?id=488246 Bug ID: 488246 Summary: maliit does not change layout when I change keyboard layout in the plasma environment Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: xwaang1...@gmail.com CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY The maliit virtual keyboard does not change layout when I change keyboard layout in the plasma environment STEPS TO REPRODUCE 1. Install and activate maliit 2. Change keyboard layout OBSERVED RESULT Maliit keyboard remains unmodified, only the physical keyboard changes to the layout specified EXPECTED RESULT Maliit keyboard should change to the specified layout. If it is not available a popup notice should higlight the need to install or create a proper one. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484833] New: Small lines appears below the panel and on the left side
https://bugs.kde.org/show_bug.cgi?id=484833 Bug ID: 484833 Summary: Small lines appears below the panel and on the left side Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- Created attachment 167994 --> https://bugs.kde.org/attachment.cgi?id=167994&action=edit Screenshot showing the issue SUMMARY A thin line 'one or two pixel wide and with changing colors) appears below the panel and on the right side STEPS TO REPRODUCE 1. Execute plasma with wayland OBSERVED RESULT A thin line appears below the panel and on the right side EXPECTED RESULT These lines should not exist SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 ADDITIONAL INFORMATION The issue appeared with Plasma 6.0 The panel floating is disabled. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484833] Small lines appears below the panel and on the left side
https://bugs.kde.org/show_bug.cgi?id=484833 --- Comment #2 from Xwang --- (In reply to fanzhuyifan from comment #1) > Are you using fractional scaling? Possible duplicate of BUG 480171. Yes, I'm using 150% fractional scaling with a screen which has physical dimension equal to 2560x1600 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484833] Small lines appears below the panel and on the left side
https://bugs.kde.org/show_bug.cgi?id=484833 --- Comment #3 from Xwang --- (In reply to Xwang from comment #2) > (In reply to fanzhuyifan from comment #1) > > Are you using fractional scaling? Possible duplicate of BUG 480171. > > Yes, I'm using 150% fractional scaling with a screen which has physical > dimension equal to 2560x1600 I've changed to 160% (that is still fine) and the issue disappeared. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485146] New: kscreen-doctor output cannot be easily used in bash scripts anymore
https://bugs.kde.org/show_bug.cgi?id=485146 Bug ID: 485146 Summary: kscreen-doctor output cannot be easily used in bash scripts anymore Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY Kscreen-doctor -o output has changed in a way that makes it easier to read for a human, but more difficult to integrate in bash scripts. Before I was able to get the names of external and internal monitors using these bash script lines: TMP_EXT_MONITOR_NAME=$(kscreen-doctor -o | grep 'DisplayPort' | grep connected | cut -d ' ' -f 3) TMP_INT_MONITOR_NAME=$(kscreen-doctor -o | grep 'Panel' | grep connected | cut -d ' ' -f 3) echo "Internal monitor is: $TMP_INT_MONITOR_NAME" echo "External monitor is: $TMP_EXT_MONITOR_NAME" because each output information was in a single line. Now the information of every monitor are split in multiple lines. STEPS TO REPRODUCE 1. Execute the four bash script lines above 2. Read the displayed names OBSERVED RESULT It is not possible to read display names EXPECTED RESULT Before it was possible to read display names because all display nformations where on the same line SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.2-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 ADDITIONAL INFORMATION Is it possible to add a command line option to obtain the previous output format? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487123] New: Dolphin crashes on file copy
https://bugs.kde.org/show_bug.cgi?id=487123 Bug ID: 487123 Summary: Dolphin crashes on file copy Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: xwaang1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.02.2) Qt Version: 6.7.0 Frameworks Version: 6.2.0 Operating System: Linux 6.8.9-arch1-2 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: Cutting files from a folder to the parent one, dolphin sometimes crashes. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [New LWP 499805] [New LWP 499806] [New LWP 499820] [New LWP 499807] [New LWP 499830] [New LWP 499819] [New LWP 499877] [New LWP 499821] [New LWP 499834] [New LWP 499837] [New LWP 499838] [New LWP 499843] [New LWP 499876] [New LWP 499822] [New LWP 499831] [New LWP 499832] [New LWP 499835] [New LWP 499808] [New LWP 499809] [New LWP 499836] [New LWP 499810] [New LWP 499868] [New LWP 499879] [New LWP 499878] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/dolphin'. Program terminated with signal SIGABRT, Aborted. #0 0x74ff53f92e44 in ?? () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x74ff4c8eeec0 (LWP 499805))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x74ff4c8eeec0 (LWP 499805))] Thread 24 (Thread 0x74ff220006c0 (LWP 499878)): #0 0x74ff53f8d4e9 in ??? () at /usr/lib/libc.so.6 #1 0x74ff53f90242 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #2 0x74ff52abef68 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt6Core.so.6 #3 0x74ff52ac0161 in ??? () at /usr/lib/libQt6Core.so.6 #4 0x74ff52abb619 in ??? () at /usr/lib/libQt6Core.so.6 #5 0x74ff53f90ded in ??? () at /usr/lib/libc.so.6 #6 0x74ff540140dc in ??? () at /usr/lib/libc.so.6 Thread 23 (Thread 0x74ff216006c0 (LWP 499879)): #0 0x74ff53f8d4e9 in ??? () at /usr/lib/libc.so.6 #1 0x74ff53f90242 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #2 0x74ff52abef68 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt6Core.so.6 #3 0x74ff52ac0161 in ??? () at /usr/lib/libQt6Core.so.6 #4 0x74ff52abb619 in ??? () at /usr/lib/libQt6Core.so.6 #5 0x74ff53f90ded in ??? () at /usr/lib/libc.so.6 #6 0x74ff540140dc in ??? () at /usr/lib/libc.so.6 Thread 22 (Thread 0x74ff28a006c0 (LWP 499868)): #0 0x74ff53f8d4e9 in ??? () at /usr/lib/libc.so.6 #1 0x74ff53f90242 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #2 0x74ff52abef68 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt6Core.so.6 #3 0x74ff52ac0161 in ??? () at /usr/lib/libQt6Core.so.6 #4 0x74ff52abb619 in ??? () at /usr/lib/libQt6Core.so.6 #5 0x74ff53f90ded in ??? () at /usr/lib/libc.so.6 #6 0x74ff540140dc in ??? () at /usr/lib/libc.so.6 Thread 21 (Thread 0x74ff494006c0 (LWP 499810)): #0 0x74ff53f8d4e9 in ??? () at /usr/lib/libc.so.6 #1 0x74ff53f8fed9 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x74ff41e9891e in ??? () at /usr/lib/dri/iris_dri.so #3 0x74ff41e766cc in ??? () at /usr/lib/dri/iris_dri.so #4 0x74ff41e9884d in ??? () at /usr/lib/dri/iris_dri.so #5 0x74ff53f90ded in ??? () at /usr/lib/libc.so.6 #6 0x74ff540140dc in ??? () at /usr/lib/libc.so.6 Thread 20 (Thread 0x74ff2b2006c0 (LWP 499836)): #0 0x74ff53f8d4e9 in ??? () at /usr/lib/libc.so.6 #1 0x74ff53f90242 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #2 0x74ff52abef68 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt6Core.so.6 #3 0x74ff52ac0161 in ??? () at /usr/lib/libQt6Core.so.6 #4 0x74ff52abb619 in ??? () at /usr/lib/libQt6Core.so.6 #5 0x74ff53f90ded in ??? () at /usr/lib/libc.so.6 #6 0x74ff540140dc in ??? () at /usr/lib/libc.so.6 Thread 19 (Thread 0x74ff49e006c0 (LWP 499809)): #0 0x74ff53f8d4e9 in ??? () at /usr/lib/libc.so.6 #1 0x74ff53f8fed9 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x74ff41e9891e in ??? () at /usr/lib/dri/iris_dri.so #3 0x74ff41e766cc in ??? () at /usr/lib/dri/iris_dri.so #4 0x74ff41e9884d in ??? () at /usr/lib/dri/iris_dri.so #5 0x74ff53f90ded in ??? () at /usr/lib/libc.so.6 #6 0x74ff540140dc in ??? () at /usr/lib/libc.so.6 Thread 18 (Thread 0x74ff4aa006c0 (LWP 499808)): #0 0x74ff5400639d in poll () at /usr/lib/libc.so.6 #1 0x74ff50487ce8 in ??? () at /usr/lib/libQt6WaylandClient.so.6 #2 0x74ff52abb619 in ??? () at /usr/lib/libQt6Core.so.6 #3
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #41 from Xwang --- (In reply to Fabio from comment #37) > I just created a merge request that fixes this bug for me. > It would be nice if someone could confirm if this is working. > > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1039 Is there any howto which explains how I can test your merge? I'm using archlinux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #44 from Xwang ---
(In reply to Domker from comment #43)
> (In reply to Xwang from comment #41)
> > (In reply to Fabio from comment #37)
> > > I just created a merge request that fixes this bug for me.
> > > It would be nice if someone could confirm if this is working.
> > >
> > > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1039
> >
> > Is there any howto which explains how I can test your merge?
> > I'm using archlinux.
>
> Live swapping files is the worst possible way to patch something!!
>
>
> $patch -d "plasma-workspace-5.22.5" -p1 < 1039.patch
>
> (plasma-workspace-5.22.5 - direcotry with source code of plasma-workspace)
>
> patching file applets/devicenotifier/package/contents/ui/DeviceItem.qml
> Hunk #1 FAILED at 31.
> Hunk #2 succeeded at 123 (offset 4 lines).
> Hunk #3 succeeded at 140 (offset 4 lines).
> Hunk #4 FAILED at 189.
> Hunk #5 succeeded at 233 (offset 4 lines).
> Hunk #6 FAILED at 250.
> 3 out of 6 hunks FAILED -- saving rejects to file
> applets/devicenotifier/package/contents/ui/DeviceItem.qml.rej
> patching file applets/devicenotifier/package/contents/ui/devicenotifier.qml
> Hunk #1 succeeded at 88 (offset 13 lines).
> Hunk #2 succeeded at 112 (offset 13 lines).
>
> !! It FAILED becouse patch is for plasma-workspace v5.23, not v5.22.5 !!
>
> >>> You need make own patch file based on differences in "ui" direcotry:
>
> 1. Make new directory:
> $ mkdir test_build && cd "$_"
>
> 2. Clone source package master repo where patch is merged:
> $ git clone https://invent.kde.org/plasma/plasma-workspace.git
>
> 3. Rename it to "b":
> $ mv plasma-workspace b
>
> 4. Download (and extract) source code plasma-workspace (current version)
> present in Arch Linux, rename directory to "a":
> $ wget
> "https://download.kde.org/stable/plasma/5.22.5/plasma-workspace-5.22.5.tar.
> xz" -qO - | tar xvJ
> $ mv plasma-workspace-5.22.5 a
>
> 5. Now you have directory "a" with current source code (plasma-workspace in
> Arch Linux) and direcotry "b" with merged patch. Make own custom.patch with
> differences in "ui" directories:
>
> $ diff -ur a/applets/devicenotifier/package/contents/ui
> b/applets/devicenotifier/package/contents/ui > custom.patch
>
> If You have now "custom.patch" file, remove "a" and "b" directories:
> $ rm -rf a b
>
> >>> Now you need build own patched package "plasma-workspace-5.22.5":
>
> 1. Go to:
> https://github.com/archlinux/svntogit-packages/tree/packages/plasma-
> workspace/trunk and download "PKGBUILD", "kde.pam" files, for quick download
> use this:
>
> $ wget
> "https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/
> plasma-workspace/trunk/PKGBUILD" && wget
> "https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/
> plasma-workspace/trunk/kde.pam"
>
> 2. Edit "PKGBUILD" file:
> source=(https://download.kde.org/stable/plasma/$pkgver/$pkgbase-$pkgver.tar.
> xz{,.sig} kde.pam
>
> https://invent.kde.org/plasma/plasma-workspace/-/commit/6379d1ec.patch)
>
> REPLACE WITH:
>
> source=(https://download.kde.org/stable/plasma/$pkgver/$pkgbase-$pkgver.tar.
> xz{,.sig} kde.pam
>
> https://invent.kde.org/plasma/plasma-workspace/-/commit/6379d1ec.patch
> custom.patch)
>
> AND:
> prepare() {
> patch -d $pkgbase-$pkgver -p1 < 6379d1ec.patch # Fix power management
> inhibition
> }
>
> REPLACE WITH:
> prepare() {
> patch -d $pkgbase-$pkgver -p1 < 6379d1ec.patch # Fix power management
> inhibition
> patch -d $pkgbase-$pkgver -p1 < custom.patch
> }
>
>
>
> SAVE CHANGES in PKGBUILD FILE!
>
> 3. Update checksums in PKGBUILD:
> $ updpkgsums PKGBUILD
>
>
> 3. Now build and install patched "plasma-workspace" package:
> $ makepkg -sri --skippgpcheck PKGBUILD
>
> #option -s (download and install dependencies)
> #option -r (remove dependency after successful package build, in this case:
> pps-tools-1.0.2-1 gpsd-3.23-1 plasma-wayland-protocols-1.4.0-1)
> #option -i (install the package if it has been built)
>
> After installing the package restart your PC. For me, a patch made in this
> way works.
>
> If something doesn't work, just force reinstall plasma-workspace from the
> repository.
> ( sudo rm
> /var/cache/pacman/pkg/plasma-workspace-5.22.5-2-x86_64.pkg.tar.zst{,.sig} &&
> sudo pacman -S plasma-workspace )
Thank you!
I'll try do that next weekend.
Anyway the bug will be in any case fixed when plasma-workspace-5.23 will be
available. Is it correct?
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-solid] [Bug 438478] Device notifier shows SD card being inserted only once
https://bugs.kde.org/show_bug.cgi?id=438478 --- Comment #13 from Xwang --- I still have the issue with kde-applications 21.04.3-1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439838] New: Customize position of "Find text"
https://bugs.kde.org/show_bug.cgi?id=439838 Bug ID: 439838 Summary: Customize position of "Find text" Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY I would like to customize okular so that the "find text" box is opened at the upper part of the window (just below the menu) and not at the lower part of the window. STEPS TO REPRODUCE 1. Open a document with okular 2. Press Ctrl+F to look for something in the text OBSERVED RESULT The "find text" box is opened at the lowest part of the okular window EXPECTED RESULT I should be possible to customize the position giving the user the possibility to open the find text box in the upper part of the window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian testing (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION I'm using okular in a debian powered touchscreen tablet configured in portrait mode and using xcfe. When I have to write something in the "find text" box, it is covered by the virtual keyboard. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439838] Customize position of "Find text"
https://bugs.kde.org/show_bug.cgi?id=439838 Xwang changed: What|Removed |Added Platform|Other |Debian testing CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439838] Customize position of "Find text"
https://bugs.kde.org/show_bug.cgi?id=439838 --- Comment #2 from Xwang --- (In reply to Nate Graham from comment #1) > Just like in Konsole, huh? Yes -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 429735] kscreenlock appears only on the external monitor after lid is opened
https://bugs.kde.org/show_bug.cgi?id=429735 --- Comment #2 from Xwang --- (In reply to Nate Graham from comment #1) > Can you try again on Plasma 5.22? Some multi-screen improvements were merged > which may have fixed this. It seems to be fixed in with Plasma 5.22. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 438478] Device notifier shows SD card being inserted only once
https://bugs.kde.org/show_bug.cgi?id=438478 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #6 from Xwang --- I have the same issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 438478] Device notifier shows SD card being inserted only once
https://bugs.kde.org/show_bug.cgi?id=438478 --- Comment #8 from Xwang --- (In reply to Oded Arbel from comment #7) > (In reply to MikeC from comment #4) > > The same issue occurs for plugging in an external usb drive - the system > > tray popup window only offers to mount it once - no other usb drive is > > offered a mount once a drive has been umounted via the right click menu > > option from the dolphin drive list. > > If you are talking about seeing a mount option for a device that was just > "ejected", then that is an old behavior - IIRC Plasma always ignored drives > that were just ejected: you have to physically disconnect it and reconnect > for it to show again. > > This report is that for SD cards, even taking them out of the slot and > putting them back it, won't show the mount option. And I can't reproduce > this with USB thumb drive - these work for me by taking them out and > plugging them back in. Up to some weeks ago, at least on my archlinux system, the sdcard was displayed and ready to be mounted again when I unmounted it without disconnecting it. IMHO this is the correct behaviour. You can unmount a device, but if it is still present, device notifier should show it and should permit to remount again. Both for sd card and USB. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 429735] kscreenlock appears only on the external monitor after lid is opened
https://bugs.kde.org/show_bug.cgi?id=429735 Xwang changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Xwang --- Plasma 5.22 works correctly. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 428172] Calendars disabled at startup and missed alerts
https://bugs.kde.org/show_bug.cgi?id=428172 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 428172] New: Calendars disabled at startup and missed alerts
https://bugs.kde.org/show_bug.cgi?id=428172 Bug ID: 428172 Summary: Calendars disabled at startup and missed alerts Product: kalarm Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: djar...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY With the latest 3.0.2 archlinux package, calendars are disabled at startup. So it is necessary to manually activate them after every boot in order to avoid missing alarms. STEPS TO REPRODUCE 1. Activate the calendar and insert an alarm 2. Reboot the PC 3. Activate kalarm with the --tray option at startup OBSERVED RESULT The calendars are disabled and the alarms do not appear EXPECTED RESULT The calendars should be enabled (the same state they were before shuting down the pc or rebooting it) and the alarms should work correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux 64 bit (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION kalarm is automatically run at startup using the following command: kalarm --tray -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477205] New: Maliit opens when tapping on the panel app menu
https://bugs.kde.org/show_bug.cgi?id=477205 Bug ID: 477205 Summary: Maliit opens when tapping on the panel app menu Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY Maliit opens when tapping on the panel app menu STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477205] Maliit opens when tapping on the panel app menu launcher
https://bugs.kde.org/show_bug.cgi?id=477205 Xwang changed: What|Removed |Added Summary|Maliit opens when tapping |Maliit opens when tapping |on the panel app menu |on the panel app menu ||launcher CC||xwaang1...@gmail.com --- Comment #1 from Xwang --- Maliit opens when tapping on the panel app menu launcher STEP TO REPRODUCE: 1) enable maliit on a touchscreen device 2) in tablet mode tap on the menu laucher in the panel OBSERVED RESULT: Maliit opens EXPECTED RESULT Maliit should automatically open only when tapping on text input area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Session is Wayland of course PS sorry for the incomplete first opening report -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477207] New: Missing option to manually open and close maliit
https://bugs.kde.org/show_bug.cgi?id=477207 Bug ID: 477207 Summary: Missing option to manually open and close maliit Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY There is no option to disable the automatic opening of maliit and replace it with a simple icon in the tray bar that opens maliit when pressed and closed it again when pressed again. the user knows when the keyboard is needed so giving that opportunity will avoid unwanted opening of the keyboard STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477207] Missing option to manually open and close maliit
https://bugs.kde.org/show_bug.cgi?id=477207 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465837] GUI to configure Maliit virtual keyboard
https://bugs.kde.org/show_bug.cgi?id=465837 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477205] Maliit opens when tapping on the panel app menu launcher
https://bugs.kde.org/show_bug.cgi?id=477205 --- Comment #3 from Xwang --- Created attachment 163639 --> https://bugs.kde.org/attachment.cgi?id=163639&action=edit Menu applet (the one at the far left of the panel) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477205] Maliit opens when tapping on the panel app menu launcher
https://bugs.kde.org/show_bug.cgi?id=477205 --- Comment #4 from Xwang --- (In reply to Nate Graham from comment #2) > Which panel app menu? Can you attach a screenshot of it? I've added the attachment. It is the one at the far left of the panel to open application using a menu ... -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 476423] New: Caveau tray icon doesn't change when vault is unlocked
https://bugs.kde.org/show_bug.cgi?id=476423 Bug ID: 476423 Summary: Caveau tray icon doesn't change when vault is unlocked Classification: Plasma Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY The "Caveau" tray icon that permits to unlock and lock plasma's vaults does not change when a vault is unocked. When at least one vault is unlocked the icon in the tray should changes to highlight that to the user. STEPS TO REPRODUCE 1. Unlock a vault 2. Observe the tray icon 3. Lock it again 4. Observe the icon again OBSERVED RESULT The tray icon is always the same EXPECTED RESULT The tray icon shows somehow (open lock or different color) that at least one vault is open (in a similar way as the USB tray icon changes when a device is plugged) SOFTWARE/OS VERSIONS Linux: Archlinux 64bit (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 2.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 476423] Caveau tray icon doesn't change when vault is unlocked
https://bugs.kde.org/show_bug.cgi?id=476423 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 429735] New: kscreenlock appears only on the external monitor after lid is opened
https://bugs.kde.org/show_bug.cgi?id=429735 Bug ID: 429735 Summary: kscreenlock appears only on the external monitor after lid is opened Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: xwaang1...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY kscreenlock appears only on the external monitor after lid is opened STEPS TO REPRODUCE 1. Use a laptop with an external monitor connected and with the external monitor set at the left of the internal one 2. Set the action to be taken on lid close to "Lock the session" in the energy management 3. Close the laptop lid 4. Reopen the laptop lid OBSERVED RESULT Closing the lid the internal monitor is shut down by the laptop firmware and the external monitor is locked. Opening the lid kscreenlock appears only on the external monitor, the laptop monitor is completely black and I can see only the mouse pointer on it. When I insert the password nothing changes on the external monitor and if I blindly insert the correct password, I can login. EXPECTED RESULT As happens if I lock the screen with the Ctrl+Alt+L, kscreenlock should appear on both screens and when I click to insert the password, the password field should be activated only on the screen where the mouse pointer is and typing the password a dot should be added for each character only on that screen. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION My laptop is an Asus n752vx with an external monitor connected using an hdmi cable. PS my pc is set to use the Italia languange so I am not sure that "Lock the session" is how it is written in English. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 429735] kscreenlock appears only on the external monitor after lid is opened
https://bugs.kde.org/show_bug.cgi?id=429735 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 493127] New: Kmymoney does not respect the number and currency settings of KDE
https://bugs.kde.org/show_bug.cgi?id=493127 Bug ID: 493127 Summary: Kmymoney does not respect the number and currency settings of KDE Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY I want to have both numbers and currencies use the dot as decimal separator and with no thousand separators. So In the KDE system setting, I've set both numbers and currency to use the C format. Indeed locale returns: LANG=it_IT.UTF-8 LC_CTYPE="it_IT.UTF-8" LC_NUMERIC=C LC_TIME="it_IT.UTF-8" LC_COLLATE="it_IT.UTF-8" LC_MONETARY=C LC_MESSAGES="it_IT.UTF-8" LC_PAPER="it_IT.UTF-8" LC_NAME="it_IT.UTF-8" LC_ADDRESS="it_IT.UTF-8" LC_TELEPHONE="it_IT.UTF-8" LC_MEASUREMENT="it_IT.UTF-8" LC_IDENTIFICATION="it_IT.UTF-8" LC_ALL= After that opening Kmymoney I can see that it uses the dot as decimal separator, but it stiil uses the comma as thousand separator. STEPS TO REPRODUCE 1. Set up number and currency in KDE to use the C format 2. Restart the PC and assure that locale is correctly configured 3. Start Kmymoney OBSERVED RESULT Numbers use the dot as decimal separator and comma as thousand separator EXPECTED RESULT Numbers should use the dot as decimal separator and should have no thousand separators SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 489971] New: Filelight wrongly computes space occupied by backintime snapshots
https://bugs.kde.org/show_bug.cgi?id=489971 Bug ID: 489971 Summary: Filelight wrongly computes space occupied by backintime snapshots Classification: Applications Product: filelight Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: xwaang1...@gmail.com CC: martin.sandsm...@kde.org Target Milestone: --- Created attachment 171498 --> https://bugs.kde.org/attachment.cgi?id=171498&action=edit Filelight output SUMMARY Filelight wrongly computes space occupied by backintime snapshots STEPS TO REPRODUCE 1. Execute filelight on a folder containing multiple backintime snapshots 2. Wait for filelight computation 3. Compare filelight space with hdd or sdd maximum space OBSERVED RESULT Filelight computes a space bigger than reality (probably summing the space of each file even though they are all pointing to the same file because it has not been changed between snapshots) EXPECTED RESULT Filelight should compute only the space really occupied on the hdd 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.
[filelight] [Bug 489971] Filelight wrongly computes space occupied by backintime snapshots
https://bugs.kde.org/show_bug.cgi?id=489971 --- Comment #1 from Xwang --- Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 489971] Filelight wrongly computes space occupied by backintime snapshots
https://bugs.kde.org/show_bug.cgi?id=489971 --- Comment #2 from Xwang --- Created attachment 171499 --> https://bugs.kde.org/attachment.cgi?id=171499&action=edit The hdd is smaller than the space claimed as occupied by filelight !!! -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 489971] Filelight wrongly computes space occupied by backintime snapshots
https://bugs.kde.org/show_bug.cgi?id=489971 --- Comment #4 from Xwang --- (In reply to Harald Sitter from comment #3) > It's my understanding that this information isn't available outside btrfs > specific ioctl commands (those would only work as root). So that is expected > behavior on btrfs. I guess you could complain to the kernel folks about not > providing suitable API for getting the real/compressed/occupied size of a > file. > > e.g. on windows we can easily tell if a file is sparse, unpinned (not > present on disk -- e.g. only available in the cloud), and then obtain the > compressed size (the size on disk). > > https://invent.kde.org/utilities/filelight/-/blob/ > cbc765ec2f23766f8f76a06d5f7753853a9d5127/src/windowsWalker.cpp Sorry I do not understand, how it is possible that going to Properties of the folder in Dolphin the space occupied by the same folder is correctly computed (as cleary shown on the second attached image)? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 489971] Filelight wrongly computes space occupied by backintime snapshots
https://bugs.kde.org/show_bug.cgi?id=489971 --- Comment #5 from Xwang --- Created attachment 171502 --> https://bugs.kde.org/attachment.cgi?id=171502&action=edit Space correctly computed by dolphin -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 489971] Filelight wrongly computes space occupied by backintime snapshots
https://bugs.kde.org/show_bug.cgi?id=489971 --- Comment #8 from Xwang --- (In reply to Harald Sitter from comment #7) > Oh BTW, there is also a visual design problem here. > > Say you have the directory @0 that looks like this: > > @0 > ├── bar > ├── foo > └── meow > > Let's further assume there is a reflinked copy @1 and a reflinked copy @2 of > @1. > > @1 has bar modified. > @2 has bar modified from @1. @2 also has foo modified. > > i.e. bar is unique in all 3. foo is unique in @2 but shared in @0 and @1. > meow is shared in all 3. > > How do you visualize that? Ok, I understand that it is not considered a bug for filelight, however as a user I found the output of filelight misleading. For example du or gnome's baobab both report measures in line with dolphin's one which IMHO seems more in line with what the user is looking for (namely a quick and maybe crude visualization of space occupied by folders). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409258] New: Okular crashes opening PDF document, version 1.7
https://bugs.kde.org/show_bug.cgi?id=409258 Bug ID: 409258 Summary: Okular crashes opening PDF document, version 1.7 Product: okular Version: 1.7.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY Okular crashes opening PDF document, version 1.7 STEPS TO REPRODUCE 1. try to open a PDF file version 1.7 OBSERVED RESULT Okular crashes immediately. The file is not opened. EXPECTED RESULT The file is opened correctly as happens with epdfview on the same pc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 (compiled with 5.12.3) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409258] Okular crashes opening PDF document, version 1.7
https://bugs.kde.org/show_bug.cgi?id=409258 --- Comment #2 from Xwang --- Your command does not return nothing so I think it is not cryptographically signed even thought I thought it was because if I divide the document with pdfsam in order to have a file for each page I get two strange results: 1)Okular opens the files generated by pdfsam even though they are version 1.7 2)the file which contains the first page of the original document says it is digitally signed even though your test keep saying nothing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] New: Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 Bug ID: 413018 Summary: Plasma crashes and restarts when doing nothing Product: plasmashell Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: xwaang1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-arch1-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Nothing, the pc was on, but I was watching TV - Unusual behavior I noticed: Plasma crashed, the panel disappeared, then plasma restarted and the panel was automatically on again. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff205476c80 (LWP 793))] Thread 9 (Thread 0x7ff1d78ff700 (LWP 1034)): #0 0x7ff2095aec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff20a0bd660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff20a0bd752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff20bd42dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff20bd4305e in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff20a0b75b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff2095a84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff209d412d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7ff1e4977700 (LWP 993)): #0 0x7ff2095aec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff20a0bd660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff20a0bd752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff20bd42dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff20bd4305e in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff20a0b75b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff2095a84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff209d412d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7ff1e5830700 (LWP 986)): #0 0x7ff209d3242c in read () at /usr/lib/libc.so.6 #1 0x7ff2083d59f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff208423a41 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7ff208425128 in () at /usr/lib/libglib-2.0.so.0 #4 0x7ff208425251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7ff20a2dda1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff20a2844ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7ff20a0b6385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7ff1e624113b in KCupsConnection::run() () at /usr/lib/libkcupslib.so #9 0x7ff20a0b75b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7ff2095a84cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7ff209d412d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7ff1efb01700 (LWP 980)): #0 0x7ff208424a5e in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7ff2084250a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff208425251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff20a2dda1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff20a2844ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff20a0b6385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff20bcb76eb in () at /usr/lib/libQt5Quick.so.5 #7 0x7ff20a0b75b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7ff2095a84cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7ff209d412d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7ff1ef300700 (LWP 975)): #0 0x7ff2095aec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff20a0bd660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff20a0bd752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff20bd42dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff20bd4305e in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff20a0b75b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff2095a84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff209d412d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7ff202561700 (LWP 944)): #0 0x7ff209d369ef in poll () at /usr/lib/libc.so.6 #1 0x7ff208425180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff208425251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #2 from Xwang --- Yes, I am. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #3 from Xwang --- Created attachment 123232 --> https://bugs.kde.org/attachment.cgi?id=123232&action=edit New crash information added by DrKonqi plasmashell (5.17.0) using Qt 5.13.1 - What I was doing when the application crashed: The pc was open and I was not in front of it. Going back to my pc I've found the bug tracker open. - Unusual behavior I noticed: Since the last update I've noticed that a folder view plasmoid continues to extend over the wallpaper even though I continue to try to reduce its height in order to avoid. -- Backtrace (Reduced): #6 0x7fb3b3b0d771 in () at /usr/lib/libQt5Core.so.5 #7 0x7fb3b3b0f2df in () at /usr/lib/libQt5Core.so.5 #8 0x7fb3b3b1170a in () at /usr/lib/libQt5Core.so.5 #9 0x7fb3b3b11d4c in () at /usr/lib/libQt5Core.so.5 #10 0x7fb3b3b11f93 in QSortFilterProxyModel::invalidate() () at /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #4 from Xwang --- Created attachment 123233 --> https://bugs.kde.org/attachment.cgi?id=123233&action=edit Overlay betweer folder view and wallpaper image This didn't happened with the previous plasma version because I was able to resize the folder view (so maybe the plasma crash did not happened with the previous version only because there wasn't any overlay) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #6 from Xwang --- (In reply to Kai Uwe Broulik from comment #5) > Can you please install debug symbols for plasma-workspace and qt core so we > get a better understanding of what's going on I am trying. As far as I've understood to do that in archlinux I've to compile from sources the packages with specific options and install them and then wait fr the next time the issue happens again. The problem is that I've found the plasma-workspace package, but not the qt core (I've tried searching for qt-core). Do you now the name of the package? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #8 from Xwang --- Yes, I am using random order. I am still trying to recompile the packages with symbols, but being the first time that I attempt to do that at the moment I'm still facing the problem that the locally compiled package files differ from those of the repository one even before adding the debug option. Probably because I have not compiled in a chroot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413038] New: The folder view plasmoid does not keep the correct size.
https://bugs.kde.org/show_bug.cgi?id=413038 Bug ID: 413038 Summary: The folder view plasmoid does not keep the correct size. Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: xwaang1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123237 --> https://bugs.kde.org/attachment.cgi?id=123237&action=edit Folder view withe the correct size SUMMARY Since 5.17.0 the folder view (see CorrectSize.png) forgets its size after a reboot or disconnection and becomes as in WrongSize.png file. STEPS TO REPRODUCE 1. Resize the folder view 2. reboot or disconnect and reconnect OBSERVED RESULT The folder view plasmoid losts its settings EXPECTED RESULT The folder view plasmoid should keeps the dimension 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 413038] The folder view plasmoid does not keep the correct size.
https://bugs.kde.org/show_bug.cgi?id=413038 --- Comment #1 from Xwang --- Created attachment 123238 --> https://bugs.kde.org/attachment.cgi?id=123238&action=edit Wrong plasmoid size after reboot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes and restarts when doing nothing
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #10 from Xwang --- (In reply to David Redondo from comment #9) > For reference the easiest way to reproduce this is to have a slideshow in > random order with as few images as possible and a short timeout. > The crash happens sometimes when invalidate() is called to generate a new > random order after all images have been shown once. Should I install the debug packages or the info I could obtain doing that is not needed anymore? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413038] The folder view plasmoid does not keep the correct size.
https://bugs.kde.org/show_bug.cgi?id=413038 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413038] The folder view plasmoid does not keep the correct size.
https://bugs.kde.org/show_bug.cgi?id=413038 --- Comment #3 from Xwang --- I unblock objects, right click on the folder widget till the "menu" on the left appears and then I move the bottom corner till the deseride position and block the objects. Is there another way to do that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413038] The folder view plasmoid does not keep the correct size.
https://bugs.kde.org/show_bug.cgi?id=413038 --- Comment #6 from Xwang --- (In reply to Nate Graham from comment #5) > Does the same thing happen with any other widgets that you manually resize, > or just Folder View? Can you test? It happens only with that folder view. On the desktop there is another folder view which is greater and which has no issue. Other widgets of different type do not have issue too. Is there maybe a minimum area for the folder view? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #24 from Xwang --- I have the same issue in Archlinux with Breeze light set in GNOME/GTK Style. It started with 5.17. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #25 from Xwang --- (In reply to Xwang from comment #24) > I have the same issue in Archlinux with Breeze light set in GNOME/GTK Style. > It started with 5.17. I forgot the issue happens in Firefox and Thunderbird which are the two GTK apps that I use. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410391] New: Unable to change forecast days
https://bugs.kde.org/show_bug.cgi?id=410391 Bug ID: 410391 Summary: Unable to change forecast days Product: kmymoney Version: 5.0.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY I'm not able to change how many days forward to execute the forecast. If I change the default 365 days it keeps calculating the forecast for 365 days. The same happens for the length in days of the cycle (it use always 30 days) STEPS TO REPRODUCE 1. Go to forecast 2. Change forecast days from 365 to 30 3. Click on the Forecast button on the right OBSERVED RESULT On click forecast days is automatically set to 365 agin and the forecast is made for 365 days grouped in 30 days EXPECTED RESULT The forecast should be executed for the requested forecast days only SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Frameworks 5.60.0 Qt 5.13.0 (compiled with 5.13.0) ADDITIONAL INFORMATION The same happens since some versions so I do not know exactly when it has started to misbehave. I think it has happened with 5.0.0, but I'm not sure -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410391] Unable to change forecast days
https://bugs.kde.org/show_bug.cgi?id=410391 --- Comment #2 from Xwang --- I can confirm that the workaround works :-) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #35 from Xwang --- Today I got th same iisue upgrading plasma from 5.60.0-1 to 5.61.0-1 as described here https://bbs.archlinux.org/viewtopic.php?id=248579 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #36 from Xwang --- (In reply to Xwang from comment #35) > Today I got th same iisue upgrading plasma from 5.60.0-1 to 5.61.0-1 as > described here > https://bbs.archlinux.org/viewtopic.php?id=248579 And I can confirm that a) the battery indicator works correctly in the login screen when you the session is locked b) restarting plasma with kquitapp5 plasmashell ; kstart5 plasmashell is a workaround that solves the issue till the following reboot. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 --- Comment #38 from Xwang --- After the plasma restart and a reboot the issue has resolved on my pc. I use sddm as login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #34 from Xwang --- Moreover as I've reported in this bug https://bugs.kde.org/show_bug.cgi?id=413934, the issue is that everytime the image is changed, you have a CPU high load spike. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 --- Comment #2 from Xwang --- 62 files (for a total of 4.8 MB) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #13 from Xwang --- I have the same problem with some PDF with Arch linux. Okular version 1.9.0 KDE Frameworks 5.64.0 Qt 5.13.2 (compiled with 5.13.2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Xwang changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #4 from Xwang --- I hace already answered to the question. There are 62 files for a total of 4.8MB of data. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Xwang changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] New: High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Bug ID: 413934 Summary: High CPU usage when switching wallpaper as slideshow Product: plasmashell Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: xwaang1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I configure the desktop to use images from a folder located on an SSD ext4 drive as wallpaper using a time ordered slideshow which changes image every 10 seconds, I see the CPU usage going up to about 25% (from a base constant level of less than 2%) every time the image is changed (it seems that one of the 4 CPU cores goes to 100%). If I change the changing rate of images nothing changes (CPU usage continue to goes up every time the image is changed) STEPS TO REPRODUCE 1. Set the wallpaper as slideshow every 10 seconds 2. Monitor the CPU usage using sudo top or a plasmoid OBSERVED RESULT CPU usage continue to goes up every time the image is changed EXPECTED RESULT Changing a wallpaper image should not require high CPU usage on an i7-6700HQ with 16GB f ram and SSD drive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.17.2-1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 414465] New: Partition manager crashes when analysing devices at startup
https://bugs.kde.org/show_bug.cgi?id=414465 Bug ID: 414465 Summary: Partition manager crashes when analysing devices at startup Product: partitionmanager Version: 4.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: xwaang1...@gmail.com Target Milestone: --- Application: partitionmanager (4.0.0) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.3.12-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: I had just opened the application and it crashed when analysing devices at startup. Une hour before it workd perfectly, but there was only an external USB device instead of two. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Floating point exception Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f895c8bac80 (LWP 1652))] Thread 5 (Thread 0x7f8947fff700 (LWP 1657)): #0 0x7f89603c742c in read () at /usr/lib/libc.so.6 #1 0x7f895ee0d9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f895ee5b9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f895ee5d0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f895ee5e0c3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f8950c60bc8 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f895ee39bb1 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f895f7cf4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f89603d62d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8950b8d700 (LWP 1656)): #0 0x7f895ee0d4e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f895ee5b15b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #2 0x7f895ee5d1b1 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f895ee5d1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f895ee5d242 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f895ee39bb1 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f895f7cf4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f89603d62d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8951900700 (LWP 1655)): #0 0x7f89603c742c in read () at /usr/lib/libc.so.6 #1 0x7f895ee0d9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f895ee5b9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f895ee5d0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f895ee5d1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f8960972b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f896091983c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f89620da3b9 in () at /usr/lib/libkpmcore.so.8 #8 0x7f896074c530 in () at /usr/lib/libQt5Core.so.5 #9 0x7f895f7cf4cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f89603d62d3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8959ac0700 (LWP 1654)): #0 0x7f89603c742c in read () at /usr/lib/libc.so.6 #1 0x7f895ee0d9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f895ee5b9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f895ee5d0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f895ee5d1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f8960972b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f896091983c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f896074b305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f89600bdb37 in () at /usr/lib/libQt5DBus.so.5 #9 0x7f896074c530 in () at /usr/lib/libQt5Core.so.5 #10 0x7f895f7cf4cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f89603d62d3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f895c8bac80 (LWP 1652)): [KCrash Handler] #6 0x7f89620e5ee9 in PartWidget::paintEvent(QPaintEvent*) () at /usr/lib/libkpmcore.so.8 #7 0x7f8961318096 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #8 0x7f89612d44e5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x7f89612dde11 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f896091ad12 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #11 0x7f8961310a78 in QWidgetPrivate::sendPaintEvent(QRegion const&) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f89613112eb in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f8961312048 in QWidgetPrivate:
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #43 from Xwang --- Created attachment 112354 --> https://bugs.kde.org/attachment.cgi?id=112354&action=edit Requested dbus-monitor.log Here you are -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #26 from Xwang --- I have the same issue in archlinux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380026] New: Plasmashell craqsh
https://bugs.kde.org/show_bug.cgi?id=380026 Bug ID: 380026 Summary: Plasmashell craqsh Product: plasmashell Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: xwaang1...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.10.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I have just installed Kmag on my archlinux system and I was searching for the app shortcut in the menu - Unusual behavior I noticed: Plasmashell crashed -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f28783bf800 (LWP 7546))] Thread 8 (Thread 0x7f27a72fa700 (LWP 7735)): #0 0x7f286c8b71c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f286c871536 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #2 0x7f286c871a20 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f286c871acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f28723c109b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f287236a8ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f27a9c9d0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #8 0x7f28721916d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f2871aa454f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f27be552700 (LWP 7721)): #0 0x7f286c8b71c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f286c870d67 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f286c8718db in () at /usr/lib/libglib-2.0.so.0 #3 0x7f286c871acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f28723c109b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f287236a8ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f2875e78fd6 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f28721916d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f2871aa454f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f284a92b700 (LWP 7720)): #0 0x7f287104c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2877b6c234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f2877b6c279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2871aa454f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f2858953700 (LWP 7712)): #0 0x7f2871a9a67d in poll () at /usr/lib/libc.so.6 #1 0x7f286c8719b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f286c871acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f28723c109b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f287236a8ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f28752c5025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f28721916d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f2871aa454f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f285a9e1700 (LWP 7690)): #0 0x7f286c8b71e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f286c87154a in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #2 0x7f286c871a20 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f286c871acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f28723c109b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f287236a8ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f28752c5025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f28721916d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f2871aa454f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f285bfff700 (LWP 7630)): #0 0x7f2871a9a67d in poll () at /usr/lib/libc.so.6 #1 0x7f286c8719b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f286c871acc in g_m
[plasmashell] [Bug 493770] Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed.
https://bugs.kde.org/show_bug.cgi?id=493770 --- Comment #4 from Xwang --- Created attachment 174878 --> https://bugs.kde.org/attachment.cgi?id=174878&action=edit journalctl messages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493770] Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed.
https://bugs.kde.org/show_bug.cgi?id=493770 --- Comment #5 from Xwang --- The issue is stiil present in 6.2.1: Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 In the attached file there are the journalctl messages from when I closed the lid (when the external monitor was still attached and in use) to the moment in which I have opened the lid and used the sysrq command. When the lid was closed the monitor has been disconnecte using the kvm switch. I wonder if that is the cause of the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493770] Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed.
https://bugs.kde.org/show_bug.cgi?id=493770 Xwang changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #6 from Xwang --- The issue is still present. You can see my message of 2024-10-16 08:45:38 UTC and the attache journalctl messages log file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493770] Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed.
https://bugs.kde.org/show_bug.cgi?id=493770 --- Comment #8 from Xwang --- (In reply to Zamundaaa from comment #7) > I tried a few times with my laptop, couldn't reproduce this issue. > > In your logs there's a lot of > > kwin_wayland_drm: Setting dpms mode failed! > which at least gives a hint of what's going on. For more information, we > need some drm debug logging of when the problem happens though; for how to > collect them, please check out > https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues I tried, but now I'm not able to reproduce it too ... I'm on archlinux so meantime since my last comment some packages for sure have been updated: Operating System: Arch Linux KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 493770] New: Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed.
https://bugs.kde.org/show_bug.cgi?id=493770 Bug ID: 493770 Summary: Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: xwaang1...@gmail.com Target Milestone: --- SUMMARY Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed. STEPS TO REPRODUCE 1. Connect an external monitor 2. Change monitor use only the external one (laptop screen turned off) 3. Close the laptop lid 4. Wait some time 5. Disconnect the external monitor (I have a KVM hdmi switch) 6. Open laptop lid OBSERVED RESULT Frequently (but not all the times) the lid screen remains black. Attaching again the external monitor shows a black screen too. Keyboard not responding (but PC is still running ... once it happened while I was playing music and music was still on even when the monitor was black). System responds to Alt+Sysrq+R and Alt+Sysrq+E by reactivating the screen and presenting the login page (in my case the GDM one). EXPECTED RESULT The internal monitor is turned on and the session is kept alive (as it happens when the issue does not appear) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1240U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Latitude 9330 ADDITIONAL INFORMATION This is the journalctl messages from the moment in which I opened the lid up to the alt+sysrq cmds: set 28 11:06:02 D9330 systemd-logind[675]: Lid opened. set 28 11:06:02 D9330 root[8139]: ACPI group/action undefined: wmi / PNP0C14:00 set 28 11:06:02 D9330 root[8141]: LID opened set 28 11:06:02 D9330 kwin_wayland[1511]: kwin_core: Failed to load cursor theme "Breeze_Snow" set 28 11:06:02 D9330 kwin_wayland[1511]: kwin_core: Failed to load cursor theme "Breeze_Snow" set 28 11:06:02 D9330 kwin_wayland[1511]: kwin_core: Failed to load cursor theme "Breeze_Snow" set 28 11:06:02 D9330 xdg-desktop-portal-kde[1735]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 pamac-tray-plasma[1953]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kded6[1644]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kactivitymanagerd[1683]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 polkit-kde-authentication-agent-1[1733]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kwalletmanager5[2197]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kalarm[2573]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kwalletd6[2166]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 python[1942]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kiod6[3013]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 org_kde_powerdevil[1734]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 plasmashell[6987]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash set 28 11:06:02 D9330 kcminit[8144]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so" set 28 11:06:02 D9330 kcminit[8144]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_style.so" set 28 11:06:02 D9330 kded6[1816]: xsettingsd: Reloading configuration set 28 11:06:02 D9330 kded6[1816]: xsettingsd: Loaded 14 settings from /home/andreak/.config/xsettingsd/xsettingsd.conf set 28 11:06:03 D9330 plasmashell[6987]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. set 28 11:06:03 D9330 root[8183]: ACPI group/action undefined: wmi / PNP0C14:00 set 28 11:06:03 D9330 org_kde_powerdevil[1734]: Delaying 6 seconds to avoid a false disconnect/connect sequence... set 28 11:06:04 D9330 root[8185]: ACPI group/action undefined: jack/lineout / LINEOUT set 28 11:06:04 D9330 root[8187]: ACPI group/action undefined: jack/videoout / VIDEOOUT set 28 11:06:05 D9330 kwin_wayland[1511]: kwin_wayland_drm: Setting dpms mode failed! set 28 11:06:05 D9330 wpa_supplicant[784]: wlp0s20f3: WNM: Disassociation Imminent - Disassociation Timer 60 set 28 11:06:05 D933
[plasmashell] [Bug 493770] Frequent black screen if external monitor is disconnected when it was the only one in use and the laptop lid was closed.
https://bugs.kde.org/show_bug.cgi?id=493770 Xwang changed: What|Removed |Added CC||xwaang1...@gmail.com --- Comment #2 from Xwang --- (In reply to Nate Graham from comment #1) > Various changes were made for Plasma 6.2 that are likely to have fixed this. > Can you test again once Plasma 6.2 is released in less than two weeks? > Thanks a lot! Sure! I'll do as soon as it will arrive on archlinux! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371677] New: Icon in the upper left corner of the windows does not follow the customized one of the menu/launcher
https://bugs.kde.org/show_bug.cgi?id=371677 Bug ID: 371677 Summary: Icon in the upper left corner of the windows does not follow the customized one of the menu/launcher Product: plasmashell Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Icon Applet Assignee: plasma-b...@kde.org Reporter: xwaang1...@gmail.com Hi, I've created different menu entries to open an application with different settings. For each entry I've changed the default app icon with a different one so that to recognize which icon to press when I add all of these launcher to my panel (which represents them each with its specified icon so the panel is OK). The (visual) problem is that if I open the application it uses always the default icon in the left upper corner of the decoration window regardless to what launcher I've used to open. Is it possible to have the same icon of the launcher which has been used to open the app? Reproducible: Always Steps to Reproduce: 1.Create a new launcher for an app with a customized icon 2.Launch the application 3.Look at the icon at the left upper corner which is different from the one in the launcher -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371677] Icon in the upper left corner of the windows does not follow the customized one of the menu/launcher
https://bugs.kde.org/show_bug.cgi?id=371677 --- Comment #1 from Xwang --- Created attachment 101779 --> https://bugs.kde.org/attachment.cgi?id=101779&action=edit Three different istances called by the 3rd, 4th and 5th button on the panel from the left In the attached file there is a screenshot of the desktop with three different instances of chromium called by the 3rd, 4th and 5th button (respectively) on the panel from the left. Each button has a different icon, but the three windows have all the default icon on the left upper corner. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 362862] New: KMyMoney has crashed when I've clicked on the left pane
https://bugs.kde.org/show_bug.cgi?id=362862 Bug ID: 362862 Summary: KMyMoney has crashed when I've clicked on the left pane Product: kmymoney4 Version: 4.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: xwaang1...@gmail.com Application: kmymoney (4.7.2) KDE Platform Version: 4.14.19 Qt Version: 4.8.7 Operating System: Linux 4.5.1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I've just entered a transaction, then clicked save and then on the account on the left pane to insert another transaction in a different account. The crash can be reproduced sometimes. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #6 0x7f22bd962fbd in QSortFilterProxyModel::parent(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 #7 0x7f22bd91b728 in QTreeView::indexRowSizeHint(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 #8 0x7f22bd91ec91 in QTreeViewPrivate::itemHeight(int) const () from /usr/lib/libQtGui.so.4 #9 0x7f22bd91fe16 in QTreeViewPrivate::updateScrollBars() () from /usr/lib/libQtGui.so.4 #10 0x7f22bd929ab1 in QTreeView::updateGeometries() () from /usr/lib/libQtGui.so.4 #11 0x7f22bd3fbb30 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #12 0x7f22bd7c15ee in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4 #13 0x7f22bd8e7073 in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib/libQtGui.so.4 #14 0x7f22bd928abc in QTreeView::viewportEvent(QEvent*) () from /usr/lib/libQtGui.so.4 #15 0x7f22bc943646 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #16 0x7f22bd3a52bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0x7f22bd3ac136 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #18 0x7f22be12f88a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #19 0x7f22bc9434dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #20 0x7f22bd443e01 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib/libQtGui.so.4 #21 0x7f22bd3f3565 in QWidget::setGeometry(QRect const&) () from /usr/lib/libQtGui.so.4 #22 0x7f22bd845aed in QAbstractScrollAreaPrivate::layoutChildren() () from /usr/lib/libQtGui.so.4 #23 0x7f22bd846ff8 in QAbstractScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4 #24 0x7f22bd8e6d0b in QAbstractItemView::event(QEvent*) () from /usr/lib/libQtGui.so.4 #25 0x7f22bd3a52dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #26 0x7f22bd3ac136 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #27 0x7f22be12f88a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #28 0x7f22bc9434dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #29 0x7f22bd443e01 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib/libQtGui.so.4 #30 0x7f22bd3f3565 in QWidget::setGeometry(QRect const&) () from /usr/lib/libQtGui.so.4 #31 0x7f22bd3d595d in QWidgetItem::setGeometry(QRect const&) () from /usr/lib/libQtGui.so.4 #32 0x7f22bd3b4690 in QBoxLayout::setGeometry(QRect const&) () from /usr/lib/libQtGui.so.4 #33 0x7f22bd3d1ced in QLayoutPrivate::doResize(QSize const&) () from /usr/lib/libQtGui.so.4 #34 0x7f22bd3a52ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #35 0x7f22bd3ac136 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #36 0x7f22be12f88a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #37 0x7f22bc9434dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #38 0x7f22bd443e01 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib/libQtGui.so.4 #39 0x7f22bd3f3565 in QWidget::setGeometry(QRect const&) () from /usr/lib/libQtGui.so.4 #40 0x7f22bd3d1ced in QLayoutPrivate::doResize(QSize const&) () from /usr/lib/libQtGui.so.4 #41 0x7f22bd3a52ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #42 0x7f22bd3ac136 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #43 0x7f22be12f88a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #44 0x7f22bc9434dd in QCoreApplication::notifyInternal(QObject*, QEve
