[plasmashell] [Bug 370411] Desktop preferences lost on login for dual screen
https://bugs.kde.org/show_bug.cgi?id=370411 --- Comment #8 from Sylvain --- I've updated to plasma 5.8.2 I and I'm still having issues with my desktop preferences on dual screen. It's working better (no more systematic lost on startup but randomly) but I'm not so sure this is exactly a duplicate of the of bug 369665 as this only affect configurations with dual monitors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372446] New: Dual-screen desktop crash after ejecting the optical disk
https://bugs.kde.org/show_bug.cgi?id=372446 Bug ID: 372446 Summary: Dual-screen desktop crash after ejecting the optical disk Product: plasmashell Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bond.never@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.4-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I just clicked on the 'eject' button in the notification area to eject the optical disk from the reader device. Then, I was prompt for the root password, I entered it and clicked on OK. While removing the ejected disk, the desktop crashed. - Unusual behavior I noticed: After crashing, the desktop reloaded itself and an icon notifying that a crash occured appeared in the notification area. I also noticed that the wallpaper of my second monitor was rested to KDE's default (but not the wallpaper of the primary screen) and when I open back my browser (chromium), all my tabs were closed and I wasn't prompted to retore my previous session after a crash (witch was the expected behavior). I know that Chromium has nothing to do with KDE but maybe the behavior is symptomatic of something ... -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9be030c7c0 (LWP 2403))] Thread 44 (Thread 0x7f5a7d17e700 (LWP 6471)): #0 0x7f9bd9a3a48d in poll () at /usr/lib/libc.so.6 #1 0x7f9bce95b121 in () at /usr/lib/libpulse.so.0 #2 0x7f9bce94c8f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f9bce94cf8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f9bce94d040 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f9bce95b069 in () at /usr/lib/libpulse.so.0 #6 0x7f9bce2ebed8 in () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #7 0x7f9bd923d454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f9bd9a437df in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7f5a7e47f700 (LWP 6406)): #0 0x7f9bd924310f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9bda12ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9bde09a395 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f9bde09ac8a in () at /usr/lib/libQt5Quick.so.5 #4 0x7f9bda12dd78 in () at /usr/lib/libQt5Core.so.5 #5 0x7f9bd923d454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f9bd9a437df in clone () at /usr/lib/libc.so.6 Thread 42 (Thread 0x7f9a80ff9700 (LWP 6017)): #0 0x7f9bd924310f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9bda12ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9b15dd31c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f9b15dd7988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f9b15dd2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f9b15dd79e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f9b15dd2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f9b15dd51f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f9bda12dd78 in () at /usr/lib/libQt5Core.so.5 #9 0x7f9bd923d454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f9bd9a437df in clone () at /usr/lib/libc.so.6 Thread 41 (Thread 0x7f9a817fa700 (LWP 6016)): #0 0x7f9bd924310f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9bda12ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9b15dd31c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f9b15dd7988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f9b15dd2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f9b15dd79e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f9b15dd2263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f9b15dd79e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f9b15dd2263 in ThreadWeaver::Weaver::app
[plasma4] [Bug 350349] Crash when ejecting a CD
https://bugs.kde.org/show_bug.cgi?id=350349 Sylvain changed: What|Removed |Added CC||bond.never@gmail.com --- Comment #1 from Sylvain --- *** Bug 372446 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372446] Dual-screen desktop crash after ejecting the optical disk
https://bugs.kde.org/show_bug.cgi?id=372446 Sylvain changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Sylvain --- *** This bug has been marked as a duplicate of bug 350349 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372446] Dual-screen desktop crash after ejecting the optical disk
https://bugs.kde.org/show_bug.cgi?id=372446 Sylvain changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370411] Desktop preferences lost on login for dual screen
https://bugs.kde.org/show_bug.cgi?id=370411 Sylvain changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370411] Desktop preferences lost on login for dual screen
https://bugs.kde.org/show_bug.cgi?id=370411 Sylvain changed: What|Removed |Added Version|5.8.0 |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 466124] New: kmail preview pane empty on wayland nvidia
https://bugs.kde.org/show_bug.cgi?id=466124
Bug ID: 466124
Summary: kmail preview pane empty on wayland nvidia
Classification: Applications
Product: kmail2
Version: 5.22.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: message list
Assignee: kdepim-b...@kde.org
Reporter: ago.sylv...@gmail.com
Target Milestone: ---
SUMMARY
Under wayland with nvidia, when opening kontact (or kmail alone), the preview
pane for email does not show the email contents and lots of error show in the
terminal. This does not happen on x11. Opening preferences, changing the layout
back and forth fixed it.
STEPS TO REPRODUCE
1. Launch a wayland session
2. Open Kontact
3. Kmail mail preview pane is empty
4. Open preferences, change in layout the settings of preview pane ("do not
show" -> apply -> "show below" -> apply)
5. Preview pane is visible.
OBSERVED RESULT
Preview pane is empty until settings are changed back and forth and terminal
show the following output:
```
[21307:21355:0220/180424.309479:ERROR:gl_context_egl.cc(259)] eglCreateContext
failed with error EGL_BAD_CONTEXT
[21307:21355:0220/180424.309492:ERROR:gpu_channel_manager.cc(753)]
ContextResult::kFatalFailure: Failed to create shared context for
virtualization.
[21307:21355:0220/180424.309498:ERROR:shared_image_stub.cc(470)]
SharedImageStub: unable to create context
[21307:21355:0220/180424.309506:ERROR:gpu_channel.cc(449)] GpuChannel: Failed
to create SharedImageStub
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
[21307:21355:0220/180434.684707:ERROR:gl_context_egl.cc(259)] eglCreateContext
failed with error EGL_BAD_CONTEXT
[21307:21355:0220/180434.684727:ERROR:gpu_channel_manager.cc(753)]
ContextResult::kFatalFailure: Failed to create shared context for
virtualization.
[21307:21355:0220/180434.684733:ERROR:shared_image_stub.cc(470)]
SharedImageStub: unable to create context
[21307:21355:0220/180434.684744:ERROR:gpu_channel.cc(449)] GpuChannel: Failed
to create SharedImageStub
org.kde.pim.akonadicore: Received response with a different tag!
```
EXPECTED RESULT
Preview pane should work
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700 CPU @ 3.60GHz
Memory: 47.0 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
Manufacturer: Dell Inc.
Product Name: XPS 8920
System Version: 1.0.10
ADDITIONAL INFORMATION
nividia driver installed from rpm-fusion repo.
| NVIDIA-SMI 525.89.02Driver Version: 525.89.02CUDA Version: 12.0 |
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 409679] Kmail crash when open through a mailto link
https://bugs.kde.org/show_bug.cgi?id=409679 --- Comment #4 from Sylvain --- Tried to reproduce it with Version 5.21.1 (22.08.1) but nothing wrong happen. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387618] words less than 3 letters are ignored
https://bugs.kde.org/show_bug.cgi?id=387618 Sylvain changed: What|Removed |Added CC||ago.sylv...@gmail.com --- Comment #13 from Sylvain --- I was going to open a bug on the same issue, as it has been bugging me for several years now (should have done it earlier, sorry). I often search for japanese names and these are often two kanjis (multibytes characters, for example 田中). I understand also the need for country code, etc. I was looking in the source to see where this check is done and see if I could fix it (I am not a C++ programmer, but I thought it could be easy), but I couldn't find the code... What I want to propose is that a first check is done : are the two characters multibytes (CJK) strings? are both letters capitalize? and if one is validated, the search is started. This could limit two "letters" search to CJK languages and for abbreviation. Would that be possible? Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436380] New: activities:///current/ should be a valid startup location
https://bugs.kde.org/show_bug.cgi?id=436380 Bug ID: 436380 Summary: activities:///current/ should be a valid startup location Product: dolphin Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ago.sylv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 138018 --> https://bugs.kde.org/attachment.cgi?id=138018&action=edit screenshot showing the error SUMMARY I want to setup dolphin to start with the location activities:///current/ so that anytime I open dolphin, it will open with files and folders I linked with the activities. (This is possible in the folder widget) STEPS TO REPRODUCE 1. Open dolphin 2. Navigate to activities:///current/ 3. Open Settings/Startup 4. Set startup location to activities:///current/ or by clicking "use current location" OBSERVED RESULT Error appears when applying the change: "The location for the home folder is invalid or does not exist, it will not be applied." EXPECTED RESULT activities:/// or tags:///, etc. as startup location should be valid SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 34 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436380] activities:///current/ should be a valid startup location
https://bugs.kde.org/show_bug.cgi?id=436380 --- Comment #2 from Sylvain --- Bug fixed before submitted! Thanks a lot for the hard work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375902] rename files linked to activity in folderview delete/move the file and corrupt file name
https://bugs.kde.org/show_bug.cgi?id=375902 Sylvain changed: What|Removed |Added CC||ago.sylv...@gmail.com --- Comment #8 from Sylvain --- I can confirm that behavior :renaming a file in folder view showing files link to activities, lead to the filename being corrupt and moved to the home folder under new corrupt name. Plasma version 5.18.5 Framework: 5.70.0 Qt: 5.14.2 Fedora 32 -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 458781] Can't use program
https://bugs.kde.org/show_bug.cgi?id=458781
Sylvain changed:
What|Removed |Added
CC||ago.sylv...@gmail.com
--- Comment #2 from Sylvain ---
Same problem here.
Using the flathub version on fedora silverblue. I will check tomorrow on my kde
workstation (fedora kde spin).
Console output:
$ flatpak run org.kde.ktouch
QSocketNotifier: Can only be used with threads started with QThread
qCoreApp Application(0x7ffc9f796c60)
qrc:/ktouch/qml/trainingscreen/TrainingScreenToolbar.qml:42:5: QML Connections:
Implicitly defined onFoo properties in Connections are deprecated. Use this
syntax instead: function onFoo() { ... }
qrc:/ktouch/qml/homescreen/HomeScreen.qml:22:5: QML Connections: Implicitly
defined onFoo properties in Connections are deprecated. Use this syntax
instead: function onFoo() { ... }
qrc:/ktouch/qml/keyboard/KeyItem.qml:193: TypeError: Cannot read property
'height' of null
qrc:/ktouch/qml/keyboard/KeyLabel.qml:52: TypeError: Cannot read property
'height' of null
qrc:/ktouch/qml/keyboard/KeyLabel.qml:52: TypeError: Cannot read property
'height' of null
qrc:/ktouch/qml/keyboard/KeyLabel.qml:52: TypeError: Cannot read property
'height' of null
qrc:/ktouch/qml/keyboard/KeyLabel.qml:52: TypeError: Cannot read property
'height' of null
qrc:/ktouch/qml/keyboard/KeyItem.qml:226: TypeError: Cannot read property
'width' of null
qrc:/ktouch/qml/keyboard/KeyItem.qml:224: TypeError: Cannot read property
'width' of null
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
info:
$ flatpak info org.kde.ktouch
KTouch - Touch Typing Tutor
ID: org.kde.ktouch
Ref: app/org.kde.ktouch/x86_64/stable
Arch: x86_64
Branch: stable
Version: 22.08.2
License: GPL-2.0+
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 8.9 MB
Runtime: org.kde.Platform/x86_64/5.15-21.08
Sdk: org.kde.Sdk/x86_64/5.15-21.08
Commit: 315507bc90d7a2a42b53096f62510509eabdaacbb9634b8bbde242ff29bbbd98
Parent: 6ccf4b252d400b299528c7b282e2d1e97c1e07fa2a2a24c7a7fe7862075ff18e
Subject: Update libxkbfile-1.1.0.tar.gz to 1.1.1 (12702c4d)
Date: 2022-10-18 03:34:34 +
System info
Fedora Linux 36.20220813.0 (Silverblue)
Gnome version: 42.3
Windowing system: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[ktouch] [Bug 422088] Can't type in Wayland
https://bugs.kde.org/show_bug.cgi?id=422088 Sylvain changed: What|Removed |Added CC||ezvezdo...@gmail.com --- Comment #13 from Sylvain --- *** Bug 458781 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 458781] Can't use program
https://bugs.kde.org/show_bug.cgi?id=458781 Sylvain changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Sylvain --- *** This bug has been marked as a duplicate of bug 422088 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390251] Plasma crash when copying files
https://bugs.kde.org/show_bug.cgi?id=390251 Sylvain changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Sylvain --- I just ran some tests with Plasma 5.20.4 and I was not able to reproduce the issue. So, please consider this as resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385395] [Openconnect] Autoconnect and save password for VPN openconnect connection
https://bugs.kde.org/show_bug.cgi?id=385395 Sylvain changed: What|Removed |Added CC||kikiesttoujour...@gmail.com --- Comment #7 from Sylvain --- Same issue in Manjaro KDE whereas it works in Mate ! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434126] New: Sort by Name should default to A-Z
https://bugs.kde.org/show_bug.cgi?id=434126 Bug ID: 434126 Summary: Sort by Name should default to A-Z Product: dolphin Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ago.sylv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If one change the sort order from "modification time" to "name", the order remain "Z-A". When sorting by modification time, it make sense to have "Newest First" but then when shifting to sort by "name", it should default to "A-Z". STEPS TO REPRODUCE 1. Sort by Modification Time 2. Order Newest First 3. Sort by Name OBSERVED RESULT Need to also adjust the order "A-Z" to have the files "correctly" sorted. EXPECTED RESULT The files should get sorted "A-Z" automatically when the "Sort by Name" is selected. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora KDE (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406348] New: dolphin produces a bug instead of browsing kdeconnect device
https://bugs.kde.org/show_bug.cgi?id=406348 Bug ID: 406348 Summary: dolphin produces a bug instead of browsing kdeconnect device Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: kde.s...@9ox.net Target Milestone: --- Created attachment 119312 --> https://bugs.kde.org/attachment.cgi?id=119312&action=edit screenshot of the request to file a bug by dolphin KDEconnect correctly launches and is active both on mobile device (Sony XZ2C with latest updates) and on laptop OS (Kubuntu 18.04 LTS) at startup, and the connection is made. Dolphin correctly displays my smartphone device in the left shortcuts panel, however after opening it when I click on folder icon towards "All Files" this bug is displayed. It usually happens randomly on and off and is not too much of a nuisance because it "resolves" quickly, actually as I am typing to file this but things have gone back to normal. It seems to be forewarned by an impossibility of copying files on the device, sometimes only in sub-folders, as if these were on read only (chmod r--) for some reason. I suspect this comes from Google's Android design, but who knows ? Also, I use no SD card, this happens with the root filesystem of the smartphone. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406348] dolphin produces a bug instead of browsing kdeconnect device
https://bugs.kde.org/show_bug.cgi?id=406348 --- Comment #2 from Sylvain --- I am copying a few music albums and it seems to work flawlessly, at least for this time. KDEConnect 1.12.6 on mobile KDEConnect 1.3.3 on desktop The latest version of the desktop app does not feature in the LTS Kubuntu's repositories, if there's an error again I'll update to the latest version and see. I've also been willing to try FreeBSD, with Plasma, and just received today « Absolute FreeBSD 3rd edition » published last year. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 407342] New: crashes under Plasma / FreeBSD fresh install
https://bugs.kde.org/show_bug.cgi?id=407342 Bug ID: 407342 Summary: crashes under Plasma / FreeBSD fresh install Product: frameworks-baloo Version: 5.56.0 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: kde.s...@0sg.net Target Milestone: --- Application: baloo_file (5.56.0) Qt Version: 5.12.1 Frameworks Version: 5.56.0 Operating System: FreeBSD 12.0-RELEASE-p3 amd64 Distribution (Platform): FreeBSD Ports -- Information about the crash: - What I was doing when the application crashed: logging in This first happened a couple times (also on logging in) with "/usr/local/bin/kdeinit5" supposedly missing - I couldn't find if there was a package to install to solve this as suggested. Here's the bug report from this first bug. I have installed the kde5 meta-package from the binary packages (not the ports tree). Now with baloo (automatic bug report, second bug) === Application: kded5 (kded5), signal: Bus error (lldb) process attach --pid 92746 Process 92746 stopped Executable module set to "/usr/local/bin/kdeinit5". Architecture set to: x86_64--freebsd12.0. (lldb) set term-width 200 (lldb) thread info thread #1: tid = 100185, 0x00080193884a libc.so.7`__sys_nanosleep + 10, name = 'kdeinit5' (lldb) bt all * thread #1, name = 'kdeinit5' * frame #0: 0x00080193884a libc.so.7`__sys_nanosleep + 10 frame #1: 0x0008011da17c libthr.so.3`___lldb_unnamed_symbol36$$libthr.so.3 + 44 frame #2: 0x00080189ee0b libc.so.7`_sleep + 59 frame #3: 0x0008002583ca libKF5Crash.so.5`___lldb_unnamed_symbol6$$libKF5Crash.so.5 + 1450 frame #4: 0x000800257b3e libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1454 frame #5: 0x0008011dd4b6 libthr.so.3`___lldb_unnamed_symbol101$$libthr.so.3 + 214 frame #6: 0x0008011dca22 libthr.so.3`___lldb_unnamed_symbol82$$libthr.so.3 + 322 frame #7: 0x7003 frame #8: 0x00080252d15a libglib-2.0.so.0`g_spawn_command_line_sync + 106 frame #9: 0x0008075e32c1 libgio-2.0.so.0`___lldb_unnamed_symbol1409$$libgio-2.0.so.0 + 289 frame #10: 0x0008075e2e5d libgio-2.0.so.0`g_dbus_address_get_for_bus_sync + 381 frame #11: 0x0008075ef578 libgio-2.0.so.0`___lldb_unnamed_symbol1543$$libgio-2.0.so.0 + 88 frame #12: 0x0008075ef4d1 libgio-2.0.so.0`g_bus_get_sync + 49 frame #13: 0x0008074bc30d libaccounts-glib.so.0`___lldb_unnamed_symbol77$$libaccounts-glib.so.0 + 701 frame #14: 0x00080758dd88 libgio-2.0.so.0`g_initable_new_valist + 200 frame #15: 0x00080758dcac libgio-2.0.so.0`g_initable_new + 124 frame #16: 0x000807469310 libaccounts-qt5.so.1`Accounts::Manager::Manager(QObject*) + 128 frame #17: 0x000807456354 libkaccounts.so.1`KAccounts::accountsManager(void) + 68 frame #18: 0x000807447299 accounts.so`___lldb_unnamed_symbol4$$accounts.so + 281 frame #19: 0x000807449cb8 accounts.so`___lldb_unnamed_symbol21$$accounts.so + 56 frame #20: 0x000801c46470 libKF5CoreAddons.so.5`KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) + 880 frame #21: 0x0008062577c3 libkdeinit5_kded5.so`___lldb_unnamed_symbol15$$libkdeinit5_kded5.so + 1955 frame #22: 0x000806256aa5 libkdeinit5_kded5.so`___lldb_unnamed_symbol11$$libkdeinit5_kded5.so + 501 frame #23: 0x000806259964 libkdeinit5_kded5.so`___lldb_unnamed_symbol30$$libkdeinit5_kded5.so + 68 frame #24: 0x00080625b35a libkdeinit5_kded5.so`kdemain + 2890 frame #25: 0x0020ac68 kdeinit5`___lldb_unnamed_symbol16$$kdeinit5 + 6584 frame #26: 0x002087c7 kdeinit5`___lldb_unnamed_symbol12$$kdeinit5 + 5239 frame #27: 0x0020611b kdeinit5`___lldb_unnamed_symbol1$$kdeinit5 + 283 thread #2, name = 'kdeinit5' frame #0: 0x00080252a741 libglib-2.0.so.0`g_mutex_lock + 1 frame #1: 0x0008024e2e88 libglib-2.0.so.0`___lldb_unnamed_symbol117$$libglib-2.0.so.0 + 392 frame #2: 0x0008024e2fb4 libglib-2.0.so.0`g_main_context_iteration + 100 frame #3: 0x00080167c84b libQt5Core.so.5`QEventDispatcherGlib::processEvents(QFlags) + 139 frame #4: 0x0008016233ce libQt5Core.so.5`QEventLoop::exec(QFlags) + 430 frame #5: 0x00080145fdfc libQt5Core.so.5`QThread::exec(void) + 140 frame #6: 0x0008003339c3 libQt5DBus.so.5`___lldb_unnamed_symbol12$$libQt5DBus.so.5 + 19 frame #7: 0x000801460c93 libQt5Core.so.5`___lldb_unnamed_symbol206$$libQt5Core.so.5 + 211 frame #8: 0x0008011d7776 libthr.so.3`___lldb_unnamed_symbol1$$libthr.so.3 + 326 thread #3, name = 'kdeinit5' frame #0: 0x0008011dfc9d libthr.so.3`___lldb_unnamed_symbol119$$libthr.so.3 + 125 frame #1: 0x0008011df86f libthr.so.3`___lldb_unnamed_
[kmail2] [Bug 409679] New: Kmail crash when open through a mailto link
https://bugs.kde.org/show_bug.cgi?id=409679 Bug ID: 409679 Summary: Kmail crash when open through a mailto link Product: kmail2 Version: 5.11.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sylv...@sbx.pm Target Milestone: --- Application: kmail (5.11.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon Plasma LTS Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I clicked on a link like mailto:x...@yyy.com, in Firefox. Kmail never opened but the error reporting tool was shown. I tried twice and the error was thrown each times. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f898767bbc0 (LWP 26688))] Thread 20 (Thread 0x7f88cbfff700 (LWP 27595)): #0 0x7f8979e31ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f88cbffe710, expected=0, futex_word=0x7f88cbffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f88cbffe7b0, mutex=0x7f88cbffe8a8, cond=0x7f88cbffe8d0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f88cbffe8d0, mutex=0x7f88cbffe8a8, abstime=0x7f88cbffe7b0) at pthread_cond_wait.c:667 #3 0x7f896ef0cb17 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f896ef0d46a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f896ef0d552 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f896eecdfb1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f896eed04c7 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f896eed0ab4 in base::internal::SchedulerWorker::RunPooledWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f896ef0f561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8979e2b6db in start_thread (arg=0x7f88cbfff700) at pthread_create.c:463 #11 0x7f89846b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f88f8ff9700 (LWP 27552)): #0 0x7f8979e319f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f88f8ff8908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f88f8ff88b8, cond=0x7f88f8ff88e0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f88f8ff88e0, mutex=0x7f88f8ff88b8) at pthread_cond_wait.c:655 #3 0x7f896ef0ca49 in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f896ef0d478 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f896ef0d50f in base::WaitableEvent::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f896eecdfc8 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f896eed07f6 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f896eed0b34 in base::internal::SchedulerWorker::RunDedicatedWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f896ef0f561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8979e2b6db in start_thread (arg=0x7f88f8ff9700) at pthread_create.c:463 #11 0x7f89846b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f88f97fa700 (LWP 27549)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f89846c7474 in ___fprintf_chk (fp=0x7f89849828b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f89645d06a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f89645b89ad in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f89645b8b44 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f89645ba46c in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f89645b0114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f896ef12db4 in base::MessagePumpLibevent::Run(base::Messag
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Sylvain changed: What|Removed |Added CC||ago.sylv...@gmail.com --- Comment #18 from Sylvain --- Thanks for developing the import functions which I feel is essential to allow recovery from backup. I have a number of vaults that were encrypted with cryfs on kubuntu 18.04. I moved to fedora kde spin and tried to import these vaults. I installed cryfs from copr as it was not available in the repo (this should be reported to fedora perhaps). I launched the import function with qdbus org.kde.kded5 /modules/plasmavault requestImportVault ; selected cryfs, the location of data and mount point but the "next button" remains greyed, only back and cancel are clickable. The terminal does not show any message. I have a backup of unencrypted data so it is not a problem but if I can of any help... -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #20 from Sylvain --- Sorry for the delay. I was working from home and the problem is on my lab pc... I attach a screenshot to show what I mean. In the screenshot attached I am trying to import the vault named "Grades and Scores", for which the encrypted data is in the folder "/home/sylvain/Classes/Grades and Scores" and the mountpoint is "/home/sylvain/Vaults/Grades and Scores/" which is an empty folder. I tried to rename the folder to remove space. For cryfs, the package I installed is : https://copr.fedorainfracloud.org/coprs/fcsm/cryfs/ Is there any way to turn debug flag on? The backup from plasmavaultrc contains the following for that vault. I could try to reimport manually but I am ok to try to debug first: [/home/sylvain/Classes/Grades and Scores] activities=1bfcdc1a-fe56-4234-93d6-1379e47f85a2 backend=cryfs lastError=Unknown device (code: 1) lastStatus=2 mountPoint=/home/sylvain/Vaults/Grades and Scores name=Grades and Scores -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #21 from Sylvain --- Created attachment 129037 --> https://bugs.kde.org/attachment.cgi?id=129037&action=edit cannot import vault the "next" button is greyed on the last step is greyed and no error is shown in the terminal -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #23 from Sylvain --- The trailing slash worked! That was not stupid :) When we use the browse button, the trailing slash is not added, so it has to be added manually afterward. Another minor point, there is no cursor appearing when we click in the text field and (for example in the next screen for password input) it is not possible to use tab to go to the next field. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #24 from Sylvain --- I believe it is in types.cpp the normalise function. I tried to look at the code (I dont know C++) but it seems it removes the trailing slash if it exists. But it was there on purpose I believe... Sorry it would take time for me to understand why this function is here and if on the reverse adding a slash here would break stuff somewhere else. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #26 from Sylvain --- No problem and sorry to not be that useful. Thanks to you for vault and your contributions. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 392275] New: Konversation crashes at shutdown when gedit has unsaved documents
https://bugs.kde.org/show_bug.cgi?id=392275 Bug ID: 392275 Summary: Konversation crashes at shutdown when gedit has unsaved documents Product: konversation Version: 1.7.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: psn00ps-...@yahoo.fr Target Milestone: --- Application: konversation (1.7.4) Qt Version: 5.9.4 Frameworks Version: 5.42.0 Operating System: Linux 4.15.9-200.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: Here is the context: gedit is open and has a document open with modifications. I click on shutdown withing gnome-shell gedit offers me to cancel the shutdown in order to save the modifications. Konversation turns to a half-closed state and crashes when I try to look at its window. The crash can be reproduced every time. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fa3a6dff940 (LWP 3299))] Thread 5 (Thread 0x7fa3916ba700 (LWP 3606)): #0 0x7fa3b19420ed in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa3aaf14150 in read (__nbytes=16, __buf=0x7fa3916b9a50, __fd=) at /usr/include/bits/unistd.h:44 #2 0x7fa3aaf14150 in g_wakeup_acknowledge (wakeup=0x55f966956f40) at gwakeup.c:210 #3 0x7fa3aaed0088 in g_main_context_check (context=context@entry=0x7fa37c000990, max_priority=2147483647, fds=fds@entry=0x7fa37c0012d0, n_fds=n_fds@entry=1) at gmain.c:3750 #4 0x7fa3aaed0520 in g_main_context_iterate (context=context@entry=0x7fa37c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3969 #5 0x7fa3aaed068c in g_main_context_iteration (context=0x7fa37c000990, may_block=1) at gmain.c:4033 #6 0x7fa3b276ea4b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fa3b271c76a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7fa3b256d9aa in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7fa3b2571ec2 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fa3b053c36d in start_thread (arg=0x7fa3916ba700) at pthread_create.c:456 #11 0x7fa3b1952b4f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 4 (Thread 0x7fa3920c2700 (LWP 3602)): #0 0x7ffc90b6bac5 in clock_gettime () #1 0x7fa3b1961c36 in __GI___clock_gettime (clock_id=1, tp=0x7fa3920c1980) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fa3b276e2c1 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x7fa3b276ce09 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x7fa3b276d205 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x7fa3b276e72c in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x7fa3b276e7ce in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #7 0x7fa3aaecfad9 in g_main_context_prepare (context=context@entry=0x7fa388000990, priority=priority@entry=0x7fa3920c1af0) at gmain.c:3536 #8 0x7fa3aaed04ab in g_main_context_iterate (context=context@entry=0x7fa388000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3952 #9 0x7fa3aaed068c in g_main_context_iteration (context=0x7fa388000990, may_block=1) at gmain.c:4033 #10 0x7fa3b276ea4b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7fa3b271c76a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7fa3b256d9aa in QThread::exec() () at /lib64/libQt5Core.so.5 #13 0x7fa3b298c659 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #14 0x7fa3b2571ec2 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #15 0x7fa3b053c36d in start_thread (arg=0x7fa3920c2700) at pthread_create.c:456 #16 0x7fa3b1952b4f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 3 (Thread 0x7fa393b47700 (LWP 3541)): #0 0x7fa3b1946a5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa3aaed0579 in g_main_context_poll (priority=, n_fds=1, fds=0x7fa3840010c0, timeout=, context=0x55f9668b8420) at gmain.c:4271 #2 0x7fa3aaed0579 in g_main_context_iterate (context=0x55f9668b8420, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3967 #3 0x7fa3aaed0912 in g_main_loop_run (loop=0x55f9668ba310) at gmain.c:4168 #4 0x7fa3975d7db6 in gdbus_shared_thread_func (user_data=0x55f9668b9d00) at gdbusprivate.c:252 #5 0x7fa3aaef7516 in g_thread_proxy (data=0x55f966861f70) at gthread.c:784 #6 0x7fa3b053c36d in start_thread (arg=0x7fa393b47700) at pthread_create.c:456 #
[plasmashell] [Bug 390251] New: Plasma crash when copying files
https://bugs.kde.org/show_bug.cgi?id=390251 Bug ID: 390251 Summary: Plasma crash when copying files Product: plasmashell Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bond.never@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.5) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.15.1-2-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I just copied a folder from a network location to an usb stick. When I pasted the folder, plasma "crashed" : desktop bar disapear, the windows title bar disapear and the seoncd screen wallpaper became all black. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f71d0bb9800 (LWP 946))] Thread 33 (Thread 0x7f708111d700 (LWP 2024)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f7081db7700 (LWP 2023)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f7082a44700 (LWP 2022)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f70835fe700 (LWP 2021)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f7083fff700 (LWP 2020)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f7098ffd700 (LWP 2019)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f7099c8a700 (LWP 2018)): #0 0x7f71c993e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f71ca78500c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f71ce5c89ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f71ce5c8e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f71ca783b2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f71c993808c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71ca08be7f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f709a937700
[plasmashell] [Bug 387175] New: Plasma crash on startup
https://bugs.kde.org/show_bug.cgi?id=387175 Bug ID: 387175 Summary: Plasma crash on startup Product: plasmashell Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bond.never@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.13.12-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: First booting my computer, auto-logon was enabled so plama had just loaded to the desktop - Unusual behavior I noticed: Desktop blink and disapear then the render was kind of "reinit" and everything goes right again. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f93788800 (LWP 957))] Thread 19 (Thread 0x7f1e92db1700 (LWP 1332)): #0 0x7f1f8c5eb38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1f8d42e45c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1f911ca7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1f911cac44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1f8d42cfcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f1f8c5e508a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1f8cd3847f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f1e937fe700 (LWP 1331)): #0 0x7f1f8c5eb38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1f8d42e45c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1f911ca7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1f911cac44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1f8d42cfcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f1f8c5e508a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1f8cd3847f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f1e93fff700 (LWP 1330)): #0 0x7f1f8c5eb38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1f8d42e45c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1f911ca7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1f911cac44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1f8d42cfcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f1f8c5e508a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1f8cd3847f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f1ea8e20700 (LWP 1329)): #0 0x7f1f8c5eb38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1f8d42e45c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1f911ca7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1f911cac44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1f8d42cfcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f1f8c5e508a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1f8cd3847f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f1eaa5fd700 (LWP 1324)): [KCrash Handler] #5 0x7f1f8cc768a0 in raise () at /usr/lib/libc.so.6 #6 0x7f1f8cc77f09 in abort () at /usr/lib/libc.so.6 #7 0x7f1f8ccb9517 in __libc_message () at /usr/lib/libc.so.6 #8 0x7f1f8ccbfc84 in malloc_printerr () at /usr/lib/libc.so.6 #9 0x7f1f8ccc1599 in _int_free () at /usr/lib/libc.so.6 #10 0x7f1f8e16d61c in () at /usr/lib/libQt5Gui.so.5 #11 0x7f1f8e16c53a in () at /usr/lib/libQt5Gui.so.5 #12 0x7f1f8e13679b in () at /usr/lib/libQt5Gui.so.5 #13 0x7f1f8e137150 in QOpenGLShaderProgram::link() () at /usr/lib/libQt5Gui.so.5 #14 0x7f1f911bd2fa in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () at /usr/lib/libQt5Quick.so.5 #15 0x7f1f91189200 in () at /usr/lib/libQt5Quick.so.5 #16 0x7f1f91189bed in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #17 0x7f1f9118b076 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #18 0x7f1f911908ee in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #19 0x7f1f91180f22 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #20 0x7f1f911813ec in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #21 0x7f1f911bc6c0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #22 0x7f1f9121b210 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #23 0x7f1f9
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 Sylvain changed: What|Removed |Added CC||kde.s...@9ox.net --- Comment #18 from Sylvain --- jonaski's Strawbs, a fork of Clementine itself a fork of Amarok, seems to have fixed this : https://github.com/clementine-player/Clementine/issues/5524#issuecomment-417370333 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 404126] New: Use cover artwork as translucent background for main panel/playlist
https://bugs.kde.org/show_bug.cgi?id=404126 Bug ID: 404126 Summary: Use cover artwork as translucent background for main panel/playlist Product: amarok Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: kde.s...@9ox.net Target Milestone: kf5 Glad to see Amarok is going to be maintained again. It is one of the main reasons why I came back to KDE and I was disappointed to see it's not part of the main software suite anymore. I hope this is going well ? I'm willing to help. Here's a suggestion : I would love to have the cover art for the current playing track/album displayed as the main panel/playlist background image. This would only need a few settings regarding desired transparency level (and possibly where/how to locate cover pictures – mine are in album folder named after %artist - %album.jpg). Perhaps also it could be enhanced to display cover art pictures for each album's total tracks following eachother in a playlist, i.e. for instance if my playlist consists of three albums in a row, have all three covers take up each the space of their corresponding tracks, no more no less. This sounds a bit more hazardous. Just an idea. I use Kubuntu Bionic Beaver 18.04 LTS with KDE Plasma. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 404126] Use cover artwork as translucent background for main panel/playlist
https://bugs.kde.org/show_bug.cgi?id=404126 --- Comment #1 from Sylvain --- NOTE : see the original suggestion to the Strawberry software developper(s) : https://github.com/jonaski/strawberry/issues/74 Strawberry is a recent fork of Clementine, itself an older -and deprecating- fork of Amarok. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404153] New: Carry [copying] operation on while waiting for prompt after minor error
https://bugs.kde.org/show_bug.cgi?id=404153 Bug ID: 404153 Summary: Carry [copying] operation on while waiting for prompt after minor error Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kde.s...@9ox.net CC: elvis.angelac...@kde.org Target Milestone: --- Oftentimes I use Dolphin to manage different disks and different partitions systems. This is prone to producing errors, because some files on my ext4 partitions ext4 have weird characters in their filenames (notably two dots, exclamation mark and interrogation mark) which are incompatible with exfat FS. When such an error happens, Dolphin asks what to do about it (Ignore, Retry etc) and it seems the operation is suspended until the user would prompt in. This is quite inconvenient as it prevents getting away from a potentially long task that one hopes would complete after a while. Ideally I suppose the task would carry on running in the background, and potential new errors add up to the error window list (instead of triggering multiple windows). In my case the system could simply suggest to replace the problematic characters. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404154] New: Nothing appears in Recent Files (Places panel section)
https://bugs.kde.org/show_bug.cgi?id=404154 Bug ID: 404154 Summary: Nothing appears in Recent Files (Places panel section) Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: kde.s...@9ox.net Target Milestone: --- The "Recent Files" section in Dolphin's Places panel displays nothing. I can open the four timelines "today", "yesterday", "this month" and "last month" but it is as if there had been no activity on the computer, while obviously I constantly create, save and edit files of all kinds. I use KDE on Kubuntu 18.04.1 LTS with Dolphin 17.12.23 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 404155] New: Need to select/click on last copied item to enable copying it
https://bugs.kde.org/show_bug.cgi?id=404155 Bug ID: 404155 Summary: Need to select/click on last copied item to enable copying it Product: klipper Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kde.s...@9ox.net Target Milestone: --- It randomly happens with Klipper that I select a portion of text and press Ctrl+C, only then Ctrl+V copies nothing as if the clipboard is empty. I have to open the Klipper applet menu and select the copied item (which is actually present) by clicking on it, and then I can copy it fine. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404172] New: "Sort by > Document > Word count" ineffective
https://bugs.kde.org/show_bug.cgi?id=404172 Bug ID: 404172 Summary: "Sort by > Document > Word count" ineffective Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kde.s...@9ox.net CC: elvis.angelac...@kde.org Target Milestone: --- Neither .txt not .odt or .doc files are sorted by word count when using this option. The file sorting order does not change. Dolphin 17.12.3 on Kubuntu 18.04 LTS LibreOffice 6.0.7.3 Kate 17.12.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404154] Nothing appears in Recent Files (Places panel section)
https://bugs.kde.org/show_bug.cgi?id=404154 --- Comment #3 from Sylvain --- I have some files in that folder, they also appear in the K menu > Recent documents (the full screen menu opened with Alt+F1 or Meta key). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404154] Nothing appears in Recent Files (Places panel section)
https://bugs.kde.org/show_bug.cgi?id=404154 --- Comment #5 from Sylvain --- Opening timeline:/calendar/ in Dolphin provokes no error, but displays an empty folder. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401523] New: enhanced multiple-files renamer
https://bugs.kde.org/show_bug.cgi?id=401523 Bug ID: 401523 Summary: enhanced multiple-files renamer Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kde.s...@9ox.net CC: elvis.angelac...@kde.org Target Milestone: --- A useful addition to Dolphin imho would be a default tool for renaming multiple files at once. It seems a pretty standard feature of any modern file manager to me, and I was disappointed to see that Dolphin has only a very basic tool. I had always been fully satisfied with XFCE's such Thunar tool when using that interface. It allows for different types of pattern renaming, especially ones based on regex. Perhaps a good source to copy. Thank you ! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401524] New: audio metadata tab in file properties
https://bugs.kde.org/show_bug.cgi?id=401524 Bug ID: 401524 Summary: audio metadata tab in file properties Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kde.s...@9ox.net CC: elvis.angelac...@kde.org Target Milestone: --- As a regular music listener, I often need to edit music tracks metadata. As a standalone complex tool I use Kid3, but I would find it useful to have a more "on the go" option available when handling individual files in Dolphin. I've tried to use this extension called "AudioMetadata", but it is deprecated and I've been unable to make it work. Perhaps a good source to start from, however. Thank you ! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401524] audio metadata tab in file properties
https://bugs.kde.org/show_bug.cgi?id=401524 Sylvain changed: What|Removed |Added CC||kde.s...@9ox.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401523] enhanced multiple-files renamer
https://bugs.kde.org/show_bug.cgi?id=401523 Sylvain changed: What|Removed |Added CC||kde.s...@9ox.net -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 401787] New: Can't open mailbox
https://bugs.kde.org/show_bug.cgi?id=401787 Bug ID: 401787 Summary: Can't open mailbox Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: sylvain.196...@free.fr Target Milestone: --- SUMMARY When I click on the folder "INBOX", I get this error message : Can't open mailbox Opening mailbox "INBOX" failed with the following message: SELECT failed: parse error: invalid message sequence number: 43,65,76,81,84 STEPS TO REPRODUCE 1. click on the folder "INBOX", OBSERVED RESULT error message occurs Can't open mailbox Opening mailbox "INBOX" failed with the following message: SELECT failed: parse error: invalid message sequence number: 43,65,76,81,84 I can not read any email. Thank you for your help. EXPECTED RESULT List of emails SOFTWARE/OS VERSIONS Lubuntu 18.10 LXQt Desktop Toolbox - Technical Info LXQt About Version: 0.13.0 LXQt Version: 0.13.0 Qt: 5.11.1 Build type: Release -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401523] enhanced multiple-files renamer
https://bugs.kde.org/show_bug.cgi?id=401523 --- Comment #3 from Sylvain --- (In reply to Kai Uwe Broulik from comment #1) > You can rename multiple files at once and provide a pattern already. From > what I recall there's even work going on right now to improve that UI and > add some feature to it. With Dolphin 17.12.3 under Kubuntu 18.04 I can only find a very basic multiple-files renaming tool, that only allows for numbering the files but erasing their original name. Is my installation missing something ? >From a duplicate report of this one, somebody also mentioned XFCE's Thunar and its excellent tool : https://docs.xfce.org/xfce/thunar/bulk-renamer/start When I was using it under XFCE I felt it offered everything I could require. I'm not trying to tell KDE developers what to say, but as somebody who came to Plasma for an interface with more "breadth", and very satisfied, it just seems odd to me that such a feature isn't included. If the developers are working on it though, great and kudos to them. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 374297] New: An error occured after editing the menu
https://bugs.kde.org/show_bug.cgi?id=374297 Bug ID: 374297 Summary: An error occured after editing the menu Product: kmenuedit Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bond.never@gmail.com Target Milestone: --- Application: kmenuedit (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I removed some elements in the plasma menu (KDE Menu Editor), then I click on the close button. An alert ask me if I wanted to save my changes, I answered yes and then plasma reported me this crash even if nothing abnormal cames to my eyes, except this error report. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6ad66bccc0 (LWP 2))] Thread 2 (Thread 0x7f6abbfff700 (LWP 27779)): #0 0x7f6ad60cd4ed in read () at /usr/lib/libc.so.6 #1 0x7f6acbd17a10 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6acbcd3235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f6acbcd3724 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f6acbcd389c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f6ad1fa62db in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f6ad1f4fd3a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f6ad1d72063 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f6ad35e3de5 in () at /usr/lib/libQt5DBus.so.5 #9 0x7f6ad1d76cf8 in () at /usr/lib/libQt5Core.so.5 #10 0x7f6acd9c4454 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f6ad60da7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f6ad66bccc0 (LWP 2)): [KCrash Handler] #6 0x02e37e00 in () #7 0x7f6ad1242186 in () at /usr/lib/libKF5Notifications.so.5 #8 0x7f6ad1242219 in () at /usr/lib/libKF5Notifications.so.5 #9 0x7f6ad1f7b831 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #10 0x7f6ad1f850df in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #11 0x7f6ad121e5f5 in () at /usr/lib/libKF5Notifications.so.5 #12 0x7f6ad6027990 in __run_exit_handlers () at /usr/lib/libc.so.6 #13 0x7f6ad60279ea in () at /usr/lib/libc.so.6 #14 0x7f6ad6012298 in __libc_start_main () at /usr/lib/libc.so.6 #15 0x004006aa in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378035] New: Plasma crash on Chromium exit
https://bugs.kde.org/show_bug.cgi?id=378035 Bug ID: 378035 Summary: Plasma crash on Chromium exit Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bond.never@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.4-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I closed all the runnning applications windows, finishing by Chromium. After closing chromium, the whole desktop blink and disapear ... then reload with this bug report status in the task bar. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f311de2b800 (LWP 4516))] Thread 47 (Thread 0x7eefb856a700 (LWP 8177)): #0 0x7f3116abfca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f30f3d0be44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f30f2975394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f30f3d0b12c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7f3116ab92e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f311751754f in clone () at /usr/lib/libc.so.6 Thread 46 (Thread 0x7eefb8d6b700 (LWP 8176)): #0 0x7f3116abf756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3117c0558b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f311b95c665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f311b95cf72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f3117c046d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f3116ab92e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f311751754f in clone () at /usr/lib/libc.so.6 Thread 45 (Thread 0x7f2fbcfb6700 (LWP 6981)): #0 0x7f3116abf756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3117c0558b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f30455ec1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f30455f09d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f30455eb263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f30455f0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f30455eb263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f30455ee249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f3117c046d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f3116ab92e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f311751754f in clone () at /usr/lib/libc.so.6 Thread 44 (Thread 0x7f2fbd7b7700 (LWP 6980)): #0 0x7f3116abf756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3117c0558b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f30455ec1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f30455f09d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f30455eb263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f30455f0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f30455eb263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f30455ee249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f3117c046d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f3116ab92e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f311751754f in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7f2fbdfb8700 (LWP 6979)): #0 0x7f3116abf756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3117c0558b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f30455ec1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f30455f09d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f30455eb263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f30455f0a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f30455e
[plasmashell] [Bug 381503] New: Plasma crash on startup
https://bugs.kde.org/show_bug.cgi?id=381503 Bug ID: 381503 Summary: Plasma crash on startup Product: plasmashell Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bond.never@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.2) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.5-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Computer boot just ended, the plasma shell was starting and the desktop was displayed for a second. - Unusual behavior I noticed: The desktop blink, the icons, the task bar and the second screen wallpaper disapear. Everything was K.O. for a few seconds then the desktop loaded again with this crash report. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd4581cbd80 (LWP 1164))] Thread 15 (Thread 0x7fd366eb2700 (LWP 1787)): #0 0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd455cbf8d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fd455cbfd3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd451f1dcbd in () at /usr/lib/libQt5Core.so.5 #5 0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd45183225f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fd367bff700 (LWP 1786)): #0 0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd455cbf8d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fd455cbfd3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd451f1dcbd in () at /usr/lib/libQt5Core.so.5 #5 0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd45183225f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fd374986700 (LWP 1785)): [KCrash Handler] #5 0x7fd3a6fedcb5 in () at /usr/lib/libnvidia-glcore.so.381.22 #6 0x7fd3a6fee035 in () at /usr/lib/libnvidia-glcore.so.381.22 #7 0x7fd3a700b910 in () at /usr/lib/libnvidia-glcore.so.381.22 #8 0x7fd3a6fd1e44 in () at /usr/lib/libnvidia-glcore.so.381.22 #9 0x7fd452c53140 in () at /usr/lib/libQt5Gui.so.5 #10 0x7fd452c535a6 in () at /usr/lib/libQt5Gui.so.5 #11 0x7fd452c1ec85 in () at /usr/lib/libQt5Gui.so.5 #12 0x7fd452c1f5f8 in QOpenGLShaderProgram::link() () at /usr/lib/libQt5Gui.so.5 #13 0x7fd455cb2968 in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () at /usr/lib/libQt5Quick.so.5 #14 0x7fd455c7f6f6 in () at /usr/lib/libQt5Quick.so.5 #15 0x7fd455c80099 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #16 0x7fd455c814c5 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #17 0x7fd455c86c24 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #18 0x7fd455c775cd in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #19 0x7fd455c77a8b in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #20 0x7fd455cb1d40 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #21 0x7fd455d0e868 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #22 0x7fd455cbadec in () at /usr/lib/libQt5Quick.so.5 #23 0x7fd455cbfcf8 in () at /usr/lib/libQt5Quick.so.5 #24 0x7fd451f1dcbd in () at /usr/lib/libQt5Core.so.5 #25 0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0 #26 0x7fd45183225f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fd375787700 (LWP 1784)): #0 0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd455cbf8d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fd455cbfd3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd451f1dcbd in () at /usr/lib/libQt5Core.so.5 #5 0x7fd4510e6297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd45183225f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fd37605b700 (LWP 1783)): #0 0x7fd4510ec39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd451f1f0eb in QWaitCondition::wait(QMutex*, unsigned long
[plasmashell] [Bug 382103] New: Plasma crash on startup
https://bugs.kde.org/show_bug.cgi?id=382103 Bug ID: 382103 Summary: Plasma crash on startup Product: plasmashell Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bond.never@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.7-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Logging into the plasma shell after initial computer boot - Unusual behavior I noticed: Shell blink, the task bar disapear then everything became black and disapear. After a few seconds, it loads up again and everything was restored The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5568630d80 (LWP 1194))] Thread 15 (Thread 0x7f5477fff700 (LWP 1622)): #0 0x7f556155239d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f55623850eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f55661258d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f5566125d3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7f5562383cbd in () at /usr/lib/libQt5Core.so.5 #5 0x7f556154c297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f5561c981ef in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f5484e8c700 (LWP 1621)): #0 0x7f556155239d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f55623850eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f55661258d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f5566125d3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7f5562383cbd in () at /usr/lib/libQt5Core.so.5 #5 0x7f556154c297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f5561c981ef in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f5485cb9700 (LWP 1620)): [KCrash Handler] #5 0x7f5561bde670 in raise () at /usr/lib/libc.so.6 #6 0x7f5561bdfd00 in abort () at /usr/lib/libc.so.6 #7 0x7f5561c1d551 in __libc_message () at /usr/lib/libc.so.6 #8 0x7f5561c23bfb in malloc_printerr () at /usr/lib/libc.so.6 #9 0x7f5561c24fd1 in _int_free () at /usr/lib/libc.so.6 #10 0x7f55630bacd6 in () at /usr/lib/libQt5Gui.so.5 #11 0x7f55630b9c54 in () at /usr/lib/libQt5Gui.so.5 #12 0x7f5563084c85 in () at /usr/lib/libQt5Gui.so.5 #13 0x7f55630855f8 in QOpenGLShaderProgram::link() () at /usr/lib/libQt5Gui.so.5 #14 0x7f5566118968 in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () at /usr/lib/libQt5Quick.so.5 #15 0x7f55660e56f6 in () at /usr/lib/libQt5Quick.so.5 #16 0x7f55660e6099 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #17 0x7f55660e74c5 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #18 0x7f55660ecc24 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #19 0x7f55660dd5cd in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #20 0x7f55660dda8b in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #21 0x7f5566117d40 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #22 0x7f5566174868 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #23 0x7f5566120dec in () at /usr/lib/libQt5Quick.so.5 #24 0x7f5566125cf8 in () at /usr/lib/libQt5Quick.so.5 #25 0x7f5562383cbd in () at /usr/lib/libQt5Core.so.5 #26 0x7f556154c297 in start_thread () at /usr/lib/libpthread.so.0 #27 0x7f5561c981ef in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f5486746700 (LWP 1619)): #0 0x7f556155239d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f55623850eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f55661258d8 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f5566125d3a in () at /usr/lib/libQt5Quick.so.5 #4 0x7f5562383cbd in () at /usr/lib/libQt5Core.so.5 #5 0x7f556154c297 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f5561c981ef in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f54871fa700 (LWP 1618)): #0 0x7f556155239d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f55623850eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.
[kdeconnect] [Bug 390153] spamming proxy
https://bugs.kde.org/show_bug.cgi?id=390153 --- Comment #5 from Sylvain Paré --- So i dont work anymore in this enterprise -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 462312] New: Okular crash on editing form
https://bugs.kde.org/show_bug.cgi?id=462312 Bug ID: 462312 Summary: Okular crash on editing form Classification: Applications Product: okular Version: 22.08.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sylvain.bouc...@gmail.com Target Milestone: --- Application: okular (22.08.3) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 5.15.0-53-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: When I edit a form (already used without problem) at the first letter I press, it crashes The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7f0bc9e24bc8 in GfxResources::doLookupFont(char const*) const () from /lib/x86_64-linux-gnu/libpoppler.so.124 #5 0x7f0bc9e24d42 in GfxResources::lookupFont(char const*) () from /lib/x86_64-linux-gnu/libpoppler.so.124 #6 0x7f0bc9e193f8 in Form::ensureFontsForAllCharacters(GooString const*, std::__cxx11::basic_string, std::allocator > const&, GfxResources*) () from /lib/x86_64-linux-gnu/libpoppler.so.124 #7 0x7f0bc9e1a4f3 in ?? () from /lib/x86_64-linux-gnu/libpoppler.so.124 #8 0x7f0bca0a630c in Poppler::FormFieldText::setText(QString const&) () from /lib/x86_64-linux-gnu/libpoppler-qt5.so.1 #9 0x7f0bf440b29d in ?? () from /lib/x86_64-linux-gnu/libOkular5Core.so.10 #10 0x7f0c05924819 in QUndoStack::push(QUndoCommand*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f0bf4578f7a in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #12 0x7f0c04a220f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0bf457d311 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #14 0x7f0c04a220f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0c056beef9 in QLineEdit::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f0c056bc3d8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f0c04a22128 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f0c056c6709 in QWidgetLineControl::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f0c056c9e9b in QWidgetLineControl::finishChange(int, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f0c056ccb34 in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f0c056befff in QLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f0c055b6708 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f0c05572763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f0c0557a4de in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f0c049ea09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f0c055d23ff in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f0c05572763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f0c049ea09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f0c04e63bfa in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7f0bfe0ab0a4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so #31 0x7f0c04a220f4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f0c04d039d3 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #33 0x7f0c04a17afe in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f0c05572763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7f0c049ea09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f0c049ed187 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f0c04a444a7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f0c02f9ad1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7f0c02fef6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x7f0c02f983c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x
[okular] [Bug 462312] Okular crash on editing form
https://bugs.kde.org/show_bug.cgi?id=462312 --- Comment #1 from Sylvain Bouchet --- Created attachment 154082 --> https://bugs.kde.org/attachment.cgi?id=154082&action=edit the form is in this pdf -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 462312] Okular crash on editing form
https://bugs.kde.org/show_bug.cgi?id=462312 --- Comment #2 from Sylvain Bouchet --- For your information, I've recently update my system to be neon based on ubuntu 22.04 LTS -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 390153] New: spamming proxy
https://bugs.kde.org/show_bug.cgi?id=390153 Bug ID: 390153 Summary: spamming proxy Product: kdeconnect Version: 1.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: sylvain.p...@gmail.com Target Milestone: --- Installed two laptops with kubuntu lastly in our enterprise. Then our admin team brought us bask this issue : our proxy wrote 5Go of acces.log in a week because kdeconnect tried to connect between the two laptops. We had to uninstall kdeconnect. I let you imagine how easy it was to evangelize kde to our admin team then. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 390153] spamming proxy
https://bugs.kde.org/show_bug.cgi?id=390153 --- Comment #2 from Sylvain Paré --- Thanks for your reply. Well why 5 Go in a week ?! It is a bit two much. Perhaps It could try to detect and stop trying to connect. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401726] New: remote keyboard don't work since android update to 9
https://bugs.kde.org/show_bug.cgi?id=401726 Bug ID: 401726 Summary: remote keyboard don't work since android update to 9 Product: kdeconnect Version: 1.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: sylvain.bouc...@gmail.com Target Milestone: --- Created attachment 116662 --> https://bugs.kde.org/attachment.cgi?id=116662&action=edit screenshot of andoid screen SUMMARY On my htc u11 life all was working well, thanks, it was the good times. Then my phone updates to android 9. Since then, the virtual input keyboard doesn't work at all. Note that the virtual mouse works well. STEPS TO REPRODUCE 1. a working phone with the previous version of android 2. update the phone to android 9 3. try the virtual keyboard OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux Mint 18.3 KDE (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.
[kdevelop] [Bug 377470] New: KDevelop sometimes crashes when right-clicking the toolbar
https://bugs.kde.org/show_bug.cgi?id=377470 Bug ID: 377470 Summary: KDevelop sometimes crashes when right-clicking the toolbar Product: kdevelop Version: 5.0.80 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: asusylv...@hotmail.fr Target Milestone: --- Application: kdevelop (5.0.80) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.10.1-1-ck x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Right-clicking the toolbar (couldn't reproduce with another UI element). I could make it crash right-clicking the "new file" button, but I remember having it crash right-clicking a separator. I didn't find a way to reproduce the crash accurately - thread race? It seems to rely on some factor I haven't figured out. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Illegal instruction Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f07e9140600 (LWP 4392))] Thread 14 (Thread 0x7f077f098700 (LWP 4862)): #0 0x7f07df95f756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f07d76b6234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f07d76b6279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f07df9592e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f07e5f3e54f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f077f899700 (LWP 4533)): #0 0x7f07dd751e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f07dd70bc99 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f07dd70c6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7f07dd70c8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f07e685b06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f07e680489a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f07e6626a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f07e662b6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f07df9592e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f07e5f3e54f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f079566d700 (LWP 4466)): #0 0x7f07df95f756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f07e662c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f07dad1c1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f07dad209d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f07dad1b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f07dad20a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f07dad1b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f07dad20a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f07dad1b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f07dad20a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f07dad1b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f07dad1e249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f07e662b6d8 in () at /usr/lib/libQt5Core.so.5 #13 0x7f07df9592e7 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f07e5f3e54f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f0795e6e700 (LWP 4465)): #0 0x7f07df95f756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f07e662c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f07dad1c1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f07dad209d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f07dad1b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f07dad1e249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f07e662b6d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f07df9592e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f07e5f3e54f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f079666f700 (LWP 4464)): #0 0x7f07df95f756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f07e662c58b in QWaitConditio
[plasmashell] [Bug 370411] New: Desktop preferences lost on login for dual screen
https://bugs.kde.org/show_bug.cgi?id=370411 Bug ID: 370411 Summary: Desktop preferences lost on login for dual screen Product: plasmashell Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: bond.never@gmail.com Every time I logout/login or fully reboot the computer, the desktop preferences for my second monitor are lost. Reproducible: Always Steps to Reproduce: 1. Right click on the desktop, select "configure Desktop". 2. Change the wallpaper, set the desktop disposition to folder view, change the icon alignment to columns or whatever you want to customize. 3. Log-out from the session or reboot the computer. Actual Results: When plasma load back, everything was reset to the system's defaults Expected Results: Plasma should have restored my previous settings. This happens whether the graphical components are locked or not. This does not apply if I unplug the second monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370411] Desktop preferences lost on login for dual screen
https://bugs.kde.org/show_bug.cgi?id=370411 Sylvain changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370411] Desktop preferences lost on login for dual screen
https://bugs.kde.org/show_bug.cgi?id=370411 --- Comment #1 from Sylvain --- Ok, after deeper testing, I update what I've said before. This issue does not appears with a simple wallpaper change but appears every times when I switch the disposition from th default "Desktop" to "Folder view". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 332372] Edit and save (PDF) Document Information
https://bugs.kde.org/show_bug.cgi?id=332372 Sylvain changed: What|Removed |Added CC||ago.sylv...@gmail.com --- Comment #1 from Sylvain --- Just wanted to add my 2 cents on this. I have been looking in okular where I can edit the metadata before understanding that it is not possible at the moment. Okular is such a great document reader that I was convinced that editing the metadata was possible The metadata are editable using exiftool, through the command line, it would be nice if this was possible through okular: the field in the property dialog should be editable. Now I understand that okular is a "viewer" but because there is no simple way to edit pdf metadata through the gui under kde, at least to my knowledge", it would be nice if okular could do it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 252550] Dolphin is very slow when listing SMB folders
https://bugs.kde.org/show_bug.cgi?id=252550 Sylvain Paré changed: What|Removed |Added CC||sylvain.p...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 252550] Dolphin is very slow when listing SMB folders
https://bugs.kde.org/show_bug.cgi?id=252550 --- Comment #12 from Sylvain Paré --- Issue stills present here with Dolphin Version 15.12.3 KDE Frameworks 5.23.0 Qt 5.5.1 (built against 5.5.1) Can you reopen this bug please? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 252550] Dolphin is very slow when listing SMB folders
https://bugs.kde.org/show_bug.cgi?id=252550 --- Comment #15 from Sylvain Paré --- agreed konqueror responds much more faster than dolphin here too -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 360299] New: bad appearance with dark themes (oxygen/breeze)
https://bugs.kde.org/show_bug.cgi?id=360299 Bug ID: 360299 Summary: bad appearance with dark themes (oxygen/breeze) Product: muon Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: asusylv...@hotmail.fr CC: aleix...@kde.org, sit...@kde.org With dark themes (tested with Oxygen and Breeze with the Breeze dark color scheme), a white gradient will appear in Muon from the bottom of the toolbar to a little further. It looks bad because of the contrast with dark themes. Reproducible: Always Steps to Reproduce: 1. Set a dark KDE theme 2. (Preferably use Breeze or Oxygen because I only had those issues on those two) 3. Launch muon (no matter what's the tab) Actual Results: The white gradient will appear on the background and kill the aspect of the program. Expected Results: It shouldn't show it. I'm using kubuntu backports. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 360299] bad appearance with dark themes (oxygen/breeze)
https://bugs.kde.org/show_bug.cgi?id=360299 --- Comment #2 from de Langen Sylvain --- Here it is : http://i.imgur.com/Ep6fAc0.png It's pretty much the only program in which I have the problem. Libreoffice looks terrible as well, yet I think this is rather caused by its nature : http://i.imgur.com/UB5GOCO.png . I can't recall of another program encountering the same issue. I use the Breeze Dark color scheme. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 360299] bad appearance with dark themes (oxygen/breeze)
https://bugs.kde.org/show_bug.cgi?id=360299 --- Comment #4 from de Langen Sylvain --- I think it's meant to be a gradient from the toolbar to the actual background. It probably ignores the color scheme. Shouldn't that be to change? -- You are receiving this mail because: You are watching all bug changes.
