[plasmashell] [Bug 453703] New: Plasmashell keeps crashing while CUPS is running
https://bugs.kde.org/show_bug.cgi?id=453703
Bug ID: 453703
Summary: Plasmashell keeps crashing while CUPS is running
Product: plasmashell
Version: 5.24.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: oss+kde+bugzi...@mayeul.net
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
Application: plasmashell (5.24.5)
Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.5-arch1-2 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I started the kde plasma session from sddm
- Unusual behavior I noticed:
Flickering desktop background, no taskbar, no desktop icons. Just the wallpaper
alternating with a flashing black screen.
I noticed mentions of cups in the logs (which I'm attaching), so I stopped the
service. Plasmashell finally started up and displayed the taskbar and
everything. Previously, I had tried renaming multiple kde-related dot files.
- Custom settings of the application:
I have a lot of printers configured with CUPS.
I am pretty sure the CUPS plasmoid crashes, which brings down the whole
plasmashell with it.
It's notable that it's far from the first time I report the ploblem. I had a
very similar issue (CUPS plasmoid-related plasmashell crash) years ago, but it
was fixed. Having any integration or plasmoid crash should not bring down the
whole shell, regardless of where the issue comes from.
The crash can be reproduced every time.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 PrinterModel::updateDest(QStandardItem*, KCupsPrinter const&)
(this=this@entry=0x5616fbff3520, destItem=0x0, printer=...) at
/usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:249
#7 0x7f94234c4503 in PrinterModel::getDestsFinished(KCupsRequest*)
(this=0x5616fbff3520, request=0x5616fbfe0fe0) at
/usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:137
#8 0x7f949418b7d6 in QObject::event(QEvent*) (this=,
e=0x5616fc011e70) at kernel/qobject.cpp:1314
#9 0x7f9494dbd2c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5616fbff3520, e=0x5616fc011e70) at
kernel/qapplication.cpp:3637
#10 0x7f94941675aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5616fbff3520, event=0x5616fc011e70) at
kernel/qcoreapplication.cpp:1064
#11 0x7f94941680a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5616fa0cdf00) at
kernel/qcoreapplication.cpp:1821
#12 0x7f94941af678 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x5616fa216290) at kernel/qeventdispatcher_glib.cpp:277
#13 0x7f9492535163 in g_main_dispatch (context=0x7f9488005010) at
../glib/glib/gmain.c:3417
#14 g_main_context_dispatch (context=0x7f9488005010) at
../glib/glib/gmain.c:4135
#15 0x7f949258b9e9 in g_main_context_iterate.constprop.0
(context=context@entry=0x7f9488005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4211
#16 0x7f94925326c5 in g_main_context_iteration (context=0x7f9488005010,
may_block=1) at ../glib/glib/gmain.c:4276
#17 0x7f94941b357a in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5616fa21c470, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#18 0x7f949415f88b in
QEventLoop::exec(QFlags) (this=0x7fff37afd600,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#19 0x7f949416afd7 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#20 0x7f94945381d2 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1867
#21 0x7f9494dbb64a in QApplication::exec() () at
kernel/qapplication.cpp:2829
#22 0x5616f9ed0f81 in main(int, char**) (argc=,
argv=0x7fff37afd7a0) at
/usr/src/debug/plasma-workspace-5.24.5/shell/main.cpp:238
[Inferior 1 (process 213427) detached]
The reporter indicates this bug may be a duplicate of or related to bug 452428.
Possible duplicates by query: bug 453681, bug 453578, bug 453546, bug 453098,
bug 453097.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 453703] Plasmashell keeps crashing while CUPS is running
https://bugs.kde.org/show_bug.cgi?id=453703 --- Comment #1 from Mayeul Cantan --- Created attachment 148766 --> https://bugs.kde.org/attachment.cgi?id=148766&action=edit plasmashell --replace output. It just keep on looping over this again and again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453703] Plasmashell keeps crashing while CUPS is running
https://bugs.kde.org/show_bug.cgi?id=453703 --- Comment #2 from Mayeul Cantan --- Created attachment 148767 --> https://bugs.kde.org/attachment.cgi?id=148767&action=edit New crash information added by DrKonqi plasmashell (5.24.5) using Qt 5.15.3 This is a second crash report generated by baloo, the backtrace might be a bit different, I'm attaching it here in case it is useful. -- Backtrace (Reduced): #6 PrinterModel::updateDest(QStandardItem*, KCupsPrinter const&) (this=this@entry=0x55a92897a4b0, destItem=0x0, printer=...) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:249 #7 0x7f8b98111503 in PrinterModel::getDestsFinished(KCupsRequest*) (this=0x55a92897a4b0, request=0x55a928967e60) at /usr/src/debug/print-manager-22.04.1/libkcups/PrinterModel.cpp:137 #8 0x7f8bff19a7d6 in QObject::event(QEvent*) (this=, e=0x55a928998580) at kernel/qobject.cpp:1314 #9 0x7f8bffdcc2c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55a92897a4b0, e=0x55a928998580) at kernel/qapplication.cpp:3637 #10 0x7f8bff1765aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a92897a4b0, event=0x55a928998580) at kernel/qcoreapplication.cpp:1064 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453703] Plasmashell keeps crashing while CUPS is running
https://bugs.kde.org/show_bug.cgi?id=453703 Mayeul Cantan changed: What|Removed |Added CC||oss+kde+bugzi...@mayeul.net -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 456919] New: Unable to re-activate color picker
https://bugs.kde.org/show_bug.cgi?id=456919 Bug ID: 456919 Summary: Unable to re-activate color picker Product: kolourpaint Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: oss+kde+bugzi...@mayeul.net Target Milestone: --- SUMMARY I played around with undocking the color picker some time ago, under sway/wayland. I closed it, but I cannot toggle it back on, there is no menu option. Configuration⇾Toolbars should include the color picker. STEPS TO REPRODUCE 1. Under sway, unlock the toolbars 2. Drag one of them, it becomes a pop-up window that you can drag around (by pressing meta, as the drag area doesn't work) and with no borders, but that you cannot reattach. 3. Close the toolbox window with the sway shortcut. 4. You cannot re-enable the color toolbox, though you can for most others. It should probably work under plasma/wayland or plasma as well. OBSERVED RESULT Once closed, the color picker toolbox cannot be opened again. Toolboxes cannot be docked again, at least under sway. EXPECTED RESULT At least put a toggle to make the toolbox appear again. Maybe also add a button to reset the default toolbox positions and assortment. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Sway, Arch Linux x86_64 KDE Frameworks Version: 5.96.0-1 Qt Version: 5.15.5 ADDITIONAL INFORMATION wayland-egl -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474992] New: Feature request: scrape travel information from plane portal
https://bugs.kde.org/show_bug.cgi?id=474992 Bug ID: 474992 Summary: Feature request: scrape travel information from plane portal Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: oss+kde+bugzi...@mayeul.net Target Milestone: --- SUMMARY *** I just became aware that some plane companies broadcast location information and ETA through their on-board Wi-Fi. It would be great to scrape this information and update the ETA, etc. *** This came to my attention thanks to the article linked by https://news.ycombinator.com/item?id=37691232 The article provides information regarding the Southwest airlines API, and a comment in the HN thread gives some info about Delta airlines. I also suggested this to the "trains" UnifiedNLP provider: https://gitlab.com/Sorunome/trains-unifiednlp/-/issues/4 They may have some information on other train APIs, I am not sure which is more featured, theirs or Itinerary's. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 453703] Plasmashell keeps crashing while CUPS is running
https://bugs.kde.org/show_bug.cgi?id=453703 --- Comment #6 from Mayeul Cantan --- Created attachment 153699 --> https://bugs.kde.org/attachment.cgi?id=153699&action=edit New backtrace 2022-11 Well, this is still happening. Unfortunately, I can't look up a bug report within Dr Konqui anymore with the port to QML, only select from the list. Attaching another backtrace. I am open to sharing my CUPS configuration; most printers in here are obsolete entries. I encountered this issue on multiple computers that had obsolete printers entries, in unrelated settings (no common printer). How can an issue with a single plasmoid bring the whole shell down? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411870] Plasma desktop crashes right after start
https://bugs.kde.org/show_bug.cgi?id=411870 --- Comment #1 from Mayeul Cantan --- Created attachment 123132 --> https://bugs.kde.org/attachment.cgi?id=123132&action=edit New crash information added by DrKonqi plasmashell (5.16.5) using Qt 5.13.1 - What I was doing when the application crashed: Starting a wayland session from sddm. Crash is reproductible everytime if starting plasmashell again from the command line. - Custom settings of the application: Sway Wayland session (with xwayland) open on other tty under the same user. -- Backtrace (Reduced): #6 0x7fa95d4a4e78 in JobModel::updateJob(int, KCupsJob const&) () at /usr/lib/libkcupslib.so #7 0x7fa95d4a6fec in JobModel::insertJob(int, KCupsJob const&) () at /usr/lib/libkcupslib.so #8 0x7fa95d4a74c0 in JobModel::getJobFinished(KCupsRequest*) () at /usr/lib/libkcupslib.so #9 0x7fa98cb9544a in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x7fa98d6a94f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411870] Plasma desktop crashes right after start
https://bugs.kde.org/show_bug.cgi?id=411870 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404452] New: Plasmashell crashed when adding a new panel on wayland
https://bugs.kde.org/show_bug.cgi?id=404452 Bug ID: 404452 Summary: Plasmashell crashed when adding a new panel on wayland Product: plasmashell Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mayeul.can...@live.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.0) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.8-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: - right clicked on the desktop -> add default panel I find plasmashell on wayland to be quite unstable. It crashed again a few minutes later when I right clicked on a kickoff icon. kwin tends to crash as well, especially when my mouse moves from one screen to another. Unfortunately, drkonqui doesn't always show up when I hit those crashes. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbbc56b680 (LWP 1184))] Thread 27 (Thread 0x7fbb517e3700 (LWP 1374)): #0 0x7fbbc09c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbc18c5c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fbbc18c5d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fbbc361292d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fbbc3612b9c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fbbc18bf96c in () at /usr/lib/libQt5Core.so.5 #6 0x7fbbc09bea9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fbbc15a9b23 in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7fbb51fe4700 (LWP 1373)): #0 0x7fbbc09c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbb3999a84 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fbbb39997a8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fbbc09bea9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fbbc15a9b23 in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fbb527e5700 (LWP 1372)): #0 0x7fbbc159a7a4 in read () at /usr/lib/libc.so.6 #1 0x7fbbbfa1c971 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fbbbfa6d0b0 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fbbbfa6e4e6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fbbbfa6e62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fbbc1ad1d04 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fbbc1a7ab2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fbbc18be569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fbbc358ae7b in () at /usr/lib/libQt5Quick.so.5 #9 0x7fbbc18bf96c in () at /usr/lib/libQt5Core.so.5 #10 0x7fbbc09bea9d in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fbbc15a9b23 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fbb52fe6700 (LWP 1371)): #0 0x7fbbc09c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbc18c5c4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fbbc18c5d3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fbbc361292d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fbbc3612b9c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fbbc18bf96c in () at /usr/lib/libQt5Core.so.5 #6 0x7fbbc09bea9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fbbc15a9b23 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fbb88ff9700 (LWP 1370)): #0 0x7fbbc09c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbb3999a84 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fbbb39997a8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fbbc09bea9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fbbc15a9b23 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fbb897fa700 (LWP 1340)): #0 0x7fbbc09c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbb3999a84 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fbbb39997a8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fbbc09bea9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fbbc15a9b23 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fbb89ffb700 (LWP 1339)): #0 0x7fbbc09c4afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbb3999a84 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fbbb39997a8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fbbc09bea9d in s
[plasmashell] [Bug 404452] Plasmashell crashed when adding a new panel on wayland
https://bugs.kde.org/show_bug.cgi?id=404452 --- Comment #1 from Mayeul Cantan --- All right, I found out shortly after that it might be related to my having only one virtual desktop after deleting some config files. Unfortunately, kwin messed up the screen, and I was in a hurry to post the crash report before restarting it, so I couldn't add that information to the original report. This seems to happen when switching TTYs. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402456] Video output identification labels broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=402456 Mayeul Cantan changed: What|Removed |Added Version|5.14.4 |5.15.1 --- Comment #1 from Mayeul Cantan --- Additionally, alt+dragging these labels cause a plasmashell (possibly kwin) crash. I can reproduce every time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #3 from Mayeul Cantan --- I came in to report the same problem. The system frequently freezes, with the mouse not moving for a couple seconds, or the screen not being refreshed. Regardless of what is causing high IO usage within baloo and akonadi, I consider them background tasks (most of the time), and I would like to see them prioritized as such. Could baloorunner be ran with the equivalent of ionice -c 3 by default? (and maybe nice as well). My CPU is quite beefy, but I suffer of I/O contention: Arch Linux Ryzen 7 2700X 8 GiB DDR4 2666 4TiB HDD system drive (WDC WD40EZRZ) I will probably upgrade to a SSD at some point, but this is no excuse for a background task to consume all of the available disk IO bandwidth ;) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 417338] New: Kate icon is out-of-date on the windows store
https://bugs.kde.org/show_bug.cgi?id=417338 Bug ID: 417338 Summary: Kate icon is out-of-date on the windows store Product: kate Version: unspecified Platform: MS Windows OS: All Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- SUMMARY I just visited the store page following that blog post: https://kate-editor.org/post/2020/2020-02-08-windows-store-status/ It looks like the icon wasn't updated there. I hope this is the right place to report, there isn't a Win store platform on the bugzilla. STEPS TO REPRODUCE 1. Visit https://www.microsoft.com/store/apps/9NWMW7BB59HW OBSERVED RESULT Old icon in the store page EXPECTED RESULT The new icon should have been used: https://kate-editor.org/post/2020/2020-01-30-new-breeze-kate-icon/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417383] New: systemsettings crash when enabling indexing
https://bugs.kde.org/show_bug.cgi?id=417383 Bug ID: 417383 Summary: systemsettings crash when enabling indexing Product: systemsettings Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.2-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Plasmashell had already be hung for a few seconds, with kickoff searching for "firefox". Meanwhile, I enabled search indexing, and everything went down. I had been browsing systemsettings, notably the online accounts section before (I didn't have kaccounts-providers installed, so I browsed away and installed it in the background before enabling indexing). -- Backtrace: Application: Configuration du système (systemsettings5), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57cd938840 (LWP 1732))] Thread 58 (Thread 0x7f56acfe0700 (LWP 1954)): #0 0x7f57d0c35c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57ca342dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f57ca3429f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 57 (Thread 0x7f56ad7e1700 (LWP 1952)): #0 0x7f57d0c35c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57ca342dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f57ca3429f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 56 (Thread 0x7f56a700 (LWP 1943)): #0 0x7f57d0c35c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57ca342dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f57ca3429f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 55 (Thread 0x7f56d0ff9700 (LWP 1941)): #0 0x7f57d0c35c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57ca342dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f57ca3429f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 54 (Thread 0x7f56d17fa700 (LWP 1936)): #0 0x7f57d0c35c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57ca342dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f57ca3429f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 53 (Thread 0x7f56d1ffb700 (LWP 1934)): #0 0x7f57d0c35c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57ca342dfc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f57ca3429f8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 52 (Thread 0x7f56d27fc700 (LWP 1931)): #0 0x7f57d204e9ef in poll () at /usr/lib/libc.so.6 #1 0x7f57d001f120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f57d001f1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f57d260903c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f57d25af4cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f57d23d3e52 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f57d23d4fc6 in () at /usr/lib/libQt5Core.so.5 #7 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6 Thread 51 (Thread 0x7f56d2ffd700 (LWP 1930)): #0 0x7f57d204e9ef in poll () at /usr/lib/libc.so.6 #1 0x7f57d001f120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f57d001f1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f57d260903c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f57d25af4cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f57d23d3e52 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f57d23d4fc6 in () at /usr/lib/libQt5Core.so.5 #7 0x7f57d0c2f4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f57d20592d3 in clone () at /usr/lib/libc.so.6
[drkonqi] [Bug 417388] New: Drkonqui crash on wayland when clicking url to report bug
https://bugs.kde.org/show_bug.cgi?id=417388 Bug ID: 417388 Summary: Drkonqui crash on wayland when clicking url to report bug Product: drkonqi Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Created attachment 125824 --> https://bugs.kde.org/attachment.cgi?id=125824&action=edit kcrash SUMMARY Konsole crashed. Drkonqui popped up to report a bug. Drkonqui crashed. Drkonqui popped up again, asking me to manually report a bug. I clicked the URL, and Drkonqui crashed again. It popped up a third time with this backtrace. I had heavy disk I/O in the background, that slowed down everything, so it could be related to threading, synchronisation issues, or due to the fact that I am running Wayland. STEPS TO REPRODUCE Unsure SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.5.2-arch1-1 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 417867] New: Add support for flutter/dart "arb" file format
https://bugs.kde.org/show_bug.cgi?id=417867 Bug ID: 417867 Summary: Add support for flutter/dart "arb" file format Product: lokalize Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: mayeul.can...@live.fr CC: sha...@ukr.net Target Milestone: --- SUMMARY It looks like google's new language/framework uses an "arb" file format in place of po files. I am not too familiar with it, but they look like plain json files, and would like to be able to use lokalize to edit them. I'd be happy with a barebones implementation for now, although the file format doesn't seem overly complex. The specification is available over there: https://github.com/google/app-resource-bundle/wiki/ApplicationResourceBundleSpecification Here is a tutorial with the expected workflow, a possible application, and a few syntax examples: https://www.codeandweb.com/babeledit/tutorials/how-to-translate-your-flutter-apps As an example, the file I attempted to translate is this one, it makes for a real-life example: https://gitlab.com/ChristianPauly/fluffychat-flutter/-/blob/9a52e938628df3c35e2cf7a2af6e33cdb5a0f6ed/lib/i18n/intl_messages.arb A german-translated one sits in the same folder: https://gitlab.com/ChristianPauly/fluffychat-flutter/-/blob/9a52e938628df3c35e2cf7a2af6e33cdb5a0f6ed/lib/i18n/intl_de.arb As well as instruction in that repository's readme: https://gitlab.com/ChristianPauly/fluffychat-flutter/-/blob/9a52e938628df3c35e2cf7a2af6e33cdb5a0f6ed/README.md#how-to-add-translations-for-your-language A mime type should probably be created as well, but that can be done independently. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 417867] Add support for flutter/dart "arb" file format
https://bugs.kde.org/show_bug.cgi?id=417867 --- Comment #1 from Mayeul Cantan --- I also created a feature request for gtranslator to support this: https://gitlab.gnome.org/GNOME/gtranslator/issues/102 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415316] New: Plasmashell crashed when scrolling with mousewheel on the network widget
https://bugs.kde.org/show_bug.cgi?id=415316 Bug ID: 415316 Summary: Plasmashell crashed when scrolling with mousewheel on the network widget Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mayeul.can...@live.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.3-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I don't recall the exact sequence and wasn't able to reproduce, but I opened the network widget,pinned it, got to the details tab, then back to the speed tab, scrolled with my mousewheel, and plasmashell crashed. I am not sure my VPN connections were displayed in the widget when it crashed (I was scrolling) but they were there after plasmashell's auto restart. I had some flatpak updates in the background, managed by discover, but that's probably unrelated. (I fiddled with the widget trying to see of total data use was reported, but couldn't find it, to my slight disappointment). The crash does not seem to be reproducible. -- Backtrace (Reduced): #8 0x7f5b012038f4 in () at /usr/lib/libQt5Core.so.5 #9 0x7f5afc93c11e in () at /usr/lib/libQt5WaylandClient.so.5 #10 0x7f5afc94b5c1 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 [...] #12 0x7f5b01445742 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7f5b01445a92 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 Possible duplicates by query: bug 415304, bug 415296, bug 415240, bug 415239, bug 415233. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415316] Plasmashell crashed when scrolling with mousewheel on the network widget
https://bugs.kde.org/show_bug.cgi?id=415316 --- Comment #1 from Mayeul Cantan --- Created attachment 124568 --> https://bugs.kde.org/attachment.cgi?id=124568&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 414535] New: Flatpak icon is low-resolution and outdated
https://bugs.kde.org/show_bug.cgi?id=414535 Bug ID: 414535 Summary: Flatpak icon is low-resolution and outdated Product: kolourpaint Version: unspecified Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: mayeul.can...@live.fr Target Milestone: --- Created attachment 124127 --> https://bugs.kde.org/attachment.cgi?id=124127&action=edit Flathub page screenshot detail with the kolourpaint icon. SUMMARY Kolourpaint is one of the featured application on discover, when flathub is the only available source. However, it shows a very low-res icon. That icon is also visible on flathub at the following address: https://www.flathub.org/apps/details/org.kde.kolourpaint -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 --- Comment #6 from Mayeul Cantan --- (In reply to Axel Braun from comment #5) > (In reply to Stefan Brüns from comment #4) > > > Even with low priority, the kernel eventually has to flush the write > > buffers, causing the high I/O latency for other tasks. > > Should the I/O traffic from higher prioritized tasks not processed before as > well? I mean, if baloo does not get any CPU time, how can it create such a > high traffic? Looking at iotop, it is mostly a factor 100 to 1000 higher > than other tasks >From this link, it seems to be the case (though a link to the kernel source would have been nicer) https://unix.stackexchange.com/questions/153505/how-disk-io-priority-is-related-with-process-priority > io_priority = (cpu_nice + 20) / 5 In my case, though, it was always baloorunner showing at 99.99 % I/O in iotop. baloo_file_extractor would also run sometimes, but with a lesser subjective impact on performance. Setting baloorunner to a lower priority using ionice seemed to improve things quite a bit, although I would have to confirm it. I get the point about needing to flush the cache at some point. Unfortunately, I am at a loss as to why my mouse freezes because of it. I am on a 8 (16 SMT)-core CPU, and only a couple are used by the kernel. CPU <-> RAM bandwidth should not be the limiting factor, and other threads should be able to go trough when CPU <-> Sata Controller is being waited on. Maybe it has to do with interrupts comming in from the SATA controller? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396783] New: Okular crashes when restoring session if the file has been deleted
https://bugs.kde.org/show_bug.cgi?id=396783 Bug ID: 396783 Summary: Okular crashes when restoring session if the file has been deleted Product: okular Version: 1.4.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: okular (1.4.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Just booting my system. My session is set to restore previously open applications. Okular was open last time I closed it, with a temporary document file open (a pdf downloaded and opened from Firefox). Okular displays a dialog box stating it can't open the file, and apparently crashes (Dr Konqui pops up) when clicking OK. - Expected behaviour: Okular should not crash when pressing OK. Alternatively, Okular could make backup copies of the opened files when saving the session (this could be done for all documents from the moment they are opened, like libreoffice). I am not sure what would be the preffered way of handling large files, though. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f000c9a3f80 (LWP 1141))] Thread 4 (Thread 0x7effe6930700 (LWP 1201)): #0 0x7f000563affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7effe74fa124 in () at /usr/lib/dri/i965_dri.so #2 0x7effe74f9e18 in () at /usr/lib/dri/i965_dri.so #3 0x7f0005635075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f00086a853f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7efff0f19700 (LWP 1166)): #0 0x7f0008fb9f54 in () at /usr/lib/libQt5Core.so.5 #1 0x7f0003066a49 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f000306744e in () at /usr/lib/libglib-2.0.so.0 #3 0x7f000306763e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f0008fba054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f0008f6594c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f0008daea99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f000940a976 in () at /usr/lib/libQt5DBus.so.5 #8 0x7f0008db8b45 in () at /usr/lib/libQt5Core.so.5 #9 0x7f0005635075 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f00086a853f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7efffab74700 (LWP 1152)): #0 0x7f000869dea9 in poll () at /usr/lib/libc.so.6 #1 0x7f0005a5b180 in () at /usr/lib/libxcb.so.1 #2 0x7f0005a5ce4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7efffd92322a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f0008db8b45 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0005635075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f00086a853f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f000c9a3f80 (LWP 1141)): [KCrash Handler] #6 0x7f000adc4c7a in () at /usr/lib/libKF5ConfigCore.so.5 #7 0x7f000adc9fbb in () at /usr/lib/libKF5ConfigCore.so.5 #8 0x7f000adbe2f9 in () at /usr/lib/libKF5ConfigCore.so.5 #9 0x7f000add2f15 in KConfigGroup::readEntry(char const*, QVariant const&) const () at /usr/lib/libKF5ConfigCore.so.5 #10 0x562ebbce4dbe in () #11 0x7f000baf5ca0 in KMainWindow::readPropertiesInternal(KConfig*, int) () at /usr/lib/libKF5XmlGui.so.5 #12 0x7f000baf5ce4 in KMainWindow::restore(int, bool) () at /usr/lib/libKF5XmlGui.so.5 #13 0x562ebbce010e in () #14 0x562ebbcdd693 in () #15 0x7f00085d306b in __libc_start_main () at /usr/lib/libc.so.6 #16 0x562ebbcded4a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 393601] New: KTorrent crashes when port changes
https://bugs.kde.org/show_bug.cgi?id=393601 Bug ID: 393601 Summary: KTorrent crashes when port changes Product: ktorrent Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mayeul.can...@live.fr Target Milestone: --- Application: ktorrent (5.1.0) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: * I opened KTorrent (a few torrents were there, downloading) * I opened the settings window * I changed the port KTorrent was listening on * I hit "Apply" * KTorrent crashed. I can always reproduce this bug. The settings seem to be remembered when I restart KTorrent. DHT is enabled, if that matters at all. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Thread 0x7fc7a635a700 (LWP 14105) exited] [Current thread is 1 (Thread 0x7fc81e469380 (LWP 14070))] Thread 7 (Thread 0x7fc7a5b59700 (LWP 14106)): #0 0x7fc818553dd6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fc7a7bd84b0 in () at /usr/lib/libnss_resolve.so.2 #2 0x7fc7a7bdaba9 in () at /usr/lib/libnss_resolve.so.2 #3 0x7fc7a7bc8c0d in _nss_resolve_gethostbyaddr2_r () at /usr/lib/libnss_resolve.so.2 #4 0x7fc7a7bc9064 in _nss_resolve_gethostbyaddr_r () at /usr/lib/libnss_resolve.so.2 #5 0x7fc818570071 in gethostbyaddr_r@@GLIBC_2.2.5 () at /usr/lib/libc.so.6 #6 0x7fc818578550 in gni_host_inet_name.isra () at /usr/lib/libc.so.6 #7 0x7fc818578c83 in getnameinfo () at /usr/lib/libc.so.6 #8 0x7fc81dc95308 in () at /usr/lib/libKF5Torrent.so.6 #9 0x7fc81dc95a41 in () at /usr/lib/libKF5Torrent.so.6 #10 0x7fc819203acd in () at /usr/lib/libQt5Core.so.5 #11 0x7fc813e250bc in start_thread () at /usr/lib/libpthread.so.0 #12 0x7fc81855e2ff in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fc7a6b5b700 (LWP 14104)): #0 0x7fc818553cd9 in poll () at /usr/lib/libc.so.6 #1 0x7fc81dc95fc5 in net::Poll::poll(int) () at /usr/lib/libKF5Torrent.so.6 #2 0x7fc81dc9217c in () at /usr/lib/libKF5Torrent.so.6 #3 0x7fc81dc92216 in () at /usr/lib/libKF5Torrent.so.6 #4 0x7fc81dc92449 in () at /usr/lib/libKF5Torrent.so.6 #5 0x7fc819203acd in () at /usr/lib/libQt5Core.so.5 #6 0x7fc813e250bc in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fc81855e2ff in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fc7fe5ed700 (LWP 14075)): [KCrash Handler] #6 0x7fc81942e0b4 in QSocketNotifier::type() const () at /usr/lib/libQt5Core.so.5 #7 0x7fc81944d0bd in () at /usr/lib/libQt5Core.so.5 #8 0x7fc811719f22 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #9 0x7fc81171a4c6 in () at /usr/lib/libglib-2.0.so.0 #10 0x7fc81171a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #11 0x7fc81944d264 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #12 0x7fc8193ef32b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #13 0x7fc8191fe72e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #14 0x7fc819203acd in () at /usr/lib/libQt5Core.so.5 #15 0x7fc813e250bc in start_thread () at /usr/lib/libpthread.so.0 #16 0x7fc81855e2ff in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fc7fedee700 (LWP 14074)): #0 0x7fc818553cd9 in poll () at /usr/lib/libc.so.6 #1 0x7fc81171a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc81171a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc81944d264 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc8193ef32b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc8191fe72e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc819203acd in () at /usr/lib/libQt5Core.so.5 #7 0x7fc813e250bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fc81855e2ff in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fc807795700 (LWP 14071)): #0 0x7fc818553cd9 in poll () at /usr/lib/libc.so.6 #1 0x7fc814465180 in () at /usr/lib/libxcb.so.1 #2 0x7fc814466e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fc80a32f82a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fc819203acd in () at /usr/lib/libQt5Core.so.5 #5 0x7fc813e250bc in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc81855e2ff in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fc81e469380 (LWP 14070)): #0 0x7fc813e2b07c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x0
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #7 from Mayeul Cantan --- To be fair, I often just change TTY and press the suspend button there. It should also work with the power button to poweroff the computer (or ctrl-alt-del), so some points here are rather moot. Showing a confirmation UI (maybe with a timer) would probably be a better solution. Ideally, the screen locker could know what kind of activity there is in the background (KTorrent downloading, disk copy, compilation) and show a message that some actions could be interrupted, but that might be just me overthinking this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402456] New: Video output identification labels broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=402456 Bug ID: 402456 Summary: Video output identification labels broken on Wayland Product: KScreen Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Created attachment 117055 --> https://bugs.kde.org/attachment.cgi?id=117055&action=edit Screenshot showing two monitor identification popups on the same screen SUMMARY When clicking on the "i" in the monitor list, all of the tooltips appear on the same screen (see attached screenshot). That might be due to Wayland not allowing manual control of window placement. STEPS TO REPRODUCE 1. Launch a Wayland session with multiple screens attached 2. Open the kscreen kcm 3. Click the "i" icon in the bottom-right corner of the screen view. OBSERVED RESULT A couple popups appear on the same screen as the mouse or kcm. EXPECTED RESULT Each popup should be placed on the appropriate screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 4.19.11 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Mesa 18.3.1 w/ R9 Fury -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match
https://bugs.kde.org/show_bug.cgi?id=385754 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #22 from Mayeul Cantan --- I can confirm this, on Arch, Discover 5.13.5. The notification in the tray displays 5 updates, only two show up in discover (I will attach a screenshot). I don't think that runtimes always appear in Discover. The output of flatpak list displays 5 packages, so all presumably need to be updated: RefOptions com.valvesoftware.Steam/x86_64/stable system,current org.freedesktop.Platform.Compat.i386/x86_64/18.08 system,runtime org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 system,runtime org.freedesktop.Platform.html5-codecs/x86_64/18.08 system,runtime org.freedesktop.Platform/x86_64/18.08 system,runtime It could be related to Bug 395923 where runtimes are handled differently as well. I was about to write that no update at all was displayed, but they just took a long time (maybe 5 minutes) to be displayed. It could be the same with people reporting that no update is shown. Adding a progress indicator, or an indication that updates are being checked for could be of some help here. After installing updates trough Discover, no updates are shown int the main windows, though one remains, and is displayed in the tray. Discover complained about org.freedesktop.Platform.Compat.i386 not being in the flathub remote, although it works with `flatapak update`. After updating this way, the tray icon disappears. If that helps for reproducing, here is the output of $ flatpak list --ostree-verbose -v -d F: No installations directory in /etc/flatpak/installations.d. Skipping F: Opening user flatpak installation at path /home/user/.local/share/flatpak F: Opening system flatpak installation at path /var/lib/flatpak RefOrigin Active commit Latest commit Installed size Options com.valvesoftware.Steam/x86_64/stable flathub eb44022a304e - 15,4 MB system,current org.freedesktop.Platform.Compat.i386/x86_64/18.08 flathub 279502715b02 - 493,8 MB system,runtime org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 flathub f4e8c0397f5a - 8,1 MB system,runtime org.freedesktop.Platform.html5-codecs/x86_64/18.08 flathub 6e3e9f613bdd - 7,9 MB system,runtime org.freedesktop.Platform/x86_64/18.08 flathub 7af74803c28b - 751,1 MB system,runtime I'm not sure if you can install the same revisions to help with reproducing this bug, but I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match
https://bugs.kde.org/show_bug.cgi?id=385754 --- Comment #23 from Mayeul Cantan --- Created attachment 115361 --> https://bugs.kde.org/attachment.cgi?id=115361&action=edit Discover 5.13.5 on Arch -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399303] New: Discover crashed when clicking the "Update" button in the tray icon
https://bugs.kde.org/show_bug.cgi?id=399303 Bug ID: 399303 Summary: Discover crashed when clicking the "Update" button in the tray icon Product: Discover Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.18.10-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Writing a comment on bug 385754, I clicked the "Update" button mutiple times (opening Discover, then closing it, reopening it...), and Discover crashed at some point after clicking it. I might have clicked on "check updates" in the client before closing it. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f23316a3800 (LWP 6869))] Thread 13 (Thread 0x7f231286c700 (LWP 7179)): #0 0x7f23359e6ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2336a405fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f2336a38024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f2336a3ff65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f23359e0a9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f2336722a43 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f22feffd700 (LWP 7178)): [KCrash Handler] #6 0x7f231e1d3fdf in () at /usr/lib/libflatpak.so.0 #7 0x7f231e214cda in flatpak_installation_list_installed_refs () at /usr/lib/libflatpak.so.0 #8 0x7f231e216f75 in flatpak_installation_list_installed_refs_for_update () at /usr/lib/libflatpak.so.0 #9 0x7f231e2dd401 in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #10 0x7f2336a37e11 in () at /usr/lib/libQt5Core.so.5 #11 0x7f2336a3ff65 in () at /usr/lib/libQt5Core.so.5 #12 0x7f23359e0a9d in start_thread () at /usr/lib/libpthread.so.0 #13 0x7f2336722a43 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f22fcff9700 (LWP 6931)): #0 0x7f2336717bb1 in poll () at /usr/lib/libc.so.6 #1 0x7f2334f5cee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f2334f5df62 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f231e067c28 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f2334f263eb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f23359e0a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f2336722a43 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f22fe7fc700 (LWP 6884)): #0 0x7f2336717bb1 in poll () at /usr/lib/libc.so.6 #1 0x7f2334f5cee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f2334f5cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f2336c40fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f2336bec8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f2336a35eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f2336a3ff65 in () at /usr/lib/libQt5Core.so.5 #7 0x7f23359e0a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f2336722a43 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f22f700 (LWP 6879)): #0 0x7f2336713734 in read () at /usr/lib/libc.so.6 #1 0x7f2334f0b781 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f2334f5ba50 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f2334f5ce86 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f2334f5cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f2336c40fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f2336bec8cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f2336a35eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f2336a3ff65 in () at /usr/lib/libQt5Core.so.5 #9 0x7f23359e0a9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f2336722a43 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f231186a700 (LWP 6878)): #0 0x7f2336713734 in read () at /usr/lib/libc.so.6 #1 0x7f2334f0b781 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f2334f5ba50 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f2334f5ce86 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f2334f5cfce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f2334f5d022 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f2334f263eb in () at /usr/lib/libglib-2.0.so.0 #7 0x7f23359e0a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f2336722a43 in clone () a
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #6 from Mayeul Cantan --- (In reply to Alexander Mentyu from comment #4) > What is there right way to gdb of plasmashell? > > I'm trying: > sudo gdb --pid $(pidof plasmashell) > thread apply all bt > > but Plasma and panel hangs and i cannot drag files or do any actions in them I am not sure this is the right way, but I didn't bother with this, and just killed plasmashell and ran it within GDB. (gdb /path/to/plasmashell, and then > run) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #7 from Mayeul Cantan --- Also, bug 377210 is marked as a duplicate of bug 385605. This could be a duplicate, but I do not have the expertise to say so. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399869] New: No feedback on the update page when updating backends
https://bugs.kde.org/show_bug.cgi?id=399869 Bug ID: 399869 Summary: No feedback on the update page when updating backends Product: Discover Version: 5.14.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- SUMMARY This is probably due to slow backends. As originally stated in https://bugs.kde.org/show_bug.cgi?id=385754#c22 Discover can be slow to display the list of packages that need updates. During this time, it displays "no updates available", which is a bit misleading, as can be seen in the aforelinked thread. STEPS TO REPRODUCE 1. Wait for some updates to show up 2. Click on the tray icon -> display updates 3. Wait for a few seconds in front of the "no updates" screen (up to a few minutes, especially on slow connections) for updates to be displayed OBSERVED RESULT Discover is slow to display the list of updates. The user does not receive any feedback during this time. EXPECTED RESULT It would be nice to display something like "Discover is compiling the list of updates" or "Discover is checking for updates", with a spinner. Best would be to list each backend separately, and display its status: no updates, checking, X updates, separately. SOFTWARE VERSIONS KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399880] New: Discover crashes when quickly going in and out of the main categories
https://bugs.kde.org/show_bug.cgi?id=399880 Bug ID: 399880 Summary: Discover crashes when quickly going in and out of the main categories Product: Discover Version: 5.14.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: plasma-discover (5.14.0) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.18.12-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Quickly moving around the categories to check them out. I can reproduce by rapidly clicking the top category, back, and the category again, etc. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63c55de800 (LWP 15624))] Thread 16 (Thread 0x7f637b7fe700 (LWP 15646)): #0 0x7f63ca45a40d in syscall () at /usr/lib/libc.so.6 #1 0x7f63c8c47f61 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f63c8cc5cb3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f63c8cc5eb3 in g_async_queue_timeout_pop () at /usr/lib/libglib-2.0.so.0 #4 0x7f63c8c69c7a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f63c8c623eb in () at /usr/lib/libglib-2.0.so.0 #6 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f638effd700 (LWP 15640)): #0 0x7f63c9722ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63ca77d5fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f63ca775024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f63ca77cf65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f63a0ff9700 (LWP 15638)): #0 0x7f63c9722ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63ca77d5fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f63ca775024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f63ca77cf65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f638700 (LWP 15637)): #0 0x7f63ca454bb1 in poll () at /usr/lib/libc.so.6 #1 0x7f63c8c98ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63c8c98fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f63c8c99022 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f63c8c623eb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f63a1ffb700 (LWP 15636)): #0 0x7f63c9722ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63ca77d5fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f63ca775024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f63ca77cf65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f63a27fc700 (LWP 15634)): #0 0x7f63ca454bb1 in poll () at /usr/lib/libc.so.6 #1 0x7f63c8c98ee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63c8c98fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f63ca97dfe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f63ca9298cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f63ca772eb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f63ca77cf65 in () at /usr/lib/libQt5Core.so.5 #7 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f63a2ffd700 (LWP 15633)): #0 0x7f63c9722ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63ca77d5fd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f63ca775024 in () at /usr/lib/libQt5Core.so.5 #3 0x7f63ca77cf65 in () at /usr/lib/libQt5Core.so.5 #4 0x7f63c971ca9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f63ca45fa43 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f63a37fe700 (LWP 15632)): #0 0x7f63ca454bb1 in poll () at /usr/lib/libc.so.6 #1 0x0
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #9 from Mayeul Cantan --- I can confirm as well, I had discover crash on me today when launching it on vanilla Arch (I usually don't since I want to see the detailed update logs, but I wanted to check it out). It crashed on launch; and Dr Konqui suggested this bug report. Installing packagekit-qt5 and packagekit seems to solve the issue. The issue doesn't remain after fatpak is installed. Here is my backtrace, just in case: Application: Découvrir (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6d7328a7c0 (LWP 6018))] Thread 67 (Thread 0x7f6cacfe1700 (LWP 6271)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 66 (Thread 0x7f6cad7e2700 (LWP 6270)): #0 0x7f6d6ea6c3b9 in syscall () at /usr/lib/libc.so.6 #1 0x7f6d6edb9087 in __cxxabiv1::__cxa_guard_acquire(__cxxabiv1::__guard*) (g=0x7f6d6da2cc08) at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/guard.cc:302 #2 0x7f6d6d78255c in () at /usr/lib/libQt5Network.so.5 #3 0x7f6d6d775ca3 in () at /usr/lib/libQt5Network.so.5 #4 0x7f6d6f15b371 in () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 65 (Thread 0x7f6cadfe3700 (LWP 6269)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 64 (Thread 0x7f6cae7e4700 (LWP 6268)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 63 (Thread 0x7f6caefe5700 (LWP 6267)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.6 Thread 62 (Thread 0x7f6caf7e6700 (LWP 6266)): #0 0x7f6d6ea672bd in poll () at /usr/lib/libc.so.6 #1 0x7f6d6936c9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f6d6936cacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6d6f39af0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6d6f3423aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6d6f15a44a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6d6f15ee9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f6d6b2b4297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6d6ea7125f in clone () at /usr/lib/libc.so.
[plasmashell] [Bug 394249] New: Logout screen countdown not cancelling on multi-monitor setups
https://bugs.kde.org/show_bug.cgi?id=394249 Bug ID: 394249 Summary: Logout screen countdown not cancelling on multi-monitor setups Product: plasmashell Version: master Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mayeul.can...@live.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112639 --> https://bugs.kde.org/attachment.cgi?id=112639&action=edit Illustration: countdown is cancelled only on the left monitor This might be related to the look and feel package as well. I would have tried to fix it myself, but I am not proficient enough with Qt/qml to easily pinpoint the problem. On multi monitor setups, the logout overlay appears on every screen. There is one countdown per screen. Moving the selection with the keyboard arrow keys interrupt the countdown on one screen, but not the others, so the log out action ends up happening anyway. It is supposed to cancel the action on every screen. It would actually be nicer not to assume that a screen is the primary one, and show the exact same state on every screen, including selection and hover (even duplicating the mouse could be interesting). My primary monitor is the center one, but the selection is displayed on the leftmost one. See the attached screenshot where only the leftmost screen has its countdown cancelled. (A bit of corruption is visible on the rightmost screen as well, I am using X, Qt 5.10.1, plasma 5.12.5) Related files might be https://cgit.kde.org/plasma-workspace.git/tree/lookandfeel/contents/logout/Logout.qml and https://cgit.kde.org/plasma-workspace.git/tree/ksmserver/shutdowndlg.cpp -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 394375] New: Kate crashes when undoing a file restoration
https://bugs.kde.org/show_bug.cgi?id=394375 Bug ID: 394375 Summary: Kate crashes when undoing a file restoration Product: kate Version: 18.04.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: kate (18.04.1) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I opened a file in Kate, and it offered me to restore its contents as it hadn't been closed correctly [1]. I couldn't display the diff [2], so I chose to restore the file. I then decided it wasn't worth it, so I hit Ctrl+Z to undo the restoration. Kate crashed. [1] I moved the file around before saving it (which, strangely, made kate display an authentication window upon hitting ctrl+s). [2] probably due to kompare or kdiff not being installed; though vimdiff -- or even diff -- could have been used as an alternative. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fadbbb3f600 (LWP 7193))] Thread 11 (Thread 0x7fad825f9700 (LWP 7206)): #0 0x7fadb1eb6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fadb6b3af9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fad953e2149 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fad953e6029 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fad953e120d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fad953e4079 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fadb6b39abd in () at /usr/lib/libQt5Core.so.5 #7 0x7fadb1eb1075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fadb643d53f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fad82dfa700 (LWP 7205)): #0 0x7fadb1eb6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fadb6b3af9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fad953e2149 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fad953e6029 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fad953e120d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fad953e4079 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fadb6b39abd in () at /usr/lib/libQt5Core.so.5 #7 0x7fadb1eb1075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fadb643d53f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fad835fb700 (LWP 7204)): #0 0x7fadb1eb6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fadb6b3af9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fad953e2149 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fad953e6029 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fad953e120d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fad953e4079 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fadb6b39abd in () at /usr/lib/libQt5Core.so.5 #7 0x7fadb1eb1075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fadb643d53f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fad83dfc700 (LWP 7202)): #0 0x7fadb1eb6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fadb6b3af9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fad953e2149 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fad953e6029 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fad953e120d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fad953e4079 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fadb6b39abd in () at /usr/lib/libQt5Core.so.5 #7 0x7fadb1eb1075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fadb643d53f in clone () at /usr/lib/libc.
[kwin] [Bug 398421] New: Wayland: pointer locking not released after application closed
https://bugs.kde.org/show_bug.cgi?id=398421 Bug ID: 398421 Summary: Wayland: pointer locking not released after application closed Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- I tried this game: https://store.steampowered.com/app/2290/Final_DOOM/ which is a DOSBOX game running trough proton (wine packaged by steam). I'm using a steam flatpak. The above shouldn't be relevant, though. The game doesn't work (black screen), I can't alt-tab out, as it comes back on top. When starting it, I get a message about pointer confinement. When closing the game trough alt-f4, my cursor remains locked in place, and I have to alt-tab once more, or press escape for seconds to unlock it. Pointer confinement should be released when the window that asked it is closed. There is also a minor alt-tab issue here, not sure if I should report it, as I don't have much information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398438] New: Desktop cube corruption on misaligned multiple monitors
https://bugs.kde.org/show_bug.cgi?id=398438 Bug ID: 398438 Summary: Desktop cube corruption on misaligned multiple monitors Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Created attachment 114866 --> https://bugs.kde.org/attachment.cgi?id=114866&action=edit Original layout I have three monitors, which are not aligned in a straight way, to match the physical layout. The resulting layout can be seen in the first attachment. When using the desktop cube animation to switch virtual desktops, corruption is shown on my screen. This bug dates back to the kde4 days, as far as I know (it might have been fixed at some point, though). I am using an Intel igpu on this specific computer, with Mesa 18.1.8. Top-left, with the shape of an auto-hiding panel (see bug 382829) that sits here, appears a part of another activity. I do not see that myself (just the panels that becomes semi-transparent; with the right background) when switching desktops, it only appears on the screenshot. Screenshots taken with spectacle -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398438] Desktop cube corruption on misaligned multiple monitors
https://bugs.kde.org/show_bug.cgi?id=398438 --- Comment #1 from Mayeul Cantan --- Created attachment 114867 --> https://bugs.kde.org/attachment.cgi?id=114867&action=edit Screenshot of the problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] New: plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 Bug ID: 398440 Summary: plasmashell crashes on wayland when dragging a file from dolphin over a panel Product: plasmashell Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: 1.0 I do not seem to hit 390430, but when dragging a folder from Dolphin on the panel (not releasing the mouse), plasmashell crashes. Steps to reproduce: Open two maximized Dolphin windows Try to drag a folder from one to another: * Click and start dragging the folder from one Dolphin window, * hover a panel (I'm using a standard task manager) to focus on the background Dolphin window * Observe plasmashell crashing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395690] (Regression) Systemsettings tooltips are displayed in top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=395690 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #9 from Mayeul Cantan --- I can reproduce. Arch Linux Qt 5.11.1 Plasma 5.13.5 Intel/Mesa 18.2.8 Especially the following behaviour, which was not mentioned in this report, but in bug 391649: > Tooltips are displayed ok - if main window was clicked before the tooltip is > shown > Tooltips are shown as separate windows on the task manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr Version|5.11.1 |5.13.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384637] Taking a screenshot of a program that includes a dropdown menu or any plasma popup is not possible under wayland
https://bugs.kde.org/show_bug.cgi?id=384637 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #6 from Mayeul Cantan --- Currently tooltips such as the ones of bug 395690 do not appear on screenshots. > The problem is that the keyboard focus while taking a screenshot is taken > away from the application and they react by closing popups. Would it be possible to let them retain the focus (or have them think so), but filter out any event so that they receive nothing? I expect such a functionality to be useful in multiple places in kwin. An alternative way could be to provide an interface to ask permission before taking the screenshot. Spectacle could add a button "request permission to record screen", and that would allow this capability for the duration of the program run. But I might be mistaken, and such a thing might be already possible trough portals? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398438] Desktop cube corruption on misaligned multiple monitors
https://bugs.kde.org/show_bug.cgi?id=398438 --- Comment #3 from Mayeul Cantan --- > (a) can you reproduce this issue when all screens are aligned in a straight > line? > (b) can you reproduce this bug if you disable the blur effect (and the > background contrast effect)? Short version: (a) Yes. (b) Yes with blur, no with background contrast. Longer version: (a) It seems to happen only if the two following conditions are met: * The two screens on the left share the same Y-coordinates * The screen on the right is lower than this. It doesn't happen if either: * One screen is disabled * The screen on the right is above * The two left screens are misaligned (b) The problem seems fixed now without background contrast. Furthermore, it didn't reappear after re-enabling it. Both blur and background contrast were originally only partially checked. I have no idea what this means. They are both fully checked now, and it seems to be working. This survived across a session connect-and disconnect. That means I can't reproduce the bug anymore for now. I'll write back if it happens again. Thanks for your help :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398438] Desktop cube corruption on misaligned multiple monitors
https://bugs.kde.org/show_bug.cgi?id=398438 --- Comment #5 from Mayeul Cantan --- (In reply to Vlad Zagorodniy from comment #4) > (In reply to Mayeul Cantan from comment #3) > > (b) The problem seems fixed now without background contrast. > You mean the blur effect, right? No. I was able to reproduce this bug with with the blur effect disabled. Then I am pretty sure I re-enabled it. I have not been able to reproduce it after disabling the background contrast effect, either with or without the blur effect. As a matter of fact, I have not been able to reproduce this bug ever since I switched the background contrast effect off, then on again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #2 from Mayeul Cantan --- Created attachment 114882 --> https://bugs.kde.org/attachment.cgi?id=114882&action=edit Backtrace of the crash Here is a backtrace obtained manually from gdb after recompiling with debug symbols. Dr Konqui somehow was unable to generate the backtrace, and asked me about debug symbols for /usr/bin/plasmashell, although those weren't stripped. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #3 from Mayeul Cantan --- It looks like some symbols are missing, though. I'm unsure of the library. Would that be part of Qt or the frameworks? Would it be useful at all to produce another backtrace with those debug symbols? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 398460] New: Screen hotplug not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=398460 Bug ID: 398460 Summary: Screen hotplug not working under Wayland Product: KScreen Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Not sure this is the right place. I use a docking station with my computer (dell lattitude 5580, dell wd15). Intel graphics, Mesa 18.2.8 (Arch). The docking station is connected over USB C, DP alternate mode, and everything works fine under X. Under Wayland, though, the screens are not detected when I plug the docking station in. Everything else works fine: keyboard, mouse, network, charging, audio, USB. The extra screens remain blank, there is no OSD to pick the layout, and the screens don't appear in the KCM, only the laptop's. Moreover, when logging out, there might be a problem with SDDM or kwin (dmesg says kwin_wayland[31085]: segfault at 556790bdc740 ip 556790bdc740 sp 7ffeca4c4798 error 15) during shutdown, as the three screens are blank, and I can't switch to a VT (even with Sysrq+R). I need to REISUB my way out of this (S and U are logged to the screen in text mode, though). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398421] Wayland: pointer locking not released after application closed
https://bugs.kde.org/show_bug.cgi?id=398421 Mayeul Cantan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mayeul Cantan --- (In reply to Alexander Mentyu from comment #1) > Related closed bugs https://bugs.kde.org/show_bug.cgi?id=395815 > https://bugs.kde.org/show_bug.cgi?id=35 > > How did you launched Final DOOM in Linux? - says invalid platform for me and > no install/play button I played it (tried to) trough SteamPlay, though you need to enable it for every game in your library. Steam settings -> steamplay -> Enable for all titles. Try not to spend too much time playing around with this ;-) I put a screenshot of the setting there some time ago: https://askubuntu.com/a/1067783/483325 Note that it isn't specific to that game (I tested this one because I needed something light), I remember seeing something similar after playing VV, which was also grabbing the mouse for some reason. The issue here is really to release the pointer after a game quit, if it didn't do it itself. This indeed seems like a duplicate of Bug 35, which I didn't see while searching. Looks like the fix will only land in the next plasma release (fix landed in git the 26th of june, 5.13 was released on the 12th). Thanks for pointing this out. *** This bug has been marked as a duplicate of bug 35 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388885] Pointer does not unfreeze after closing an app that locks it
https://bugs.kde.org/show_bug.cgi?id=35 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr --- Comment #8 from Mayeul Cantan --- *** Bug 398421 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398618] New: Changing tabs with the scrollwheel scrolls as well
https://bugs.kde.org/show_bug.cgi?id=398618 Bug ID: 398618 Summary: Changing tabs with the scrollwheel scrolls as well Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- I like to switch tabs by hovering them with my mouse, then using the scrollwheel. In various systemsettings kcms, like power management or network options, that contain tabs as well as a scollable area beneath, doing so scrolls the view as well, which is annoying. Steps to reproduce: * open systemsettings5 * scroll to power management * ensure the window is small enough that the area becomes scrollable * switch tabs by hovering over them, and scrolling with the mousewheel: the page scrolls as well Expected behaviour: * the scrollwheel should switch tabs, but not scroll the content. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398619] New: Wrong subcategory selected in the sidebar after clearing search bar
https://bugs.kde.org/show_bug.cgi?id=398619 Bug ID: 398619 Summary: Wrong subcategory selected in the sidebar after clearing search bar Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: mayeul.can...@live.fr Target Milestone: --- * Open the systemsettings, make sure the window is large enough to display the subcategory sidebar * search an item that appears in a subcategory that is not the first one, like "cookies" * select the category so that the kcm is displayed * clear the search bar * the wrong subcategory is selected (it is always the first one, "Proxy" in my case) This makes it harder to discover the subcategory specific settings are in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376631] New: Kwin crash in fullscreen game
https://bugs.kde.org/show_bug.cgi?id=376631 Bug ID: 376631 Summary: Kwin crash in fullscreen game Product: kwin Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: kwin_x11 (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.8-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Playing payday2 fullscreen (this is the first time I have a kwin crash in game) - Unusual behavior I noticed: The game seemed to be slower than usual, a bit laggy in combat-heavy scenes, with a bit of what could be seen as network lag. It might be related to new DDR2 sticks I installed recently (4GB -> 8GB), though it might be related to kwin, given the crash. The game completely froze, so I switched to a virtual terminal, and noticed what seemed to be an unusual ram usage. WHen I went back, the game had crashed, and I had a kwin crash report prompt. I am not sure this will be useful, but the backtrace seems more or less clean. I can't tell if kwin or the game initiated the crash. Somewhat related: Interestingly, kickoff wouldn't show up when clicking on the icon just after the crash (while the other plasmoids are working fine). I solved it by using an alternative launcher and reverting. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd77cf02840 (LWP 1697))] Thread 7 (Thread 0x7fd743055700 (LWP 4526)): [KCrash Handler] #6 0x7fd77c8b404f in raise () at /usr/lib/libc.so.6 #7 0x7fd77c8b547a in abort () at /usr/lib/libc.so.6 #8 0x7fd779da0e21 in () at /usr/lib/libQt5Core.so.5 #9 0x7fd7605bb3e3 in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #10 0x7fd779fc10be in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #11 0x7fd779fcdd98 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7fd779fc1b63 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7fd77ac7734c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fd77ac7eb61 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7fd779f95440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7fd779fe8cbe in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #17 0x7fd779fe6bda in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7fd779f9389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7fd779db5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7fd779dba6d8 in () at /usr/lib/libQt5Core.so.5 #21 0x7fd775ba7454 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7fd77c9697df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fd742854700 (LWP 1848)): #0 0x7fd775bad10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd778f24234 in () at /usr/lib/libQt5Script.so.5 #2 0x7fd778f24279 in () at /usr/lib/libQt5Script.so.5 #3 0x7fd775ba7454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd77c9697df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd743b5b700 (LWP 1845)): #0 0x7fd775bad10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd74b63dc5b in () at /usr/lib/xorg/modules/dri/r600_dri.so #2 0x7fd74b63dab7 in () at /usr/lib/xorg/modules/dri/r600_dri.so #3 0x7fd775ba7454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd77c9697df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd759f79700 (LWP 1832)): #0 0x7fd77c960551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fd779fe52f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fd779fe696a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fd779f9389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd779db5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fd7748b6025 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fd779dba6d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7fd775ba7454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd77c9697df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd75bfff700 (LWP 1780)): #0 0x7fd77c960551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fd779fe52f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fd779fe696a in Q
[k3b] [Bug 384678] New: K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678
Bug ID: 384678
Summary: K3b fails reading cue files with title larger than 80
bytes
Product: k3b
Version: 17.08.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Image Formats
Assignee: k...@kde.org
Reporter: mayeul.can...@live.fr
CC: mich...@jabster.pl, tr...@kde.org
Target Milestone: ---
Hello there,
I was batch-converting some music files with k3b, ripped with cue files, and it
looks like k3b fails to parse the cue file if the TITLE section is larger than
80 bytes.
For now, I ran
`LANG=C sed -i 's/TITLE\s\+"\(.\{80\}\).\+"/TITLE "\1"/' *.cue`
on my files, but this is less than ideal.
Tested with k3b 17.08.1 on Arch linux (this version doesn't appear on the bug
tracker page).
k3b fails with:
(K3b::CueFileParser) unknown Cue line: ' "TITLE \"This is a title wider than 80
bytes**\"" '
What's nice is that the bug is EXTREMELY EASY to reproduce: just create a file
with the following line and a .cue extension.
TITLE "This is a title wider than 80
bytes*"
Remove a star, and you instead get:
(K3b::CueFileParser) successfully parsed cue file.
I would like to see the following happening:
- Support for titles longer than 80 bytes, with unicode if possible
- If too complicated, cut the title to 80 bytes and warn the user
- If this can't be implemented because of manpower constraints, at least
provide a decent error message.
I could try to do it myself, but I suspect that it will take no time to fix for
someone familiar with the codebase.
Thanks for maintaining k3b,
Mayeul
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #1 from Mayeul Cantan --- Created attachment 107841 --> https://bugs.kde.org/attachment.cgi?id=107841&action=edit Failing test file -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #2 from Mayeul Cantan --- Created attachment 107842 --> https://bugs.kde.org/attachment.cgi?id=107842&action=edit Passing cue file -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 Mayeul Cantan changed: What|Removed |Added Attachment #107841|text/plain |application/x-cue mime type|| Attachment #107841|Failing test file |Failing cue file description|| -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #3 from Mayeul Cantan --- Comment on attachment 107842 --> https://bugs.kde.org/attachment.cgi?id=107842 Passing cue file Note that this isn't a useful cue file, and k3b will still output an error, but not the same as the other file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378825] New: kwin crash in-game
https://bugs.kde.org/show_bug.cgi?id=378825 Bug ID: 378825 Summary: kwin crash in-game Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mayeul.can...@live.fr Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.9-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Playing the game PAYDAY 2 fullscreen, browsing websites with the steam overlay. - What happened: Everything was fine until I suddenly couldn't interact with the window anymore. I tried Alt-tabbing, switching virtual desktops, going to another tty (that one worked) and coming back. My graphics card's fan then suddenly went silent, the actions I tried to perform were executed as if they had been queued up, and I was presented with the bug report window. DrKonqi says that the backtrace is useful, so I figured it could be interesting to report the bug. I did not try to reproduce, as this happened after a long time, and without any obvious trigger. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff141ee7840 (LWP 1327))] Thread 6 (Thread 0x7ff1075d9700 (LWP 1458)): #0 0x7ff13ab8c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff13df03234 in () at /usr/lib/libQt5Script.so.5 #2 0x7ff13df03279 in () at /usr/lib/libQt5Script.so.5 #3 0x7ff13ab862e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7ff14194a54f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7ff10c80b700 (LWP 1437)): #0 0x7ff13ab8c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff114943b9b in () at /usr/lib/xorg/modules/dri/r600_dri.so #2 0x7ff1149438c7 in () at /usr/lib/xorg/modules/dri/r600_dri.so #3 0x7ff13ab862e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7ff14194a54f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7ff117b99700 (LWP 1429)): #0 0x7ff14194076b in ppoll () at /usr/lib/libc.so.6 #1 0x7ff13efc42f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7ff13efc596a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7ff13ef7289a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff13ed94a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7ff1398ad025 in () at /usr/lib/libQt5Qml.so.5 #6 0x7ff13ed996d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7ff13ab862e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff14194a54f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7ff12653d700 (LWP 1335)): #0 0x7ff14194076b in ppoll () at /usr/lib/libc.so.6 #1 0x7ff13efc42f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7ff13efc596a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7ff13ef7289a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff13ed94a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7ff138a57125 in () at /usr/lib/libQt5DBus.so.5 #6 0x7ff13ed996d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7ff13ab862e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff14194a54f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7ff12868d700 (LWP 1328)): #0 0x7ff14194067d in poll () at /usr/lib/libc.so.6 #1 0x7ff140a598e0 in () at /usr/lib/libxcb.so.1 #2 0x7ff140a5b679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7ff129769239 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7ff13ed996d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7ff13ab862e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff14194a54f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7ff141ee7840 (LWP 1327)): [KCrash Handler] #6 0x7ff13f4fb808 in QOpenGLContext::format() const () at /usr/lib/libQt5Gui.so.5 #7 0x7ff139f58c9b in QSGBatchRenderer::Renderer::Renderer(QSGDefaultRenderContext*) () at /usr/lib/libQt5Quick.so.5 #8 0x7ff139f84231 in QSGDefaultRenderContext::createRenderer() () at /usr/lib/libQt5Quick.so.5 #9 0x7ff139fdb088 in QQuickWindowPrivate::syncSceneGraph() () at /usr/lib/libQt5Quick.so.5 #10 0x7ff139f76b6f in () at /usr/lib/libQt5Quick.so.5 #11 0x7ff139f77b25 in () at /usr/lib/libQt5Quick.so.5 #12 0x7ff13f4cdd05 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5 #13 0x7ff139fe44a5 in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #14 0x7ff07
