[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094
Simone Lazzaris changed:
What|Removed |Added
CC||sim...@omni.it
--- Comment #11 from Simone Lazzaris ---
I think I'm starting to see the same issue: it happens when the screen saver
kicks in *and* the screen(s) turns off. If I try to log back in, I'm greeted
with a black screen and the writing
"the screen locker is broken and unlocking is not possible anymore". Then there
are instructions about switching to a console and "manually" unlock the screen
with the "loginctl unlock-session" command.
Which works, so that is an inconvenience but not a show stopper.
Journalctl reports:
```
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126137]:
QMetaObject::invokeMethod: No such method
ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError)
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126137]:
QMetaObject::invokeMethod: No such method
ScreenLocker::AccessDeniedNetworkReply::error(QNetworkReply::NetworkError)
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: qt.qpa.wayland: Loading
shell integration failed.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: qt.qpa.plugin: Could
not load the Qt platform plugin "wayland" in "" even though it was found.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126303]: This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform
plugins are: offscreen, vnc, linuxfb, eglfs, xcb, minimalegl, minimal, wayland,
wayland-egl, vkkhrdisplay.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: qt.qpa.wayland: Loading
shell integration failed.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: qt.qpa.plugin: Could
not load the Qt platform plugin "wayland" in "" even though it was found.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126307]: This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform
plugins are: offscreen, vnc, linuxfb, eglfs, xcb, minimalegl, minimal, wayland,
wayland-egl, vkkhrdisplay.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: qt.qpa.wayland: Loading
shell integration failed.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: qt.qpa.plugin: Could
not load the Qt platform plugin "wayland" in "" even though it was found.
giu 26 08:26:49 betelgeuse kscreenlocker_greet[126314]: This application failed
to start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform
plugins are: offscreen, vnc, linuxfb, eglfs, xcb, minimalegl, minimal, wayland,
wayland-egl, vkkhrdisplay.
```
I'm using archlinux, kde 6.1.0, framework 6.3.0 on wayland.
Note that this wasn't happening until I upgraded from the 6.0.X branch.
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 Simone Lazzaris changed: What|Removed |Added Version|6.0.1 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it --- Comment #9 from Simone Lazzaris --- I'm seeing the same problem. Archlinux, kde 6.1.0, amd ryzen 9 5900X, radeon 7600X. It seems to crash when the screensaver kicks in *and* the monitor shuts down. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084 Simone Lazzaris changed: What|Removed |Added Version|6.0.3 |6.1.0 --- Comment #10 from Simone Lazzaris --- Note it wasn't happening on kde 6.0.X -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483094] When monitor goes to sleep and system locks, kscreenlocker becomes unresponsive/stuck when monitor wakes up
https://bugs.kde.org/show_bug.cgi?id=483094 --- Comment #12 from Simone Lazzaris --- Likely a duplicate of https://bugs.kde.org/show_bug.cgi?id=485084 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 --- Comment #13 from Simone Lazzaris --- (In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? I'm using dual screen. I've also got an update: with kde 6.1.1, the unlock screen works, I don't need to switch to a console, but still there are crashes. Now apparently kmail also crashes, but I'm not sure if it is related. giu 27 20:44:30 betelgeuse systemd-coredump[131031]: Process 130365 (kmail) of user 1000 terminated abnormally with signal 11/SEGV, processing... giu 27 20:44:30 betelgeuse systemd[1]: Started Process Core Dump (PID 131031/UID 0). giu 27 20:44:30 betelgeuse systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. giu 27 20:44:30 betelgeuse kernel: kscreenlocker_g[130883]: segfault at 8 ip 7d59a31aaee4 sp 7fffa7d681a8 error 4 in libQt6Gui.so.6.7.2[7d59a30d9000+618000] likely on CPU 10 (core 12, socket 0) giu 27 20:44:30 betelgeuse kernel: Code: 84 00 00 00 00 00 f0 83 28 01 75 9a 48 8b 7d b0 ff 15 90 87 68 00 eb 8e ff 15 80 8c 68 00 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 57 08 48 8b 02 48 85 c0 74 10 8b 40 04 85 c0 74 09 48 8b 42 giu 27 20:44:44 betelgeuse systemd-coredump[131029]: [🡕] Process 125756 (plasmashell) of user 1000 dumped core. Stack trace of thread 125879: #0 0x7e68684a8e44 n/a (libc.so.6 + 0x94e44) #1 0x7e6868450a30 raise (libc.so.6 + 0x3ca30) #2 0x7e686b31b643 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6643) #3 0x7e6868450ae0 n/a (libc.so.6 + 0x3cae0) #4 0x7e68699a540b _ZNK15QtWaylandClient14QWaylandWindow16devicePixelRatioEv (libQt6WaylandClient.so.6 + 0x9140b) #5 0x7e686236ff0c _ZN15QtWaylandClient17QWaylandEglWindow13updateSurfaceEb (libQt6WaylandEglClientHwIntegration.so.6 + 0x8f0c) #6 0x7e6862370905 _ZN15QtWaylandClient17QWaylandGLContext11makeCurrentEP16QPlatformSurface (libQt6WaylandEglClientHwIntegration.so.6 + 0x9905) #7 0x7e68694adc28 _ZN14QOpenGLContext11makeCurrentEP8QSurface (libQt6Gui.so.6 + 0x4adc28) #8 0x7e686966f112 n/a (libQt6Gui.so.6 + 0x66f112) #9 0x7e686a418647 n/a (libQt6Quick.so.6 + 0x418647) #10 0x7e686a419f9a n/a (libQt6Quick.so.6 + 0x419f9a) #11 0x7e6868cc9747 n/a (libQt6Core.so.6 + 0x2c9747) #12 0x7e68684a6ded n/a (libc.so.6 + 0x92ded) #13 0x7e686852a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 125756: #0 0x7e68684a34e9 n/a (libc.so.6 + 0x8f4e9) #1 0x7e68684a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) #2 0x7e6868cce120 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce120) #3 0x7e686a413bd4 n/a (libQt6Quick.so.6 + 0x413bd4) #4 0x7e686a4148bd n/a (libQt6Quick.so.6 + 0x4148bd) #5 0x7e686a24d8de _ZN12QQuickWindowD1Ev (libQt6Quick.so.6 + 0x24d8de) #6 0x60db1a4bea40 n/a (plasmashell + 0x3ca40) #7 0x7e6868b8be0a _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18be0a) #8 0x7e686aafc51c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc51c) #9 0x7e6868b44d28 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144d28) #10 0x7e6868b450eb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1450eb) #11 0x7e6868da49ec n/a (libQt6Core.so.6 + 0x3a49ec) #12 0x7e686764da89
[kscreenlocker] [Bug 485084] Screen Locker broken on resume from sleep with wayland protocol error (wl_display@1: error 1: invalid arguments for wl_display@1.get_registry)
https://bugs.kde.org/show_bug.cgi?id=485084 Simone Lazzaris changed: What|Removed |Added Version|6.1.0 |6.1.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489532] New: plasmashell sudden crash
https://bugs.kde.org/show_bug.cgi?id=489532 Bug ID: 489532 Summary: plasmashell sudden crash Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: sim...@omni.it Target Milestone: 1.0 Application: plasmashell (6.1.1) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.6-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.1 [CoredumpBackend] -- Information about the crash: Plasmashell crashed and restarted, I was not doing anything particular, just switching from one window to another. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x79ef8f0a8eb3 in __pthread_kill_internal (threadid=, signo=6) at pthread_kill.c:78 #7 0x79ef8f050a30 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x79ef8f0384c3 in __GI_abort () at abort.c:79 #9 0x79ef8f039354 in __libc_message_impl (fmt=fmt@entry=0x79ef8f1c22ea "%s\n") at ../sysdeps/posix/libc_fatal.c:132 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489532] plasmashell sudden crash
https://bugs.kde.org/show_bug.cgi?id=489532 --- Comment #1 from Simone Lazzaris --- Created attachment 171223 --> https://bugs.kde.org/attachment.cgi?id=171223&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] New: Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 Bug ID: 482711 Summary: Switching keyboard mapping doesn't work Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: sim...@omni.it CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY I have a keyboard with an Italian layout, and I used to use Italian keyboard mapping. I've upgraded to KDE6 and now I'm stuck with the English layout. STEPS TO REPRODUCE 1. Go to system settings -> keyboard -> mappings 2. Enable keyboard mapping 3. Add any mapping (I've tried Italian and German) 4. Click on `apply` 5. Try to enter text using non-alphanumeric characters, and see that you're still using English layout Note that the OSD display shows the correct language if/when "switching" layout using the meta/alt/k combo. The systray indicator, instead, always says "EN". 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.
[plasmashell] [Bug 482711] Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #1 from Simone Lazzaris --- Also note that in the system config tool, the `label` field for the mappings is shown as a couple of rectangles (like unicode missing glyphs) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 Simone Lazzaris changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482593 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482593] Adding the 2nd keyboard layout does not make the system tray layout indicator appear until re-login
https://bugs.kde.org/show_bug.cgi?id=482593 Simone Lazzaris changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482711 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #2 from Simone Lazzaris --- Logging out and logging back in didn't fix anything (rif. bug 482593) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #3 from Simone Lazzaris --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #4 from Simone Lazzaris --- Update: keyboard mapping is working in X11 based applications: I've tried xterm and mattermost desktop and the keys are in the correct nationalization. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] Switching keyboard mapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #5 from Simone Lazzaris --- Another update: the very first keystroke sent to a new application is actually correct: the character typed is the one corresponding to my selected mapping. But only the first one; all subsequent characters are taken from the US layout. Very very odd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] On Wayland, keyboard layout switches to US English after typing one character
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #7 from Simone Lazzaris --- No, on a clean account I can use the first mapping (Italian in my case). I still can't switch mapping, I'll try to see if that still persist after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] On Wayland, keyboard layout switches to US English after typing one character
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #10 from Simone Lazzaris --- After a reboot, the language indicator in the systray area works, I can switch languages clicking on it or using the hotkeys. It seems that you need to restart plasma to make that indicator works as intended. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482711] On Wayland, keyboard layout switches to US English after typing one character
https://bugs.kde.org/show_bug.cgi?id=482711 --- Comment #11 from Simone Lazzaris --- So, to recap: - existing user, upgraded from kde5 to kde6: keyboard stuck in US English using wayland, works using X11 - new user, on wayland, without a restart: first mapping works immediately after being configured, indicator in systray area not present, can't switch using hotkeys (alt-meta-k in my case) - new user, on wayland, after a plasma restart: everything works -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482339] [Wayland] Tasks Show on incorrect screen after monitor reconnected
https://bugs.kde.org/show_bug.cgi?id=482339 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it --- Comment #21 from Simone Lazzaris --- I get the same on my setup, but I don't even need to disable a monitor. STEPS TO REPRODUCE 1. Configure multiple monitors 2. Add a panel with a task bar to each monitor 3. set task bar to only show tasks from current screen. OBSERVED RESULT The panel on the left most screen shows all tasks. Tasks are still shown on other screens but can't be left clicked to activate the application or right click for more options. EXPECTED RESULT Tasks are only shown when on that screen and can be clicked to activate. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482339] Tasks Show on incorrect screen after monitor reconnected
https://bugs.kde.org/show_bug.cgi?id=482339 --- Comment #29 from Simone Lazzaris --- (In reply to Nate Graham from comment #25) > If you're using the systemd-enabled Plasma startup feature (which is on by > default), then the preferred approach is to run `systemctl restart --user > plasma-plasmashell.service` This workaround works for me -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it Resolution|FIXED |--- Version|20.12.0 |21.08.3 Status|RESOLVED|REOPENED --- Comment #6 from Simone Lazzaris --- I'm reopening this bug as I've got the same behavior in the newer version (21.08.3). OS: Arch Linux x86_64 Kernel: 5.15.3-arch1-1 KDE Plasma Version: 5.23.3 KDE Gear: 21.08.3 Qt Version: 5.15.2 Okular Version: 21.08.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 Simone Lazzaris changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Simone Lazzaris --- After an update and a reboot, it started to work for me too. Sorry for the fuss. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414955] KMail stops responding when preview pane active on Wayland-Plasma
https://bugs.kde.org/show_bug.cgi?id=414955 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it --- Comment #7 from Simone Lazzaris --- I confirm the bug (or a avery similar one): kmail stop responding when the cursor shapes changes (e.g. when I hoover over a resizable border). SOFTWARE/OS VERSIONS Archlinux, with intel graphics. kwin 5.18.5-1 plasma-desktop 5.18.5-2 plasma-workspace 5.18.5-3 kmail 20.04.1-1 kparts 5.70.0-1 qt5-base 5.14.2-3 qt5-webengine 5.14.2-3 qt5-wayland 5.14.2-1 wayland 1.18.0-2 wayland-protocols 1.20-1 mesa 20.0.7-3 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 Simone Lazzaris changed: What|Removed |Added Ever confirmed|0 |1 CC||sim...@omni.it Status|UNCONFIRMED |CONFIRMED --- Comment #6 from Simone Lazzaris --- I'm also having this issue. Archlinux, kde 17.12.2, Qt 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 261939] kmail crashes when opening a (malformed?) message with tnef attachment
https://bugs.kde.org/show_bug.cgi?id=261939 Simone Lazzaris changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from Simone Lazzaris --- Closing due to inactivity -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"
https://bugs.kde.org/show_bug.cgi?id=297930 --- Comment #24 from Simone Lazzaris --- Absolutely NOT resolved and NOT fixed. Still experiencings random freezes. Restarting akonadi sometime is not sufficient. Archlinux, KMail 5.4.1, KDE Frameworks 5.30.0, akonadi 16.12.1. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"
https://bugs.kde.org/show_bug.cgi?id=297930 --- Comment #27 from Simone Lazzaris --- I've set innodb_buffer_pool_size=128M; let's see if this solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 Simone Lazzaris changed: What|Removed |Added CC||kde...@mailinator.com --- Comment #7 from Simone Lazzaris --- *** Bug 393841 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 393841] Scrolling is broken in chat windows
https://bugs.kde.org/show_bug.cgi?id=393841 Simone Lazzaris changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||sim...@omni.it --- Comment #3 from Simone Lazzaris --- *** This bug has been marked as a duplicate of bug 388082 *** -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 --- Comment #8 from Simone Lazzaris --- The bug persists, in spite of Archlinux, KDE 18.04.1, KDE Frameworks 5.46.0, QT 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 401851] New: Crash while adding owncloud account to kde
https://bugs.kde.org/show_bug.cgi?id=401851 Bug ID: 401851 Summary: Crash while adding owncloud account to kde Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sim...@omni.it Target Milestone: --- Application: kcmshell5 (5.14.3) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.16-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was trying to share a PDF opened in okular with my owncloud server. I've added the credential and logged in, but when trying to shaer the application crashed The crash can be reproduced every time. -- Backtrace: Application: Modulo delle impostazioni di sistema (kcmshell5), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f86e866f380 (LWP 10706))] Thread 5 (Thread 0x7f869affd700 (LWP 10841)): #0 0x7f86e8bd912b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7f86e8b52d76 in _int_free () at /usr/lib/libc.so.6 #2 0x7f86e8d2b307 in _dl_deallocate_tls () at /lib64/ld-linux-x86-64.so.2 #3 0x7f86e6396793 in free_stacks () at /usr/lib/libpthread.so.0 #4 0x7f86e6396e2a in __deallocate_stack () at /usr/lib/libpthread.so.0 #5 0x7f86e6397d28 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f86e8bcbb23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f86d77fe700 (LWP 10710)): #0 0x7f86e8bc0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f86e53acee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f86e53adf62 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f86dc73ac28 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f86e53763eb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f86e6397a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f86e8bcbb23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f86d7fff700 (LWP 10709)): #0 0x7f86e8bc0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f86e53acee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f86e53acfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f86e53ad022 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f86e53763eb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f86e6397a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f86e8bcbb23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f86dddc7700 (LWP 10708)): #0 0x7f86e8bd912b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7f86e8b564ae in realloc () at /usr/lib/libc.so.6 #2 0x7f86e7584ade in QArrayData::reallocateUnaligned(QArrayData*, unsigned long, unsigned long, QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f86e7586afb in QByteArray::reallocData(unsigned int, QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f86e7586cc1 in QByteArray::resize(int) () at /usr/lib/libQt5Core.so.5 #5 0x7f86e778c2ec in () at /usr/lib/libQt5Core.so.5 #6 0x7f86e778c655 in () at /usr/lib/libQt5Core.so.5 #7 0x7f86e778a52c in QTextCodec::fromUnicode(QStringView) const () at /usr/lib/libQt5Core.so.5 #8 0x7f86e75f9b03 in QString::toLocal8Bit_helper(QChar const*, int) () at /usr/lib/libQt5Core.so.5 #9 0x7f86e7574645 in () at /usr/lib/libQt5Core.so.5 #10 0x7f86e756f8b6 in () at /usr/lib/libQt5Core.so.5 #11 0x7f86e756fc79 in () at /usr/lib/libQt5Core.so.5 #12 0x7f86e7540087 in QMessageLogger::warning(char const*, ...) const () at /usr/lib/libQt5Core.so.5 #13 0x7f86e7784e70 in () at /usr/lib/libQt5Core.so.5 #14 0x7f86e53ab952 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #15 0x7f86e53ace86 in () at /usr/lib/libglib-2.0.so.0 #16 0x7f86e53acfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x7f86e7784fc9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7f86e77308cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f86e7579eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7f86e8684ba6 in () at /usr/lib/libQt5DBus.so.5 #21 0x7f86e7583f65 in () at /usr/lib/libQt5Core.so.5 #22 0x7f86e6397a9d in start_thread () at /usr/lib/libpthread.so.0 #23 0x7f86e8bcbb23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f86e866f380 (LWP 10706)): [KCrash Handler] #6 0x7f86e8b07d7f in raise () at /usr/lib/libc.so.6 #7 0x7f86e8af2672 in abort () at /usr/lib/libc.so.6 #8 0x7f86e8b4a878 in __libc_message () at /usr/lib/libc.so.6 #9 0x7f86e8b5118a in () at /usr/lib/libc.so.6 #10 0x7f86e8b513d4 in malloc_consolidate () at /usr/lib/libc.so.6 #11 0x7f86e8b52c8c in _int_free () at /usr/lib/libc.so.6 #12 0x7f86e75ce2e9 in QHashData::free_
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"
https://bugs.kde.org/show_bug.cgi?id=297930
--- Comment #32 from Simone Lazzaris ---
I've tried to inspect strace output when kmail is stuck on "retrieving
folder."
I've see many lines like:
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN},
{fd=75, events=POLLIN}, {fd=84, events=POLLIN}], 5, 17901^Cstrace: Process 2170
detached
Out of curiosity I've tracked the FD used:
lrwx-- 1 simone simone 64 6 mar 12.31 /proc/2170/fd/5 ->
anon_inode:[eventfd]
lrwx-- 1 simone simone 64 6 mar 12.31 /proc/2170/fd/7 -> socket:[48922]
lr-x-- 1 simone simone 64 6 mar 12.31 /proc/2170/fd/75 ->
anon_inode:inotify
lr-x-- 1 simone simone 64 6 mar 12.31 /proc/2170/fd/84 ->
anon_inode:inotify
It seems that kmail is waiting for something that never happens I've found
that if I kill the process and restart kmail, akonadi is not impacted and the
kmail resume its correct behaviour.
Maybe this can help?
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly
https://bugs.kde.org/show_bug.cgi?id=360792 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"
https://bugs.kde.org/show_bug.cgi?id=297930 --- Comment #34 from Simone Lazzaris --- (in reply to ianse...@btinternet.com) That seems not true in my case: I've found that kmail freezes in (roughly) equal rates for new and old messages. Beside that, I've got a very high number of incoming and older mail, so marking all "not read" without actually reading them is an option I'm not willing to take. Frankly, I'd rather change the mail client -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 289097] error "Unable to fetch item from backend" when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 Simone Lazzaris changed: What|Removed |Added CC||sim...@omni.it --- Comment #85 from Simone Lazzaris --- I still see this bug in archlinux, kmail 5.4.0, akonadi 16.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 507109] New: Secondary screen not turning off during inactivity
https://bugs.kde.org/show_bug.cgi?id=507109 Bug ID: 507109 Summary: Secondary screen not turning off during inactivity Classification: Plasma Product: plasmashell Version First 6.4.0 Reported In: Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Power management & brightness Assignee: plasma-b...@kde.org Reporter: sim...@omni.it Target Milestone: 1.0 SUMMARY I have a dual screen setup, and I want the screen to turn off after 10 min of inactivity The primary screen indeed turns off correctly, but the secondary screen doesn't and. STEPS TO REPRODUCE 1. Connect two monitor 2. Wait 10 minutes 3. The primary screen is turned off but the secondary is not OBSERVED RESULT Only one monitor is turned off after 10 min of inactivity EXPECTED RESULT Both monitor should turn off. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.15.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 32 GiB of RAM (31.2 GiB usable) Graphics Processor: AMD Radeon RX 7600 ADDITIONAL INFORMATION Not sure if it is relevant, but my primary screen is connected to the second port of the graphic card (using a display port cable), while the secondary is on the first one, with an HDMI cable, I started getting this issue around 6.4.0 version of kde, it was working correctly before. -- You are receiving this mail because: You are watching all bug changes.
