[frameworks-solid] [Bug 491422] Plasmashell crashes in Solid::Backends::Fstab::FstabHandling::_k_updateMtabMountPointsCache() when turning on the monitor
https://bugs.kde.org/show_bug.cgi?id=491422 Matthias Fabinski changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Matthias Fabinski --- Hello Nate, thanks again for looking into this. The coredump did not occur to me in the resent weeks and i could not find a way to reproduce it. In Coredumpctl i've seen, that the bug occured way before i turned the monitors on, so it is unrelated to this. Therefore i think, this bug can be closed as "WORKSFORME" - sorry for the noise. Kind regards Matthias -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 491422] Plasmashell crashes in Solid::Backends::Fstab::FstabHandling::_k_updateMtabMountPointsCache() when turning on the monitor
https://bugs.kde.org/show_bug.cgi?id=491422 --- Comment #3 from Matthias Fabinski --- Hello, thanks for looking into it. I assumed it is monitor related, because i only see the message after turning on the monitor after longer time of keeping the system running, but with monitor turned off. Is it possible to find the time of the crash in order to correlate, if the bug occured at the time of turning on the monitor, or if it happened during the night? All my mounts in the fstab work, i'm unsure, if there are some obvious errors. > ## /dev/sdc1 > #UUID=3eb51d00-a1c6-4ba5-8e05-636eacb8c9b4 / ext4 > rw,defaults,noatime,discard 0 1 > > ## /dev/sdc2 > #UUID=77299e97-ec88-48b7-938a-ae5017b4b9d0 noneswap > defaults,noatime,discard 0 0 > > # /dev/sda1 > # Festplatte old UUID=A2DCE3A1DCE36E4B /mnt/fun > ntfs-3g defaults,uid=1000,rw,nofail 0 0 > # ssd: > UUID=DxxC /mnt/funntfs-3g > defaults,uid=1000,rw,nofail 0 0 > > # /dev/sdf1 > UUID=fxxx-bxx7-4xx6-9xxc-axx4 /mnt/backup ext4 > rw,defaults,nofail,x-systemd.device-timeout=1,noauto,x-systemd.automount > 0 0 > > # toshiba ext > UUID=4xx5 /mnt/text ntfs-3g > defaults,uid=1000,rw,nofail,noauto0 0 > > # big backup > UUID=7xxA /mnt/bigbackup ntfs-3g > defaults,uid=1000,rw,nofail,noauto 0 0 > > ### old fstab above > > # /dev/nvme0n1p1 > UUID=4xxa-axxa-4xx5-9xx7-6xx6 / ext4 > rw,relatime 0 1 > > //.home/lexmark/mnt/lexmarkcifs > defaults,nofail,username=matthias,password=notmyrealpw,x-systemd.automount,x-systemd.requires=network-online.target,uid=1000,file_mode=0644,dir_mode=0755 > 0 0 > //.home/gemeinsam /mnt/gemeinsam cifs > defaults,nofail,username=matthias,password=notmyrealpw,x-systemd.automount,x-systemd.requires=network-online.target,uid=1000,file_mode=0644,dir_mode=0755 > 0 0 > //.home/matthias /mnt/matthias cifs > defaults,nofail,username=matthias,password=notmyrealpw,x-systemd.automount,x-systemd.requires=network-online.target,uid=1000,file_mode=0644,dir_mode=0755 > 0 0 > //.home/multimedia /mnt/multimedia cifs > defaults,nofail,username=matthias,password=notmyrealpw,x-systemd.automount,x-systemd.requires=network-online.target,uid=1000,file_mode=0644,dir_mode=0755 > 0 0 > //.home/syncthing /mnt/syncthing cifs > defaults,nofail,username=matthias,password=notmyrealpw,x-systemd.automount,x-systemd.requires=network-online.target,uid=1000,file_mode=0644,dir_mode=0755 > 0 0 I can give more logs etc. but don't know where to look for. Kind regards, Matthias -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491422] Plasmashell Crash when turning on the monitor
https://bugs.kde.org/show_bug.cgi?id=491422 Matthias Fabinski changed: What|Removed |Added Summary|Plasmashell Crash |Plasmashell Crash when ||turning on the monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491422] New: Plasmashell Crash
https://bugs.kde.org/show_bug.cgi?id=491422 Bug ID: 491422 Summary: Plasmashell Crash Classification: Plasma Product: plasmashell Version: 6.1.3 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matthias@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.3) Qt Version: 6.7.2 Frameworks Version: 6.4.0 Operating System: Linux 6.10.2-arch1-2 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.3 [CoredumpBackend] -- Information about the crash: This crash happens some times, when I turn on one of my monitors (2x 4K LG). I don't know how to reproduce it, but it happens frequently. This time only one Monitor was configured, and as i started this monitor, the crash info was shown. Currently only 1 Monitor is set. Operating System: Arch Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-arch1-2 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x710589c9fa39 in Solid::Backends::Fstab::FstabHandling::_k_updateMtabMountPointsCache () at /usr/src/debug/solid/solid-6.4.0/src/solid/devices/backends/fstab/fstabhandling.cpp:364 #7 0x710589ca1615 in Solid::Backends::Fstab::FstabHandling::_k_updateMtabMountPointsCache () at /usr/src/debug/solid/solid-6.4.0/src/solid/devices/backends/fstab/fstabhandling.cpp:330 #8 Solid::Backends::Fstab::FstabHandling::deviceList () at /usr/src/debug/solid/solid-6.4.0/src/solid/devices/backends/fstab/fstabhandling.cpp:235 #9 0x710589c9a449 in Solid::Backends::Fstab::FstabManager::_k_updateDeviceList (this=this@entry=0x710330ffce30) at /usr/src/debug/solid/solid-6.4.0/src/solid/devices/backends/fstab/fstabmanager.cpp:107 #10 0x710589c9b94c in Solid::Backends::Fstab::FstabManager::onMtabChanged (this=0x710330ffce30) at /usr/src/debug/solid/solid-6.4.0/src/solid/devices/backends/fstab/fstabmanager.cpp:132 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 411196] gwenview very slow to launch
https://bugs.kde.org/show_bug.cgi?id=411196 Matthias Fabinski changed: What|Removed |Added CC||matthias@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] configure desktop effects dialog has scaling bug which makes reading the effects names imposible
https://bugs.kde.org/show_bug.cgi?id=396725 --- Comment #1 from Matthias Fabinski --- small update: I tested with different scaling factors and found out, that with 1.0, 2.0 and 3.0 the dialog works properly. The following scaling factors where tested and had similar graphical glitches: 1.2, 1.5, 2.5. The fontsetting has no impact on this, so it can be ignored in further work on this bug. Can someone point me to the sourcecode (repository) of the Desktop Effects Dialog, as i was not able to find it. Information about where to find documentation about the settingsapplication would be appreciated too. Kind regards, Matthias Fabinski -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] New: configure desktop effects dialog has scaling bug which makes reading the effects names imposible
https://bugs.kde.org/show_bug.cgi?id=396725 Bug ID: 396725 Summary: configure desktop effects dialog has scaling bug which makes reading the effects names imposible Product: systemsettings Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: matthias@gmail.com Target Milestone: --- Created attachment 114047 --> https://bugs.kde.org/attachment.cgi?id=114047&action=edit Shows the desktop effects dialog with the bug Application systemsettings Version 5.13.3 Linux (x86_64) release 4.17.8-1-ARCH When opening the Desktop Effects Dialog in System Settings the text cannot be read. I attach a screenshot of the dialog. I think the issue results from my scaling settings (upgraded to 4k monitor) which I set to scalingfactor 1.2 with the default Displays System Settings dialog. Furthermore i set the Fonts with "Force Fonts DPI" to 115. Changing the window size of the dialog does not change the outcome, the problem persists. It happens with Treeview, Icon View and Sidebar View. Other dialogs in the systemsettings work without a problem. Kind regards, Matthias Fabinski -- You are receiving this mail because: You are watching all bug changes.
