[khelpcenter] [Bug 484545] New: khelpcenter lost the find feature
https://bugs.kde.org/show_bug.cgi?id=484545 Bug ID: 484545 Summary: khelpcenter lost the find feature Classification: Applications Product: khelpcenter Version: 6.0.24021 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY khelpcenter used to have a Find/Search feature, no more. Please, restore the search/find feature. For instance, it is useful to search for a keyword in a man page (khelpcenter man:bash) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477758] Embrace the PIN to unlock the session
https://bugs.kde.org/show_bug.cgi?id=477758 --- Comment #2 from Miguel Rozsas --- Not exactly that way. The way I described it is an improvement . For instance, the unlock screen shows no indication it is expecting a PIN. Also, I have to press ENTER after the PIN. I've followed this [blog](https://blog.fancypi.cn/blog/pin_login_in_kde.html) and manually install the package libpam-pwdfile and manually edited the file /usr/lib/pam.d/kde. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477758] New: Embrace the PIN to unlock the session
https://bugs.kde.org/show_bug.cgi?id=477758 Bug ID: 477758 Summary: Embrace the PIN to unlock the session Classification: Plasma Product: kscreenlocker Version: 5.90.0 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- I just setup my system, after a little struggle, to accept a PIN to unlock a session already open using the regular password. I wish you could embrace the PIN to unlock the kde session, fully ! I mean, make easy to the user to choose to use a PIN by giving the proper GUI option in kde config panel and make the screenlocker to display the proper prompt at unlock screen, and accept the PIN without a ENTER key at end. A button to switch to use the full password (one time action) to unlock the screen would be nice too. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 476012] New: kinfo not inform the graphics mode.
https://bugs.kde.org/show_bug.cgi?id=476012 Bug ID: 476012 Summary: kinfo not inform the graphics mode. Classification: Plasma Product: kde-cli-tools Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- rpm -qf /usr/bin/kinfo kde-cli-tools5-5.27.8-1.2.x86_64 STEPS TO REPRODUCE 1. open a terminal 2. run `kinfo` OBSERVED RESULT Graphics Platform: offscreen it should inform X11 or Wayland. on terminal, DISPLAY is properly set to :1 EXPECTED RESULT The proper graphical environment, X11 or Wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: openSUSE Tumbleweed 20231020 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform: offscreen Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 474306] Yakuake crash on pressing F12
https://bugs.kde.org/show_bug.cgi?id=474306 --- Comment #2 from Miguel Rozsas --- Fixed by updating KDE. KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 474300] KDE crash on start
https://bugs.kde.org/show_bug.cgi?id=474300 --- Comment #2 from Miguel Rozsas --- Fixed by updating kde. KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 474306] New: Yakuake crash on pressing F12
https://bugs.kde.org/show_bug.cgi?id=474306 Bug ID: 474306 Summary: Yakuake crash on pressing F12 Classification: Applications Product: yakuake Version: 23.08.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- Application: yakuake (23.08.0) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Yakuake crash when I press F12 to bring it to screen. It is related with a recent KDE update. Operating System: openSUSE Tumbleweed 20230902 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-1-default (64-bit) Graphics Platform: offscreen Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 The crash can be reproduced every time. -- Backtrace: Application: Yakuake (yakuake), signal: Segmentation fault [KCrash Handler] #4 0x7fe5e4da1607 in QAction::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #5 0x7fe5ac5699c5 in Konsole::Screen::setReplMode(int) () from /lib64/libkonsoleprivate.so.1 #6 0x7fe5ac58602c in Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int) () from /lib64/libkonsoleprivate.so.1 #7 0x7fe5ac578a47 in Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates, unsigned int) () from /lib64/libkonsoleprivate.so.1 #8 0x7fe5ac578dd9 in Konsole::Vt102Emulation::receiveChars(QVector const&) () from /lib64/libkonsoleprivate.so.1 #9 0x7fe5ac5539d3 in Konsole::Emulation::receiveData(char const*, int) () from /lib64/libkonsoleprivate.so.1 #10 0x7fe5e4125812 in ?? () from /lib64/libQt5Core.so.5 #11 0x7fe5ac5427c6 in Konsole::Pty::receivedData(char const*, int) () from /lib64/libkonsoleprivate.so.1 #12 0x7fe5ac5592f2 in Konsole::Pty::dataReceived() () from /lib64/libkonsoleprivate.so.1 #13 0x7fe5e4125812 in ?? () from /lib64/libQt5Core.so.5 #14 0x7fe5ac749566 in ?? () from /lib64/libKF5Pty.so.5 #15 0x7fe5ac749809 in ?? () from /lib64/libKF5Pty.so.5 #16 0x7fe5e41257b3 in ?? () from /lib64/libQt5Core.so.5 #17 0x7fe5e4128b84 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #18 0x7fe5e412932e in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7fe5e4da519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fe5e40ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7fe5e4146f7d in ?? () from /lib64/libQt5Core.so.5 #22 0x7fe5e27169b8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7fe5e2716dc8 in ?? () from /lib64/libglib-2.0.so.0 #24 0x7fe5e2716e5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7fe5e41464a6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7fe5e40ebffb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7fe5e40f4490 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x55c98b891acd in ?? () #29 0x7fe5e36281b0 in __libc_start_call_main () from /lib64/libc.so.6 #30 0x7fe5e3628279 in __libc_start_main_impl () from /lib64/libc.so.6 #31 0x55c98b891cc5 in ?? () [Inferior 1 (process 1949) detached] The reporter indicates this bug may be a duplicate of or related to bug 474284. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 474300] New: KDE crash on start
https://bugs.kde.org/show_bug.cgi?id=474300 Bug ID: 474300 Summary: KDE crash on start Classification: Applications Product: yakuake Version: 23.08.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- Application: yakuake (23.08.0) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: After an KDE update, Yakuake always fail to start up. Operating System: openSUSE Tumbleweed 20230902 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-1-default (64-bit) Graphics Platform: offscreen Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 The crash can be reproduced every time. -- Backtrace: Application: Yakuake (yakuake), signal: Segmentation fault [KCrash Handler] #4 0x7f865bda1607 in QAction::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #5 0x7f861a4ab9c5 in Konsole::Screen::setReplMode(int) () from /lib64/libkonsoleprivate.so.1 #6 0x7f861a4c802c in Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int) () from /lib64/libkonsoleprivate.so.1 #7 0x7f861a4baa47 in Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates, unsigned int) () from /lib64/libkonsoleprivate.so.1 #8 0x7f861a4badd9 in Konsole::Vt102Emulation::receiveChars(QVector const&) () from /lib64/libkonsoleprivate.so.1 #9 0x7f861a4959d3 in Konsole::Emulation::receiveData(char const*, int) () from /lib64/libkonsoleprivate.so.1 #10 0x7f865b125812 in ?? () from /lib64/libQt5Core.so.5 #11 0x7f861a4847c6 in Konsole::Pty::receivedData(char const*, int) () from /lib64/libkonsoleprivate.so.1 #12 0x7f861a49b2f2 in Konsole::Pty::dataReceived() () from /lib64/libkonsoleprivate.so.1 #13 0x7f865b125812 in ?? () from /lib64/libQt5Core.so.5 #14 0x7f861bbef566 in ?? () from /lib64/libKF5Pty.so.5 #15 0x7f861bbef809 in ?? () from /lib64/libKF5Pty.so.5 #16 0x7f865b1257b3 in ?? () from /lib64/libQt5Core.so.5 #17 0x7f865b128b84 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #18 0x7f865b12932e in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f865bda519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f865b0ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f865b146f7d in ?? () from /lib64/libQt5Core.so.5 #22 0x7f865967d9b8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7f865967ddc8 in ?? () from /lib64/libglib-2.0.so.0 #24 0x7f865967de5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7f865b1464a6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7f865b0ebffb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f865b0f4490 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x558199900acd in ?? () #29 0x7f865a6281b0 in __libc_start_call_main () from /lib64/libc.so.6 #30 0x7f865a628279 in __libc_start_main_impl () from /lib64/libc.so.6 #31 0x558199900cc5 in ?? () [Inferior 1 (process 1971) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 469578] notes should have a lock to avoid unintentional edits
https://bugs.kde.org/show_bug.cgi?id=469578 --- Comment #2 from Miguel Rozsas --- I don't have this option. I don't understand...knotes does not have a title bar...?!?!?! Anyway, right clicking on a note only shows options to change the note's color or remove it. Operating System: openSUSE Tumbleweed 20230413 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS Em qua., 10 de mai. de 2023 às 11:58, Laurent Montel < bugzilla_nore...@kde.org> escreveu: > https://bugs.kde.org/show_bug.cgi?id=469578 > > Laurent Montel changed: > >What|Removed |Added > > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > We have it. > Right click on title bar => lock > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 469578] New: notes should have a lock to avoid unintentional edits
https://bugs.kde.org/show_bug.cgi?id=469578 Bug ID: 469578 Summary: notes should have a lock to avoid unintentional edits Classification: Applications Product: knotes Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mig...@rozsas.eng.br CC: myr...@kde.org Target Milestone: --- Whishlist SUMMARY Notes are good to hold information you want to be available right there, right now. Frequently this information needs to be copied to another place where it is needed. The problem is when we select a text on a note to copy it, the note enter in edit mode and a single keyboard stroke is enough to erase that information. I wish you could select a text on a note and the note remains in a read-only mode to avoid accidental alteration of selected text. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463753] systemsettings crash on "Edit VPN" in NetworkManager - untick "All users may connect to this network"
https://bugs.kde.org/show_bug.cgi?id=463753 Miguel Rozsas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Miguel Rozsas --- (In reply to Harald Sitter from comment #13) > Is this still reproducible? Can we get a more complete backtrace if it is, > please? No, not anymore in KDE 5.27.4 . I guess it was fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467112] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467112 Miguel Rozsas changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #11 from Miguel Rozsas --- fixed on 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468628] Plasmashell memory usage increase steadly over time.
https://bugs.kde.org/show_bug.cgi?id=468628 --- Comment #2 from Miguel Rozsas --- Yes. I have 2 monitors, 4 workspaces, 2 activities. Em ter., 18 de abr. de 2023 22:26, Nate Graham escreveu: > https://bugs.kde.org/show_bug.cgi?id=468628 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > Component|general |generic-performance > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Do you have multiple screens? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468628] New: Plasmashell memory usage increase steadly over time.
https://bugs.kde.org/show_bug.cgi?id=468628 Bug ID: 468628 Summary: Plasmashell memory usage increase steadly over time. Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 158172 --> https://bugs.kde.org/attachment.cgi?id=158172=edit output of: 'while /bin/true ; do date >> tmp/plasmashell_mem.log; ps -e -o comm,%cpu,cputime,etime,rss,%mem | grep -E "plasmashell|COMMAND" | tee -a tmp/plasmashell_mem.log; sleep 30m; done' SUMMARY Plamashell starts using about 400kbytes of memory and after 5:30h it is using more than 8G ! Must be a memory leak somewhere. STEPS TO REPRODUCE I collected the memory used by plasmasheel with a simple script. The data is attached. Note that, between 12:00h and 13:30h it was my lunch time, the computer was idle, even so, the memory usage increased from 3665792 to 5375696 bytes. After 5:30h since the KDE was started it was using 8142588 bytes. OBSERVED RESULT Memory usage increase over time. EXPECTED RESULT A more discrete usage of memory. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230413 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS ADDITIONAL INFORMATION Please , see the attached file. It has the used plasmashell memory in 30m intervals. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467112] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467112 --- Comment #8 from Miguel Rozsas --- (In reply to Nate Graham from comment #7) > > I use variety > Oh, that seems like it might be relevant. This thing? > https://peterlevi.com/variety/how-to-install/ The warning applies to KDE4 ! Check here: https://peterlevi.com/variety/2014/05/variety-and-kde/ "Shortly put, in KDE 4 it is impossible to change the wallpaper from a program" > Any chance you can stop using this piece of software for a while and see if > the bug stops happening? Although the warning is relevant to KDE 4, yes, sure, I can live without those gorgeous wallpapers for a while. Consider it done by the time you read this. I want to stress that I didn't lose any widgets after 5.27.3 (the last time was when transitioning from 5.27.2 -> 5.27.3) and opensuse TW is about to update to 5.27.4. I return here if anything different happens. Thank you so far. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467112] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467112 --- Comment #6 from Miguel Rozsas --- Created attachment 157905 --> https://bugs.kde.org/attachment.cgi?id=157905=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467112] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467112 --- Comment #5 from Miguel Rozsas --- Created attachment 157903 --> https://bugs.kde.org/attachment.cgi?id=157903=edit ~/.config/plasmashellrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467112] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467112 --- Comment #4 from Miguel Rozsas --- Sorry it is not what you expected so far Loosing the widgets is really a bumper. First time you recreate then again, but when you reach the 4th ou 5th time, you start to think is is worth the trouble at the point I moved my notes to obsidian, I really need then as it has numbers, ids, shortcuts and all kind of info I use all the time... The system indicators are too cool to not use them... 1. Did widgets disappear form multiple screens, or only one? >From multiple screens, Looks like there is a single bit that controls the widget notes and when the bug happens, all widgets are lost. 2. When the widgets disappeared, was the wallpaper also reset on the screen the widgets disappeared from? Or was the background reset to be all black? err...not sure. I use variety, and variety is not affected by this bug, so I really don't know what happens with the standard/static wallpaper. 3. If you happen to have the old monitor you were replacing, do the widgets re-appear if you plug that one in again? I am not sure if I understand, or if you understood. I don't replaced any monitor. I don't switch monitors. I have only 2 monitors. None of this was caused by changing the monitors or ports where the monitors are attached to. Also, which one is the primary monitor is not affected by this bug. Even if the HDMI monitor is not the original primary monitor it still is the primary monitor as I configured in first first time I plugged in, more than 1 year ago now. Can you attach your ~/.config/plasmashellrc and ~/.config/plasma-org.kde.plasma.desktop-appletsrc files, after scrubbing them of any sensitive or personally identifying information? Sure I can. Look at attached files please. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 467112] all my notes disappeared no raeson
https://bugs.kde.org/show_bug.cgi?id=467112 --- Comment #2 from Miguel Rozsas --- @Nate Graham: Thank you for taking care of this issue: Answering your questions: 1. Did the desktowith the notes have other widgets or icons on it, or only sticky note widgets? Yes , it had : a weather widget, a analog clock widget, 2 kargos widgets, several system widgets (CPU, Mem, disk, net), and the most important the 6 or 7 notes widgets, distributed between 2 physical monitors. The left/right, primary/secondary monitor didn't change. 1a. If it did, did those things disappear too? Yes, ALL widgets disappeared. 2. If you right-click on the desktop, choose "Enter Edit Mode", click on "Manage Desktops and Panels" on the toolbar that drops down from the top of the screen, can you find the desktop with your Sticky Notes on it and drag it back to the monitor you're currently using? No, it shows just the 2 current screens, there is no additional screen. However, the content of notes are still there in .local/share/plasma_notes as individual files. 3. How many screens are connected, or were connected when this happened? I have 2 monitors. The HDMI one is new and curved and I set it as primary (not the default configuration), the other one on the DVI port. Both on the same external video card (Radeon RX 6600) This happened several times, the last when running 5.27.3, but the configuration was made when running a previous version of KDE, not sure what. I am running a rolling distro and update each 3 or 4 weeks, so there is a big chance it was 5.27.2, but I can't confirm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467167] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467167 Miguel Rozsas changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Miguel Rozsas --- No, was not the case. There is only 2 desktops there, the current ones. I recreate 5 system monitors, 1 Kargos widget and 1 weather widget. Lets see if they are more robust now, as it was created on 5.27.2. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467167] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467167 --- Comment #4 from Miguel Rozsas --- I get it now ! Thank you ! Yeah, I think it is good only for desktops and panels, not for the widgets that I've lost (system monitor, clock, weather, etc). Anyway I appreciate your help and effort ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467167] All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467167 --- Comment #2 from Miguel Rozsas --- Hi, Thank you so far. Yes, I understand that a previous setup may have inconsistencies not addressable in the current refactoring. Good to know. I would like very much to try that "UI to recover missing desktops " but I was unable to find it ! Is it a extra package I should install or is it somewhere in configuration panel ? Sorry if I was unable to find it...Search in google didn't return anything I appreciate any help here, I didn't put back any widgets yet so I think I could restore all my widgets back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467167] New: All my widgets disappeared
https://bugs.kde.org/show_bug.cgi?id=467167 Bug ID: 467167 Summary: All my widgets disappeared Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** I had a desktop populated with several widgets: several system monitors, analog clock, weather, knotes. I logoff and them poweroff the computer and on the next day all widgets disappeared whitout any raeson: I didn't changed anything, I didn't install anything. I have a two monitor setup and an amd video card. *** STEPS TO REPRODUCE 1. logoff 2. power off 3. next day power on, log in OBSERVED RESULT All widgets disappeared. EXPECTED RESULT All widgets there in their previous location. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230302 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS Not a new bug, widgets disappearing from multi monitor setups are well know (the bug, not the fix) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 467112] New: all my notes disappeared no raeson
https://bugs.kde.org/show_bug.cgi?id=467112 Bug ID: 467112 Summary: all my notes disappeared no raeson Classification: Plasma Product: kdeplasma-addons Version: git-stable-Plasma/5.27 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: notes Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY *** Even on 5.27.2 my notes disappeared from desktop on login. Last night, when I logoff, they were there. Today, after login, no notes anymore. I had a dozen or so. *** STEPS TO REPRODUCE 1. Use knotes 2. Do nothing 3. Buum ! There is no notes anymore Sorry, this is a well know bug with KDE/Plasma/Knotes. For no reason they disappear without notice. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230302 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461924] crash when change setting in Network config
https://bugs.kde.org/show_bug.cgi?id=461924 --- Comment #1 from Miguel Rozsas --- If you click on "global" change settings (on top of NM panel, next to the pin) you are prompt to root password, which is fine. After typing the correct root password all connections are showed to choose one to modify. If a select a connection that all users can use and I try to modify this property, it crash. Instead, if I click on local configure button that shows when you click on the arrow in the list of connections then the configure connection panel for that connection show up (just like before), but now, no root password is asked and if I click on the check mark to change the setting (all users can use this connection) it not crash, allowing me to edit the list of authorized users ! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461924] New: crash when change setting in Network config
https://bugs.kde.org/show_bug.cgi?id=461924 Bug ID: 461924 Summary: crash when change setting in Network config Classification: Applications Product: systemsettings Version: 5.26.3 Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- Application: systemsettings (5.26.3) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.8-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: in a connetion window, geral configuration tab, there is a setting named "all users can connect to this network" that is set. As Windows Manager is asking me root password every time I want to use this configuration, I will try to disable it and them , add my specific user to the next field. But when I click on the check box above, it crash. I already provided root password to show this window..So, there is at least 2 bugs here. It is asking root password to use a connection already set to all users and it crahs whem I change this setting. Opensuse Tumbleweed S S The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Configurações do sistema (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fe15ece1c28 in WifiSecurity::setStoreSecretsSystemWide(bool) () from /lib64/libplasmanm_editor.so #5 0x7fe19bd132cd in ?? () from /lib64/libQt5Core.so.5 #6 0x7fe19bd132cd in ?? () from /lib64/libQt5Core.so.5 #7 0x7fe19caa7fde in QCheckBox::stateChanged(int) () from /lib64/libQt5Widgets.so.5 #8 0x7fe19ca98c4a in ?? () from /lib64/libQt5Widgets.so.5 #9 0x7fe19ca98d97 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #10 0x7fe19c9e6c38 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7fe19c9a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7fe19c9ad922 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7fe19bcdc128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7fe19c9aba9e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #15 0x7fe19c9ffa58 in ?? () from /lib64/libQt5Widgets.so.5 #16 0x7fe19ca02fb0 in ?? () from /lib64/libQt5Widgets.so.5 #17 0x7fe19c9a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7fe19bcdc128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7fe19c17b9ad in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #20 0x7fe19c14f37c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #21 0x7fe1987210fa in ?? () from /lib64/libQt5XcbQpa.so.5 #22 0x7fe19a46aa90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7fe19a46ae48 in ?? () from /lib64/libglib-2.0.so.0 #24 0x7fe19a46aedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7fe19bd33b56 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7fe19bcdab9b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7fe19bce2d06 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x5596496bffa8 in ?? () #29 0x7fe19b42c5b0 in __libc_start_call_main () from /lib64/libc.so.6 #30 0x7fe19b42c679 in __libc_start_main_impl () from /lib64/libc.so.6 #31 0x5596496c08d5 in ?? () [Inferior 1 (process 8333) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456915] activities should rememeber the active workspace
https://bugs.kde.org/show_bug.cgi?id=456915 Miguel Rozsas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Miguel Rozsas --- Someone pointed to me already have that setting: Configuration/Activities/Change tab/remember each activity (needs restart). Sorry and thanks, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456915] New: activities should rememeber the active workspace
https://bugs.kde.org/show_bug.cgi?id=456915 Bug ID: 456915 Summary: activities should rememeber the active workspace Product: kwin Version: 5.25.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY *** WHISLIST : When switching activities, the workspace is the same on all activities. I think would be nice if each activity has its own current workspace. lets say we have the situation ACTIVITY WORKSPACE A1w1, w2*, w3, w4 A2w1, w2, w3, w4* where * denotes the current/active workspace in each Activity Switching to A2, should display the content of w4. Switching back to A1, should display the content of w2. *** STEPS TO REPRODUCE 1. currently the content of workspace 1 is displayed. 2. Switch to another Activity 3. the content of workspace 1 on another activity is displayed OBSERVED RESULT Switching activities did not switch workspace number. EXPECTED RESULT Switching activities should display the active workspace number on that activity. ADDITIONAL INFORMATION Operating System: openSUSE Tumbleweed 20220714 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9-2-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448022] New: incorrect and kind of offensive translation for "faces" in brazilian portuguese.
https://bugs.kde.org/show_bug.cgi?id=448022 Bug ID: 448022 Summary: incorrect and kind of offensive translation for "faces" in brazilian portuguese. Product: digikam Version: 7.3.0 Platform: unspecified OS: All Status: REPORTED Severity: minor Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: mig...@rozsas.eng.br 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 *** It is a translation problem, not a code problem. In Brazilian portuguese translation the term used for "faces" is not appropriate, even it is kind of offensive, since "caras" is a term reserved for animals. People, in brazilian portuguese, has a "face" or "rosto". Only animals have "caras". -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 442346] New: Yakuake does not follow mouse when the mouse is on a second monitor and Wayland
https://bugs.kde.org/show_bug.cgi?id=442346 Bug ID: 442346 Summary: Yakuake does not follow mouse when the mouse is on a second monitor and Wayland Product: yakuake Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY Yakuake does not follow mouse when the mouse is on a second monitor and Wayland. It follows the mouse and open as expected when using X11. STEPS TO REPRODUCE 1. Use a wayland session and a second monitor 2. Move the mouse pointer to the second monitor 3. Press the shortcut to open yakuake (mine is the default F12) OBSERVED RESULT It opens the window on the primary monitor, not on the second one. EXPECTED RESULT I expect it open the yakuake terminal on the second monitor, as it does when on a X11 session. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210910 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.1-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION It works as expected in a X11 session. It is a Wayland related problem. I don't know if it is related to 411681 bug. Mine always open on the primary monitor, not secondary monitor as described on 411681. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 422616] Garbled HTML information in system tray icon tooltips when apps put HTML in there
https://bugs.kde.org/show_bug.cgi?id=422616 --- Comment #41 from Miguel Rozsas --- Nah...I am using opensuse tumbleweed (rolling release) up to date (installed: 20210804) and currently it has firewall-applet-0.9.3-3.3.noarch so I am wondering why opensuse has not it in the factory already -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 422616] Garbled HTML information in system tray icon tooltips when apps put HTML in there
https://bugs.kde.org/show_bug.cgi?id=422616 --- Comment #38 from Miguel Rozsas --- According to this: https://github.com/firewalld/firewalld/commit/69489661ec8eca1c2ed3c6159024c271e7e6eb2b it was fixed on 20 Apr. Any idea how long it takes to be available to the users ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433789] Windows maximized on a second monitor are moved to the primary monitor when the monitor goes off
https://bugs.kde.org/show_bug.cgi?id=433789 Miguel Rozsas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Miguel Rozsas --- This bug was fixed somehow and it does not manifest itself anymore, probably it was fixed in some iteration of kde 5.21 updates. My system, currently is running: Operating System: openSUSE Tumbleweed 20210330 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424473] duplicate icons on the second monitor when changing activities
https://bugs.kde.org/show_bug.cgi?id=424473 Miguel Rozsas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Miguel Rozsas --- This bug was fixed somehow and it does not manifest itself anymore, during the last iterations of kde 5.21 updates. My system, currently is running: Operating System: openSUSE Tumbleweed 20210330 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424473] duplicate icons on the second monitor when changing activities
https://bugs.kde.org/show_bug.cgi?id=424473 --- Comment #1 from Miguel Rozsas --- Just to say this same problem still there in 5.21 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433789] New: Windows maximized on a second monitor are moved to the primary monitor when the monitor goes off
https://bugs.kde.org/show_bug.cgi?id=433789 Bug ID: 433789 Summary: Windows maximized on a second monitor are moved to the primary monitor when the monitor goes off Product: kwin Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY In a dual monitor setup, the windows maximized on the second monitor are moved to the primary monitor when the second monitor goes off and goes on again. The windows that are not maximized on the second monitor or any windows in the first monitor are not affected. They remain where it are supposed to be. In general, the monitors goes off as result of the automatic lock screen followed by a long period (15min) of inactivity, but it happens manually. I mean, turn the second monitor off by the monitor switch and turn it on again after a short period (seconds). STEPS TO REPRODUCE 1. In a dual monitor setup, place windows on the first and second monitor. Then maximize some windows, specially on the second monitor. 2. Turn the second monitor off by pressing its power off switch. 3. Wait a few seconds. Turn the second monitor on again. You see the maximized windows placed on the second monitor to show up on the first monitor. OBSERVED RESULT The maximized windows placed on the second monitor are showed now on the first monitor. The maximized windows on the first monitor are not affected. Any non maximized window in any monitor are not affected. EXPECTED RESULT Any windows must stay in its the original place. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION This bug happens since KDE 5.20 at least. Its not new on KDE 5.21. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428644] Yakuake with dark stripes on terminal area
https://bugs.kde.org/show_bug.cgi?id=428644 --- Comment #5 from Miguel Rozsas --- I change the theme from Dark-openSUSE to Breeze, no effect. The stripes remain. Then I changed the Yakuake theme from Breeze to plastik and Legacy. No effect. I changed the Yakuake transparency setting too. No effect. In fact, looks like the transparency setting it is not working at all. It remains opaque even if it is set to 10%. Another settings that is not working is the background color. To make sure the settings were applied, I run yakuake in a terminal windows and close and re-run the program after each change and then, I notice it issues a warning message when starts. I don't know if it is relevant or not: kf.newstuff.core: Using a deprecated location for the knsrc file "yakuake.knsrc" - please contact the author of the software which provides this file to get it updated to use the new location -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428644] Yakuake with dark stripes on terminal area
https://bugs.kde.org/show_bug.cgi?id=428644 --- Comment #4 from Miguel Rozsas --- Sure ! Here: kimera:/home/miguel # rpm -qa | grep -i nvidia kernel-firmware-nvidia-20201023-2.1.noarch nvidia-glG05-450.80.02-35.1.x86_64 nvidia-gfxG05-kmp-default-450.80.02_k5.8.15_1-35.1.x86_64 nvidia-computeG05-450.80.02-35.1.x86_64 x11-video-nvidiaG05-450.80.02-35.1.x86_64 kimera:/home/miguel # -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428644] Yakuake with dark stripes on terminal area
https://bugs.kde.org/show_bug.cgi?id=428644 --- Comment #2 from Miguel Rozsas --- hi, Tested with a new user in the same machine: same result. Stripes when height is bigger than 50%, I have a second machine, same system, different hardware thought. In this another computer there is no issue ! Operating System: openSUSE Tumbleweed 20201022 KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.15-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i3-2350M CPU @ 2.30GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 3000 Looks like a graphical glitch, caused by NVidia driver, since the second computer does not have a NVidia card and not have the issue, even with height larger than 50%. Strange is, only yakuake it is affected by this. No other graphical app have the issue. I even play steam games without issues. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428644] New: Yakuake with dark stripes on terminal area
https://bugs.kde.org/show_bug.cgi?id=428644 Bug ID: 428644 Summary: Yakuake with dark stripes on terminal area Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- Created attachment 132993 --> https://bugs.kde.org/attachment.cgi?id=132993=edit yakuake terminal with stripes when height it is set to 90% SUMMARY Yakuake show dark horizontal stripes on inside its terminal area when termianl height is bigger than 50% STEPS TO REPRODUCE 1. Open Yakuake by its keyboard shortcut (mine it is the default, F12) 2. Set the terminal height to a value bigger than 50%. Close the terminal. 3. Open Yakuake again and you see dark stripes on terminal area. The bigger is the terminal height, bigger are the stripes. With 50% and lower there is no stripes. With 60% there are just "lines". With 100% there are large stripes. OBSERVED RESULT Stripes on terminal area when terminal height is bigger than 50% EXPECTED RESULT plain background at any height SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20201025 KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.15-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 422616] Garbled HTML information in system tray icon tooltips when apps put HTML in there
https://bugs.kde.org/show_bug.cgi?id=422616 --- Comment #36 from Miguel Rozsas --- (In reply to Nicolas Fella from comment #35) > *** Bug 428597 has been marked as a duplicate of this bug. *** Please, note that the Bug 422616 that affect firewalld applet, qibitorrent and Clementine was fixed by the teams of qibitorrent and Clementine only. No one was assigned to take care of this bug in firewalld in it remains. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428597] New: firewalld tooltip displaying html raw code (unformatted)
https://bugs.kde.org/show_bug.cgi?id=428597 Bug ID: 428597 Summary: firewalld tooltip displaying html raw code (unformatted) Product: frameworks-plasma Version: 5.75.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tooltips Assignee: notm...@gmail.com Reporter: mig...@rozsas.eng.br CC: k...@davidedmundson.co.uk, plasma-b...@kde.org Target Milestone: --- SUMMARY The firewalld widget (from Thomas Woerner , Jiri Popelka and Eric Garver ) displays a tooltip (the one when you move the mouse point over it, not clicking) with unformatted HTML code I mean: "..." STEPS TO REPRODUCE 1. Add the firewall widget to the taskbar 2. Move the mouse pointer over it 3. ckeck the unformatted HTML code displayed OBSERVED RESULT "..." EXPECTED RESULT A well formatted output SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20201023 KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.15-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION This is a old bug, present since 5.18 at least. Amazing it is still there. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 424477] New: the tooltip of firewall widget is displaying RAW HTML
https://bugs.kde.org/show_bug.cgi?id=424477 Bug ID: 424477 Summary: the tooltip of firewall widget is displaying RAW HTML Product: kdeplasma-addons Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- Created attachment 130290 --> https://bugs.kde.org/attachment.cgi?id=130290=edit how the tooltip is displayed SUMMARY The tooltip of firewall is displaying RAW HTML code STEPS TO REPRODUCE 1. add the firewall widget 2. hover the mouse on it 3. see the unformatted HTML code showing OBSERVED RESULT RAW HTML EXPECTED RESULT Proper formatted output SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200717 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424473] New: duplicate icons on the second monitor when changing activities
https://bugs.kde.org/show_bug.cgi?id=424473 Bug ID: 424473 Summary: duplicate icons on the second monitor when changing activities Product: plasmashell Version: 5.19.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mig...@rozsas.eng.br CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 130287 --> https://bugs.kde.org/attachment.cgi?id=130287=edit screen capture showing 3 icons on the second monitor, first activity and 7 icons (4 of them are ghosts) on the second activity. SUMMARY In a dual monitor setup, put some icons (launchers) on the second monitor first activity. STEPS TO REPRODUCE 1. Create 2 activities. 2. put some icons (launchers) on the second monitor, first activity 3. Switch to second activity and back to the first activity. OBSERVED RESULT Note that at some point the icons on the second monitor get duplicated. The duplicate icons are "ghosts" as they don't work to launch the associated program. EXPECTED RESULT The icons should not have duplicates ghosts. SOFTWARE/OS VERSIONS Windows: macOS: Operating System: openSUSE Tumbleweed 20200717 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 14.6 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION See the image. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 Miguel Rozsas changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #13 from Miguel Rozsas --- I was curious about how is the Gnome behavior for that situation (turning off the primary monitor). And I've learned it is the same ! The mouse freezes on the second monitor and the keyboard is turned off. Then I wanted to know how is the Microsoft Windows 10 behavior for this since it could be a X11 problem or even a kernel thing...(my machine has dual boot. I use windows rarely) Well, beyond all my expectations, the Windows 10 1909 has exactly the same behavior ! The system freezes, the keyboard is turned off and when the primary monitor is turned on, the keyboard gets a reset and everything went to normal. So it is not a KDE problem. It is something related with the hardware/bios, I don't know... So, I am marking this as RESOLVED/NOT A BUG since it is not a KDE problem after all, for sure. However, this is interesting anyway. cheers, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 --- Comment #12 from Miguel Rozsas --- The bug is still present after changing the video card to a GeForce GTX 970/PCIe/SSE2 4G RAM, openGL 4.6.0 NVIDIA 430.50 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 --- Comment #11 from Miguel Rozsas --- The bug still present after updating to Plasma 5.18.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 --- Comment #9 from Miguel Rozsas --- The bug still present after updating to Plasma 5.18.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 --- Comment #4 from Miguel Rozsas --- oh.. and doing the opposite, I mean, turning OFF the secondary monitor, nothing special occurs. The primary monitor and the mouse pointer are both alive and turning ON the secondary monitor, the keyboard DID NOT receive a reset. The secondary monitor goes back, and the previous image is displayed as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 --- Comment #3 from Miguel Rozsas --- For me happens all the time. As soon I turn off the primary monitor the mouse pointer on the second monitor freezes. As soon I turn on the primary monitor the mouse pointer goes back to action AND the keyboard gets a reset (I can tell that because my keyboard is a RGB keyboard that when gets a reset it glows in a special way to indicate that) Following additional information right from Configuration Center and Kinfo: Kubuntu 19.10, plasma: 5.18.0; KDE Framework: 5.67.0; Qt: 5.12.4; kernel:5.3.0.-29-generic Processor:8 x Intel Core i7-3770 CPU @ 3.4GHz Memory: 14,6GiB RAM (installed 2x8G bytes, dual Channel) Primary Monitor (on the left): DELL U2312HM (DVI-I-1) (1920x1080) Secondary monitor(on the right): 2343 (DVI-D-0) (1920x1080) - (AOC monitor) GeForce GTX 760/PCe/SSE2 OpenGL 4.6.0 NVIDIA 430.50 Kernel module: i915 Using a X server: 1.20.5 version: 11.0 Screen #0 dimension: 3849x1080 resolution: 94 x 94 ppp I can provide any other information you need. Just ask. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 --- Comment #1 from Miguel Rozsas --- I mean "3. You could't do anything else until you turn the primary monitor on again." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417525] New: the system freeze if the primary monitor is turned off in a two monitor setup
https://bugs.kde.org/show_bug.cgi?id=417525 Bug ID: 417525 Summary: the system freeze if the primary monitor is turned off in a two monitor setup Product: kwin Version: 5.18.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY the windows system freeze if the primary monitor is turned off in a two monitor setup STEPS TO REPRODUCE 1. Move the mouse pointer to the second monitor 2. Turn off the primary monitor 3. You could do anything else until you turn the primary monitor on again. OBSERVED RESULT The mouse pointer freezes, the keyboard did not receive input; EXPECTED RESULT I expect that I could use the OS/System on the second monitor normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.18.0 (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION If I turn on the primary monitor the keyboard receive a reset. Besides that, everything goes to normal. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 413527] widgets are unlocked at login even so it was locked before
https://bugs.kde.org/show_bug.cgi?id=413527 Miguel Rozsas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Miguel Rozsas --- with ubuntu updates of Oct 30, 2019 this issue was, somehow, fixed. I do not know what was the package involved. I just realized that, after the updates was in place. The symptom that I described, unlocked widgets, kargos and notes plugins are now acting as expected, so I am closing this bug report. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 413527] New: widgets are unlocked at login even so it was locked before
https://bugs.kde.org/show_bug.cgi?id=413527 Bug ID: 413527 Summary: widgets are unlocked at login even so it was locked before Product: Active Window Control Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: mig...@rozsas.eng.br CC: plasma-b...@kde.org Target Milestone: --- Every time I log in in the system, desktop widgets are unlocked even so when it was locked at previous logout. I do not know if it is related, but kargos-plugin that I put on desktop are in random positions and with random windows sizes. STEPS TO REPRODUCE 1. Lock widgets 2. Logout 3. Login OBSERVED RESULT The widgets are unlocked (right-click on desktop to get the menu); widgets using Kargos plugin are in different positions and sizes they are before logout. EXPECTED RESULT The state of "Lock widgets" should not change between sessions. Kargos widgets should not change position and sizes during between sessions. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
