[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #39 from Mathias Homann --- (In reply to Philippe Cloutier from comment #38) > Hum, thanks Mathias. But in that case, should this ticket be re-titled to be > more general (not specific to "/")? that is the weird bit - the popup usually complains about / even when / is on a SSD or NVMe and it's actually some /users/$USER or /shared/data that comes in via NFS and is dragging things down. Almost as if whatever is broken doesn't even notice that someting is mounted somewhere under /users/ or similar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Mathias Homann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Mathias Homann changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #37 from Mathias Homann --- (In reply to Philippe Cloutier from comment #35) > (In reply to ManuelBoe from comment #34) > > The dialog described above appears when the file system is unusually slow. > > This may indicate that the hard disk is about to fail or may have other > > causes. > > This bug is unfortunately not limited to OSes hosted on HDDs. and not necessarily limited to the filesystem where the OS is installed either - in my case, $HOME and several network shares are NFS, and this bug gets triggered whenever the file server is under heavier load than usual - running AIDE, installing updates, etc. definitely NOT a "feature". a "feature" would be the option to limit whatever process fails with this message to local harddisks only. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 464784] New: Spectacle captures random images in a NVIDIA Prime offset rendering setup
https://bugs.kde.org/show_bug.cgi?id=464784 Bug ID: 464784 Summary: Spectacle captures random images in a NVIDIA Prime offset rendering setup Classification: Applications Product: Spectacle Version: 22.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: mathias.hom...@opensuse.org CC: k...@david-redondo.de Target Milestone: --- SUMMARY I'm using spectacle in a setup with the intel driver as primary, and a nvidia card through prime render offsetting. I have spectacle bound to the printscreen key. When I try capturing a screenshot of an "offloaded" openGL app (any game or the likes) spectacle sometimes (about half of the time) captures not the game but some other window that is also on screen. STEPS TO REPRODUCE 1. Set up a laptop with intel and nvidia prime offset redering 2. run any openGL app / game 3. try catching a screenshot of the game. OBSERVED RESULT spectacle catches a screenshot of one of the running windows but not necessarily the one running in foreground EXPECTED RESULT spectacle should take a screenshot of what is on my screen, not of what other windows would look like if they were still running in the foreground ADDITIONAL INFO SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION mathias@mio:~> inxi -G Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] driver: nvidia v: 525.85.05 Device-3: Acer HD Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X: loaded: intel,modesetting unloaded: nvidia dri: i965 gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel Xe Graphics (TGL GT2) mathias@mio:~> gamemoderun inxi -G gamemodeauto: gamemodeauto: gamemodeauto: Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] driver: nvidia v: 525.85.05 Device-3: Acer HD Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X: loaded: intel,modesetting unloaded: nvidia dri: i965 gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6.0 NVIDIA 525.85.05 renderer: NVIDIA GeForce GTX 1650 Ti with Max-Q Design/PCIe/SSE2 mathias@mio:~> Operating System: openSUSE Tumbleweed 20230123 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Prestige 14 A11SCS System Version: REV:1.0 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 289515] the /media command sends the song data twice
https://bugs.kde.org/show_bug.cgi?id=289515 --- Comment #6 from Mathias Homann --- Now i actually installed and tried kopete: - still broken to the point of being unusable - /media command isn't even around anymore. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 289515] the /media command sends the song data twice
https://bugs.kde.org/show_bug.cgi?id=289515 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #5 from Mathias Homann --- I have stopped using kopete when it became broken to the point of being unusable, and that was almost 10 years ago. since then there has been almost no noticeable work on kopete. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 267536] clicking the "chat" button in the "soanso came online" notification doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=267536 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Mathias Homann --- Now there are no "soandso is online" notifications anymore... so technically I can't verify this anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462512] [NVIDIA] Missing sensor information after driver update
https://bugs.kde.org/show_bug.cgi?id=462512 --- Comment #7 from Mathias Homann --- I don't think it is - the GPU sensors are there, they just return nothing but zeros. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 Mathias Homann changed: What|Removed |Added Attachment #154300|Anothre screenshot showing |Another screenshot showing description|how this can lead to|how this can lead to |unusable widgets... |unusable widgets... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 --- Comment #5 from Mathias Homann --- Personally, I don't think having more than two digits after the dot on a Loadaverage display would give any meaningful information. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #4 from Mathias Homann --- Created attachment 154300 --> https://bugs.kde.org/attachment.cgi?id=154300=edit Anothre screenshot showing how this can lead to unusable widgets... -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 400124] kopete does not automatically log in to my messenger accounts even though it is configured to do so
https://bugs.kde.org/show_bug.cgi?id=400124 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Mathias Homann --- yep, still reproduces. is kopete even still maintained? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 400125] kopete does not save / restore the UI settings (hide menu, small toolbar icons w/o text, etc)
https://bugs.kde.org/show_bug.cgi?id=400125 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Mathias Homann --- yep, still reproduces. is kopete even still maintained? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 422853] Unable to reboot or shutdown the system when logged in with a networked user
https://bugs.kde.org/show_bug.cgi?id=422853 --- Comment #2 from Mathias Homann --- has not happened for quite some time now, and my underlying infrastructure has changed a lot by now. If noone else still reproduces this it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462024] New: Unable to read stats of my NVidia card
https://bugs.kde.org/show_bug.cgi?id=462024 Bug ID: 462024 Summary: Unable to read stats of my NVidia card Classification: Plasma Product: plasma-systemmonitor Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Since a few days system monitor doesn't display the stats of my GTX1050 anymore STEPS TO REPRODUCE 1. Create a sheet (or a desktop widget) that monitors something off the nvidia card, i.e. GPU 1 Temperature OBSERVED RESULT The monitor shows 0°C EXPECTED RESULT It should show the actual temperature as shown by nvidia-smi SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221117 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION NVIDIA Driver version is 525.53 and ... "it used to work", until some recent update... -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 381159] No support for direct messages longer than 160 characters
https://bugs.kde.org/show_bug.cgi?id=381159 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Mathias Homann --- to be honest, right now it looks as if direct messages dont work at all - I just sent two from my account to another test account, one of 150 and ones of 280 characters - neither of them show in neither of the two accounts when I use the website to look for them. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461540] New: Choqok does not store the "read state" of tweets anymore
https://bugs.kde.org/show_bug.cgi?id=461540 Bug ID: 461540 Summary: Choqok does not store the "read state" of tweets anymore Classification: Applications Product: choqok Version: 1.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Choqok does not store the "read state" of tweets anymore STEPS TO REPRODUCE 1. quit chocok with no unread tweets 2. start choqok again 3. notice how there are loads of "new" tweets again, including mentions and DMs from months ago. OBSERVED RESULT I see old tweets and mentions as "unread" even when they are months old after restarting choqok EXPECTED RESULT I expect tweets and DMs to "stay read" once I've seen them. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461511] Presentation mode always goes to the next page after 5 seconds no matter what is set in preferences
https://bugs.kde.org/show_bug.cgi?id=461511 --- Comment #1 from Mathias Homann --- oh by the way just in case it depends on the PDF file: here's the link to the one that I'm having trouble with https://www.deviantart.com/stjepan-sejic/art/Fine-print-book-1-complete-pdf-935744275 Careful tho, you might consider that PDF NSFW. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461511] New: Presentation mode always goes to the next page after 5 seconds no matter what is set in preferences
https://bugs.kde.org/show_bug.cgi?id=461511 Bug ID: 461511 Summary: Presentation mode always goes to the next page after 5 seconds no matter what is set in preferences Classification: Applications Product: okular Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY When I use okular in presentation mode it always goes to the next page after about 5 seconds even when I turn "auto advance" off in preferences, or set it to a much longer delay STEPS TO REPRODUCE 1. open any supported file 2. start presentation mode 3. notice how the presentation advances after 5 seconds no matter what you do OBSERVED RESULT see above EXPECTED RESULT If I disable "auto advance" I expect it not to auto advance. If I set the delay to 60 seconds I expect the presentation to run at 60 seconds per slide, not 5. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 252359] Kompare could not parse some patch files
https://bugs.kde.org/show_bug.cgi?id=252359 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #19 from Mathias Homann --- There are still cases when kompare chokes on a diff - mainly when there's non-english errors embedded in it. but that's just a question of what options to pass to the diff command. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 326646] Password to unlock the kde wallet should not time out so fast
https://bugs.kde.org/show_bug.cgi?id=326646 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Mathias Homann --- ... can't you automatically close stuff that is for KDE4... -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Version|5.10.3 |5.21.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Mathias Homann --- does not reproduce anymore. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #48 from Mathias Homann --- 4 years old. this bug has disappeared and resurfaced many times since then, most likely different reasons each time. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #20 from Mathias Homann --- Bugs like this one keep disappearing and reappearing. TWO years later this specific occurence is most likely long gone. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 416136] kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=416136 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Mathias Homann --- right now this does not reproduce. Operating System: openSUSE Tumbleweed 20221003 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 458058] New: ktorrent crashes when a magnet "data download" is done and the actual torrent starts
https://bugs.kde.org/show_bug.cgi?id=458058 Bug ID: 458058 Summary: ktorrent crashes when a magnet "data download" is done and the actual torrent starts Product: ktorrent Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: ktorrent (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I'm trying to get some downloads started, but when the "magnet process" is done and the actual torrent starts, ktorrent crashes, and when I restart it, the torrent AND the magnet download are both active, leading to the same crash in a few seconds. repeat ad nauseam. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7fde0c525d7f in kt::MagnetManager::update (this=0x561c9f6819d0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/libktcore/torrent/magnetmanager.cpp:339 #5 0x561c9e903efa in kt::Core::update (this=0x561c9f64ead0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:900 #6 0x7fde0a512e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd5f3cd0e0, r=0x561c9f64ead0, this=0x561c9f680df0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x561c9f64eaf8, signal_index=3, argv=0x7ffd5f3cd0e0) at kernel/qobject.cpp:3886 #8 0x7fde0a50c22f in QMetaObject::activate (sender=, m=m@entry=0x7fde0a7b39a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5f3cd0e0) at kernel/qobject.cpp:3946 #9 0x7fde0a516aca in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #10 0x7fde0a50757d in QObject::event (this=0x561c9f64eaf8, e=0x7ffd5f3cd230) at kernel/qobject.cpp:1336 #11 0x7fde0b1a541e in QApplicationPrivate::notify_helper (this=, receiver=0x561c9f64eaf8, e=0x7ffd5f3cd230) at kernel/qapplication.cpp:3637 #12 0x7fde0a4dbfb8 in QCoreApplication::notifyInternal2 (receiver=0x561c9f64eaf8, event=0x7ffd5f3cd230) at kernel/qcoreapplication.cpp:1064 #13 0x7fde0a532851 in QTimerInfoList::activateTimers (this=0x561c9f3dd3a0) at kernel/qtimerinfo_unix.cpp:643 #14 0x7fde0a5330e4 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #15 0x7fde085bfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7fde085c0258 in ?? () from /lib64/libglib-2.0.so.0 #17 0x7fde085c02ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7fde0a533456 in QEventDispatcherGlib::processEvents (this=0x561c9f3e8840, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7fde0a4daa2b in QEventLoop::exec (this=this@entry=0x7ffd5f3cd470, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x7fde0a4e2b96 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x561c9e8f82b9 in main (argc=, argv=) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/main.cpp:253 [Inferior 1 (process 7454) detached] The reporter indicates this bug may be a duplicate of or related to bug 458057, bug 396727. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 458057] New: Crash when a magnet torrent starts
https://bugs.kde.org/show_bug.cgi?id=458057 Bug ID: 458057 Summary: Crash when a magnet torrent starts Product: ktorrent Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: ktorrent (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I have started a magnet "download" to start a torrent, when I close the "download to" popup to actually get started ktorrent crashes. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7f9088c98d74 in QListData::at (i=, this=) at /usr/include/qt5/QtCore/qlist.h:117 #5 QList::at (i=, this=) at /usr/include/qt5/QtCore/qlist.h:572 #6 kt::MagnetManager::update (this=0x55d2409ef4c0) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/libktcore/torrent/magnetmanager.cpp:339 #7 0x55d23eaf9efa in kt::Core::update (this=0x55d2409b3580) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:900 #8 0x7f9086b12e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffe1d06bbf0, r=0x55d2409b3580, this=0x55d2409ee8e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x55d2409b35a8, signal_index=3, argv=0x7ffe1d06bbf0) at kernel/qobject.cpp:3886 #10 0x7f9086b0c22f in QMetaObject::activate (sender=, m=m@entry=0x7f9086db39a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe1d06bbf0) at kernel/qobject.cpp:3946 #11 0x7f9086b16aca in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #12 0x7f9086b0757d in QObject::event (this=0x55d2409b35a8, e=0x7ffe1d06bd40) at kernel/qobject.cpp:1336 #13 0x7f90877a541e in QApplicationPrivate::notify_helper (this=, receiver=0x55d2409b35a8, e=0x7ffe1d06bd40) at kernel/qapplication.cpp:3637 #14 0x7f9086adbfb8 in QCoreApplication::notifyInternal2 (receiver=0x55d2409b35a8, event=0x7ffe1d06bd40) at kernel/qcoreapplication.cpp:1064 #15 0x7f9086b32851 in QTimerInfoList::activateTimers (this=0x55d240754860) at kernel/qtimerinfo_unix.cpp:643 #16 0x7f9086b330e4 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #17 0x7f9084dbfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f9084dc0258 in ?? () from /lib64/libglib-2.0.so.0 #19 0x7f9084dc02ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f9086b33456 in QEventDispatcherGlib::processEvents (this=0x55d2407566a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f9086adaa2b in QEventLoop::exec (this=this@entry=0x7ffe1d06bf80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f90879ad3a7 in QDialog::exec (this=this@entry=0x7ffe1d06c110) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x55d23eafd536 in kt::FileSelectDlg::execute (location_hint=..., skip_check=0x7ffe1d06c06e, start=0x7ffe1d06c06f, tc=0x55d240f292b0, this=0x7ffe1d06c110) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/dialogs/fileselectdlg.cpp:156 #24 kt::Core::init (this=, tc=, group=..., location=..., silently=) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:235 #25 0x55d23eafdd23 in kt::Core::loadFromData (this=0x55d2409b3580, data=..., dir=..., group=..., silently=, url=...) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:320 #26 0x55d23eaff29f in kt::Core::load (this=0x55d2409b3580, data=..., url=..., group=..., savedir=...) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:469 #27 0x55d23eafb8fb in kt::Core::onMetadataDownloaded (this=0x55d2409b3580, mlink=..., data=..., options=...) at /usr/src/debug/ktorrent-22.04.3-1.1.x86_64/ktorrent/core.cpp:1236 #28 0x7f9086b07760 in QObject::event (this=0x55d2409b3580, e=0x55d2418e6770) at kernel/qobject.cpp:1314 #29 0x7f90877a541e in QApplicationPrivate::notify_helper (this=, receiver=0x55d2409b3580, e=0x55d2418e6770) at kernel/qapplication.cpp:3637 #30 0x7f9086adbfb8 in QCoreApplication::notifyInternal2 (receiver=0x55d2409b3580, event=0x55d2418e6770) at kernel/qcoreapplication.cpp:1064 #31 0x7f9086adef51 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55d240662040) at kernel/qcoreapplication.cpp:1821 #32 0x7f9086b33c53 in postEventSourceDispatch (s=0x55d2407473c0) at kernel/qeventdispatcher_glib.cpp:277 #33 0x7f9084dbfea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #34 0x7f9084dc0258 in ?? () from
[kontact] [Bug 457958] New: crash on close
https://bugs.kde.org/show_bug.cgi?id=457958 Bug ID: 457958 Summary: crash on close Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.20.3 (22.04.3)) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I closed knotact with ctrl-q and it crashed. Didn't see if it happens all the time. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7face2b7d444 in QTabWidget::count() const (this=0x55b0692fced0) at widgets/qtabwidget.cpp:1212 #5 0x7fac5d60f56f in MessageList::Pane::PanePrivate::updateTabControls() () at /lib64/libKF5MessageList.so.5 #6 0x7face1d12e6f in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x77917340, r=0x55b066407c20, this=0x55b0665d04f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x55b0665ee7a0, signal_index=3, argv=0x77917340) at kernel/qobject.cpp:3886 #8 0x7face1896678 in KCoreConfigSkeleton::save() (this=0x55b0665ee7a0) at /usr/src/debug/kconfig-5.96.0-1.1.x86_64/src/core/kcoreconfigskeleton.cpp:1245 #9 0x7fac5d5bd058 in () at /lib64/libKF5MessageList.so.5 #10 0x7fac5d5bd516 in () at /lib64/libKF5MessageList.so.5 #11 0x7fac5d5e94e8 in () at /lib64/libKF5MessageList.so.5 #12 0x7fac5d617519 in MessageList::Widget::~Widget() () at /lib64/libKF5MessageList.so.5 #13 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066345780) at kernel/qobject.cpp:2104 #14 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0663d72d0, __in_chrg=) at kernel/qwidget.cpp:1522 #15 0x7face2b59f89 in QStackedWidget::~QStackedWidget() (this=0x55b0663d72d0, __in_chrg=) at widgets/qstackedwidget.cpp:147 #16 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b0664227f0) at kernel/qobject.cpp:2104 #17 0x7face29e2666 in QWidget::~QWidget() (this=0x55b066407c20, __in_chrg=) at kernel/qwidget.cpp:1522 #18 0x7fac5d97c6bd in CollectionPane::~CollectionPane() (this=0x55b066407c20, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/widgets/collectionpane.cpp:24 #19 CollectionPane::~CollectionPane() (this=0x55b066407c20, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/widgets/collectionpane.cpp:24 #20 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066378410) at kernel/qobject.cpp:2104 #21 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0666f9a90, __in_chrg=) at kernel/qwidget.cpp:1522 #22 0x7face2b55229 in QSplitter::~QSplitter() (this=0x55b0666f9a90, __in_chrg=) at widgets/qsplitter.cpp:979 #23 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066698130) at kernel/qobject.cpp:2104 #24 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0666f9a50, __in_chrg=) at kernel/qwidget.cpp:1522 #25 0x7face2b55229 in QSplitter::~QSplitter() (this=0x55b0666f9a50, __in_chrg=) at widgets/qsplitter.cpp:979 #26 0x7fac5d9c8cf3 in KMMainWidget::deleteWidgets() (this=this@entry=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:987 #27 0x7fac5d9cb9f6 in KMMainWidget::destruct() (this=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:395 #28 KMMainWidget::destruct() (this=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:384 #29 0x7facb8621c1f in KMailPart::~KMailPart() (this=0x55b0662d4640, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmail_part.cpp:89 #30 0x7facb8621d69 in KMailPart::~KMailPart() (this=0x55b0662d4640, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmail_part.cpp:92 #31 0x7face33468fe in KontactInterface::Plugin::~Plugin() (this=this@entry=0x55b0662d06b0, __vtt_parm=__vtt_parm@entry=0x7fac5dfa1b30 , this=, __vtt_parm=) at /usr/src/debug/kontactinterface-22.04.3-1.1.x86_64/src/plugin.cpp:74 #32 0x7fac5df8ed11 in KMailPlugin::~KMailPlugin() (this=0x55b0662d06b0, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:145 #33 0x7fac5df8ed49 in KMailPlugin::~KMailPlugin() (this=0x55b0662d06b0, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:145 #34 0x7face337b59e in qDeleteAll::const_iterator>(QList::const_iterator, QList::const_iterator) (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320 #35 qDeleteAll >(QList
[kalendar] [Bug 457941] New: calandar notifications still crashing
https://bugs.kde.org/show_bug.cgi?id=457941 Bug ID: 457941 Summary: calandar notifications still crashing Product: kalendar Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: mathias.hom...@opensuse.org CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: still the same: i dismiss a calendar notification and i get drkonqi. The crash can be reproduced sometimes. -- Backtrace: Application: Erinnerungen (kalendarac), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=, this=, this=, __m=) at /usr/include/c++/12/bits/atomic_base.h:486 #5 QAtomicOps::loadRelaxed (_q_value=..., _q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x7f1ed25cd954) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #7 QWeakPointer::internalData (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:698 #8 QPointer::data (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qpointer.h:77 #9 QPointer::operator KNotification* (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qpointer.h:83 #10 AlarmNotification::~AlarmNotification (this=, this=) at /usr/src/debug/akonadi-calendar-22.04.3-1.1.x86_64/reminder-daemon/alarmnotification.cpp:23 #11 KalendarAlarmClient::dismiss (this=0x7ffc13c67720, notification=0x5625eff302b0) at /usr/src/debug/akonadi-calendar-22.04.3-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:120 #12 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66ce0, r=0x7ffc13c67720, this=0x5625eff2b4b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x5625eff7c650, signal_index=9, argv=0x7ffc13c66ce0) at kernel/qobject.cpp:3886 #14 0x7f1bc410c22f in QMetaObject::activate (sender=sender@entry=0x5625eff7c650, m=m@entry=0x7f1bc50ec6a0, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #15 0x7f1bc50b4903 in KNotification::closed (this=this@entry=0x5625eff7c650) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotification.cpp:582 #16 0x7f1bc50b7817 in KNotification::textChanged (this=0x5625eff7c650) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/src/knotification.cpp:358 #17 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66e10, r=0x7f1bc50ee060 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=0x5625effacb20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate (sender=0x5625effad9a0, signal_index=3, argv=0x7ffc13c66e10) at kernel/qobject.cpp:3886 #19 0x7f1bc410c22f in QMetaObject::activate (sender=, m=m@entry=0x7f1bc50ec620 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc13c66e10) at kernel/qobject.cpp:3946 #20 0x7f1bc50b4aef in KNotificationPlugin::finished (this=, _t1=) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotificationplugin.cpp:173 #21 0x7f1bc50cb891 in NotifyByPopup::onNotificationClosed (this=0x5625effad9a0, dbus_id=, reason=3) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/src/notifybypopup.cpp:150 #22 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66fe0, r=0x5625effad9a0, this=0x5625effaf1b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x5625effad9d8, signal_index=5, argv=0x7ffc13c66fe0) at kernel/qobject.cpp:3886 #24 0x7f1bc410c22f in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffc13c66fe0) at kernel/qobject.cpp:3946 #25 0x7f1bc50d7599 in OrgFreedesktopNotificationsInterface::NotificationClosed (_t2=, _t1=, this=) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:287 #26 OrgFreedesktopNotificationsInterface::qt_static_metacall (_o=_o@entry=0x5625effad9d8, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7ffc13c67130) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:148 #27 0x7f1bc50d7f83 in OrgFreedesktopNotificationsInterface::qt_metacall (this=0x5625effad9d8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7ffc13c67130) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:242 #28 0x7f1bc4b6056b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=...,
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 --- Comment #7 from Mathias Homann --- Created attachment 150864 --> https://bugs.kde.org/attachment.cgi?id=150864=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 still crashing every time I dismiss a notification. My calendar data comes from a nextcloud if that makes any difference. -- Backtrace (Reduced): #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=32617) at codecs/qutfcodec.cpp:383 #7 0x7f69fa97bd95 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5380 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5372 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 --- Comment #3 from Mathias Homann --- Created attachment 150576 --> https://bugs.kde.org/attachment.cgi?id=150576=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 reminder crashes when dismissing a notification. -- Backtrace (Reduced): #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=21892) at codecs/qutfcodec.cpp:383 #7 0x7f791997bd95 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5380 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5372 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] New: Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 Bug ID: 456157 Summary: Crash on dismissing a reminder Product: kalendar Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: mathias.hom...@opensuse.org CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.2) Qt Version: 5.15.2 Frameworks Version: 5.95.0 Operating System: Linux 5.18.6-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.1 [KCrashBackend] -- Information about the crash: The reminder app crashed when I dismissed a reminder that I already had dismissed on a different device (calendar event is in a webdav calendar) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Erinnerungen (kalendarac), signal: Segmentation fault [KCrash Handler] #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=32570) at codecs/qutfcodec.cpp:383 #7 0x7f3b0d37bc75 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5376 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5368 #9 0x7f3b0e0adeeb in QString::toUtf8() const & (this=) at /usr/include/qt5/QtCore/qstring.h:684 #10 KConfigBase::isGroupImmutable (this=0x7ffd8fb599c0, aGroup=...) at /usr/src/debug/kconfig-5.95.0-1.1.x86_64/src/core/kconfigbase.cpp:83 #11 0x7f3b0e0b6ddf in KConfigGroup::KConfigGroup (this=, master=, _group=..., this=, master=, _group=...) at /usr/src/debug/kconfig-5.95.0-1.1.x86_64/src/core/kconfiggroup.cpp:471 #12 0x55bc6df9eaf5 in KalendarAlarmClient::removeNotification (this=0x7ffd8fb5a4f0, notification=0x55bc6f122910) at /usr/src/debug/akonadi-calendar-22.04.2-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:181 #13 KalendarAlarmClient::dismiss (this=0x7ffd8fb5a4f0, notification=0x55bc6f122910) at /usr/src/debug/akonadi-calendar-22.04.2-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:118 #14 0x7f3b0d512b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd8fb59ab0, r=0x7ffd8fb5a4f0, this=0x55bc6f30c8b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate (sender=0x55bc6f30ca10, signal_index=9, argv=0x7ffd8fb59ab0) at kernel/qobject.cpp:3886 #16 0x7f3b0d50beff in QMetaObject::activate (sender=sender@entry=0x55bc6f30ca10, m=m@entry=0x7f3b0e5a76a0, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #17 0x7f3b0e56f903 in KNotification::closed (this=this@entry=0x55bc6f30ca10) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotification.cpp:582 #18 0x7f3b0e572817 in KNotification::textChanged (this=0x55bc6f30ca10) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/src/knotification.cpp:358 #19 0x7f3b0d512b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd8fb59be0, r=0x7f3b0e5a9060 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=0x55bc6f318c80) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x55bc6f318460, signal_index=3, argv=0x7ffd8fb59be0) at kernel/qobject.cpp:3886 #21 0x7f3b0d50beff in QMetaObject::activate (sender=, m=m@entry=0x7f3b0e5a7620 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd8fb59be0) at kernel/qobject.cpp:3946 #22 0x7f3b0e56faef in KNotificationPlugin::finished (this=, _t1=) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotificationplugin.cpp:173 #23 0x7f3b0e586891 in NotifyByPopup::onNotificationClosed (this=0x55bc6f318460, dbus_id=, reason=3) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/src/notifybypopup.cpp:150 #24 0x7f3b0d512b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd8fb59db0, r=0x55bc6f318460, this=0x55bc6f325950) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #25 doActivate (sender=0x55bc6f318498, signal_index=5, argv=0x7ffd8fb59db0) at kernel/qobject.cpp:3886 #26 0x7f3b0d50beff in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd8fb59db0) at kernel/qobject.cpp:3946 #27 0x7f3b0e592599 in OrgFreedesktopNotificationsInterface::NotificationClosed (_t2=, _t1=, this=) at /usr/src/debug/knotifications-5.95.0-1.1.x86_64/build/src/notifications_interface.moc:287 #28 OrgFreedesktopNotificationsInterface::qt_static_metacall (_o=_o@entry=0x55bc6f318498, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7ffd8fb59f00) at
[choqok] [Bug 455644] more "crash on exit"
https://bugs.kde.org/show_bug.cgi?id=455644 --- Comment #2 from Mathias Homann --- (In reply to Frédéric Brière from comment #1) > FYI, you can currently work around this bug by disabling the automatic > spellchecking option. that actually worked! -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #34 from Mathias Homann --- (In reply to Frédéric Brière from comment #33) > (In reply to Mathias Homann from comment #32) > > I have built rpms for openSUSE with those two patches, and I'm still getting > > a crash on exit every time I try. Backtrace's attached. > > Despite what it looks like, this appears to be a different bug. Could you > file a separate issue for this one? Thanks! done that: https://bugs.kde.org/show_bug.cgi?id=455644 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 455644] New: more "crash on exit"
https://bugs.kde.org/show_bug.cgi?id=455644 Bug ID: 455644 Summary: more "crash on exit" Product: choqok Version: 1.7.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: choqok (1.7.0) Qt Version: 5.15.2 Frameworks Version: 5.95.0 Operating System: Linux 5.18.4-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.0 [KCrashBackend] -- Information about the crash: reproduce: run choqok, press ctrl-q - it will segfault on exit. The crash can be reproduced every time. -- Backtrace: Application: Choqok (choqok), signal: Segmentation fault [KCrash Handler] #4 0xfff0 in ?? () #5 0x7f938a712b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffdf4f82c40, r=0x55ddcc0257f0, this=0x55ddcc1788d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x55ddcc0257f0, signal_index=7, argv=0x7ffdf4f82c40) at kernel/qobject.cpp:3886 #7 0x7f938a712b6c in doActivate (sender=0x55ddcc048660, signal_index=3, argv=0x7ffdf4f82d00) at kernel/qobject.cpp:3898 #8 0x7f938b59ef83 in QWidgetTextControl::qt_metacall (this=0x55ddcc048660, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffdf4f82df0) at .moc/moc_qwidgettextcontrol_p.cpp:489 #9 0x7f938a7128aa in doActivate (sender=0x55ddcc0485f0, signal_index=4, argv=0x7ffdf4f82df0) at kernel/qobject.cpp:3912 #10 0x7f938a70beff in QMetaObject::activate (sender=, m=m@entry=0x7f938b109820 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #11 0x7f938aff7f33 in QTextDocument::contentsChanged (this=) at .moc/moc_qtextdocument.cpp:427 #12 0x7f938aca931c in QTextDocumentPrivate::finishEdit (this=0x55ddcb7d5d60) at text/qtextdocument_p.cpp:1247 #13 0x7f938aca96f5 in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1203 #14 0x7f938acf4951 in QSyntaxHighlighter::setDocument (this=0x55ddcf941ab0, doc=0x0) at text/qsyntaxhighlighter.cpp:342 #15 0x7f938acf4b89 in QSyntaxHighlighter::~QSyntaxHighlighter (this=0x55ddcf941ab0, __in_chrg=) at text/qsyntaxhighlighter.cpp:324 #16 0x7f9387ffa469 in Sonnet::Highlighter::~Highlighter (this=, this=) at /usr/src/debug/sonnet-5.95.0-1.1.x86_64/src/ui/highlighter.cpp:165 #17 0x7f938a70505e in QObjectPrivate::deleteChildren (this=0x55ddcf946b40) at kernel/qobject.cpp:2104 #18 0x7f938a710bc0 in QObject::~QObject (this=this@entry=0x55ddcacf79c0, __in_chrg=) at kernel/qobject.cpp:1082 #19 0x7f9387ffaaae in Sonnet::SpellCheckDecorator::~SpellCheckDecorator (this=, this=) at /usr/src/debug/sonnet-5.95.0-1.1.x86_64/src/ui/spellcheckdecorator.cpp:225 #20 0x7f938b925de3 in KTextDecorator::~KTextDecorator (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit.cpp:32 #21 KTextDecorator::~KTextDecorator (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit.cpp:32 #22 0x7f938b91bb02 in KTextEditPrivate::~KTextEditPrivate (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit_p.h:47 #23 0x7f938b91bc29 in KTextEditPrivate::~KTextEditPrivate (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit_p.h:56 #24 0x7f938b92196b in std::default_delete::operator() (__ptr=, this=) at /usr/include/c++/12/bits/unique_ptr.h:95 #25 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #26 KTextEdit::~KTextEdit (this=, this=) at /usr/src/debug/ktextwidgets-5.95.0-1.1.x86_64/src/widgets/ktextedit.cpp:258 #27 0x7f938bfc0538 in Choqok::UI::TextEdit::~TextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/libchoqok/ui/choqoktextedit.cpp:98 #28 0x7f937c13fb63 in TwitterApiTextEdit::~TwitterApiTextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/helperlibs/twitterapihelper/twitterapitextedit.cpp:57 #29 0x7f937c4cbf8e in TwitterTextEdit::~TwitterTextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/microblogs/twitter/twittertextedit.cpp:58 #30 TwitterTextEdit::~TwitterTextEdit (this=, this=) at /usr/src/debug/choqok-1.7.0-47.2.x86_64/microblogs/twitter/twittertextedit.cpp:58 #31 0x7f938a70505e in QObjectPrivate::deleteChildren (this=this@entry=0x55ddcc534bf0) at kernel/qobject.cpp:2104 #32 0x7f938b3e24b6 in QWidget::~QWidget (this=0x55ddcc5277d0, __in_chrg=) at kernel/qwidget.cpp:1522 #33 0x7f938b3e27f9 in QWidget::~QWidget (this=0x55ddcc5277d0, __in_chrg=) at kernel/qwidget.cpp:1546 #34 0x7f938a70505e in QObjectPrivate::deleteChildren (this=this@entry=0x55ddcc406390) at kernel/qobject.cpp:2104 #35 0x7f938b3e24b6 in QWidget::~QWidget
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #32 from Mathias Homann --- Created attachment 149940 --> https://bugs.kde.org/attachment.cgi?id=149940=edit New crash information added by DrKonqi choqok (1.7.0) using Qt 5.15.2 I have built rpms for openSUSE with those two patches, and I'm still getting a crash on exit every time I try. Backtrace's attached. -- Backtrace (Reduced): #5 0x7f6a60712b3f in QtPrivate::QSlotObjectBase::call (a=0x7ffecaee5ee0, r=0x56220171b420, this=0x562201c178d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x56220171b420, signal_index=7, argv=0x7ffecaee5ee0) at kernel/qobject.cpp:3886 #7 0x7f6a60712b6c in doActivate (sender=0x562201a0c930, signal_index=3, argv=0x7ffecaee5fa0) at kernel/qobject.cpp:3898 #8 0x7f6a6159ef83 in QWidgetTextControl::qt_metacall (this=0x562201a0c930, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffecaee6090) at .moc/moc_qwidgettextcontrol_p.cpp:489 #9 0x7f6a607128aa in doActivate (sender=0x562201a0c880, signal_index=4, argv=0x7ffecaee6090) at kernel/qobject.cpp:3912 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #28 from Mathias Homann --- (In reply to Frédéric Brière from comment #27) > (In reply to Justin Zobel from comment #23) > > I can't replicate this with Choqok 1.7.0 on Fedora 36. Can everyone please > > test and confirm if the crash is still reproducible? > > This bug involves calling a method on a destroyed object, so whether or not > it will trigger a crash may depend on random factors. > > I submitted a draft merge request fixing this a long time ago, but kinda > forgot about it and left it to rot since then. My bad. It should be good > to go now. choqok 1.7.0, plasma 5.25, openSUSE Tumbleweed - still crashing. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #27 from Mathias Homann --- Works for me on a MSI Prestige 14 running openSUSE Tumbleweed. RPMs for Tumbleweed containing that fix can be found on OBS at https://build.opensuse.org/package/show/home:lemmy04:branches:KDE:Frameworks5/powerdevil5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455382] Setting screen brightness is not working right
https://bugs.kde.org/show_bug.cgi?id=455382 Mathias Homann changed: What|Removed |Added Summary|Setting screen brightness |Setting screen brightness |is now working right|is not working right -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455382] New: Setting screen brightness is now working right
https://bugs.kde.org/show_bug.cgi?id=455382 Bug ID: 455382 Summary: Setting screen brightness is now working right Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: k...@privat.broulik.de, m...@ratijas.tk Target Milestone: 1.0 SUMMARY When I try to change the screen brightness with the slider on the power applet, or the configured hotkeys, the brightness changes in leaps and bounds and never goes to 100% STEPS TO REPRODUCE 1. Upgrade to Plasma 5.25 on a laptop that supports changing the screen brightness 2. try changing the screen brightness 3. observe that changing screen brightness with the xbacklight tool works the way it should OBSERVED RESULT see above EXPECTED RESULT before plasma 5.25 this worked normally so that is what i'd expect SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220613 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.18.2-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Prestige 14 A11SCS System Version: REV:1.0 ADDITIONAL INFORMATION Running openSUSE Tumbleweed which introduced Plasma 5.25 in snapshot 20220613 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #24 from Mathias Homann --- Still crashing here. Operating System: openSUSE Tumbleweed 20220512 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 453281] New: When muted notifications are unmuted after a set time the notification sound stays muted if the unmuting happens at login
https://bugs.kde.org/show_bug.cgi?id=453281 Bug ID: 453281 Summary: When muted notifications are unmuted after a set time the notification sound stays muted if the unmuting happens at login Product: frameworks-knotifications Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Whenever I set my notifications to "silent until such time" the sound stays muted if i log out and log in only after the time when the notifications should be unmuted STEPS TO REPRODUCE 1. mute your notifications for some set time, i.e. "until tomorrow" 2. take note of the actual time when the notifications should unmute, i.e. 6:00am 3. logoff 4. stay away from that account until **after** the time from 2., then log in again OBSERVED RESULT After logging in, notifications are unmuted but the sound for notifications, for example the "pop" sound from kmix when you change volume, is **not** EXPECTED RESULT I expect **all** notifications to be unmuted, including sound SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220428 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Workaround: manually mute and then unmute notifications Fun fact: this can easily lead to believing that sound has stopped working, triggering some longish bug search o.0. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 453037] New: on first start after log in, kmail starts all imap agents in "offline mode"
https://bugs.kde.org/show_bug.cgi?id=453037 Bug ID: 453037 Summary: on first start after log in, kmail starts all imap agents in "offline mode" Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. reboot or relogin to plasma 2. start kontact OBSERVED RESULT all imap connections are in offline mode EXPECTED RESULT I expect the imap ressources to be in online mode when the connection to the mailserver is available at startup time SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220424 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 449239] New: kmail treats background color of plaintext emails as html mail background
https://bugs.kde.org/show_bug.cgi?id=449239 Bug ID: 449239 Summary: kmail treats background color of plaintext emails as html mail background Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. configure kmails color settings as follows: [x] Eigene farben benutzen (use own colors) [X] Farbe der ursprünglichen HTML mail nicht ändern (don't change colors in html mails) 2. open a plaintext email OBSERVED RESULT The text is colord according to the customized colors but the background of a PLAINTEXT email is switched to white, making the whole mess unreadable in my case. EXPECTED RESULT I would expect kmail to change all colors, including the background, if the mail is plaintext only. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220125 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION The problem here is using a Plasma-wide dark color scheme - you HAVE to have kmail adjust the colors, or mails will be unreadable. but there seems to be no working combination of these two options that works equally well with plaintext- and html emails. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 447341] New: Saved UI settings are not used
https://bugs.kde.org/show_bug.cgi?id=447341 Bug ID: 447341 Summary: Saved UI settings are not used Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Main Application Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY *** I have changed the toolbar settings and turned off the menu but when I restart kopete the windows "comes back" using the defaults, i.e. menu is visible, toolbar icon size is medium with text *** STEPS TO REPRODUCE 1. hide the menu (ctrl-m) 2. change toolbar icons to "small, no text" 3. quit kopete with ctrl-q 4. start kopete OBSERVED RESULT Kopete uses standard size toolbar icons with text, and has the menu visible EXPECTED RESULT The kopete main window should behave as configured above. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211218 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 447340] New: saved login settings are not used at startup
https://bugs.kde.org/show_bug.cgi?id=447340 Bug ID: 447340 Summary: saved login settings are not used at startup Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY *** I have set kopete to log in my messenger accounts on startup, but it does not do it. *** STEPS TO REPRODUCE 1. configure kopete to log in on start 2. quit kopete while online 3. start kopete again OBSERVED RESULT Accounts are not being logged in EXPECTED RESULT Accounts should be logged in if configured to do so on start SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211218 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 --- Comment #22 from Mathias Homann --- Created attachment 144033 --> https://bugs.kde.org/attachment.cgi?id=144033=edit New crash information added by DrKonqi choqok (1.7.0) using Qt 5.15.2 - What I was doing when the application crashed: quit chokoq with ctrl-q. this reproducibly happens EVERY time chocoq is closed. -- Backtrace (Reduced): #6 QStackedWidget::indexOf (this=0x4fcd4efb80a92cdd, widget=0x55e3864a31e0) at widgets/qstackedwidget.h:86 #7 0x7f591f8e5ff1 in Choqok::UI::ChoqokTabBar::removePage (this=0x55e3843f8030, widget=) at /usr/src/debug/choqok-1.7.0-3.2.x86_64/libchoqok/ui/choqoktabbar.cpp:411 #8 0x7f591e318043 in QtPrivate::QSlotObjectBase::call (a=0x7ffe4251b2c0, r=0x55e3843f8030, this=0x55e3864a9e20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x55e3864a31e0, signal_index=0, argv=0x7ffe4251b2c0) at kernel/qobject.cpp:3886 [...] #11 0x7f591e3115bf in QObject::destroyed (this=this@entry=0x55e3864a31e0, _t1=, _t1@entry=0x55e3864a31e0) at .moc/moc_qobject.cpp:219 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440623] Scheduled "do not disturb" mode doesn't enable sounds when coming out of "do not disturb"
https://bugs.kde.org/show_bug.cgi?id=440623 --- Comment #4 from Mathias Homann --- (In reply to Mathias Homann from comment #3) > (In reply to Kai Uwe Broulik from comment #1) > > Did you restart your computer or plasmashell in the meantime? > > I've been having this issue for some weeks by now, so yes - rebooted any > number of times. It doesn't seem to make a difference whether there's a > reboot between going into a timed "do not disturb" and going back out, or > not. after a bit more testing it looks as if coming out of "do not disturb" works just fine as long as there's no restart between going quiet and coming back to normal... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440623] Scheduled "do not disturb" mode doesn't enable sounds when coming out of "do not disturb"
https://bugs.kde.org/show_bug.cgi?id=440623 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Mathias Homann --- (In reply to Kai Uwe Broulik from comment #1) > Did you restart your computer or plasmashell in the meantime? I've been having this issue for some weeks by now, so yes - rebooted any number of times. It doesn't seem to make a difference whether there's a reboot between going into a timed "do not disturb" and going back out, or not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 440623] New: Scheduled "do not disturb" mode doesn't enable sounds when coming out of "do not disturb"
https://bugs.kde.org/show_bug.cgi?id=440623
Bug ID: 440623
Summary: Scheduled "do not disturb" mode doesn't enable sounds
when coming out of "do not disturb"
Product: frameworks-knotifications
Version: 5.84.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: mathias.hom...@opensuse.org
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
I like the option of disabling notifications until a fixed time ("Do not
disturb until monday morning"). But when I use it and the time for turning
notifications back on has been reached, sounds are not turned back on.
STEPS TO REPRODUCE
1. Disable notifications for some period of time
2. Wait
3. Trigger some notification and notice that there is no sound with the
notification. (The easiest trigger is to hover the mousewheel over the kmix
icon in one's tray and use the mouse wheel to change the volume)
OBSERVED RESULT
The notifications show on screen but without a sound
EXPECTED RESULT
I would expect the sound to be turned back on as well as the popups.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210802
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
Kernel Version: 5.13.6-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 437578] Context menu appear in wrong position when there is a secondary monitor on top or left
https://bugs.kde.org/show_bug.cgi?id=437578 --- Comment #8 from Mathias Homann --- same here: primary is on the right, secondary is on the left - right-clicking an icon on the right screen pops open the context menu on the left screen. Operating System: openSUSE Tumbleweed 20210611 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437578] Context menu appear in wrong position when there is a secondary monitor on top or left
https://bugs.kde.org/show_bug.cgi?id=437578 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #7 from Mathias Homann --- Created attachment 139284 --> https://bugs.kde.org/attachment.cgi?id=139284=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 --- Comment #43 from Mathias Homann --- you do realize that a two year old copy of the GeoIP informations is about as useful as not having any at all? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437234] New: unable to authorize with github due to 2 factor authentication
https://bugs.kde.org/show_bug.cgi?id=437234 Bug ID: 437234 Summary: unable to authorize with github due to 2 factor authentication Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Project provider: Github Assignee: kdevelop-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY I can't use the github project provider plugin because my github account is set up with two factor authentication STEPS TO REPRODUCE 1. Enable 2FA on your github account 2. try to authorize your github account from within kdevelop OBSERVED RESULT "Authorization failed" EXPECTED RESULT I would expect a popup asking for the 2FA pin SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210515 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.3-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437233] New: Unable to clone from github with ssh
https://bugs.kde.org/show_bug.cgi?id=437233 Bug ID: 437233 Summary: Unable to clone from github with ssh Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VCS: Git Assignee: kdevelop-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY I can't clone a project from github STEPS TO REPRODUCE 1. start a new session 2. click on "fetch project" 3. enter project details, the git address has to be the ssh "version" OBSERVED RESULT kdevelop messes up the url and fails to fetch the project EXPECTED RESULT it should work - write access with ssh is not such an uncommon thing after all SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210515 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.3-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Output from trying to clone the project: /home/mathias/work> git clone --progress -- file:///home/mathias/g...@github.com:lemmy04/phoenix-firestorm-lgpl.git /home/mathias/work/phoenix-firestorm-lgpl.git Command exited with value 128. Cloning into '/home/mathias/work/phoenix-firestorm-lgpl.git'... fatal: '/home/mathias/g...@github.com:lemmy04/phoenix-firestorm-lgpl.git' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Command finished with error UnknownError. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 --- Comment #1 from Mathias Homann --- Created attachment 138106 --> https://bugs.kde.org/attachment.cgi?id=138106=edit New crash information added by DrKonqi kopete (1.13.0) using Qt 5.15.2 - What I was doing when the application crashed: again, crash on exit. there is no additional iformation to be added. -- Backtrace (Reduced): #4 KHTMLPart::begin(QUrl const&, int, int) (this=this@entry=0x557e2be9af40, url=..., xOffset=xOffset@entry=0, yOffset=yOffset@entry=0) at /usr/src/debug/khtml-5.81.0-lp152.218.1.x86_64/src/khtml_part.cpp:2074 #5 0x7f47aee2b037 in ChatMessagePart::writeTemplate() (this=this@entry=0x557e2be9af40) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1291 #6 0x7f47aee328ad in ChatMessagePart::changeStyle() (this=0x557e2be9af40) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1269 #7 0x7f47aee27185 in ChatMessagePart::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/build/kopete/chatwindow/kopetechatwindow_shared_autogen/EWIEGA46WW/moc_chatmessagepart.cpp:238 #8 0x7f47ddbaf63b in QObject::event(QEvent*) (this=0x557e2be9af40, e=0x557e2c152500) at kernel/qobject.cpp:1314 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436516] New: Kopete does nto start as "online" even when configured to do so
https://bugs.kde.org/show_bug.cgi?id=436516 Bug ID: 436516 Summary: Kopete does nto start as "online" even when configured to do so Product: kopete Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Kopete does nto start as "online" even when configured to do so STEPS TO REPRODUCE 1. start kopete 2. configure the startup statzs to be "online" 3. restart kopete OBSERVED RESULT kopete does not log in to your messenger accounts even when the "startup state" setting does indeed say "online" EXPECTED RESULT I would expect this to work. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436514] New: kopete does not change UI settings on exit
https://bugs.kde.org/show_bug.cgi?id=436514 Bug ID: 436514 Summary: kopete does not change UI settings on exit Product: kopete Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Kopete 1.13 does not save changed UI settings STEPS TO REPRODUCE 1. start kopete 2. change some UI settings, i.e. hide the menu, change the toolbar layout, etc 3. quit kopete 4. start kopete OBSERVED RESULT the changes are gone EXPECTED RESULT i would expect such changes to be saved in the settings file. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.72-preempt OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] New: kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Bug ID: 436513 Summary: kopete crashed on exit Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.3.18-lp152.72-preempt x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: kopete crashed on exit. on stdout i had literally hundreds of lines like this: QFSFileEngine::open: No file name specified The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #4 KHTMLPart::begin(QUrl const&, int, int) (this=this@entry=0x5577f82a9320, url=..., xOffset=xOffset@entry=0, yOffset=yOffset@entry=0) at /usr/src/debug/khtml-5.81.0-lp152.218.1.x86_64/src/khtml_part.cpp:2074 #5 0x7fe44789f037 in ChatMessagePart::writeTemplate() (this=this@entry=0x5577f82a9320) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1291 #6 0x7fe4478a68ad in ChatMessagePart::changeStyle() (this=0x5577f82a9320) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/chatwindow/chatmessagepart.cpp:1269 #7 0x7fe44789b185 in ChatMessagePart::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/build/kopete/chatwindow/kopetechatwindow_shared_autogen/EWIEGA46WW/moc_chatmessagepart.cpp:238 #8 0x7fe47676f63b in QObject::event(QEvent*) (this=0x5577f82a9320, e=0x5577f825c990) at kernel/qobject.cpp:1314 #9 0x7fe4776e037c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5577f6344be0, receiver=receiver@entry=0x5577f82a9320, e=e@entry=0x5577f825c990) at kernel/qapplication.cpp:3632 #10 0x7fe4776e7170 in QApplication::notify(QObject*, QEvent*) (this=0x7fff3c103f20, receiver=0x5577f82a9320, e=0x5577f825c990) at kernel/qapplication.cpp:3156 #11 0x7fe47673b443 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5577f82a9320, event=0x5577f825c990) at kernel/qcoreapplication.cpp:1063 #12 0x7fe47673b61e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=receiver@entry=0x5577f82a9320, event=event@entry=0x5577f825c990) at kernel/qcoreapplication.cpp:1458 #13 0x7fe47673de61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5577f631b0d0) at kernel/qcoreapplication.cpp:1817 #14 0x7fe47673e3e8 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1676 #15 0x7fe47679e523 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5577f6486940) at kernel/qeventdispatcher_glib.cpp:277 #16 0x7fe46e000624 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x7fe46e0009c0 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7fe46e000a4c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7fe47679dbcc in QEventDispatcherGlib::processEvents(QFlags) (this=0x5577f6495520, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #20 0x7fe476739cca in QEventLoop::exec(QFlags) (this=this@entry=0x7fff3c103e40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #21 0x7fe4767434c7 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1371 #22 0x5577f439299b in main(int, char**) (argc=, argv=) at /usr/src/debug/kopete-21.04.0-lp152.2.4.x86_64/kopete/main.cpp:121 [Inferior 1 (process 8864) detached] The reporter indicates this bug may be a duplicate of or related to bug 393807. Possible duplicates by query: bug 409464, bug 401181, bug 400283, bug 393807, bug 393662. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 436256] New: kontact crashed on quit
https://bugs.kde.org/show_bug.cgi?id=436256 Bug ID: 436256 Summary: kontact crashed on quit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.17.0 (21.04.0)) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.3.18-lp152.72-preempt x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: Kontact crashed as I closed the application - no error message of any kind, just crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f07661906f4 in QTabWidget::count() const (this=0x5572bd28ed30) at widgets/qtabwidget.cpp:1212 #5 0x7f06d175d9bf in MessageList::Pane::Private::updateTabControls() (this=0x5572bbb05510) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/pane.cpp:846 #6 0x7f076505bb57 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdb3314d10, r=0x5572bbba5890, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x5572bb96cbb0, signal_index=3, argv=0x7ffdb3314d10) at kernel/qobject.cpp:3886 #8 0x7f0765055012 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5572bb96cbb0, m=m@entry=0x7f0762909f20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #9 0x7f07626bfc00 in KCoreConfigSkeleton::configChanged() (this=this@entry=0x5572bb96cbb0) at /usr/src/debug/kconfig-5.81.0-lp152.256.1.x86_64/build/src/core/KF5ConfigCore_autogen/EWIEGA46WW/moc_kcoreconfigskeleton.cpp:154 #10 0x7f07626e68ed in KCoreConfigSkeleton::save() (this=0x5572bb96cbb0) at /usr/src/debug/kconfig-5.81.0-lp152.256.1.x86_64/src/core/kcoreconfigskeleton.cpp:1244 #11 0x7f06d16f2668 in MessageList::Core::Manager::saveGlobalConfiguration() (this=0x5572bbc04360) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:943 #12 MessageList::Core::Manager::saveConfiguration() (this=this@entry=0x5572bbc04360) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:948 #13 0x7f06d16f2af7 in MessageList::Core::Manager::~Manager() (this=0x5572bbc04360, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:59 #14 0x7f06d16f2c09 in MessageList::Core::Manager::~Manager() (this=0x5572bbc04360, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:66 #15 0x7f06d16ee516 in MessageList::Core::Manager::unregisterWidget(MessageList::Core::Widget*) (pWidget=, pWidget@entry=0x5572bb9d3bd0) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:87 #16 0x7f06d173cd8d in MessageList::Core::Widget::~Widget() (this=0x5572bb9d3bd0, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/widgetbase.cpp:152 #17 0x7f06d176aa39 in MessageList::Widget::~Widget() (this=0x5572bb9d3bd0, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/widget.cpp:86 #18 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bb7f41c0) at kernel/qobject.cpp:2104 #19 0x7f0765fff576 in QWidget::~QWidget() (this=0x5572bbbaa730, __in_chrg=) at kernel/qwidget.cpp:1522 #20 0x7f076616dac9 in QStackedWidget::~QStackedWidget() (this=0x5572bbbaa730, __in_chrg=) at widgets/qstackedwidget.cpp:147 #21 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bbce6500) at kernel/qobject.cpp:2104 #22 0x7f0765fff576 in QWidget::~QWidget() (this=0x5572bbba5890, __in_chrg=) at kernel/qwidget.cpp:1522 #23 0x7f06d26b6d71 in CollectionPane::~CollectionPane() (this=0x5572bbba5890, __in_chrg=) at /usr/src/debug/kmail-21.04.0-lp152.185.1.x86_64/src/widgets/collectionpane.h:13 #24 CollectionPane::~CollectionPane() (this=0x5572bbba5890, __in_chrg=) at /usr/src/debug/kmail-21.04.0-lp152.185.1.x86_64/src/widgets/collectionpane.h:13 #25 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bbb80190) at kernel/qobject.cpp:2104 #26 0x7f0765fff576 in QWidget::~QWidget() (this=0x5572bbb643b0, __in_chrg=) at kernel/qwidget.cpp:1522 #27 0x7f076616ccb9 in QSplitter::~QSplitter() (this=0x5572bbb643b0, __in_chrg=) at widgets/qsplitter.cpp:979 #28 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bba7b1f0) at
[kontact] [Bug 435643] New: akonadi mail dispatcher agent fails to store the password for smtp auth permanently
https://bugs.kde.org/show_bug.cgi?id=435643 Bug ID: 435643 Summary: akonadi mail dispatcher agent fails to store the password for smtp auth permanently Product: kontact Version: 5.16.80 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY my mailaccounts all need smtp auth - kmail fails to remember the password, and then takes several minutes to time out and retry STEPS TO REPRODUCE 1. have a mail account that requires smtp auth 2. configure kmail accordingly 3. try to send mail OBSERVED RESULT kmail asks for the smtp password, then sits there for minutes doing nothing. Finally a pop up appears, saying "the remote has closed the connection", after that sending mail works fine until the next reboot. EXPECTED RESULT I would expect the checkbox "store password" to ... make kmail store the password. Also, I'd expect kmail to immediately retry the sending process, not after a timeout of several minutes. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.69-default OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION - other email clients work fine with my server... thunderbird on windows or linux, android phones, k9mail on android, iphones, you name it, it works. Just kmail collapses on me. severity: grave because a mail client that can't send mail reliably is DEAD IN THE WATER. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433141] ksysguardd plasmoids are strangely "bilingual", leading to plasmoids not working
https://bugs.kde.org/show_bug.cgi?id=433141 Mathias Homann changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #6 from Mathias Homann --- other ksysguard plasmoids seem to work fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433141] ksysguardd plasmoids are strangely "bilingual", leading to plasmoids not working
https://bugs.kde.org/show_bug.cgi?id=433141 --- Comment #3 from Mathias Homann --- (In reply to Mathias Homann from comment #2) > at least the part about the disk usage plasmoind displaying "Linux > Filesystem" instead of the device or mountpoint has been solved - the > filesystems in question did not have a file system label. > I believe that should actually be in the documentation for the plasmoid > somewhere. in fact, what happened to using the actual mountpoint? That would be much more informative. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 433141] ksysguardd plasmoids are strangely "bilingual", leading to plasmoids not working
https://bugs.kde.org/show_bug.cgi?id=433141 --- Comment #2 from Mathias Homann --- at least the part about the disk usage plasmoind displaying "Linux Filesystem" instead of the device or mountpoint has been solved - the filesystems in question did not have a file system label. I believe that should actually be in the documentation for the plasmoid somewhere. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 433141] ksysguardd plasmoids are strangely "bilingual", leading to plasmoids not working
https://bugs.kde.org/show_bug.cgi?id=433141 --- Comment #1 from Mathias Homann --- Created attachment 135814 --> https://bugs.kde.org/attachment.cgi?id=135814=edit screenshot of plasmoids on computer 2 Specifically, compare the "disk usage" plasmoid in both screenshots. Both computers have their storage set up the same way: one physical harddisk, all filesystems are logical volumes in LVM in the same volumegroup, even the names are similar, for example the root filesystem is /dev/system/rootvol on both computers. Also, the user running the desktop is member of the same groups (wheel, disk, and all that) on both systems. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 433141] New: ksysguardd plasmoids are strangely "bilingual", leading to plasmoids not working
https://bugs.kde.org/show_bug.cgi?id=433141 Bug ID: 433141 Summary: ksysguardd plasmoids are strangely "bilingual", leading to plasmoids not working Product: ksysguard Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasmoid / Applet Assignee: ksysguard-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: plasma-b...@kde.org Target Milestone: --- Created attachment 135813 --> https://bugs.kde.org/attachment.cgi?id=135813=edit screenshot of plasmoids on computer 1 SUMMARY ksysguardd plasmoids are "bilingual", leading to some values not being monitorable since the plasmoid seems to expect german but the underlying tools deliver english output. STEPS TO REPRODUCE 1. ? 2. ? 3. ? ... i haven't found any way to clearly reproduce it. I have two systems both running the same versions of packages (I ran rpm -qa | sort -V on both and fed the output into diff), and the behaviour of ksysguardd plasmoids is broken on both, but differently. OBSERVED RESULT Plasmoids display no values, or values with german (unusable) descriptions. I've attached two screenshots from my two desktops which make it much more clear. EXPECTED RESULT plasmoids should consistently use the same language all over, and consistently monitor and display system values. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.63-default OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 430652] New: Repeating tasks can't be created unless you put a start and due date in
https://bugs.kde.org/show_bug.cgi?id=430652 Bug ID: 430652 Summary: Repeating tasks can't be created unless you put a start and due date in Product: kontact Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY I can't create a repeating task without a start and finish time and date STEPS TO REPRODUCE 1. create a task 2. do NOT specify a start and end time 3. try to set the task to repeat OBSERVED RESULT everything in the "repeats" tab is disabled EXPECTED RESULT I expect to be able to create a task that (for example) repeats every friday without giving it a start and end time. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.57-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION calendar is stored in nextcloud -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 430651] New: Weekly repeating tasks can only be created on the weekday that they happen on
https://bugs.kde.org/show_bug.cgi?id=430651 Bug ID: 430651 Summary: Weekly repeating tasks can only be created on the weekday that they happen on Product: kontact Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Weekly repeating tasks can only be created on the day they repeat on STEPS TO REPRODUCE 1. create a task in kontact 2. Set start and due date to some day in the future 3. set it to repeat weekly OBSERVED RESULT The weekday that is "today" is always in the list of repetitions and can not be removed EXPECTED RESULT I expect to be able to create a task that repeats only on fridays on any day of the week, not just on fridays SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.57-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION calendar is stored in nextcloud -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377324] akonadi server crashed when trying to create a task in my calendar
https://bugs.kde.org/show_bug.cgi?id=377324 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Mathias Homann --- this has not happened anymore for a while... -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393613] kopete crashes on exit, does not save settings or kontact list
https://bugs.kde.org/show_bug.cgi?id=393613 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #3 from Mathias Homann --- still happens every time. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393662] Kopete Crashes on Program exit
https://bugs.kde.org/show_bug.cgi?id=393662 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Mathias Homann --- it still happens. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #22 from Mathias Homann --- (In reply to Erik Kurzinger from comment #19) > If you do so, it would help if you could run the nvidia-bug-report.sh script > that we distribute with the driver and attach the file it generates. mail sent. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #21 from Mathias Homann --- Created attachment 133791 --> https://bugs.kde.org/attachment.cgi?id=133791=edit nvidia bug report logfile -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #20 from Mathias Homann --- I'm running glxspheres, and "nvidia-smi dmon" and "nvidia-smi pmon" both show only zeros for sm,%, mem%, power consumption, and encoder/decoder usage, but running "nvidia-smi" without any parameters shows the actual usage stats. Is that a bug, or not? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 403875] can't open https links
https://bugs.kde.org/show_bug.cgi?id=403875 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Mathias Homann --- I have akregator 5.15.3 here, and with some blogs, all links work and with some, http links don't... here's another test case: add this feed: http://seraphimsl.com/feed/atom/ and try out any links that point at urls like this: http://maps.secondlife.com/secondlife/Follys End/33/231/2001 those still don't work, I have to go the "log way around" and open the post and use the link from there. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 249976] kompare complains about malformed diffs
https://bugs.kde.org/show_bug.cgi?id=249976 Mathias Homann changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #29 from Mathias Homann --- actually that last comment's invalid - the reason for the error *was* because of some binary files... -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 249976] kompare complains about malformed diffs
https://bugs.kde.org/show_bug.cgi?id=249976 --- Comment #28 from Mathias Homann --- by the way, my script to run diff with LANG="" doesn't help anymore for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 249976] kompare complains about malformed diffs
https://bugs.kde.org/show_bug.cgi?id=249976 Mathias Homann changed: What|Removed |Added Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #27 from Mathias Homann --- (In reply to Kevin Kofler from comment #26) > But Kompare can also be used to view diffs that are already in a .diff file. > I cannot control how diff was run in that case. ...in which case we can tell the user about it. But that's no reason not to "do it right" when you *can* control how diff is run. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 428714] New: kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=428714 Bug ID: 428714 Summary: kontact crash on exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.15.2 (20.08.2)) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.3.18-lp152.47-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: quitting kontact makes it crash - are my settings saved? ((I don't have anything else to say about it but I can't file the report unless this text is long enough which is weird.)) The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [New LWP 7637] [New LWP 7638] [New LWP 7645] [New LWP 7647] [New LWP 7653] [New LWP 7654] [New LWP 7655] [New LWP 7656] [New LWP 7657] [New LWP 7659] [New LWP 7660] [New LWP 7682] [New LWP 7684] [New LWP 7724] [New LWP 7726] [New LWP 8500] [New LWP 8501] [New LWP 8502] [New LWP 8503] [New LWP 8504] [New LWP 8505] [New LWP 8506] [New LWP 8507] [New LWP 8559] [New LWP 15423] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f7e03f206db in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f7e076bf480 (LWP 7631))] Thread 26 (Thread 0x7f7d13fff700 (LWP 15423)): #0 0x7f7df8b74bab in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7dfd1d3f76 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x0d03 in () #3 0x098179f8 in () #4 0x0ce2 in () #5 0x098179f8 in () #6 0x in () Thread 25 (Thread 0x7f7d1bfff700 (LWP 8559)): #0 0x7f7df8b7487d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7dfd1d3e8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 24 (Thread 0x7f7d36ffd700 (LWP 8507)): #0 0x7f7e03f25839 in syscall () at /lib64/libc.so.6 #1 0x7f7e046a38e4 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:116 #2 0x7f7e046a38e4 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:135 #3 0x7f7e046a38e4 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 0x7f7e046a38e4 in futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 0x7f7e046a38e4 in QSemaphore::acquire(int) (this=0x7f7df9cc6900, n=) at thread/qsemaphore.cpp:326 #6 0x7f7df99ffa64 in () at /usr/lib64/libQt5Network.so.5 #7 0x7f7e046a14ac in QThreadPrivate::start(void*) (arg=0x7f7df9cc68e0) at thread/qthread_unix.cpp:329 #8 0x7f7df8b6e4f9 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7e03f2afbf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f7d377fe700 (LWP 8506)): #0 0x7f7df62afad4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f7df62641b1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7df6264720 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7df626488c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7e048f9ddb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7d48002de0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7e04895eba in QEventLoop::exec(QFlags) (this=this@entry=0x7f7d377fdbb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #6 0x7f7e0469ff97 in QThread::exec() (this=) at thread/qthread.cpp:547 #7 0x7f7e046a14ac in QThreadPrivate::start(void*) (arg=0x555fe9e7f8c0) at thread/qthread_unix.cpp:329 #8 0x7f7df8b6e4f9 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7e03f2afbf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f7d37fff700 (LWP 8505)): #0 0x7f7e03f206db in poll () at /lib64/libc.so.6 #1 0x7f7df6264779 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7df626488c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7e048f9ddb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7d540031e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7e04895eba in QEventLoop::exec(QFlags) (this=this@entry=0x7f7d37ffebb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #5 0x7f7e0469ff97 in QThread::exec() (this=) at thread/qthread.cpp:547 #6 0x7f7e046a14ac in
[kontact] [Bug 428627] New: "Combined view" has stopped working
https://bugs.kde.org/show_bug.cgi?id=428627 Bug ID: 428627 Summary: "Combined view" has stopped working Product: kontact Version: 5.15.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: akregator Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY When I use "Combined view" for my feeds the window stays empty STEPS TO REPRODUCE 1. Set up akregator with many different feeds 2. Switch to "combined view" OBSERVED RESULT The view pane stays empty EXPECTED RESULT The view pane should display all new posts from one feed in one view SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.3.18-lp152.47-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Possible regression: it had happened one already almost a year ago, see #416114 which was never acted upon -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #18 from Mathias Homann --- (In reply to Mathias Homann from comment #17) > (In reply to Erik Kurzinger from comment #14) > > Bar1 is the portion of video memory that can be accessed by the CPU over > > PCIe. > > > > And yes, a graphical desktop environment would be expected to utilize GPU > > memory bandwidth, but only if you're actually interacting with it. If it's > > just sitting idle then it wouldn't be surprising that nvidia-smi reportes 0% > > mem utilization. > > > > Could you try running "nvidia-smi dmon" and, moving windows around or > > activating some desktop effects? This should cause the mem and SM values to > > increase, unless there really is a bug. > > hm. > > so on my desktop pc (the one where monitoring doesn't work) I just ran > "nvidia-smi dmon" in one xterm, and then dragged another one around all over > my two screens, with the "wobbly windows when moving" effect turned up all > the way to max - and the values stayed zero. > > on the other hand, on my laptop which uses optimus technology and is set up > for prime render offloading, so to my understanding the nvidia GPU should > really not do anything unless I run a binary explicitely on that card, > nvidia-dmon reports values for sm and mem even when the thing really does > nothing, GPU-wise... so something seems to be off... ok i correct this - on my laptop nvidia-smi reports as expected. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #17 from Mathias Homann --- (In reply to Erik Kurzinger from comment #14) > Bar1 is the portion of video memory that can be accessed by the CPU over > PCIe. > > And yes, a graphical desktop environment would be expected to utilize GPU > memory bandwidth, but only if you're actually interacting with it. If it's > just sitting idle then it wouldn't be surprising that nvidia-smi reportes 0% > mem utilization. > > Could you try running "nvidia-smi dmon" and, moving windows around or > activating some desktop effects? This should cause the mem and SM values to > increase, unless there really is a bug. hm. so on my desktop pc (the one where monitoring doesn't work) I just ran "nvidia-smi dmon" in one xterm, and then dragged another one around all over my two screens, with the "wobbly windows when moving" effect turned up all the way to max - and the values stayed zero. on the other hand, on my laptop which uses optimus technology and is set up for prime render offloading, so to my understanding the nvidia GPU should really not do anything unless I run a binary explicitely on that card, nvidia-dmon reports values for sm and mem even when the thing really does nothing, GPU-wise... so something seems to be off... -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #13 from Mathias Homann --- waitaminute. when you're running a graphical desktop with all kind of openGL based eye candy, wouldn't the BANDWIDTH greater than zero? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #12 from Mathias Homann --- ...what is bar1? and is there a way to have nvidia-smi report only the total framebuffer memory size? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #9 from Mathias Homann --- I just got the next nvidia driver through openSUSE updates, now I have 450.80.02. Same problem. Actually it appears to me as if nvidia-smi-[dp]mon is broken, nvidia-smi without any further parameters shows the memory consumption just fine: lemmy@kumiko:~> nvidia-smi Thu Oct 15 07:19:02 2020 +-+ | NVIDIA-SMI 450.80.02Driver Version: 450.80.02CUDA Version: 11.0 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce GTX 1050Off | :01:00.0 On | N/A | | 35% 42CP0N/A / 75W |389MiB / 1997MiB | 0% Default | | | | N/A | +---+--+--+ -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #8 from Mathias Homann --- interesting detail: on my laptop which also uses a nvidia card "nvidia-smi dmon" properly reports memory usage... Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #7 from Mathias Homann --- (In reply to David Edmundson from comment #2) > Edit, > > nvidia-smi dmon oops. lemmy@kumiko:~> nvidia-smi dmon # gpu pwr gtemp mtempsm mem enc dec mclk pclk # Idx W C C % % % % MHz MHz 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -44 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 0 -43 - 0 0 - - 3504 1784 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #6 from Mathias Homann --- I just checked - it's not a "root thing". -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Mathias Homann --- lemmy@kumiko:/tmp> nvidia-smi pmon # gpupid typesm mem enc dec command # Idx # C/G % % % % name 0 2440 G - - - - X 0 3824 G - - - - kwin_x11 0 4140 G - - - - akonadi_archive 0 4145 G - - - - akonadi_google_ 0 4148 G - - - - akonadi_imap_re 0 4151 G - - - - akonadi_imap_re 0 4152 G - - - - akonadi_imap_re 0 4154 G - - - - akonadi_imap_re 0 4157 G - - - - akonadi_imap_re 0 4158 G - - - - akonadi_imap_re 0 4160 G - - - - akonadi_imap_re 0 4163 G - - - - akonadi_imap_re 0 4173 G - - - - akonadi_mailfil 0 4186 G - - - - akonadi_sendlat 0 4187 G - - - - akonadi_unified 0 4421 G - - - - nextcloud 0 4875 G - - - - Keybase --type= 0 24732 G - - - - krunner 0 30109 G - - - - plasmashell 0 2440 G - - - - X 0 3824 G - - - - kwin_x11 0 4140 G - - - - akonadi_archive 0 4145 G - - - - akonadi_google_ 0 4148 G - - - - akonadi_imap_re 0 4151 G - - - - akonadi_imap_re 0 4152 G - - - - akonadi_imap_re 0 4154 G - - - - akonadi_imap_re 0 4157 G - - - - akonadi_imap_re 0 4158 G - - - - akonadi_imap_re 0 4160 G - - - - akonadi_imap_re 0 4163 G - - - - akonadi_imap_re 0 4173 G - - - - akonadi_mailfil 0 4186 G - - - - akonadi_sendlat 0 4187 G - - - - akonadi_unified 0 4421 G - - - - nextcloud 0 4875 G - - - - Keybase --type= 0 24732 G - - - - krunner 0 30109 G - - - - plasmashell 0 2440 G - - - - X 0 3824 G - - - - kwin_x11 0 4140 G - - - - akonadi_archive 0 4145 G - - - - akonadi_google_ 0 4148 G - - - - akonadi_imap_re 0 4151 G - - - - akonadi_imap_re -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #5 from Mathias Homann --- looks like nvidia-smi is broken...? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #3 from Mathias Homann --- Created attachment 132303 --> https://bugs.kde.org/attachment.cgi?id=132303=edit screenshot of GPU monitoring widget Screenshot who -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] New: monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 Bug ID: 427603 Summary: monitoring my NVIDIA does not show any info except temperature Product: ksysguard Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create a ksysguardd widget on desktop, line diagram style 2. Add Sensors for "GPU 1 Memory Usage %", "GPU 1 Shared Memory Usage %", "GPU 1 Power Usage" and "GPU 1 Temperature" 3. Hit "Apply" OBSERVED RESULT Only the GPU termperature display shows any data, the rest stays on 0 EXPECTED RESULT I'd expect all sensors to display data - they used to until not too long ago. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.3.18-lp152.44-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION NVIDIA Driver is 450.66 as provided by NVIDIA/openSUSE as rpm package -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #6 from Mathias Homann --- ...it just got weird. I have two computers running plasma, on both kmail is configured the same way, on computer #2 i can't reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #5 from Mathias Homann --- (In reply to stakanov.s from comment #4) > You said "TLS" so I suppose SSL/TLS on 587 as setting in Kmail as opposed to > STARTTLS? > > Just to avoid somebody else looses your time. ssl/tls on port 465. kmail autodetects it that way w/o problems. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #3 from Mathias Homann --- the mail server in question is my OWN mailserver, and I have not made any changes to it. The notification only showed up a few weeks ago after a huge KDE/Plasma upgrade. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #1 from Mathias Homann --- I found something to reproduce the weird "already authenticated" message. If I "fetch all mail" just before sending the message appears; If i don't, it doesnt (unless of course kmail had just now automatically fetched mail). -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 427432] New: Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 Bug ID: 427432 Summary: Weird message when sending mail Product: kontact Version: 5.15.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Every time I'm sending email I get a pop up that says: "5.5.1 Error: already authenticated", followed by another one that says "successfully sent" STEPS TO REPRODUCE 1. I don't know any other step than to send a mail... OBSERVED RESULT see above EXPECTED RESULT I'd expect EITHER sending to fail, OR to succeed, but not fail first, succeed right after... SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.3.18-lp152.44-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Email accounts are all IMAP, sending is smtp with TLS. No other mail client shows this weird behaviour, nothing on the server has been changed in years. -- You are receiving this mail because: You are watching all bug changes.
