[plasmashell] [Bug 493195] Automatically clone panel when connecting a new display
https://bugs.kde.org/show_bug.cgi?id=493195 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486514] Notifications are too narrow on X11 with dual-screen setup and NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=486514 --- Comment #14 from Fabio C. Barrionuevo --- I created a new user with Administrator role, but no notification was displayed in the new user, so I could not verify if the error also occurs in the new user. That said, the error apparently was fixed somehow in one of the last major updates of KDE Neon, as the error no longer occurs in the user I was seeing the error in. This is the version I actually have: Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS PRO WIFI System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486514] Notifications are too narrow on X11 with dual-screen setup and NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=486514 Fabio C. Barrionuevo changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #12 from Fabio C. Barrionuevo --- I still have this issue with the version: Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.5.0-45-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS PRO WIFI System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 482036] root apps not launching via desktop menu in plasma 6
https://bugs.kde.org/show_bug.cgi?id=482036 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com Version|6.0.0 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483701] unable to launch Software Sources - root password never accepted
https://bugs.kde.org/show_bug.cgi?id=483701 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486514] Notifications are too narrow
https://bugs.kde.org/show_bug.cgi?id=486514 --- Comment #8 from Fabio C. Barrionuevo --- Created attachment 169547 --> https://bugs.kde.org/attachment.cgi?id=169547&action=edit nvidia control panel configurations (In reply to Nate Graham from comment #6) > Also have you used the NVIDIA control panel to change any screen > settings? No. I left everything as it was in the default configuration on Nvidia control panel. I have attached the screenshot of the NVidia control panel as well -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486514] Notifications are too narrow
https://bugs.kde.org/show_bug.cgi?id=486514 --- Comment #7 from Fabio C. Barrionuevo --- Created attachment 169546 --> https://bugs.kde.org/attachment.cgi?id=169546&action=edit System Settings > Display & Monitor page (In reply to Nate Graham from comment #6) > Do you have multiple screens, or did you in the past? Yes, I use 2 screens, both connected using individual DisplayPort cables, connected to an Nvidia RTX 4060 Ti. > If so can you attach a screenshot of the System Settings > Display & Monitor > page that shows the > layout? Attached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486514] Discover available update notification window is shown in insufficient size for the content.
https://bugs.kde.org/show_bug.cgi?id=486514 --- Comment #5 from Fabio C. Barrionuevo --- Created attachment 169405 --> https://bugs.kde.org/attachment.cgi?id=169405&action=edit Notification window expands vertically instead of maintaining a default minimum horizontal size for the monitor resolution An update: the file copy progress notification also appears smaller, although it doesn't cut any text, the notification popup is stretched vertically, now I don't know if it's a bug or a feature. Notification window expands vertically instead of maintaining a default minimum horizontal size for the monitor resolution -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486514] Discover available update notification window is shown in insufficient size for the content.
https://bugs.kde.org/show_bug.cgi?id=486514 --- Comment #2 from Fabio C. Barrionuevo --- (In reply to Nate Graham from comment #1) > Ew, this would be a bug with the code for the notifications themselves. > > Some questions to help us narrow it down: > 1. Do you observe it happening with any other notifications from other apps? No. I can't remember any other notification type with the same problem. Furthermore, the only notifications I remember seeing frequently are from Spectacle when I take a screenshot, and they have no issues. > 2. Can you make it happen with any permutations of running `notify-send` > with various options? I tried and was unable to reproduce the issue using notify-send . > 3. Does it happen in the Wayland session too, or only on X11? Currently, I only use X11 since Google Chrome has erratic behavior on Wayland, and my daily work doesn't give me time to have the patience to wait for it to stabilize. I tried to reproduce the problem in Wayland by simply logging out of the X11 session and logging into the Wayland session. However, the notification no longer appears, probably because the action that launches it has already been executed and/or has been marked as read (if such a thing exists). Since the notification only appears when I have cold-booted the computer and there is some new update to install, over the next few days, I will first try starting the computer in a Wayland session to see if the problem also occurs on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486514] New: Discover available update notification window is shown in insufficient size for the content.
https://bugs.kde.org/show_bug.cgi?id=486514 Bug ID: 486514 Summary: Discover available update notification window is shown in insufficient size for the content. Classification: Applications Product: Discover Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: bna...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 169150 --> https://bugs.kde.org/attachment.cgi?id=169150&action=edit Discover available update notification window *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Discover available update notification window is shown in insufficient size for the content. STEPS TO REPRODUCE 1. Start KDE Neon OS 2. If an update is available, the Discover notification will be displayed at the top of the screen. OBSERVED RESULT The notification window displayed at the top of the screen is smaller than the content to be shown, that is, it does not show all the content and cuts off the text. Check the attached image. EXPECTED RESULT The notification window must be displayed at the top of the screen as usual and be rendered at the correct size for the content to be displayed, as was the previous behavior we had in the last version of Plasma 5.x.x SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS PRO WIFI System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]
https://bugs.kde.org/show_bug.cgi?id=481308 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414805] On X11, crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()
https://bugs.kde.org/show_bug.cgi?id=414805 --- Comment #60 from Fabio C. Barrionuevo --- I use KDE Neon and preferably use X11 sessions. I did the update process for Plasma 6 via "sudo pkcon refresh && sudo pkcon update -v ; flatpak update -y" and then restarted. I don't know if this is a new bug, however when putting KDE Neon into sleep mode and waking it up, instead of seeing the login screen I only see the mouse arrow on a 100% black screen on all monitors. The login screen does not return even after waiting a few minutes and then I am forced to open a terminal session (CRTL + ALT + F4) and perform a manual restart, which involves having to manually kill all instances of Google Chrome (so as not to lose my open tabs) and only then perform reboot. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480179] KDE Connect Daemon crashes after update to Frameworks 5.114.0
https://bugs.kde.org/show_bug.cgi?id=480179 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[discuss.kde.org] [Bug 472717] New: Change the subject prefix of emails to [KDE Discuss] on Discourse configuration
https://bugs.kde.org/show_bug.cgi?id=472717 Bug ID: 472717 Summary: Change the subject prefix of emails to [KDE Discuss] on Discourse configuration Classification: Websites Product: discuss.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: forum-ad...@kde.org Reporter: bna...@gmail.com CC: kde-...@kde.org Target Milestone: --- SUMMARY I guess it would be good to rename the email format of the "FROM" field to "KDE Discuss " and the subject prefix to "[KDE Discuss]" in order to be able to quickly identify in the email inbox which emails are from this KDE forum and which are from others. I participate in a few other forums that use Discourse, and they all use the same setup, which makes it a little tricky to tell them apart quickly without actually opening the email. I guess this change would not be so complicated to make. 1 - It currently shows like this in Gmail: https://discuss-cdn.kde.org/uploads/default/original/2X/9/9a3c9976600e2b4ae8eec6aa1f04f19172a66efd.png My suggestion is to configure discourse in order to show like this: https://discuss-cdn.kde.org/uploads/default/original/2X/c/ced3a78fa1c13e03aaf5c41d180983dca1772e51.png 2 - Same for the "From" field in the email body. This is what we currently have: https://discuss-cdn.kde.org/uploads/default/original/2X/1/1bd19df87b1ad59e2b277a9f472780bc9df68ece.png This is what it should look like in the email raw body after configuration in the discourse: https://discuss-cdn.kde.org/uploads/default/original/2X/1/1b2b0127c6ea459a6040cba870fafca5018ef3ad.png --- You can read the same message on https://discuss.kde.org/t/initial-feedback-on-forum/34/14 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 472159] New: Partition Manager does not disable suspension (sleep) mode while executing a task, which can cause data loss
https://bugs.kde.org/show_bug.cgi?id=472159 Bug ID: 472159 Summary: Partition Manager does not disable suspension (sleep) mode while executing a task, which can cause data loss Classification: Applications Product: partitionmanager Version: 23.04.3 Platform: Neon OS: Other Status: REPORTED Severity: major Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: bna...@gmail.com Target Milestone: --- SUMMARY Hello, I started KDE Neon via USB to perform NTFS partition resizing via PartitionManager. The resizing process would take over 1 hour so I left to do something else and when I came back I realized the computer was off. The problem was that by default, KDE Neon was set to go into suspension (sleep) mode after 15 minutes of no interaction. PartitionManager should be able to temporarily disable any setting that causes the computer to go into suspension, hibernation, or low power mode while some task is being performed. I guess entering suspension (sleep) mode while performing a task on a partition can cause data loss in some cases STEPS TO REPRODUCE 1. Start KDE Neon Live USB 2. Start the PartitionManager and start performing a very long-time task 3. Do not interact with the system for at least 15 minutes and after that the OS will go into suspension mode OBSERVED RESULT Even with Partition Manager performing the long task of moving a partition, the OS may still go into suspension mode. EXPECTED RESULT While Partition Manager is executing any task, the OS should NEVER go into suspension, hibernation or low power mode SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User Edition 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466862] Cannot pkcon update due to unmet dependencies with poppler and okular-backends
https://bugs.kde.org/show_bug.cgi?id=466862 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com --- Comment #21 from Fabio C. Barrionuevo --- Hello, Jonathan Riddell yesterday I managed to solve most of my problems by uninstalling several 32bit packages (related to wine and lutris and some installed by Steam) and then running again the sudo pkcon update https://gist.github.com/luzfcb/5c323433b980d79aa1597f9bd32a0b2f Today pkcon informs me that support for HP printers and other applications will be removed so that it will be possible to downgrade some libraries The fact is: I'm afraid if I run this, it will break even more, and I'll have another round of crashing packets. Since this machine is also the machine I use for work, I was wondering whether or not this downgrade is expected to occur and if i can go ahead and update ❯ sudo pkcon update Getting updates [=] Finished [=] Testing changes [=] Finished [ ] (0%) The following packages have to be removed: flowblade-2.8.0.3-3.allnon-linear video editor hplip-3.21.12+dfsg0-1.amd64HP Linux Printing and Imaging System (HPLIP) libharfbuzz-subset0-6.0.0+dfsg-3+22.04+jammy+release+build1.amd64 OpenType text shaping engine (subset library) libraqm-dev-0.10.0-0xneon+22.04+jammy+release+build13.amd64Development files for Raqm library libraqm0-0.10.0-0xneon+22.04+jammy+release+build13.amd64 Library for complex text layout lutris-0.5.11.all video game preservation platform python3-matplotlib-3.5.1-2build1.amd64 Python based plotting system in a style similar to Matlab (Python 3) python3-pil-9.0.1-1ubuntu0.1.amd64 Python Imaging Library (Python3) python3-pil.imagetk-9.0.1-1ubuntu0.1.amd64 Python Imaging Library - ImageTk Module (Python3) python3-reportlab-3.6.8-1.all ReportLab library to create PDF documents using Python3 The following packages have to be downgraded: gir1.2-harfbuzz-0.0-2.7.4-1ubuntu3.1.amd64 OpenType text shaping engine (GObject introspection data) libharfbuzz-dev-2.7.4-1ubuntu3.1.amd64 Development files for OpenType text shaping engine libharfbuzz-gobject0-2.7.4-1ubuntu3.1.amd64OpenType text shaping engine ICU backend (GObject library) libharfbuzz-icu0-2.7.4-1ubuntu3.1.amd64OpenType text shaping engine ICU backend libharfbuzz0b-2.7.4-1ubuntu3.1.amd64 OpenType text shaping engine (shared library) Proceed with changes? [N/y] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Fabio C. Barrionuevo changed: What|Removed |Added Platform|Archlinux |Neon Version|5.23.3 |5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com --- Comment #10 from Fabio C. Barrionuevo --- This would be very helpful. Better than that, just something that works totally out of the box on multiple monitors like the panel provided by tint2. tint2 is not as powerful and customizable as plasma panels, but at least it works well with multiple screens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445362] Every time on boot with two monitors, Plasma crashes in ContainmentInterface::adjustToAvailableScreenRegion()
https://bugs.kde.org/show_bug.cgi?id=445362 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com --- Comment #2 from Fabio C. Barrionuevo --- Brier and Nate, I have a similar (or the same) error. Can you reproduce the error if you perform the steps I describe in https://bugs.kde.org/show_bug.cgi?id=451276#c1 ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451276] Plasma crashes if put into suspension mode with monitors ON and then being woken up from suspension with the monitors OFF
https://bugs.kde.org/show_bug.cgi?id=451276 --- Comment #1 from Fabio C. Barrionuevo --- How to reproduce the issue: On a computer with at least one monitor connected that can be turned off and turned on independently of the computer: 1 - put the computer in suspension mode 2 - turn off the monitor's power using the on/off button or by removing it entirely from its power supply (disconnect the power cable) 3 - turn on the computer 4 - turn on the monitor by using the on/off button or connect the power cable 5 - authenticate on Plasma 6 - try to interact with the menus on the panel Usually, this error is generated almost immediately in step 6 Note: In my case, I have two external monitors connected on the computer using two DisplayPort of my Nvidia GTX 1650 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451276] New: Plasma crashes if put into suspension mode with monitors ON and then being woken up from suspension with the monitors OFF
https://bugs.kde.org/show_bug.cgi?id=451276 Bug ID: 451276 Summary: Plasma crashes if put into suspension mode with monitors ON and then being woken up from suspension with the monitors OFF Product: plasmashell Version: 5.24.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bna...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.2) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-30-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I have two monitors individually connected to my Nvidia GTX 1650 via DisplayPort on my Desktop PC (Ryzen 9 3900X + Gigabyte X570 Aorus Pro Wifi Motherboard + 32GB RAM + SSD NVMe). Every day when I finish my work day, I put the computer in suspension mode and after that I turn off both monitors by pressing the On/Off button that each monitor has. When starting a new workday, I first press the power button on the computer (or press some key on the keyboard), and then the computer wakes up. After that I turn on the two monitors. After the login process, Plasma may or may not work normally for a few minutes. It usually fails after I interact with some button on the panel. I have been reporting similar errors over the past 2 years. While my knowledge of C++ and QT is less than what I need to be able to resolve the bug myself, I wish I could help more and maybe learn enough to be able to maybe help generate better bug reports. If there's anything else I can do to make myself more useful, then let me know. Help me help. Thanks for all the hard work. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 2635] [New LWP 2655] [New LWP 2803] [New LWP 2821] [New LWP 2824] [New LWP 2825] [New LWP 2826] [New LWP 2981] [New LWP 3037] [New LWP 3046] [New LWP 3055] [New LWP 5313] [New LWP 106771] [New LWP 106840] [New LWP 106884] [New LWP 107180] [New LWP 984427] [New LWP 985970] [New LWP 985971] [New LWP 985972] [New LWP 985973] [New LWP 985974] [New LWP 985975] [New LWP 985976] [New LWP 985977] [New LWP 985978] [New LWP 985979] [New LWP 985980] [New LWP 985981] [New LWP 985982] [New LWP 985983] [New LWP 985984] [New LWP 985985] [New LWP 985986] [New LWP 985987] [New LWP 985988] [New LWP 985989] [New LWP 985990] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fa547bda9cf in __GI___poll (fds=0x7fff923bf1b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fa543d2d4c0 (LWP 2626))] Thread 39 (Thread 0x7fa47bfff700 (LWP 985990)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fa47bffeb50, clockid=, expected=0, futex_word=0x55b7d16168b4) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fa47bffeb50, clockid=, mutex=0x55b7d1616860, cond=0x55b7d1616888) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55b7d1616888, mutex=0x55b7d1616860, abstime=0x7fa47bffeb50) at pthread_cond_wait.c:656 #3 0x7fa547f70668 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x55b7d1616860, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55b7d1616860) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x55b7d5348630, mutex=mutex@entry=0x55b7cfcd18c8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fa547f6db71 in QThreadPoolThread::run() (this=0x55b7d5348620) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7fa547f6a543 in QThreadPrivate::start(void*) (arg=0x55b7d5348620) at thread/qthread_unix.cpp:331 #8 0x7fa547a4d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fa547be7163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 38 (Thread 0x7fa473fff700 (LWP 985989)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fa473ffeb50, clockid=, expected=0, futex_word=0x55b7d519fba0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fa473ffeb50, clockid=, mutex=0x55b7d519fb50, cond=0x55b7d519fb78) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55b7d519fb78, mutex=0x55b7d519fb50, abstime=0x7fa473ffeb50) at pthread_cond_wait.c:656 #3 0x7fa547f70668 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x55b7d519fb50, deadline=...) at thread/qwaitcondition_unix.cpp:136
[plasmashell] [Bug 449845] Plasma or other desktop plasma software fails to wake up from suspencion mode with two monitors connected to individual displayport outputs
https://bugs.kde.org/show_bug.cgi?id=449845 --- Comment #1 from Fabio C. Barrionuevo --- Created attachment 146488 --> https://bugs.kde.org/attachment.cgi?id=146488&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449845] New: Plasma or other desktop plasma software fails to wake up from suspencion mode with two monitors connected to individual displayport outputs
https://bugs.kde.org/show_bug.cgi?id=449845 Bug ID: 449845 Summary: Plasma or other desktop plasma software fails to wake up from suspencion mode with two monitors connected to individual displayport outputs Product: plasmashell Version: 5.24.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bna...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.24.0) Qt Version: 5.15.3 Frameworks Version: 5.90.0 Operating System: Linux 5.13.0-28-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.0 [KCrashBackend] -- Information about the crash: I repeatedly see this same error (or very similar error) for at least 1 year and a half. I've reported it at least 4 times. I would like to learn enough to help debug and resolve this error, however, my knowledge of C++ and QT is insufficient at this time. My KDE Neon now has the latest version of Plasma Desktop and KDE Framework and the bug keeps repeating. It's a little frustrating that I can't do anything else to be able to help in any way. Is there any documentation somewhere that teaches how to interpret the traceback captured by drkonqi? I can easily do this for Python tracebacks, but C++ + QT tracebacks is still a mystery to me. Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 The crash can be reproduced every time. -- Backtrace (Reduced): #4 QScreen::geometry() const (this=0x0) at kernel/qscreen.cpp:413 #5 0x55c2e81824e8 in PanelView::updateEnabledBorders() (this=this@entry=0x55c2ea3d3c40) at /usr/include/c++/9/bits/atomic_base.h:413 #6 0x55c2e818682b in PanelView::resizeEvent(QResizeEvent*) (this=0x55c2ea3d3c40, ev=0x7ffe514a5720) at ./shell/panelview.cpp:786 #7 0x7f2d59c03e0d in QWindow::event(QEvent*) (this=this@entry=0x55c2ea3d3c40, ev=ev@entry=0x7ffe514a5720) at kernel/qwindow.cpp:2438 #8 0x7f2d5b30a24b in QQuickWindow::event(QEvent*) (this=this@entry=0x55c2ea3d3c40, e=e@entry=0x7ffe514a5720) at items/qquickwindow.cpp:1901 Possible duplicates by query: bug 445362, bug 421895, bug 421611, bug 415240, bug 373461. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 446925] drkonqi does not persist authentication credentials even if save option is checked.
https://bugs.kde.org/show_bug.cgi?id=446925 --- Comment #6 from Fabio C. Barrionuevo --- (In reply to Harald Sitter from comment #2) > Does your password contain any special characters other than: > > % > & > > > , > > I cannot reproduce the issue, new login data is correctly stored in the > wallet and (incorrect) existing data is correctly updated. Not quite sure > what to do here. my password only contains lowercase ASCII characters and numbers -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 446925] drkonqi does not persist authentication credentials even if save option is checked.
https://bugs.kde.org/show_bug.cgi?id=446925 --- Comment #5 from Fabio C. Barrionuevo --- Created attachment 144606 --> https://bugs.kde.org/attachment.cgi?id=144606&action=edit application connected to kwallet the application connected to kwallet -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 446925] drkonqi does not persist authentication credentials even if save option is checked.
https://bugs.kde.org/show_bug.cgi?id=446925 --- Comment #4 from Fabio C. Barrionuevo --- Created attachment 144605 --> https://bugs.kde.org/attachment.cgi?id=144605&action=edit kwallet settings my kwallet settings -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 446925] drkonqi does not persist authentication credentials even if save option is checked.
https://bugs.kde.org/show_bug.cgi?id=446925 --- Comment #1 from Fabio C. Barrionuevo --- >> ADDITIONAL INFORMATION: >> I checked and kwallet is active. >> I don't know if this has anything to do with the bug to do with the problem, >> but there is an entry for drkonqi, and the values saved in it are >> from >> the attached screenshot. >> I would enter the correct credentials again into drkonqi but apparently, >> this record is not updated in kwallet and no new deliveries are >> entered >> into kwallet. ignore this part of the original report. I kwallet contains the correct credentials but drkonqi doesn't seem to be using them. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 446925] New: drkonqi does not persist authentication credentials even if save option is checked.
https://bugs.kde.org/show_bug.cgi?id=446925 Bug ID: 446925 Summary: drkonqi does not persist authentication credentials even if save option is checked. Product: drkonqi Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bna...@gmail.com Target Milestone: --- Created attachment 144509 --> https://bugs.kde.org/attachment.cgi?id=144509&action=edit drkonqi kwallet SUMMARY When an error occurs, KDE Neon opens drkonqi to warn of the error. When trying to report an error, you are prompted for a login and password and there is an option to save this authentication credential. The problem is that even checking the option to save the credentials if a new error happens, I will be forced to enter the authentication credentials again, which seems to me to be the wrong behavior for the option to save authentication credentials. OBSERVED RESULT Authentication information is always prompted when trying to report an error, even if the option to save authentication credentials was previously checked. EXPECTED RESULT Enter the authentication information, check the option to save this credential, and not have to re-enter this information at any time in the future, ie during the current session or after one or more cycles of turning KDE Neon on and off SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 ADDITIONAL INFORMATION: I checked and kwallet is active. I don't know if this has anything to do with the bug to do with the problem, but there is an entry for drkonqi, and the values saved in it are from the attached screenshot. I would enter the correct credentials again into drkonqi but apparently, this record is not updated in kwallet and no new deliveries are entered into kwallet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445498] Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu.
https://bugs.kde.org/show_bug.cgi?id=445498 --- Comment #6 from Fabio C. Barrionuevo --- (In reply to Nate Graham from comment #5) > It's Bug 414805. The issue is in Qt itself, not any KDE code. > > *** This bug has been marked as a duplicate of bug 414805 *** Okay, thanks for pointing out that the bug is in QT and not KDE. Since I keep getting this error repeatedly and https://invent.kde.org/qt/qt/qtbase/-/merge_requests/33 has merged 5 months ago, (and I can assume it's already integrated for general use in KDE Neon), is there any other issue that I should be aware of to see and/or help with more information that deals with this specific issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445498] Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu.
https://bugs.kde.org/show_bug.cgi?id=445498 Fabio C. Barrionuevo changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445498] Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu.
https://bugs.kde.org/show_bug.cgi?id=445498 --- Comment #4 from Fabio C. Barrionuevo --- Created attachment 144146 --> https://bugs.kde.org/attachment.cgi?id=144146&action=edit New crash information added by DrKonqi plasmashell (5.23.3) using Qt 5.15.3 I'm always up to date with KDE Neon, and this failure keeps happening. I'm not sure if the merge-request that this issue was marked as a duplicate refers to can actually fix this specific issue. Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 -- Backtrace (Reduced): #4 0x7f3f18a4a331 in QXcbVirtualDesktop::surfaceFormatFor(QSurfaceFormat const&) const (this=0x0, format=...) at qxcbobject.h:53 #5 0x7f3f18a4a9d6 in QXcbScreen::surfaceFormatFor(QSurfaceFormat const&) const (this=this@entry=0x557609276240, format=...) at qxcbscreen.cpp:653 #6 0x7f3f1769dd00 in QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const (this=, context=0x5576069eb600) at qxcbglxintegration.cpp:196 #7 0x7f3f18a42a88 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const (this=, context=0x5576069eb600) at qxcbintegration.cpp:282 #8 0x7f3f1d6e6ef1 in QOpenGLContext::create() (this=0x5576069eb600) at ../../include/QtGui/5.15.3/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:110 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445498] Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu.
https://bugs.kde.org/show_bug.cgi?id=445498 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445498] Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu.
https://bugs.kde.org/show_bug.cgi?id=445498 --- Comment #1 from Fabio C. Barrionuevo --- Created attachment 143552 --> https://bugs.kde.org/attachment.cgi?id=143552&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445498] New: Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu.
https://bugs.kde.org/show_bug.cgi?id=445498 Bug ID: 445498 Summary: Plasma crashes when waking up the computer from suspension mode and clicking on any item on the menu. Product: plasmashell Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bna...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.3) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Wake up the computer from suspension mode and click on any item of the menu. This bug is reproducible 100% of the time. Note: I'm running KDE Neon on X11 + Nvidia GTX 1650 with proprietary driver installed via ubuntu-drivers + 2 monitors connected via Displayport. Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 The crash can be reproduced every time. -- Backtrace (Reduced): #4 0x7f17ea977c38 in QScreen::handle() const (this=0x556a3472d9c0) at kernel/qscreen.cpp:182 #5 0x7f17e494dce4 in QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const (this=, context=0x7f17e002ac00) at qxcbglxintegration.cpp:195 #6 0x7f17e5cf1a88 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const (this=, context=0x7f17e002ac00) at qxcbintegration.cpp:282 #7 0x7f17ea995ef1 in QOpenGLContext::create() (this=0x7f17e002ac00) at ../../include/QtGui/5.15.3/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:110 #8 0x7f17ebfefd98 in QSGRenderThread::sync(bool, bool) (this=this@entry=0x7f17e0018200, inExpose=inExpose@entry=true, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:620 Possible duplicates by query: bug 445327, bug 442126, bug 440124, bug 437266, bug 437090. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442126] New: Crash after resume and click into Bluetooth widget
https://bugs.kde.org/show_bug.cgi?id=442126 Bug ID: 442126 Summary: Crash after resume and click into Bluetooth widget Product: plasmashell Version: 5.22.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bna...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.5) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.11.0-27-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: This has happened several times. Always right after resuming, and clicking on the Bluetooth widget The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #4 0x7efd7af41c48 in QScreen::handle() const (this=0x55cf0d4b4830) at kernel/qscreen.cpp:182 #5 0x7efd74f6ece4 in QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const (this=, context=0x55cf0f596d60) at qxcbglxintegration.cpp:195 #6 0x7efd762c6a88 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const (this=, context=0x55cf0f596d60) at qxcbintegration.cpp:282 #7 0x7efd7af5ff01 in QOpenGLContext::create() (this=0x55cf0f596d60) at ../../include/QtGui/5.15.3/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:110 #8 0x7efd7c5a7cb8 in QSGRenderThread::sync(bool, bool) (this=this@entry=0x55cf12b5c450, inExpose=inExpose@entry=true, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:620 Possible duplicates by query: bug 440124, bug 437266, bug 437090, bug 435058, bug 434154. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442126] Crash after resume and click into Bluetooth widget
https://bugs.kde.org/show_bug.cgi?id=442126 --- Comment #1 from Fabio C. Barrionuevo --- Created attachment 141360 --> https://bugs.kde.org/attachment.cgi?id=141360&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391951] New: plasmashell crash after 2018-03-15 update
https://bugs.kde.org/show_bug.cgi?id=391951 Bug ID: 391951 Summary: plasmashell crash after 2018-03-15 update Product: plasmashell Version: 5.12.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bna...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.3) Qt Version: 5.9.3 Frameworks Version: 5.44.0 Operating System: Linux 4.13.0-37-generic x86_64 Distribution: KDE neon LTS User Edition 5.12 -- Information about the crash: - Unusual behavior I noticed: plasmashell crash after 2018-03-15 update 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 0x7f6a4365e900 (LWP 6518))] Thread 14 (Thread 0x7f695a1b1700 (LWP 6534)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695a1b1700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f695adfd700 (LWP 6533)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695adfd700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f695b7fe700 (LWP 6532)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695b7fe700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f695bfff700 (LWP 6531)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a41195ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f6a411967b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3c2c86ba in start_thread (arg=0x7f695bfff700) at pthread_create.c:333 #6 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f6963e3d700 (LWP 6529)): #0 0x7f6a3cd2474d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6a37b1338c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a37b1349c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a3d64b6cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a3d5f3e2a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a3d41c8f4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f696631b517 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f6a3d421709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a3c2c86ba in start_thread (arg=0x7f6963e3d700) at pthread_create.c:333 #9 0x7f6a3cd3041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f697d02a700 (LWP 6526)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6a3d42265b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6a
[neon] [Bug 374339] login screen text is unreadably small on external screen
https://bugs.kde.org/show_bug.cgi?id=374339 --- Comment #3 from Fabio C. Barrionuevo --- I am using KDE Neon User LTS (with Plasma 5.8) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 374339] login screen text is unreadably small on external screen
https://bugs.kde.org/show_bug.cgi?id=374339 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com --- Comment #2 from Fabio C. Barrionuevo --- Created attachment 105291 --> https://bugs.kde.org/attachment.cgi?id=105291&action=edit sddm login screen with wrong resolution login screen is also small on the laptop screen and external screen, both have 1920x1080 of physical resolution. Dell Latitude 3450. This is hwinfo hardware report: https://gist.github.com/luzfcb/b39ab7db870272a238c116cead2e0bc1 -- You are receiving this mail because: You are watching all bug changes.
