[ksysguard] [Bug 418968] Network speed in bits per second
https://bugs.kde.org/show_bug.cgi?id=418968 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434999] Neon user edition does not boot on new Intel Tiger Lake laptop
https://bugs.kde.org/show_bug.cgi?id=434999 --- Comment #2 from Vishal Rao --- Just an update that I was using the Ventoy multi ISO boot tool which seems to be the root cause of the issue. If I write the neon ISO directly to USB stick it boots and progresses a bit, but since the current neon user ISO still is on older 5.4 kernel the boot hangs with some errors on screen. If the neon ISO is updated with latest ubuntu 20.04.2 bits (kernel 5.8 hardware enablement stack) I am sure it will work fine. Will report back with a newer neon ISO and close this ticket and contact the Ventoy tool developer to report the boot issue to them. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434999] Neon user edition does not boot on new Intel Tiger Lake laptop
https://bugs.kde.org/show_bug.cgi?id=434999 --- Comment #1 from Vishal Rao --- Created attachment 137096 --> https://bugs.kde.org/attachment.cgi?id=137096&action=edit lshw output from ubuntu 20.04.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434999] Neon user edition does not boot on new Intel Tiger Lake laptop
https://bugs.kde.org/show_bug.cgi?id=434999 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434999] New: Neon user edition does not boot on new Intel Tiger Lake laptop
https://bugs.kde.org/show_bug.cgi?id=434999 Bug ID: 434999 Summary: Neon user edition does not boot on new Intel Tiger Lake laptop Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: vishal...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 137095 --> https://bugs.kde.org/attachment.cgi?id=137095&action=edit dmesg output from ubuntu 20.04.2 Trying the latest Neon user ISO on a new HP Pavilion 14 laptop model dv0054tu with Intel Core i5 1135G7 CPU and Iris Xe iGPU - Tiger Lake platform - does not work - meaning it boots to blank screen - and unresponsive - after a few moments pressing the power key immediately shuts down the laptop indicating some sort of hang. FYI, the stock Ubuntu 20.04 with the 5.4 kernel boots into live session, the stock ubuntu 20.10 with kernel 5.8 boots and everything appears to work well. Tried the new ubuntu 20.04.2 release which has kernel 5.8 and it works well. This current Neon user ISO has the latest HWE kernel 5.8 yet it does not boot. I have tried some kernel boot parameters like nomodeset along with i915.modeset=0 but those didn't work. I am unable to switch to TTY or anything to look at any logs etc. even if I remove the "quiet splash" options there is just blank screen. Any suggestions to troubleshoot/fix this issue? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418311] Firefox never becomes default browser
https://bugs.kde.org/show_bug.cgi?id=418311 --- Comment #1 from Vishal Rao --- I should mention I have the Plasma browser integration plugin installed. Was not sure which component to file this bug against so went with neon. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418311] New: Firefox never becomes default browser
https://bugs.kde.org/show_bug.cgi?id=418311 Bug ID: 418311 Summary: Firefox never becomes default browser Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: vishal...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Unable to set Firefox as the default browser. On next run of Firefox it again prompts to set it as default. In Firefox preferences also unable to set browser as default. This is on Neon User edition with Plasma version 5.18.2 fully updated. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418311] Firefox never becomes default browser
https://bugs.kde.org/show_bug.cgi?id=418311 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381893] Add .VolumeIcon.png neon logo to root of install image
https://bugs.kde.org/show_bug.cgi?id=381893 --- Comment #2 from Vishal Rao --- Should the filename be `.VolumeIcon.png` or `.VolumeIcon` or can it be either? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381893] Add .VolumeIcon.png neon logo to root of install image
https://bugs.kde.org/show_bug.cgi?id=381893 --- Comment #1 from Vishal Rao --- Here is an example of some code I proposed in the experimental elementary OS pantheon installer: https://github.com/elementary/pantheon-installer/pull/41 It gives some polish to KDE neon branding while other third party installers (and maybe bootloaders) are being used :-) What are your thoughts? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381893] New: Add .VolumeIcon.png neon logo to root of install image
https://bugs.kde.org/show_bug.cgi?id=381893 Bug ID: 381893 Summary: Add .VolumeIcon.png neon logo to root of install image Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: vishal...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- This is a request to include the neon logo as a .VolumeIcon.png file in the root of the installed image so that when running other installers they can pick up the OS logo during multiboot configuration. Perhaps this one https://packaging.neon.kde.org/neon/settings.git/plain/usr/share/pixmaps/neon.png See https://github.com/elementary/pantheon-installer/issues/39 for some context. Also, see https://github.com/dab2000/rEFInd-custom/blob/master/refind/lib.c#L958 and https://github.com/dab2000/rEFInd-custom/blob/master/libeg/image.c#L366 as an example of what is being sought after. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381893] Add .VolumeIcon.png neon logo to root of install image
https://bugs.kde.org/show_bug.cgi?id=381893 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 376829] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=376829 --- Comment #1 from Vishal Rao --- Well, duh, seems to fixed already with updates coming in a few minutes ago. Really should have patience when running the dev unstable edition :-) -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 376829] New: Crash on startup
https://bugs.kde.org/show_bug.cgi?id=376829 Bug ID: 376829 Summary: Crash on startup Product: kamoso Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: aleix...@gmail.com Reporter: vishal...@gmail.com Target Milestone: --- Running neon dev unstable edition (git master) and running kamoso from commandline (I have kamoso-dbgsym installed too) results in the following output: Playing device changed "/dev/video0" Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") new gamma 105 new gamma 106 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Slider.qml:204:5: QML RangeModel: Binding loop detected for property "value" New saturation 100 New contrast 100 terminate called after throwing an instance of 'QGlib::Error' what(): no property "video-direction" in element "videoflip0" Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 376829] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=376829 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 358045] Kdialog display nothing with --progressbar
https://bugs.kde.org/show_bug.cgi?id=358045 --- Comment #5 from Vishal Rao --- OK it looks like the fork() call is causing dbus to not work. If I comment out the fork portion and also add KDBusService as attempted by Christoph the dialog becomes visible and is operable by qdbus commands. But it does not hide or go into background of course, so some other approach is needed than fork. I also came across another project bug which might imply fork() is not safe with QDBus code: https://github.com/mumble-voip/mumble/issues/2820 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 358045] Kdialog display nothing with --progressbar
https://bugs.kde.org/show_bug.cgi?id=358045 --- Comment #4 from Vishal Rao --- Using KDE Neon dev unstable edition here and kdialog progressbar does not seem to be visible to qdbus. I tried to look and fix the code but can't get it even visible to qdbus. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 358045] Kdialog display nothing with --progressbar
https://bugs.kde.org/show_bug.cgi?id=358045 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #22 from Vishal Rao --- Just FYI, got this version: 2.2.1+p16.04+git20161026.1000-0 in Neon dev unstable update just now and it seems to be working okay. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #17 from Vishal Rao --- Just an update that while the issue occurs on my updated Neon dev unstable edition, it does not occur on a freshly installed neon user edition 5.8.2 at this time. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #16 from Vishal Rao --- I have built dummy backend also as part of kpmcore and noted both the default partitionmanager binary and my built one both try to load the backends from /usr/lib/x86.../qt5/plugins folder, so I tried replacing the original with my built ones and only the default partitionmanager binary from /usr/bin crashed and not my built one. One other difference I see is that when I run the default /usr/bin/partitionmanager it seems to trigger KDE-SU UI while my binary triggers/picks up gksudo... see different console output below during early run: vishal@skybird:/usr/bin$ ./partitionmanager org.kde.kdesu: Daemon not safe (not sgid), not using it. vishal@skybird:~/SRC/partitionmanager-2.2.1+p16.04+git20160920.0957/build/src$ ./partitionmanager (gksudo:2327): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (gksudo:2327): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #13 from Vishal Rao --- I should mention if I run my local build of partitionmanager/kpmcore it does not crash, not sure if it's because I made a debug build. But when I run the one that came installed in /usr/bin I get the previously posted stacktrace crash during startup. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #12 from Vishal Rao --- While trying to install source and building/debugging (not much success here, newbie) I noticed my stacktrace now has Device::setIconName() call as follows. doing a quick grep, it looks like only the dummy backend is calling setIconName in its scanDevice() method, unless, of course, I'm making some mistake: Thread 1 (Thread 0x7fb4f85eb940 (LWP 5843)): [KCrash Handler] #4 0x7fb4f4d5e37c in QString::operator=(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb4f80fc337 in Device::setIconName (this=0x7fb4d4060950, name=...) at /home/vishal/SRC/kpmcore-2.2.1+p16.04+git20161011.0712/src/core/device.h:92 #6 0x0044e8a9 in ListDeviceWidgetItem::ListDeviceWidgetItem (d=..., this=0xab6cc0) at /workspace/build/src/gui/listdevices.cpp:32 #7 ListDevices::updateDevices (this=0x7eef20, devices=...) at /workspace/build/src/gui/listdevices.cpp:57 #8 0x0045294a in MainWindow::on_m_OperationStack_devicesChanged (this=0x7d5820) at /workspace/build/src/gui/mainwindow.cpp:623 #9 0x00484885 in MainWindow::qt_metacall (this=0x7d5820, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x7fb4d402c2c0) at /workspace/build/obj-x86_64-linux-gnu/src/moc_mainwindow.cpp:197 #10 0x7fb4f4edba19 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #11 from Vishal Rao --- In the original reporter's (and mine) stacktrace it seems to indicate operator= for QString when it's trying to read/set Device::deviceNode() so something about scanning an m.2 device (mine is NVMe) while Ben's could be m.2 "SATA" based. Anything we (or I could do) to run/capture more debugging info? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #4 from Vishal Rao --- Correction to my previous comment "was trying to format the pen drive when came across this issue" - I didn't write correct - I meant to say I also faced this issue during startup of partition manager, when it scans the devices, it lists my devices and not sure if this is important but when it reaches my /dev/nvme0n1 is when the crash happens. Any system info I can provide? What commands to run and post output that would help? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #5 from Vishal Rao --- Output of running "sudo fdisk -l" minus the snipped sections of /dev/ramX items: https://paste.kde.org/p1fbzr2po -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 --- Comment #3 from Vishal Rao --- I faced the same issue. I have Neon 5.8 dev unstable edition, same backtrace as original reporter's. I have a SATA SSD, an NVMe m.2 SSD, an HDD, an external USB HDD, and a USB pen drive plugged in, was trying to format the pen drive when came across this issue. Attaching output of my lsblk command, let me know if anything further required. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 370384] KDE Partition Manager crashes while starting up
https://bugs.kde.org/show_bug.cgi?id=370384 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com --- Comment #2 from Vishal Rao --- Created attachment 101641 --> https://bugs.kde.org/attachment.cgi?id=101641&action=edit output of lsblk command -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Vishal Rao changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=358839 --- Comment #1 from Vishal Rao --- Added bug # 358839 to the "see also" field, that looks like a more effort wishlist. This bug is intended to ask for getting things started for ability to add/customise splash qmls. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] New: KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Bug ID: 369592 Summary: KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML Product: ksplash Version: 5.7.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: vishal...@gmail.com I wanted to edit the default ksplashqml theme to include a background image. Adding the image was easy enough to the existing Splash.qml in /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash but of course whenever there's is an update it gets overwritten to the default again. So I tried copying just the splash folder contents to vishal@skybird:~/.local/share/plasma/look-and-feel/org.kde.vishal.desktop/contents/splash and also modified the metadata.desktop file (to name it org.kde.vishal.desktop to avoid clashing with breeze) and while that seems to work for the splash screen theme, but it also creates a new item under "look and feel" settings. I guess this bug report might be a wishlist to move the theme config load/save away from the overall "look and feel" package/KCM config group so that it's easy for people to create new QML splash themes and configure it in the Splash Screen KCM separate from the selected (default Breeze) Look and Feel options. Looking around the code I couldn't figure out where the "splashmainscript" string literal is being used (loaded/saved) but I guess the code in ksplash QML and KCM portions would need to be updated: https://github.com/KDE/plasma-workspace/blob/master/ksplash/ksplashqml/splashwindow.cpp#L117 https://github.com/KDE/plasma-desktop/blob/master/kcms/ksplash/kcm.cpp#L108 Searching the code for "splashmainscript" found these other places: https://github.com/KDE/plasma-desktop/blob/master/kcms/lookandfeel/kcm.cpp#L194 https://github.com/KDE/plasma-framework/blob/master/src/plasmaquick/private/packages.cpp#L71 https://github.com/KDE/plasma-workspace/blob/master/shell/packageplugins/lookandfeel/lookandfeel.cpp#L71 Although I'm reporting this for 5.7.95 I guess this is too late for the LTS and I hope this might be addressed for 5.9 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 --- Comment #34 from Vishal Rao --- Appears to be working for me too now. Thank you! Note on some reboots it still shows "stop job running" but completes at about 7 seconds duration when I set the /etc/systemd/system.conf interval settings to 30 seconds. And on some reboots it's so fast I don't even get to press ESC during the plymouth shutdown animation to see the console output :-) Could anyone post a link to the commit or change that works around or fixes this issue, just for the curious? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368942] New: Splash screen spinner should disappear instead of pause when fading into desktop
https://bugs.kde.org/show_bug.cgi?id=368942 Bug ID: 368942 Summary: Splash screen spinner should disappear instead of pause when fading into desktop Product: Breeze Version: 5.7.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: vishal...@gmail.com While the KDE Plasma 5.8 LTS Beta splash screen (after login but before desktop appears) is has a very slick spinner animation it should hide or disappear or change to full circle (maybe) instead of pausing in place while fading out into the desktop. Reproducible: Always Steps to Reproduce: 1. Login to your KDE Plasma 5.8 LTS Beta desktop. 2. Watch the splash screen animation. Actual Results: The pretty looking spinner smooth animation pauses midway while the splash screen fades out and the desktop fades in. Expected Results: Spinner animation should probably hide or disappear or maybe show some full circle or check tick mark to indicate it's completed. Running KDE Neon Developer Unstable edition with Plasma 5.8 LTS Beta fully updated as of 2016-09-17 date. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368941] New: Login screen password field is not auto selected when returning from Different Users list
https://bugs.kde.org/show_bug.cgi?id=368941 Bug ID: 368941 Summary: Login screen password field is not auto selected when returning from Different Users list Product: Breeze Version: 5.7.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: vishal...@gmail.com In the KDE Plasma 5.8 LTS Beta (running Neon Dev Unstable edition) default login screen if you click the "Different Users" icon and after that screen slides in if you just click Back icon to go back to the user login then the password entry field is not auto selected which I think should be for fit-and-finish polishing. Not an important/urgent issue of course! Reproducible: Always Steps to Reproduce: 1. Boot into KDE 5.8 LTS Beta until login screen appears. 2. Click the "Different Users" icon and let the other user login screen slide in. 3. Click the icon to go back (Back/Users) to the main default user login screen. Actual Results: Password entry field is not automatically selected for entry the way it is when first boot to login screen. Expected Results: Password entry field should be selected automatically when returning to the default user login screen. Running KDE Neon Developer Unstable edition updated as of 2016-09-17 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 357704] Muon notifier crashes on apt package list updates
https://bugs.kde.org/show_bug.cgi?id=357704 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com --- Comment #2 from Vishal Rao --- *** Bug 357791 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357791] Backtrace from MuonApplicationNotifier.so
https://bugs.kde.org/show_bug.cgi?id=357791 Vishal Rao changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Vishal Rao --- Marking as dup... *** This bug has been marked as a duplicate of bug 357704 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357791] Backtrace from MuonApplicationNotifier.so
https://bugs.kde.org/show_bug.cgi?id=357791 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357791] New: Backtrace from MuonApplicationNotifier.so
https://bugs.kde.org/show_bug.cgi?id=357791 Bug ID: 357791 Summary: Backtrace from MuonApplicationNotifier.so Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vishal...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.3.0-5-generic x86_64 Distribution: Ubuntu Xenial Xerus (development branch) -- Information about the crash: - What I was doing when the application crashed: I believe whenever I run "sudo apt-get update" in konsole it triggers the crash handler window popup. I am running Kubuntu 16.04 current (pre-alpha) with the Kubuntu Xenial Landing PPA enabled for Plasma 5.5.3 and friends. One of the lines in the backtrace is: #8 0x7fa63428e4a9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover-notifier/MuonApplicationNotifier.so When I went to install the debug symbols via the crash handler window it messaged that "Symbols not available for MuonApplicationNotifier.so" but it did install symbols for qt5base and plasma-desktop FYI. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6f9f108c0 (LWP 7369))] Thread 7 (Thread 0x7fa6e524d700 (LWP 7372)): #0 0x7fa6f460f83d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa6f86d9c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa6f86db8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa6e73964a9 in QXcbEventReader::run (this=0x17e3680) at qxcbconnection.cpp:1229 #4 0x7fa6f4d0587e in QThreadPrivate::start (arg=0x17e3680) at thread/qthread_unix.cpp:331 #5 0x7fa6f3df166a in start_thread (arg=0x7fa6e524d700) at pthread_create.c:333 #6 0x7fa6f461ae4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fa6de8fd700 (LWP 7374)): #0 0x7fa6f460f83d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa6f13a430c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6f13a441c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6f4f3d2eb in QEventDispatcherGlib::processEvents (this=0x7fa6d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa6f4ee42fa in QEventLoop::exec (this=this@entry=0x7fa6de8fcce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa6f4d008d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa6f75abc85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa6f4d0587e in QThreadPrivate::start (arg=0x18a9540) at thread/qthread_unix.cpp:331 #8 0x7fa6f3df166a in start_thread (arg=0x7fa6de8fd700) at pthread_create.c:333 #9 0x7fa6f461ae4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fa6cfb63700 (LWP 7375)): #0 0x7fa6f460f83d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa6f13a430c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6f13a441c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6f4f3d2eb in QEventDispatcherGlib::processEvents (this=0x7fa6c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa6f4ee42fa in QEventLoop::exec (this=this@entry=0x7fa6cfb62ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa6f4d008d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa6f75abc85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa6f4d0587e in QThreadPrivate::start (arg=0x1ae9770) at thread/qthread_unix.cpp:331 #8 0x7fa6f3df166a in start_thread (arg=0x7fa6cfb63700) at pthread_create.c:333 #9 0x7fa6f461ae4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fa6cdcb1700 (LWP 7376)): #0 0x7fa6f460f83d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa6f13a430c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6f13a441c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6f4f3d2eb in QEventDispatcherGlib::processEvents (this=0x7fa6c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fa6f4ee42fa in QEventLoop::exec (this=this@entry=0x7fa6cdcb0ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa6f4d008d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fa6f75abc85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa6f4d0587e in QThreadPrivate::start (arg=0x1c00b30) at thread
