[Discover] [Bug 381170] show security update status
https://bugs.kde.org/show_bug.cgi?id=381170 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #7 from Shai --- This is marked as fixed but I still can't tell which are the security updates -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381170] Show which updates are security updates
https://bugs.kde.org/show_bug.cgi?id=381170 Shai changed: What|Removed |Added Status|RESOLVED|REOPENED Summary|Show in notifier which |Show which updates are |updates are security|security updates |updates | Resolution|INTENTIONAL |--- Ever confirmed|0 |1 --- Comment #9 from Shai --- Indeed. But I think the expectation -- certainly mine, but also what I read in the Description -- is to show which updates are security updates in Discover, not in the notifier. Instead of marking each update accordingly, IIUC Aleix changed the whole page icon for updates to match that in the notifier. That does not add information. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 138506] Wish: Manually managed item folders
https://bugs.kde.org/show_bug.cgi?id=138506 Shai changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Shai --- "More than 5 years"... 14 and counting... I don't use Akregator regularly these days, so I no longer need this feature. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 --- Comment #16 from Shai --- (In reply to Alois Wohlschlager from comment #14) > Thank you for this information, this is quite helpful since we can now > determine what configuration can be applied to make it work. Notably, the > configuration created by GNOME contains the following settings in its > nmconnection file that the KDE one does not: > > group=ccmp; > pairwise=ccmp; > proto=rsn; > [...] > Can you try the following and report if and at what place things > begin to work? (You either have to set up a fresh connection or undo the > above command with 'nmcli connection modify WIFI-Share > 802-11-wireless-security.proto ""' (two double quotes at the end).) > > nmcli connection modify WIFI-Share 802-11-wireless-security.group ccmp > nmcli connection modify WIFI-Share 802-11-wireless-security.pairwise ccmp > nmcli connection modify WIFI-Share 802-11-wireless-security.proto rsn > After the second of these (nmcli connection modify WIFI-Share 802-11-wireless-security.pairwise ccmp) things started to work. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #13 from Shai --- I have a similar issue -- in my case, a set of Samsung Galaxy phones (S20 and S23) have been unable to connect for a few months; a laptop running Debian testing could. I finally got tired of it and searched, and found this post on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?id=293307 The original poster complains that his hotspot does not work when created from KDE, but doing the same from Gnome does make it work. The reply says to run: nmcli connection modify WIFI-Share 802-11-wireless-security.proto wpa where "WIFI-Share" is the name of the WIFI configuration created for the hotspot. I did that, and it solved the problem for me. I should note that I encountered the problem at first a couple of years ago, and then switching from wpa-supplicant to iwd mostly fixed things (it still had minor issues). But for several months, this stopped working too. Anyway, I find it hard to believe that the problem can be brushed aside as "not in plasma" when it works in Gnome. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 --- Comment #15 from Shai --- Hi, Thanks, this is very helpful! (In reply to Alois Wohlschlager from comment #14) > (In reply to Shai from comment #13) > > The reply says to run: > > > > nmcli connection modify WIFI-Share 802-11-wireless-security.proto wpa > > > > where "WIFI-Share" is the name of the WIFI configuration created for the > > hotspot. I did that, and it solved the problem for me. > > This is not a very good idea, since it disables WPA2 and only leaves you > with WPA. Thanks for the heads-up! > Can you try the following and report if and at what place things > begin to work? (You either have to set up a fresh connection or undo the > above command with 'nmcli connection modify WIFI-Share > 802-11-wireless-security.proto ""' (two double quotes at the end).) > > nmcli connection modify WIFI-Share 802-11-wireless-security.group ccmp > nmcli connection modify WIFI-Share 802-11-wireless-security.pairwise ccmp > nmcli connection modify WIFI-Share 802-11-wireless-security.proto rsn > Will check later, when it's more convenient. > > I should note that I encountered the problem at first a couple of years ago, > > and then switching from wpa-supplicant to iwd mostly fixed things (it still > > had minor issues). But for several months, this stopped working too. > > I wouldn't be surprised if the "several months" coincided with the release > of iwd 2.18, which introduced WPA3 support. Can you confirm this if > convenient? It would either mean that hostapd and iwd have the same bug, or > it's at a lower level (driver, firmware or hardware). > I can't be completely sure -- but I upgraded from iwd 2.17 to 2.19 on July 21, and removed iwd (that is, gave up on trying to make it work) on August 16 (the system providing the hotspot is also Debian testing). > > Anyway, I find it hard to believe that the problem can be brushed aside as > > "not in plasma" when it works in Gnome. > > The underlying bug unlikely to be in Plasma since the problem can be > reproduced with plain hostapd without adding weird settings. FWIW I don't have hostapd installed, and never heard of it before the searches I did yesterday. > That does not mean that Plasma can't add a workaround if an upstream fix > can't be > expected. Since you have figured out that it works in GNOME, that workaround > could even consist of setting whatever GNOME does to make it work. That makes perfect sense (except credit for finding that it works in Gnome should go to Vamp898 from the Arch Linux forum). Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Support for real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #257 from Shai --- (In reply to Nate Graham from comment #246) > (In reply to Lassi Väätämöinen from comment #245) > > From KDE perspective, the bug is fixed. It's the upstream that this depends > > on. So perhaps the upstream issue could be linked here. > > > > >this fix will actually reach no users before that date. > > > > What comes to this part, the real user-visible fix(es) will only show once > > the applications adopt this, which may be now, later, or never. So in that > > regard it doesn't make sense to keep this big open, as far as I see it. > > Yep, this is accurate and reflects the Bugzilla ticket lifecycle that KDE > uses. > > The next step is for client software (Plasma and apps) to implement support > now. So -- just to clarify -- are app-specific instances of this bug (e.g. https://bugs.kde.org/show_bug.cgi?id=461780 for konsole) supposed to stay open, or are they to be marked as duplicates of this bug (as has been done, it seems, in its earlier history)? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461780] Add option to restore tabs upon restart
https://bugs.kde.org/show_bug.cgi?id=461780 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #9 from Shai --- I'm not sure about the intention, but I suspect this bug should depend on https://bugs.kde.org/show_bug.cgi?id=436318. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388591] Rename malfunction
https://bugs.kde.org/show_bug.cgi?id=388591 Shai Gluskin changed: What|Removed |Added Version|5.8.0 |5.9.0 CC||s...@content2zero.com --- Comment #3 from Shai Gluskin --- "some people might want the order to refresh after each rename. I guess a corresponding checkbox in settings would be fair for everyone" That is exactly my situation. I sort on name and expect refresh after name change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503215] New: Screen not waking up after being turned off due to inactivity on Wayland with 240Hz monitor
https://bugs.kde.org/show_bug.cgi?id=503215 Bug ID: 503215 Summary: Screen not waking up after being turned off due to inactivity on Wayland with 240Hz monitor Classification: Plasma Product: kwin Version: 6.3.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: shai@proton.me Target Milestone: --- SUMMARY I am using KDE Plasma with Wayland on Arch Linux. I have a weird problem when the screen turns off due to inactivity. I have a Samsung Odyssey G65B monitor running in 2560x1440 resolution and 240Hz refresh rate. When I let the screen turn off due to inactivity, the monitor tells me it doesn't detect a signal, so it will go to standby mode in 60 seconds, which is normal. After it goes to standby mode, I shake the mouse to wake the system up. The screen flashes, which it usually does when being turned on or off, and I also hear KDE system sounds. However, instead of turning on, the screen tells me it can't detect a signal, and it goes back to standby mode. Shaking the mouse more causes more system sounds to play, but the screen won't wake up. I know the system does wake up, since I can blindly type my password to enter the desktop, and the keyboard lights up since its drivers take over. I can also blindly press a shortcut to open a terminal and type a command like `sudo reboot now`, and the system reboots. After reboot, everything is normal again. So the system does wake up and the desktop session works, but the screen doesn't pick up the signal. There are some weird conditions and consequences of this problem, which I am not able to understand. * The problem only happens on Wayland. If I switch to X11 and let the screen turn off and then wake it up, everything works fine. The screen wakes up, and I see the login screen. * The problem only happens on 240Hz. If I change the screen refresh rate to 120Hz or 60Hz, there is no problem. The screen wakes up, and I see the login screen. * Turning the monitor off and on usually doesn't fix anything, but there was one time it did make the screen wake up. I am not able to reproduce it consistently, though. * If I press Ctrl+Alt+F3 to go to a virtual console, the screen wakes up and goes to the virtual console. Pressing Ctrl+Alt+F1 after that to return to the desktop session fixes the problem, and I see the login screen. This and rebooting are the only consistent workarounds to this problem I found. As you see in SOFTWARE/OS VERSIONS below, I have an NVIDIA GeForce RTX 4070 SUPER GPU. I have the latest `nvidia`, `nvidia-utils`, and `lib32-nvidia-utils` packages installed for the drivers. I don't know if this problem is specific to Wayland, NVIDIA, or my Odyssey G65B monitor, or a combination of them, so I am not sure how easily other people could reproduce this problem, but I can reproduce it consistently using the following steps. STEPS TO REPRODUCE 1. Make sure to use a Wayland session and a 240Hz refresh rate monitor. 2. Let the screen turn off due to inactivity and let it go to standby mode. 3. Try to wake the system by moving the mouse or pressing the keyboard. OBSERVED RESULT KDE plays some system sounds, which seem to indicate that the system wakes up, and the monitor does act like it picks up a signal, but it doesn't get a signal and goes back to standby mode. The system is awake, however, and you can log in and operate it blindly. EXPECTED RESULT The screen wakes up and shows the login screen, so I can log in and continue the session. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kernel Version: 6.14.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 28 × Intel® Core™ i7-14700K Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070 SUPER Manufacturer: ASUS ADDITIONAL INFORMATION I first reported this issue in the Arch forum to try and find a solution: https://bbs.archlinux.org/viewtopic.php?pid=2238190#p2238190. There, I discovered most of the details that I report now (like the problem being specific to Wayland and 240Hz refresh rate), but I didn't find a solution, and the conclusion was that I should report this problem here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503215] Monitor not waking up after being turned off due to inactivity on Wayland even when Plasma is active
https://bugs.kde.org/show_bug.cgi?id=503215 --- Comment #3 from Shai Avraham --- I tested it on the LTS kernel (6.12.25), and it still happens. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 322459] Subject line not right-aligned when RTL (BiDi regression)
https://bugs.kde.org/show_bug.cgi?id=322459 Shai changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #10 from Shai --- Still as reported, with KMail 5.2.3, Using KDE Frameworks 5.25.0 and Qt 5.6.1 on Debian Testing. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 361435] New: Crash while going thrugh unread articles
https://bugs.kde.org/show_bug.cgi?id=361435 Bug ID: 361435 Summary: Crash while going thrugh unread articles Product: akregator Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: s...@platonix.com Application: akregator (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.7 Operating System: Linux 4.0.0-2-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Opened a feed with very many unread articles, and started going over them. At some point, when moving (with KB -- right arrow, "next article"), akregator crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 GetAt (nIndex=, this=0x3be9aa0) at ../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:54 #7 c4_Column::ReleaseSegment (this=0x3be9aa0, index_=) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:116 #8 0x7f4a02a98d6d in c4_Column::ReleaseAllSegments (this=this@entry=0x3be9aa0) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:124 #9 0x7f4a02a98dc1 in c4_Column::SetLocation (this=this@entry=0x3be9aa0, pos_=pos_@entry=-228961430, size_=size_@entry=125) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:142 #10 0x7f4a02aa5c03 in c4_SaveContext::CommitColumn (this=this@entry=0x7ffd46207400, col_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:819 #11 0x7f4a02aa1895 in c4_FormatB::Commit (this=0x24c86f0, ar_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:775 #12 0x7f4a02aa5cdd in c4_SaveContext::CommitSequence (this=this@entry=0x7ffd46207400, seq_=..., selfDesc_=selfDesc_@entry=false) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:841 #13 0x7f4a02aa269a in c4_FormatV::Commit (this=0x24c4790, ar_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1174 #14 0x7f4a02aa5cdd in c4_SaveContext::CommitSequence (this=this@entry=0x7ffd46207400, seq_=..., selfDesc_=selfDesc_@entry=true) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:841 #15 0x7f4a02aa62aa in c4_SaveContext::SaveIt (this=this@entry=0x7ffd46207400, root_=..., spacePtr_=spacePtr_@entry=0x24c7170, rootWalk_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:709 #16 0x7f4a02aa6619 in c4_Persist::Commit (this=0x24c7170, full_=) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:933 #17 0x7f4a02aa66c1 in c4_Persist::Commit (this=, full_=) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:935 #18 0x7f4a02aab51e in c4_Storage::Commit (this=, full_=full_@entry=false) at ../../../../akregator/plugins/mk4storage/metakit/src/store.cpp:361 #19 0x7f4a02ab0d7f in Akregator::Backend::FeedStorageMK4Impl::commit (this=0x208c860) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:181 #20 0x7f4a02ab6dd5 in Akregator::Backend::StorageMK4Impl::commit (this=0x1f9fe00) at ../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:178 #21 0x7f4a02ab633a in Akregator::Backend::StorageMK4Impl::slotCommit (this=0x1f9fe00) at ../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:283 #22 0x7f4a1bab038c in QMetaObject::activate (sender=sender@entry=0x9e9b6f0, m=m@entry=0x7f4a1bdfe540 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #23 0x7f4a1bab96ba in timeout (this=0x9e9b6f0) at .moc/release-shared/qtimer.moc:96 #24 QSingleShotTimer::timerEvent (this=0x9e9b6f0) at kernel/qtimer.cpp:317 #25 0x7f4a1bab4953 in QObject::event (this=0x9e9b6f0, e=) at kernel/qobject.cpp:1253 #26 0x7f4a1c4ba7bc in QApplicationPrivate::notify_helper (this=this@entry=0x1cf0e80, receiver=receiver@entry=0x9e9b6f0, e=e@entry=0x7ffd46207b10) at kernel/qapplication.cpp:4570 #27 0x7f4a1c4c12d8 in QApplication::notify (this=this@entry=0x7ffd46207f70, receiver=receiver@entry=0x9e9b6f0, e=e@entry=0x7ffd46207b10) at kernel/qapplication.cpp:4356 #28 0x7f4a1d2381aa in KApplication::notify (this=0x7ffd46207f70, receiver=0x9e9b6f0, event=0x7ffd46207b10) at ../../kdeui/kernel/kapplication.cpp:311 #29 0x7f4a1ba9b36d in QCoreApplication::notifyInternal (this=0x7ffd46207f70, receiver=0x9e9b6f0, event=event@entry=0x7ffd46207b10) at kernel/qcoreapplication.cpp:955 #30 0x7f4a1baccffb in sendEvent (event=0x7ffd46207b10, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #31 QTimerInfoList::activateTimers (this=0x1cf61a0) at kernel/qeventdispatcher_unix.cpp:621 #32 0x7f
