[Discover] [Bug 372375] New: System is up-to-date although updates are mentioned
https://bugs.kde.org/show_bug.cgi?id=372375 Bug ID: 372375 Summary: System is up-to-date although updates are mentioned Product: Discover Version: 5.8.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- In the statusbar I see the cogwheel indicating I have pending updates. When I click on it Discover opens and tells me after a second or so that my system is up-to-date -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 449883] New: Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=449883
Bug ID: 449883
Summary: Akonadi crashes
Product: kaddressbook
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: jan.muss...@gmail.com
CC: to...@kde.org
Target Milestone: ---
Application: kaddressbook (5.19.2 (21.12.2))
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I wanted to start Kmail but this didn't work, instead nothing happened on
screen for a long time (several minutes). Then a small window appeared with a
bar in the center which was filled for maybe 3%. I waited again for a couple of
minutes to see if the bar was filled but nothing happened.
I then rebooted and started Akonadi by hand which was also slow and crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KAddressBook (kaddressbook), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 0x7f60e8740eb5 in Kvantum::Style::advanceProgressbar
(this=0x5578fbe54850) at
/usr/src/debug/kvantum-1.0.0-1.1.x86_64/Kvantum/style/Kvantum.cpp:847
#7 0x7f6104afc4f3 in QtPrivate::QSlotObjectBase::call (a=0x7ffdcb4b6a90,
r=0x5578fbe54850, this=0x5578fbe5b5e0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8 doActivate (sender=0x5578fbe53890, signal_index=3,
argv=0x7ffdcb4b6a90) at kernel/qobject.cpp:3886
#9 0x7f6104af59bf in QMetaObject::activate (sender=,
m=m@entry=0x7f6104d9bc00 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdcb4b6a90)
at kernel/qobject.cpp:3946
#10 0x7f6104b003aa in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#11 0x7f6104af23bf in QObject::event (this=0x5578fbe53890,
e=0x7ffdcb4b6c10) at kernel/qobject.cpp:1336
#12 0x7f6105676a7f in QApplicationPrivate::notify_helper (this=, receiver=0x5578fbe53890, e=0x7ffdcb4b6c10) at
kernel/qapplication.cpp:3632
#13 0x7f6104ac5e2a in QCoreApplication::notifyInternal2
(receiver=0x5578fbe53890, event=0x7ffdcb4b6c10) at
kernel/qcoreapplication.cpp:1064
#14 0x7f6104b1c70b in QTimerInfoList::activateTimers (this=0x5578fbc11ab0)
at kernel/qtimerinfo_unix.cpp:643
#15 0x7f6104b1cfdc in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:183
#16 idleTimerSourceDispatch (source=source@entry=0x5578fbc15a70) at
kernel/qeventdispatcher_glib.cpp:230
#17 0x7f61026fed5f in g_main_dispatch (context=0x7f60f8005000) at
../glib/gmain.c:3381
#18 g_main_context_dispatch (context=0x7f60f8005000) at ../glib/gmain.c:4099
#19 0x7f61026ff0e8 in g_main_context_iterate
(context=context@entry=0x7f60f8005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#20 0x7f61026ff19f in g_main_context_iteration (context=0x7f60f8005000,
may_block=1) at ../glib/gmain.c:4240
#21 0x7f6104b1d364 in QEventDispatcherGlib::processEvents
(this=0x5578fbc11810, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7f6104ac482b in QEventLoop::exec (this=this@entry=0x7ffdcb4b6e50,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7f6104accb00 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7f6104f1625c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#25 0x7f61056769f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#26 0x5578fb3b7cbd in main (argc=, argv=) at
/usr/src/debug/kaddressbook-21.12.2-1.1.x86_64/src/main.cpp:90
[Inferior 1 (process 32390) detached]
Possible duplicates by query: bug 449872, bug 449741, bug 448140, bug 448106,
bug 447519.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 489554] New: Panel on external screen does not unfold so icons are not visible.
https://bugs.kde.org/show_bug.cgi?id=489554 Bug ID: 489554 Summary: Panel on external screen does not unfold so icons are not visible. Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jan.muss...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 171243 --> https://bugs.kde.org/attachment.cgi?id=171243&action=edit Panels on both screens are setup the same, sometimes the one on the left looks like is shown *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Sometimes when I boot into the OS I see that the panel is very short. Only the menu icon is visible, for the rest the panel is empty. STEPS TO REPRODUCE 1. Boot 2. See the result 3. OBSERVED RESULT A too short panel EXPECTED RESULT The panel as I have set it up. In the attachment you can see the panel as it should be (on the right) and how it is when it did not unfold. Right screen is the built-in screen of my laptop, the left screen is an external one, connected through HDMI. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Kinoite 40 (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486897] New: Not able to create shortcuts
https://bugs.kde.org/show_bug.cgi?id=486897 Bug ID: 486897 Summary: Not able to create shortcuts Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: jan.muss...@gmail.com CC: butir...@gmail.com, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 169387 --> https://bugs.kde.org/attachment.cgi?id=169387&action=edit Error message *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org I did, but this did not result in a working answer. If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. In system-settings select Keyboard - Shortcuts, button Add new and then select Command or Script 2. Select the item you want to have a shortcut made for 3. When clicking Add the input window disappears and on top of the window an error message in red appears: Error while communicating with the global shortcuts service OBSERVED RESULT No shortcut added EXPECTED RESULT Having a new shortcut SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.4 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This happened both in Fedora 40 KDE spin as well as in Fedora 40 Kinoite. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 433453] changing the identity updates the signature, but leaves the templates values unchanged
https://bugs.kde.org/show_bug.cgi?id=433453 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #3 from DeMus --- As Dmitri said on January 16, 2021: It is REALLY a very critical problem And it is still not solved. Using an HTML signature is not possible because fonts are changed automatically by the program. I am using KDE 5.27.9 on openSUSE Tumbleweed at the moment, but also on Fedora 38 I noticed the same issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472012] New: Brightness control does not work
https://bugs.kde.org/show_bug.cgi?id=472012 Bug ID: 472012 Summary: Brightness control does not work Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- SUMMARY *** I own a Lenovo Legion 5 Pro laptop with an AMD Ryzen 7 6800 CPU and an AMD Rembrandt [Radeon 680M] GPU, next to an Nvidia GA106M [GeForce RTX 3060 Mobile one. I use the AMD one. Controlling screen brightness does not work at all when using Wayland. In X11 I can use xrandr to set a value, but in Wayland this does not work: The function keys on the built-in keyboard don't work, hovering the mouse over the battery symbol and using the mouse-wheel doesn't work. I always have 100% brightness. I use the Fedora38 KDE spin. *** STEPS TO REPRODUCE 1. Using the keyboard function keys 2. Hovering the mouse over the battery symbol and using the mouse-wheel 3. OBSERVED RESULT Always 100% brightness EXPECTED RESULT Controllable brightness SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 38 KDE, kernel 6.3.11-200.fc38.x86_64 (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472012] Brightness control does not work
https://bugs.kde.org/show_bug.cgi?id=472012 DeMus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from DeMus --- Hi, this bug is not a KDE bug so it can be taken away from here. It turned out it is something in Fedora Linux. After installing a package called "light" I can set, increase and decrease the brightness of the monitor. Sorry for all the commotion. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463962] New: Kmail crashes when changes data for archiving
https://bugs.kde.org/show_bug.cgi?id=463962 Bug ID: 463962 Summary: Kmail crashes when changes data for archiving Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Application: akonadi_archivemail_agent (5.22.0 (22.12.0)) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.1.0-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: I noticed that my archive files are 3 days old while there should be a new set every day. I tried to edit the settings but since the email folders are greyed out I can't. I then edited the output folder on disk and created a new folder for the archives. That worked, but after a few seconds the system crashed. The crash can be reproduced every time. -- Backtrace: Application: akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::operator++ (this=0x61006a002f0065) at /usr/include/c++/12/bits/atomic_base.h:384 #5 QAtomicOps::ref (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:283 #6 QBasicAtomicInteger::ref (this=0x61006a002f0065) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:118 #7 QUrl::QUrl (this=this@entry=0x7ffc5706ca38, other=...) at io/qurl.cpp:1861 #8 0x562ed07ddc5d in ArchiveMailInfo::url (this=) at /usr/src/debug/kmail-22.12.0/agents/archivemailagent/archivemailinfo.cpp:185 #9 ArchiveMailInfo::dirArchive (this=0x562ed15b2510, dirExit=@0x7ffc5706caf7: true) at /usr/src/debug/kmail-22.12.0/agents/archivemailagent/archivemailinfo.cpp:57 #10 0x562ed07df6c8 in ArchiveMailInfo::listOfArchive (dirExist=@0x7ffc5706caf7: true, folderName=..., this=) at /usr/src/debug/kmail-22.12.0/agents/archivemailagent/archivemailinfo.cpp:87 #11 ArchiveMailManager::backupDone (this=0x562ed161a230, info=) at /usr/src/debug/kmail-22.12.0/agents/archivemailagent/archivemailmanager.cpp:103 #12 0x562ed07e0d7a in ArchiveJob::slotBackupDone (this=0x562ed1b28050, info=...) at /usr/src/debug/kmail-22.12.0/agents/archivemailagent/job/archivejob.cpp:112 #13 0x7f5e7e7132cd in QtPrivate::QSlotObjectBase::call (a=0x7ffc5706cd00, r=0x562ed1b28050, this=0x562ed15b2430) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x562ed1b5e920, signal_index=3, argv=0x7ffc5706cd00) at kernel/qobject.cpp:3919 #15 0x7f5e7e70c74f in QMetaObject::activate (sender=, m=m@entry=0x7f5e7f810ae0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc5706cd00) at kernel/qobject.cpp:3979 #16 0x7f5e7f707022 in MailCommon::BackupJob::backupDone (this=, _t1=...) at /usr/src/debug/mailcommon-22.12.0/build/src/KF5MailCommon_autogen/AYU7XCIYTN/moc_backupjob.cpp:143 #17 0x7f5e7f771a4b in MailCommon::BackupJob::finish (this=0x562ed1b5e920) at /usr/src/debug/mailcommon-22.12.0/src/job/backupjob.cpp:202 #18 0x7f5e7e707c40 in QObject::event (this=0x562ed1b5e920, e=0x7f5e38062200) at kernel/qobject.cpp:1347 #19 0x7f5e7eba53fe in QApplicationPrivate::notify_helper (this=, receiver=0x562ed1b5e920, e=0x7f5e38062200) at kernel/qapplication.cpp:3637 #20 0x7f5e7e6dc128 in QCoreApplication::notifyInternal2 (receiver=0x562ed1b5e920, event=0x7f5e38062200) at kernel/qcoreapplication.cpp:1064 #21 0x7f5e7e6df0c1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x562ed14e97d0) at kernel/qcoreapplication.cpp:1821 #22 0x7f5e7e734353 in postEventSourceDispatch (s=0x562ed15c3590) at kernel/qeventdispatcher_glib.cpp:277 #23 0x7f5e7b869a90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f5e7b869e48 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7f5e7b869edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f5e7e733b56 in QEventDispatcherGlib::processEvents (this=0x562ed15d4c10, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7f5e7e6dab9b in QEventLoop::exec (this=this@entry=0x7ffc5706d1a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #28 0x7f5e7e6e2d06 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #29 0x562ed07dba39 in Akonadi::AgentBase::init (argv=, argc=) at /usr/include/KF5/AkonadiAgentBase/akonadi/agentbase.h:469 #30 main (argc=, argv=) at /usr/src/debug/kmail-22.12.0/agents/archivemailagent/archivemailagent.cpp:141 [Inferior 1 (process 2055) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400106] New: Auto-hide dock pops up when active window on screen is not maximized
https://bugs.kde.org/show_bug.cgi?id=400106 Bug ID: 400106 Summary: Auto-hide dock pops up when active window on screen is not maximized Product: latte-dock Version: 0.8.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 115803 --> https://bugs.kde.org/attachment.cgi?id=115803&action=edit Dock pops up when changing active/inactive window SUMMARY When a small sized window is the active window on screen the dock pops up and only hides again when that smaller window is not active anymore. It also does that when I restore the size of a maximized window to its previous (smaller) size. STEPS TO REPRODUCE 1. Open a window maximized, docks hides after the set time 2. Restore size of window to previous size, dock pops up 3. Maximize window again, docks hides. See attached video, sorry for bad quality. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (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.
[kmix] [Bug 408183] New: Audio feedback when volume changes
https://bugs.kde.org/show_bug.cgi?id=408183 Bug ID: 408183 Summary: Audio feedback when volume changes Product: kmix Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KMix Panel Docking Assignee: es...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 120479 --> https://bugs.kde.org/attachment.cgi?id=120479&action=edit Audio volume settings window SUMMARY When I right-click the loudspeaker icon in the panel and choose Configure audio volume, I can choose to have or not to have audio feedback when the volume changes. The text next to the item says however: Provide visual feedback. STEPS TO REPRODUCE 1. See above 2. See attachment Audio volume settings volume picture 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux KDE edition (available in About System) KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 408183] Audio feedback when volume changes
https://bugs.kde.org/show_bug.cgi?id=408183 DeMus changed: What|Removed |Added Component|KMix Panel Docking |Visual: Layout and GUI Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409544] New: Width of Places Panel is not remembered
https://bugs.kde.org/show_bug.cgi?id=409544 Bug ID: 409544 Summary: Width of Places Panel is not remembered Product: dolphin Version: 19.04.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 121348 --> https://bugs.kde.org/attachment.cgi?id=121348&action=edit Picture 1 with the way I set the width of the panel SUMMARY STEPS TO REPRODUCE 1. Open Dolphin 2. 3. OBSERVED RESULT Width of places panel is smaller than when I closed the program. Names of directories are only shown half. EXPECTED RESULT Same width as when closing the program. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux, Dolphin 19.04.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Picture 1 shows the way I set it in Dolphin, by dragging the line between the places panel and the main window. Picture 2 is how it appears when I re-open Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409544] Width of Places Panel is not remembered
https://bugs.kde.org/show_bug.cgi?id=409544 --- Comment #1 from DeMus --- Created attachment 121349 --> https://bugs.kde.org/attachment.cgi?id=121349&action=edit Picture 2 is how it appears when I re-open Dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409544] Width of Places Panel is not remembered
https://bugs.kde.org/show_bug.cgi?id=409544 --- Comment #2 from DeMus --- SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux, Dolphin 19.04.2 (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version:5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413772] New: KDE Settings crashes when program is stopped after making a change in one of the settings
https://bugs.kde.org/show_bug.cgi?id=413772 Bug ID: 413772 Summary: KDE Settings crashes when program is stopped after making a change in one of the settings Product: systemsettings Version: 5.17.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had changed something in the Display and Monitor module. When I closed the program I got the message it crashed and I could file a bugreport. This does also happens with changes in others modules. I did not notice it when I did not make a change. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f09995800 (LWP 2579))] Thread 7 (Thread 0x7f1ee2fe6700 (LWP 2895)): #0 0x7f1f0dc71bdf in poll () from /lib64/libc.so.6 #1 0x7f1f0a412a5e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f0a413993 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1ee816c606 in ?? () from /usr/lib64/libgio-2.0.so.0 #4 0x7f1f0a3efc4d in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f0ad31f2a in start_thread () from /lib64/libpthread.so.0 #6 0x7f1f0dc7c4af in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f1ee1fa5700 (LWP 2894)): #0 0x7f1f0dc6d60c in read () from /lib64/libc.so.6 #1 0x7f1f0a3c470f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f0a41136e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1f0a412a02 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1f0a412b2f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f0a412b81 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f1f0a3efc4d in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7f1f0ad31f2a in start_thread () from /lib64/libpthread.so.0 #8 0x7f1f0dc7c4af in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1eea170700 (LWP 2648)): #0 0x7f1f0dc6d60c in read () from /lib64/libc.so.6 #1 0x7f1f0a3c470f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f0a41136e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1f0a412a02 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1f0a412b2f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f0c5be99b in QEventDispatcherGlib::processEvents (this=0x7f1ee4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f1f0c5670db in QEventLoop::exec (this=this@entry=0x7f1eea16fd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f1f0c39f021 in QThread::exec (this=this@entry=0x56145041ef90) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f1f0b8893f5 in QQmlThreadPrivate::run (this=0x56145041ef90) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:152 #9 0x7f1f0c3a01a2 in QThreadPrivate::start (arg=0x56145041ef90) at thread/qthread_unix.cpp:360 #10 0x7f1f0ad31f2a in start_thread () from /lib64/libpthread.so.0 #11 0x7f1f0dc7c4af in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f1eff39a700 (LWP 2584)): #0 0x7f1f0ad386a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1eff85ef3b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f1eff85ee37 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f1f0ad31f2a in start_thread () from /lib64/libpthread.so.0 #4 0x7f1f0dc7c4af in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1f06333700 (LWP 2582)): #0 0x7f1f0dc6d60c in read () from /lib64/libc.so.6 #1 0x7f1f0a3c470f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f0a41136e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1f0a412a02 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1f0a412b2f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f0c5be99b in QEventDispatcherGlib::processEvents (this=0x7f1ef8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f1f0c5670db in QEventLoop::exec (this=this@entry=0x7f1f06332d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f1f0c39f021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f1f0b4c84f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f1f0c3a01a2 in QThrea
[dolphin] [Bug 409544] Width of Places Panel is not remembered
https://bugs.kde.org/show_bug.cgi?id=409544 --- Comment #3 from DeMus --- Please discard this "bug" since it is not a bug. It was my own stupidity which caused the events I saw. Things are well now. Cause: I switched back from a beta version of Manjaro to the normal version while keeping the hidden config folders and files in my home folder. Somehow the normal version doesn't play well with files from the beta version. Apologies for filing this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 415196] New: Size, location and duration of the volume change applet
https://bugs.kde.org/show_bug.cgi?id=415196 Bug ID: 415196 Summary: Size, location and duration of the volume change applet Product: plasma-pa Version: 5.17.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: jan.muss...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Changing the volume shows an applet in the middle of the screen which stays there for 1800 msec. The size of the icon is huge, the duration is too long and the location is wrong. Well, according to me. I know how to change it but with the next update the files I have changed are overwritten: /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/osd/Osd.qml and OsdItem.qml. Please put these settings somewhere in the /home/user/.config directory structure so they are not overwritten by a backup. Why isn't this a user setting? STEPS TO REPRODUCE 1. Change volume 2. 3. OBSERVED RESULT Huge applet which stays visible too long in the center of the screen EXPECTED RESULT A nice small applet somewhere in the corner which stays there as long as I want it visible, with a size that I like. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.27.4 (available in About System) KDE Plasma Version: 5.17.4 (and older) KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395750] New: No password asked when installing programs
https://bugs.kde.org/show_bug.cgi?id=395750 Bug ID: 395750 Summary: No password asked when installing programs Product: Discover Version: 5.13.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- When I install a program using Discover, I am never asked for a password. When I uninstall a program I am asked for a password. Apparently uninstalling from hard disk is more dangerous than installing from the net. The general idea about Linux and safety is that writing to system disk can only be done when the correct password is given. Now I can do without. Please say this is a bug and not a feature because that would undermine everything safety related. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 390963] New: Balance the scale
https://bugs.kde.org/show_bug.cgi?id=390963 Bug ID: 390963 Summary: Balance the scale Product: gcompris Version: 0.80 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: jan.muss...@gmail.com Target Milestone: --- In Gcompris' game Balance the scale the help text says: To balance the scales, move the weights on the left or right side. First of all weights can't be placed on the right side, the program refuses that, secondly move weights on a side should be: move weights to the left side. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390733] KMail cannot send mails using gmail smtp
https://bugs.kde.org/show_bug.cgi?id=390733 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #3 from DeMus --- Same here. I have 1 POP and 1 IMAP account in KMail but sending from both accounts is not possible. Mail just stays in the outbox folder. I also setup the 2-step verification (at the moment just for the IMAP account) but doesn't make a difference. I was hoping through more security it would work, but no. I can not send mails at all now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390733] KMail cannot send mails using gmail smtp
https://bugs.kde.org/show_bug.cgi?id=390733 --- Comment #4 from DeMus --- (In reply to DeMus from comment #3) > Same here. I have 1 POP and 1 IMAP account in KMail but sending from both > accounts is not possible. Mail just stays in the outbox folder. > I also setup the 2-step verification (at the moment just for the IMAP > account) but doesn't make a difference. I was hoping through more security > it would work, but no. I can not send mails at all now. Forgot to mention: I'm using Manjaro Linux 17.1.6 Hakoila - Testing, with Plasmashell 5.12.2, Kontact 5.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390733] KMail cannot send mails using gmail smtp
https://bugs.kde.org/show_bug.cgi?id=390733 --- Comment #5 from DeMus --- The problems with KMail not being able to send mails using a Gmail account are as old as January 2007. I found message on the Kubuntu forum from that date. This means for 11 years already people around the world are having these problems. Why other e-mail clients can do this and KMail can not? Did the KDE developers working on KMail (Kontact) ever discussed the matter with Google to come to a solution? If not, why not and isn't it time to do so? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390733] KMail cannot send mails using gmail smtp
https://bugs.kde.org/show_bug.cgi?id=390733 --- Comment #6 from DeMus --- Message I get is: E-Mail Sending Failed Failed to transport message. Connection timed out Failed to store result in item. Item query returned empty result set Is there a way to setup a time-out somewhere? Google says: Server timeouts Greater than 1 minute (5 is recommended) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 391372] New: Articles columns are not remembered
https://bugs.kde.org/show_bug.cgi?id=391372 Bug ID: 391372 Summary: Articles columns are not remembered Product: akregator Version: 5.7.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 70 --> https://bugs.kde.org/attachment.cgi?id=70&action=edit Screenshot of initial column widths at start of the program After a (re)start of Kontact, in Akregator the widths of the columns in the article list field are not remembered. Especially the Title column is very small and needs to be expanded manually after every start. Feed, Author and Date columns are not perfect after a new start, but normally text is readable. I widen the Title column so the right side of the date column is against the right side of the window. That's how I leave the program. I use Kontact 5.7.2, KDE Frameworks 5.43, Qt 5.10.1 (built against 5.10.0), xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 391372] Articles columns are not remembered
https://bugs.kde.org/show_bug.cgi?id=391372 --- Comment #1 from DeMus --- There is more wrong with the article list window. I see a horizontal line underneath indicating the part of the total window I see at the moment. When I try to reduce the width of the most right column, Date, this line does not change length. Also when dragging the right side of the Date column to the left doesn't really work, the selection escapes from the cursor and jumps back to the original spot making it impossible to reduce the width. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391686] New: Discover allows to install programs without a password
https://bugs.kde.org/show_bug.cgi?id=391686 Bug ID: 391686 Summary: Discover allows to install programs without a password Product: Discover Version: 5.12.3 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- I just booted my computer and started Discover to install a package. Installing the package was done without asking me for my password. When I uninstalled the same package I was asked for a password. Is this by design or is it really a bug? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391701] New: Searching for a program needs the whole package name
https://bugs.kde.org/show_bug.cgi?id=391701 Bug ID: 391701 Summary: Searching for a program needs the whole package name Product: Discover Version: 5.12.3 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- I was looking for Wayland in Discover but got no answer. Even Plasma-Wayland gave nothing. Only Plasma-Wayland-session showed what I was looking for. It would be nice if the search became more intelligent and as a result shows everything matching the search item, so it would be more like a filter than a search. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #200 from DeMus --- I can confirm this bug with both an IMAP and a POP account. Mails are sometimes (not always, filters don't always work well) transferred from the inbox to the correct folder and a little bit later the mails are also back in the inbox. This can go on forever. When I delete them from the inbox it is over and they don't appear anymore. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393426] New: When starting Kontact, Kmail does not start
https://bugs.kde.org/show_bug.cgi?id=393426 Bug ID: 393426 Summary: When starting Kontact, Kmail does not start Product: kmail2 Version: 5.8.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 112191 --> https://bugs.kde.org/attachment.cgi?id=112191&action=edit Error message When I started Kontact I received a message saying can't load part for Mail. The error message is shown in the attachment. I looked and saw that the "missing" file kmail.so is present. Kontact version 18.04.0 Manjaro unstable, using 4.15.18 kernel Qt 5.10.1, Frameworks 5.45.0, Plasma 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393426] When starting Kontact, Kmail does not start
https://bugs.kde.org/show_bug.cgi?id=393426 --- Comment #1 from DeMus --- Some more info from starting kontact in a terminal: kontact [0423/214050.923414:WARNING:stack_trace_posix.cc(648)] Failed to open file: /tmp/.gl3nttJm (deleted) Error: No such file or directory [0423/214050.923546:WARNING:stack_trace_posix.cc(648)] Failed to open file: /home/jan/#1048881 (deleted) Error: No such file or directory org.kde.pim.kontactinterface: "Cannot load library /usr/lib/qt/plugins/kmailpart.so: (/usr/lib/libKF5MailCommon.so.5: undefined symbol: _ZNK7Akonadi21EntityOrderProxyModel16parentCollectionERK11QModelIndex)" Error loading text-to-speech plug-in "speechd" "https://manjaro.org/feed/"; "https://dot.kde.org/rss.xml"; "https://www.linux.com/feeds/rss"; "https://planetkde.org/rss20.xml"; "https://store.kde.org/content.rdf"; Received signal 11 SEGV_MAPERR #0 0x7f4693998e76 #1 0x7f469261688c #2 0x7f46939991ec #3 0x7f46a23148e0 r8: 558eab0e61c0 r9: 002f r10: 558eaa97a010 r11: r12: 7ffea26a9df8 r13: 558eaa9fa2e0 r14: 7f4631bb5538 r15: di: 0001 si: 7ffea26a9df8 bp: 0001 bx: 7f4631bb5510 dx: 558eaa9fa2e0 ax: cx: 558eaa9fa2e0 sp: 7ffea26a8de8 ip: efl: 00010206 cgf: 002b0033 erf: 0014 trp: 000e msk: cr2: [end of stack trace] Calling _exit(1). Core file will not be generated. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393426] When starting Kontact, Kmail does not start
https://bugs.kde.org/show_bug.cgi?id=393426 --- Comment #2 from DeMus --- I have found the error. With the update to 18.04 Akonadi was not updated by the system. I just did that manually and now it works again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393426] When starting Kontact, Kmail does not start
https://bugs.kde.org/show_bug.cgi?id=393426 DeMus changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 393574] New: Spectacle misses the Exit-button
https://bugs.kde.org/show_bug.cgi?id=393574 Bug ID: 393574 Summary: Spectacle misses the Exit-button Product: Spectacle Version: 18.04.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: jan.muss...@gmail.com Target Milestone: --- Spectacle used to have an exit button called Save & Exit. Now it is only Save or Save-as. Please Please Please restore the Exit function. This was the only one I use after creating a screenshot: save it and exit the program in one go. Why was it deleted anyway? Sorry, but this is a bad choice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget with QSG_RENDER_LOOP=basic
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #102 from DeMus --- KDE 5.12.4, Frameworks 5.45.0, Qt 5.10.1. When using the slide-show memory is filling up pretty fast. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393714] New: No sound when playing youtube movies
https://bugs.kde.org/show_bug.cgi?id=393714 Bug ID: 393714 Summary: No sound when playing youtube movies Product: Falkon Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: jan.muss...@gmail.com Target Milestone: --- When I watch a Youtube movie (and possibly on other sites as well) I get no sound. Do I copy the URL from that webpage into Chromium I do have sound. And yes, the volume slider at the bottom of the movie frame is set at maximum. I use: Application version 3.0.0 QtWebEngine version 5.10.1 Plasma 5.12.4 Framework 5.45.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 393715] New: Spectacle misses save & exit button
https://bugs.kde.org/show_bug.cgi?id=393715 Bug ID: 393715 Summary: Spectacle misses save & exit button Product: Spectacle Version: 18.04.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: jan.muss...@gmail.com Target Milestone: --- Spectacle used to have a Save & Exit button. Now it's just Save (or Save as). I always used the Save & Exit button, it's the one key I actually used making working with Spectacle very fast and conveniant. Now I have to click Save and then the cross in the upper right corner to exit the program. Plasma 5.12.4 Frameworks 5.45 Qt 5.10.1 Version 18.0.4 On: https://www.kde.org/applications/graphics/spectacle/ I read about the save&exit button. Will it be re-instated? Please do. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 352776] Labels of file items wrap over themselves in file dialog widget (open/save)
https://bugs.kde.org/show_bug.cgi?id=352776 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #5 from DeMus --- Using Manjaro Linux KDE 17.1.0 Hakoila with Plasma 5.11.5, Frameworks 5.41.0 and Qt 5.10.0. I can confirm the fact that Kdialog is not always showing filenames complete. It looks like columns don't have the correct width and text is cut-off. When making the window larger it normally gets better, but not always. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 383807] Doubled mail after filtering
https://bugs.kde.org/show_bug.cgi?id=383807 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #3 from DeMus --- I also have the same problem: moved mails sometimes appear 2-3 times in the destination folder and still a copy remains in the inbox. Other times mails are not moved at all, at least not automatically. Doing so by hand moves them to the correct folder. I use: Kontact 5.7.3 KDE Frameworks 5.44.0 Qt 5.10.1 (built against 5.10.1) The xcb windowing system on Manjaro Linux 17.1.6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 392599] New: Media Frame widget and wallpaper slideshow have memory leak
https://bugs.kde.org/show_bug.cgi?id=392599 Bug ID: 392599 Summary: Media Frame widget and wallpaper slideshow have memory leak Product: frameworks-kconfigwidgets Version: 5.44.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Both the Wallpaper slideshow and the Media Frame widget have memory leaks. Because my wife's computer crashed a lot lately I looked into CPU temperature and RAM usage. Well, temp was okay but memory was filling up till at the end the system crashed. The widget has a default refresh time of 6.8 seconds and in that rhythm I saw a memory increase. I now deleted the frame from the desktop and memory usage stays normal now. KDE Plasma 5.12.3 KDE Frameworks 5.44.0 Qt version 5.10.1 Kernel 5.15.14-1-Manjaro -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 390268] New: Spoken text does not match the shown pictures
https://bugs.kde.org/show_bug.cgi?id=390268 Bug ID: 390268 Summary: Spoken text does not match the shown pictures Product: gcompris Version: 0.80 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: jan.muss...@gmail.com Target Milestone: --- I'm working on the Dutch translation for the program and therefore installed it to see where the texts are used for. In the Match the Colors sections you can mix colors by moving sliders on tubes of paint, so I'm told. I don't see sliders, I only see a plus and minus button to increase or decrease the amount of paint used. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 390910] New: In the maze game the arrow keys don't function
https://bugs.kde.org/show_bug.cgi?id=390910 Bug ID: 390910 Summary: In the maze game the arrow keys don't function Product: gcompris Version: 0.80 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: jan.muss...@gmail.com Target Milestone: --- In Gcompris 0.81-1, in the game Maze the instructions say: Use the arrows on your keyboard to find your way out. The keys do absolutely nothing. What moves Tux is clicking the left-mouse-key in the direction he needs to go, one step further than where he is. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 390912] New: In "Melody" I hear no tones
https://bugs.kde.org/show_bug.cgi?id=390912 Bug ID: 390912 Summary: In "Melody" I hear no tones Product: gcompris Version: 0.80 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: jan.muss...@gmail.com Target Milestone: --- The sound of the xylophone can not be heard. The voice with directions is fine. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 390915] New: Gcompris 0.81-1 Subtraction and addition and subtraction memory games
https://bugs.kde.org/show_bug.cgi?id=390915 Bug ID: 390915 Summary: Gcompris 0.81-1 Subtraction and addition and subtraction memory games Product: gcompris Version: 0.80 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 110905 --> https://bugs.kde.org/attachment.cgi?id=110905&action=edit Help texts in the wrong game In the addition and subtraction memory game the text below the title in the help says: Turn the cards over to find 2 numbers which subtract the same In the subtraction memory game the help text says: Turn the cards over to find two numbers which add or subtract the same. It seems to me those two texts are placed in the wrong game, they have to be interchanged. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389497] New: Systemsettings crash when using global shortcuts after web shortcuts
https://bugs.kde.org/show_bug.cgi?id=389497 Bug ID: 389497 Summary: Systemsettings crash when using global shortcuts after web shortcuts Product: systemsettings Version: 5.11.5 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: jan.muss...@gmail.com Target Milestone: --- In systemsettings when using the shortcuts section, clicking on global shortcuts after having clicked web shortcuts, the program crashes each time. This was reported on the Manjaro forum: https://forum.manjaro.org/t/kde-systemsettings5-crash-method-with-web-shortcut/39123 by Volcrote and after doing the same here it also crashes. Manjaro 17.1.2, KDE 5.11.5, QT 5.10.0, Framework 5.42.0, kernel 4.14.15 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378897] missing cursor in timeline
https://bugs.kde.org/show_bug.cgi?id=378897 --- Comment #6 from DeMus --- As an answer to comment 4 I can say it is happening with multiple versions of 16.x and 17.x It's not just one version. Older versions don't seem to have this but suddenly this bug was introduced and never left. I now have 17.11.70.r9142, still there. It makes the program unusable, there is no way to edit a movie. I use it on Manjaro Linux 17.06 with KDE desktop. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'
https://bugs.kde.org/show_bug.cgi?id=379820 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #1 from DeMus --- Same thing as what pmarget...@gmail.com writes happens to me in my Manjaro 17.01 KDE. Only when the sort key is set to "name" things are okay, if not file and folder names are chopped after second character. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'
https://bugs.kde.org/show_bug.cgi?id=379820 --- Comment #2 from DeMus --- P.s. KDE Plasma 5.9.5 KDE Frameworks 5.33.0 Qt version 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 394821] New: KDE config files are found all around the place
https://bugs.kde.org/show_bug.cgi?id=394821 Bug ID: 394821 Summary: KDE config files are found all around the place Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- KDE is known to have a 1001 settings which can be changed to suit the users wishes. This can take a long time. When you re-install a distro, or perhaps jump to another, you've got to do it all again. I have a few questions about this: 1) Is it possible (sure it is) to place each and every KDE config file (for each and every program and part of Plasma, etc) in one directory, now they are everywhere. Making a backup would be so much easier to do. 2) Can you create a backup program to backup the settings, just as you did in Kontact where it is now very easy to create a backup of all your mail from within the program, instead of trying to find all the akonadi files which are scattered around. Kudos for that. For a modern DE, and I considder KDE to be THE DE this is almost mandatory to have. So if somebody can have a look at this, I and I'm sure many with me, will be very happy Setting up a new installation will then be peanuts compared to what it is now. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #32 from DeMus --- Qt5.11, Plasma 5.12.5, Frameworks 5.46.0, Kontact 5.8.1 Outgoing mails are sent back from draft to the local folders Outbox and stay there, after some time I receive a notification there is a time-out. Tried downgrading, doesn't work, tried exchange SSl to TSL, didn't work. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen
https://bugs.kde.org/show_bug.cgi?id=382264 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #13 from DeMus --- Okay, so now there is a text file which should cure things. That is wonderful, but what to do with it? Where do I place it, how do I name it, should I run it once, every time I boot, will it be read by the system. How does this work? Sorry, but not every Linux user is an expert in these things. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen
https://bugs.kde.org/show_bug.cgi?id=382264 --- Comment #15 from DeMus --- Created attachment 114869 --> https://bugs.kde.org/attachment.cgi?id=114869&action=edit Latte dock with poorly visible icons -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen
https://bugs.kde.org/show_bug.cgi?id=382264 --- Comment #16 from DeMus --- I use Latte-dock on KDE 5.13.5. Some of the used icons are poorly visible on a dark background, they are volume, network and media-player. As icon theme I use Breeze. When I asked about it on the KDE forum I was pointed to this bug-report and so here I am. Latte is using a transparant background to still see the wallpaper on my desktop. When I open Latte on a light background, for example in Dolphin, the icons are visible. I added a picture called Latte.png to show what I mean. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398447] New: Some icons are badly visible on a dark background
https://bugs.kde.org/show_bug.cgi?id=398447 Bug ID: 398447 Summary: Some icons are badly visible on a dark background Product: latte-dock Version: 0.8.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 114870 --> https://bugs.kde.org/attachment.cgi?id=114870&action=edit Poorly visible icons in Latte dock Hi, I use some icons on my dock which are hardly visible when the background is dark. The dock's background is completely transparent, cause that's what I want. Most of the icons are visible very well, but they are in full color. The one I speak about now are black, like the volume icon, the multi-media and network ones. On the KDE bugreport (https://bugs.kde.org/show_bug.cgi?id=382264) there is a solution for poorly visible icons on the log-out screen. Can this solution be implemented in Latte as well? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398610] New: Mouse settings have lost lot of settings
https://bugs.kde.org/show_bug.cgi?id=398610 Bug ID: 398610 Summary: Mouse settings have lost lot of settings Product: systemsettings Version: 5.13.1 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: jan.muss...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- Since sometime now, the mouse-settings have been reduced to almost nothing. Where in previous versions you could adjust the mouse the way you wanted, you can adjust nothing now anymore. This results in unexpected and unwanted behavior. Example: scrolling in Dolphin with mouse-wheel. Where I could set to scroll 1 or 2 lines per notch of the wheel, I can adjust nothing now. Moving the mouse-wheel one notch now results in a totally new screen contents since the content of the window is scrolled way too much. Please bring back the old settings and let KDE be KDE, where everything is adjustable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] New: Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 Bug ID: 394962 Summary: Wallpaper slideshow fills memory Product: plasmashell Version: 5.12.5 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: jan.muss...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 113017 --> https://bugs.kde.org/attachment.cgi?id=113017&action=edit Desktop with Conky and Kinfo-screen Hi, Just tried the slidewhow again, now with KDE Plasma 5.12.5, Frameworks 5.46 and Qt5.11. Eventhough, as was said, the memoryleak would have been taken care off, I'm sorry to say but it's still there. When my laptop starts it consumes around 800MB of memory. With a slideshow changing time of 5 sec. it was not long when I had used 2GB already. No other programs started, except which was running all the time: Conky to show me the increase in memory. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #2 from DeMus --- Created attachment 113027 --> https://bugs.kde.org/attachment.cgi?id=113027&action=edit System monitor I added a screenshot of the Kinfo center in my first post, you can see it there. What does this mean: If you still have an issue I want to see a trace in massif. I add another screenshot, now from system-monitor, on which you can see that the blue memory line is not changing much anymore (I have 4GB) but the red Swap line is constantly getting higher. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 394821] KDE config files are found all around the place
https://bugs.kde.org/show_bug.cgi?id=394821 --- Comment #4 from DeMus --- As I see it, and I am only a computer user no somebody who can dive deep into things, placing all files belonging to KDE app in 1 folder would make backing them up very easy: all you need to do is copy that 1 folder and you are sure you have everything. Doesn't have to be so complicated. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 394980] New: Cursor is placed in a field so you can type something, but the field is not active, needs mouse-click
https://bugs.kde.org/show_bug.cgi?id=394980 Bug ID: 394980 Summary: Cursor is placed in a field so you can type something, but the field is not active, needs mouse-click Product: Falkon Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: jan.muss...@gmail.com Target Milestone: --- When I, for example, open the gmail page I get a google window inwhich I can type my username. Although the curor is blinking in that field, it does not accept what I type on my keayboard. I need to left-click the field first, then I can start typing my username. This does not only happen with the gmail page, it happens in every page where text can be entered in a field. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 --- Comment #4 from DeMus --- 1) I installed valgrind and massif-visualizer 2) I then typed both commands in a terminal 3) Changed wallpaper to slideshow, refresh time 1 sec to speed things up 4) In the Conky on my screen I see NO increase in memory use 5) With ctrl-C I stopped the valgrind command 6) I then typed plasmashell to get my desktop, slideshow is still active 7) NO memory inscrease 8) Stopped the plasmashell command 9) Rebooted 10) Memory is filling rapidly, slideshow is still active, refreshtime is 1 sec. Found the massive fie, attach it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 --- Comment #5 from DeMus --- Created attachment 113028 --> https://bugs.kde.org/attachment.cgi?id=113028&action=edit Massif file Massif file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 --- Comment #6 from DeMus --- Created attachment 113031 --> https://bugs.kde.org/attachment.cgi?id=113031&action=edit 2nd test with valgrind --tool=massif plasmashell I've done the test again, now a bit longer but when plasmashell is started from a terminal, with or without valgrind, there is no memory increase at all. When I reboot and plasmashell is started the normal way, memory fills up. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393358] Web Extensions support
https://bugs.kde.org/show_bug.cgi?id=393358 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #2 from DeMus --- I also miss some extensions which make browsing so much more fun. So, if it's possible, please ad the possibility to add them. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 394980] Cursor is placed in a field so you can type something, but the field is not active, needs mouse-click
https://bugs.kde.org/show_bug.cgi?id=394980 --- Comment #1 from DeMus --- Another thing I experience is when I open a new page and I want to scroll through it using the cursor keys (up/down) it doesn't work straight away. I need to left-click the page first. I use that a lot since the mouse-wheel makes quite some noise. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 395143] New: Open files in Dolphin does not start corresponding program
https://bugs.kde.org/show_bug.cgi?id=395143 Bug ID: 395143 Summary: Open files in Dolphin does not start corresponding program Product: frameworks-kinit Version: 5.46.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: jan.muss...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- When I click, for example, an rc file, normally Kate would open. I now see an error: KDEInit could not launch '/usr/bin/kate' Other file types (jpg, png, pdf, mp4) don't show the error but nothing happens, no program is started. Starting the matching programs from the KDE menu works. KDE Plasma: 5.12.5 Frameworks: 5.46.0 Qt version: 5.11.0 Kernel: 4.17.0-2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364053] Dolphin is very slow when listing NFS folders
https://bugs.kde.org/show_bug.cgi?id=364053 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #6 from DeMus --- I use Dolphin 18.04-2 on KDE Plasma 5.12.5, Frameworks 5.46.0 and Qt 5.11.0 and I see a slow Dolphin not only on nfs shares but also in local directories. It happens when I: use additional information ==> size (to show the size of files and amount of items in a folder) and Preview, to see pictures instead of icons. When I deselect Preview the Size info is instantaneous. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364053] Dolphin is very slow when listing NFS folders
https://bugs.kde.org/show_bug.cgi?id=364053 --- Comment #7 from DeMus --- See my previous post; I have now downgraded Dolphin in a few steps until 16.12-2 and the situation is exactly the same, so I wonder if it is caused by Dolphin. Using the older versions never showed a problem and now there is a problem with them. I guess it's caused by something else. Additional folder info (size) using Preview view mode is shown very slow (2-3 seconds per folder) No previews of pictures, text files, etc. Also not in the F11 preview panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 --- Comment #7 from DeMus --- Created attachment 113160 --> https://bugs.kde.org/attachment.cgi?id=113160&action=edit Start of 5 minute test with interval of 5 sec. I did a 5 minute test with the slideshow active. In the two pictures you can see the memory use at the bottom left of the pictures. As you can see the second one is almost double ofthe first one. Nothing was done with the machine, no programs were started or whatever, I just sat in front of the screen for 5 minutes watching the memory use go up with every change of the pictures. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 --- Comment #8 from DeMus --- Created attachment 113161 --> https://bugs.kde.org/attachment.cgi?id=113161&action=edit End of 5 minutes test This is the 2nd picture, taken 5 minutes after the first one. I also show Kinfocenter to show I do use Qt5.11 Memory use is almost double of that in the first picture. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394962] Wallpaper slideshow fills memory
https://bugs.kde.org/show_bug.cgi?id=394962 --- Comment #9 from DeMus --- I did a complete re-install of the OS and now the error with the wallpaper slideshow is gone. No idea what is different now. This bug can be closed now. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395530] New: Discover installs packages without asking for password
https://bugs.kde.org/show_bug.cgi?id=395530 Bug ID: 395530 Summary: Discover installs packages without asking for password Product: Discover Version: 5.13.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Just used Discover to install a package and as soon as I click the install button, next to the name of the package, the installation starts already. I was not asked for a password. I then uninstalled the same package and now I was asked for a password. I closed Discover, started it again and did the same things again, and again I could install without giving my password. Plasma 5.13, Qt 5.11, Frameworks 5.47, Discover 5.13 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 395143] Open files in Dolphin does not start corresponding program
https://bugs.kde.org/show_bug.cgi?id=395143 --- Comment #2 from DeMus --- Yes, even after many reboots. When I start Dolphin with dbus-launch Dolphin it is okay. When things are wrong I also don't see previews from files and folders, plus the additional file and folder info "Size" appears very slow. When I open a directory with several directories inside, the number of items in those directories appear about 1 per 3 seconds, one folder at the time. With dbus-launch dolphin it is almost instant. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395623] New: Mouse settings are minimized
https://bugs.kde.org/show_bug.cgi?id=395623 Bug ID: 395623 Summary: Mouse settings are minimized Product: systemsettings Version: 5.13.1 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: jan.muss...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- Since 5.13 mouse settings have been minimized. It is, for example, no longer possible to set the amount of lines the contents of a window scrolls with one mouse-wheel notch. It is by default set to 3 which is way too many. In Dolphin, in icon vuew, the complete contents of a directory is scrolled of screen by one simple notch. Unworkable. Please restore the old settings. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379351] i cannot make a showslide clip and i cannot render a clip with jpg images
https://bugs.kde.org/show_bug.cgi?id=379351 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #6 from DeMus --- Also see https://bugs.kde.org/show_bug.cgi?id=376464 which tells about the same bug. It's not only Windows, it is also the linux version. I don't know when it started, which Kdenlive version, but suddenly it didn't work anymore. I now have a huge project which I can't finish becuase of it. Converting all images from jpg to png is possible but a lot of extra work. Is it possible somebody takes a look at this? Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366798] Timeline cursor and all timeline features not working but clip monitor still functional
https://bugs.kde.org/show_bug.cgi?id=366798 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #9 from DeMus --- HI, I'm using 16.12.3, Framework 5.32.0 and I am seeing the same things as others see: time cursor does not move, not by means of mouse-wheel, not by means of arrow keys. I can reset it by deleting the kdenliverc file in my home folder but then I loose all my settings and have to set them up again. I saw here that the error existed in 16.08 already, shame it didn't get fixed in the mean time. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378897] missing cursor in timeline
https://bugs.kde.org/show_bug.cgi?id=378897 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #3 from DeMus --- Created attachment 107377 --> https://bugs.kde.org/attachment.cgi?id=107377&action=edit Start of timeline in Kdenlive I clicked the cursor on the timeline and between 10 and 20 seconds you see this small grey line, but below it is no cursor. In the preview screen the time does also not change to the point in time where I clicked. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376464] JPG clip rendered as white screen although preview works
https://bugs.kde.org/show_bug.cgi?id=376464 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #9 from DeMus --- I use 17.11.70 on Linux Manjaro and in my case both the preview as the rendered movie is white. I also use jpg pictures to turn them into a movie. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368983] Kmail crashes randomly
https://bugs.kde.org/show_bug.cgi?id=368983 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #1 from DeMus --- SolydKEE 64-bit, based on Debian 9 Testing KMail 5.2.3 KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) The xcb windowing system KMail crashes when adding Gmail IMAP account. Did try again and happened again. Crashreport: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3c7c419e40 (LWP 2789))] Thread 25 (Thread 0x7f3b409e4700 (LWP 2851)): #0 0x7f3c73085024 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3c7303f3c1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c7303f974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 24 (Thread 0x7f3bc141e700 (LWP 2840)): #0 0x7f3c7387a18f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f3c66a69574 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f3c66a695b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 23 (Thread 0x7f3bc2dba700 (LWP 2832)): #0 0x7f3c7a26aea9 in QMutex::unlock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f3c7a49fd25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3c7303f3c9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7303f974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 22 (Thread 0x7f3bc35bb700 (LWP 2830)): #0 0x7f3c7996450d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3c7303f9d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 21 (Thread 0x7f3bc3dbc700 (LWP 2828)): #0 0x7f3c73085024 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3c7303eecc in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c7303f8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c7303faec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c7a4a051b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3c7a44819a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c7a26de53 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c7a272d78 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c73874464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3c7996d97f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread
