[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Tony changed: What|Removed |Added CC|wladys...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486531] plasmashell crash at restore from lock screen
https://bugs.kde.org/show_bug.cgi?id=486531 --- Comment #2 from Tony --- Created attachment 169551 --> https://bugs.kde.org/attachment.cgi?id=169551=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 Stepped away from my machine for a few minutes. When I returned, the screen was locked so I unlocked it. When the screen unlocked I saw that Google Chrome was no longer running and the KDE Crash Handler dialog was showing on the screen. -- Backtrace (Reduced): #8 0x7f7257686b0d in ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8 [...] #11 0x7f7258174c5c in wl_display_dispatch_queue_pending () from /opt/amdgpu/lib/x86_64-linux-gnu/libwayland-client.so.0 #12 0x7f725712b872 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #13 0x7f7255cdd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f7256b62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486531] plasmashell crash at restore from lock screen
https://bugs.kde.org/show_bug.cgi?id=486531 Tony changed: What|Removed |Added CC||tman1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 482642] On X11, cannot change multi-screen settings via OSD
https://bugs.kde.org/show_bug.cgi?id=482642 Tony changed: What|Removed |Added CC|wladys...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 482642] On X11, cannot change multi-screen settings via OSD
https://bugs.kde.org/show_bug.cgi?id=482642 Tony changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #16 from Tony --- >From what I can see, this bug seems to be half-fixed. Changing screen layout through system tray option/button is fixed and works as it should. Changing such option via OSD when you hit Meta + P still does nothing. Plasma: 6.0.3 Frameworks: 6.0.0 Qt: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483993] New: Display Configuration OSD / Screen Layout - adjusting settings doesn't work under X11
https://bugs.kde.org/show_bug.cgi?id=483993 Bug ID: 483993 Summary: Display Configuration OSD / Screen Layout - adjusting settings doesn't work under X11 Classification: Plasma Product: KScreen Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OSD and Plasma applet Assignee: kscreen-bugs-n...@kde.org Reporter: wladys...@outlook.com Target Milestone: --- SUMMARY I have laptop + external display setup. X11 session. After updating to Plasma 6, I cannot longer quickly manage my screens through "shortcuts" - either Meta+P or "Display Configuration" option in system tray. Selecting "Switch to external screen", "Switch to laptop screen", "Extend to left" or "Extend to right" does nothing. In order to configure my displays the way I want, now I have to right click on desktop > select "Configure Display Settings" and explicitly check and apply what is primary display or what display I want to disable. STEPS TO REPRODUCE 1. Hit Meta + P or under system tray click "Display Configuration" 2. Select any option, like "Switch to external screen" OBSERVED RESULT Nothing happens EXPECTED RESULT Selecting appropriate option should work - i.e. disable external/built-in screen, extend screen to left/right SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This functionality worked perfectly under Plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #61 from Tony --- (In reply to Jakob Petsovits from comment #60) > Esc in the screen locker is the key assigned to turning the screen off. When > it's already turned off, a second press of Esc or any other key should turn > the screen back on and show the password input field. > > Could you go into detail about how the behavior differs from this expected > behavior on your system? Ideally create a new bug because we don't want this > thread to become a collection for all things related to screens turning off, > just the screen turning off when the screen locker activates. Oh, my bad - I wasn't aware of such behavior. Thanks for the clarification! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Tony changed: What|Removed |Added CC||wladys...@outlook.com --- Comment #59 from Tony --- Whenever lock screen is triggered and I hit Esc in order to show input password field - screen becomes black like it used to before mentioned fix. Happens on latest Plasma 6.0.2 under X11 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP BLUE SCREEN SHOWS NOTHING
https://bugs.kde.org/show_bug.cgi?id=482950 Tony Murray changed: What|Removed |Added CC||murrayt...@gmail.com --- Comment #2 from Tony Murray --- Duplicate of 481968 and 482836, I'm going to leave this open until 24.02.1 is released next week which contains the fix. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482189] Akonadi not working after upgrading from 5.27 to 6.0
https://bugs.kde.org/show_bug.cgi?id=482189 Tony Bazeley changed: What|Removed |Added CC||tba...@gmail.com --- Comment #4 from Tony Bazeley --- I have what looks to be the same problem sudo pkcon get-packages | grep akonadi-backend Available akonadi-backend-mysql-4:24.02.0-0xneon+22.04+jammy+release+build50.amd64 (user_jammy-jammy-main) Available akonadi-backend-postgresql-4:24.02.0-0xneon+22.04+jammy+release+build50.amd64 (user_jammy-jammy-main) Available akonadi-backend-sqlite-4:24.02.0-0xneon+22.04+jammy+release+build50.all (user_jammy-jammy-main) apt policy akonadi-backend-mysql akonadi-backend-mysql: Installed: (none) Candidate: 4:24.02.0-0xneon+22.04+jammy+release+build50 Version table: 4:24.02.0-0xneon+22.04+jammy+release+build50 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 100 /var/lib/dpkg/status 4:23.08.4-0xneon+22.04+jammy+release+build48 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 500 http://archive.neon.kde.org/user jammy/main all Packages 4:23.08.4-0xneon+22.04+jammy+release+build47 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 500 http://archive.neon.kde.org/user jammy/main all Packages 4:23.08.4-0xneon+22.04+jammy+release+build46 500 500 http://archive.neon.kde.org/user jammy/main amd64 Packages 500 http://archive.neon.kde.org/user jammy/main all Packages 4:21.12.3-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Is sudo pkcon install akonadi-backend-mysql the recommended fix?? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 481968] RDP session won't launch - Could not connect to server
https://bugs.kde.org/show_bug.cgi?id=481968 Tony Murray changed: What|Removed |Added CC||shivar...@gmail.com --- Comment #8 from Tony Murray --- *** Bug 482836 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482836] Unable to login with domain user
https://bugs.kde.org/show_bug.cgi?id=482836 Tony Murray changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||murrayt...@gmail.com --- Comment #1 from Tony Murray --- *** This bug has been marked as a duplicate of bug 481968 *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] KRDC should use libfreerdp instead of embedding the client (doesn't work properly under Wayland)
https://bugs.kde.org/show_bug.cgi?id=377911 Tony Murray changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #29 from Tony Murray --- This is fixed by https://invent.kde.org/network/krdc/-/merge_requests/58 Unfortunately, there is still a lot of missing functionality. Any help restoring/adding that is appreciated. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481962] wlfreerdp is missing
https://bugs.kde.org/show_bug.cgi?id=481962 Tony Murray changed: What|Removed |Added CC||murrayt...@gmail.com Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Tony Murray --- KRDC no longer uses wlfreerdp or xfreerdp executables. It requires libfreerdp. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 481968] RDP session won't launch - Could not connect to server
https://bugs.kde.org/show_bug.cgi?id=481968 Tony Murray changed: What|Removed |Added CC||murrayt...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Tony Murray --- This is fixed by https://invent.kde.org/network/krdc/-/merge_requests/84 Which I backported to the 24.02 branch, regrettably, I couldn't get it in before 24.02.0 was released. It will be in 24.02.1 so things at least kind of function. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481606] New: system breaking update
https://bugs.kde.org/show_bug.cgi?id=481606 Bug ID: 481606 Summary: system breaking update Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Other Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tonyg...@null.net 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. install os 2. update system 3. then restart and it hangs and goes nowhere from there OBSERVED RESULT broken os EXPECTED RESULT updated running os 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.
[KScreen] [Bug 466208] OSD and applet: "Switch to external display" mode not remembered after reboot
https://bugs.kde.org/show_bug.cgi?id=466208 Tony changed: What|Removed |Added CC|wladys...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 421451] Kate raises hspell error when launched from command line
https://bugs.kde.org/show_bug.cgi?id=421451 tony den haan changed: What|Removed |Added CC||kdeb...@tuxick.net --- Comment #18 from tony den haan --- (In reply to Fergal Mullally from comment #17) > For anyone coming across this issue, I solved it by installing hspell on my > system with apt. It's about 1.2Mb in size > > ``` > sudo apt install hspell -y > > > My guess -- and it's only a guess -- is that Kate comes bundled with hspell, > but it missing some of the dictionary files. Installing hspell directly > installs those dictionary files and removes the warning. But why does it even try? I don't need Hebrew spelling. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479396] kdeconnect-sms: conversations list and message lists completely messed up
https://bugs.kde.org/show_bug.cgi?id=479396 --- Comment #4 from Tony Green --- (In reply to Simon Redman from comment #3) > Did this break recently for you? I had actually tried kdeconnect-sms some time ago and abandoned it because of this behaviour. I came back to try it again and decided I'd better report the problem. So the short answer is "no". > > What messaging app are you using on your phone? The Samsung messaging app. When I tried in the past I was using Textra. > > (In reply to Tony Green from comment #0) > > 1. In general, only single person conversations are listed (so none of > > those where I've sent SMS messages to multiple contacts). Though ONE > > multi-person conversation IS listed. > > Can you confirm that the messages you've sent to multiple contacts are > actually *MMS*? As far as I understand, SMS can only have a single target. I think you're right, evidently I may be using incorrect terminology. Though curiously, the *one* multi person conversation that appears on my desktop has some messages on my 'phone marked MMS and others not. Though that's a fairly old conversation, not touched since last June. > > (In reply to Tony Green from comment #0) > > Not all conversations shown in my SMS app are shown in the conversations > > list. > > Can you try to narrow down what is special about all the conversations which > are not shown? Are they special messages from your network? Messages from a > SIM/phone number which used to be in this phone? Are they from an email > address? Etc. No pattern I can discern, unfortunately. I *did* change network a couple of months ago, but given the fact that the previous time I tried it i had the same problem, I'm guessing that's probably irrelevant to this problem. > > (In reply to Tony Green from comment #0) > > 3. A number of long-deleted conversations (no longer shown on the app) are > > shown. > > This sounds like you might have only hidden (archived, etc.) the > conversation using your messaging app on Android. Anything like that would > be an app-specific setting, so KDE Connect reading messages from the > messages databases wouldn't have the information that they should not be > displayed. I can't see any option to hide messages in the app, so I don't think I've done that. > > (In reply to Tony Green from comment #1) > > Created attachment 164672 [details] > > Screenshot showing incorrect messages for contact > > > > The messages shown for this contact were from a completely different one, > > which doesn't even appear on the conversations list. > > This smells like the conversation ID is somehow being corrupted. Its feeling like the problem is something screwed up on my 'phone rather than in KDEConnect. So I'm inclined to suggest closing this off and assuming it's a one-off problem at the user-end. Since I can *send* messages from the command line with kdeconnect-cli, I've got most of the functionality I really need anyway. Thanks for your work on this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479396] kdeconnect-sms: conversations list and message lists completely messed up
https://bugs.kde.org/show_bug.cgi?id=479396 --- Comment #2 from Tony Green --- Shame I can't edit previous comments. My comment about the summary for contacts being from another contact should say that all messages shown are from a different contact. More info in other comments. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479396] kdeconnect-sms: conversations list and message lists completely messed up
https://bugs.kde.org/show_bug.cgi?id=479396 --- Comment #1 from Tony Green --- Created attachment 164672 --> https://bugs.kde.org/attachment.cgi?id=164672=edit Screenshot showing incorrect messages for contact The messages shown for this contact were from a completely different one, which doesn't even appear on the conversations list. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479396] New: kdeconnect-sms: conversations list and message lists completely messed up
https://bugs.kde.org/show_bug.cgi?id=479396 Bug ID: 479396 Summary: kdeconnect-sms: conversations list and message lists completely messed up Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: k...@web-brewer.co.uk Target Milestone: --- Created attachment 164671 --> https://bugs.kde.org/attachment.cgi?id=164671=edit Screenshot showing faulty message list. SUMMARY Rather a vague-looking summary, but the best I can come up with. Using kdeconnect on my Samsung Android 'phone (app version 1.29, Android version 13) with kdeconnect-sms on my Linux desktop (kdeconnect-sms 23.08-4, Manjaro Linux fully up to date). All necessary permissions have been granted and the requisite SMS plugins are enabled at both ends. * Conversation list: 1. In general, only single person conversations are listed (so none of those where I've sent SMS messages to multiple contacts). Though ONE multi-person conversation IS listed. 2. Not all conversations shown in my SMS app are shown in the conversations list. 3. A number of long-deleted conversations (no longer shown on the app) are shown. 4. The preview of some conversations shows text from a completely different contact. * Message list. Many message lists show only messages from many years ago, with no sign of more recent ones. STEPS TO REPRODUCE 1. Pair 'phone and desktop 2. Run kdeconnect-sms OBSERVED RESULT As described above EXPECTED RESULT All messages should be available for all contacts (and groups) and should have correct summaries. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10-1 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467822] SMS messages are sent but not acknowledged and replies are not received on CalyxOS
https://bugs.kde.org/show_bug.cgi?id=467822 --- Comment #2 from Tony Schmidt --- Still haven't figured out whether this is an issue that should be fixed on the KDE Connect or Android ROM side, but just switched phones to FairPhone5/eOS on Android13 and now things are working fine. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477673] New: KDEConnect - sshfs finished with exit code 1 when attempting to browse
https://bugs.kde.org/show_bug.cgi?id=477673 Bug ID: 477673 Summary: KDEConnect - sshfs finished with exit code 1 when attempting to browse Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: ard...@gmx.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Fullu updated system, But when trying to browse phone error - KDEConnect - sshfs finished with exit code 1 when attempting to browse sshfs is already the newest version (3.7.1+repack-2). Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: X11 Processors: 2 × Intel® Celeron® 6305 @ 1.80GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: LENOVO Product Name: 82H9 System Version: IdeaPad 3 17ITL6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439900] Plasma UI is disabled while 'advanced options' dialog opened from Kickoff is open
https://bugs.kde.org/show_bug.cgi?id=439900 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 475265] New: Never becomes active at startup
https://bugs.kde.org/show_bug.cgi?id=475265 Bug ID: 475265 Summary: Never becomes active at startup Classification: Applications Product: k3b Version: 23.04.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: GUI/Usability Assignee: k...@kde.org Reporter: tony.cook@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY The splash scree/initial screen appears then nothing, no matter how long I wait. If I start it under strace I can see that it is "statt"ing ever single file in my unfortunately enormous home directory STEPS TO REPRODUCE 1. Start K3b 2. Initial screen is displayed 3. Wait forever. Nothing happens in under 30 minutes, occasionally it will return and allow further interaction, but then it appears to go back to scanning my entire home directory. 4. Sometimes it eventually actually works perfectly, maybe it caches its insane scan of the home directory. 5. If you go into settings, it starts again. OBSERVED RESULT No result EXPECTED RESULT Functioning K3b SOFTWARE/OS VERSIONS Linux/Gnome: Fedora 38 (available in About System) KDE Plasma Version: dont' know KDE Frameworks Version: don't know Qt Version: 5.15.10-9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 439219] exr thumbnailer crashes on empty file
https://bugs.kde.org/show_bug.cgi?id=439219 --- Comment #8 from Tony --- Cannot reproduce anymore with plasma 5.27 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364039] Dolphin crashed on file transfer in KIO::WidgetsAskUserActionHandler::askUserRename()
https://bugs.kde.org/show_bug.cgi?id=364039 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446874] Crash in QSGOpaqueTextureMaterialShader::updateState()
https://bugs.kde.org/show_bug.cgi?id=446874 Tony changed: What|Removed |Added CC|wladys...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445527] Dolphin crashes when closed while Ark compresses a file
https://bugs.kde.org/show_bug.cgi?id=445527 Tony changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=432891| -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 432891] Ark crashes when closed while loading an archive
https://bugs.kde.org/show_bug.cgi?id=432891 Tony changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=445527| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371560] Do not automatically append the Meta key to the list of shortcuts when Alt+F1 is set; instead let the actual Meta key itself be used or removed as a shortcut
https://bugs.kde.org/show_bug.cgi?id=371560 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] Dolphin doesn't remember icon size per folder with 'remember properties for each folder' configuration
https://bugs.kde.org/show_bug.cgi?id=408617 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442145] Doesn't open iphone in Dolphin
https://bugs.kde.org/show_bug.cgi?id=442145 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469266] New: Clicking on a window snapped into a tile unsnaps it
https://bugs.kde.org/show_bug.cgi?id=469266 Bug ID: 469266 Summary: Clicking on a window snapped into a tile unsnaps it Classification: Plasma Product: kwin Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: murrayt...@gmail.com CC: notm...@gmail.com Target Milestone: --- SUMMARY Windows unsnap when clicked, but not moved. It seems some applications immediately goes into "move mode" when clicked, unsnapping the window. STEPS TO REPRODUCE 1. Hold shift and drag a Google Chrome (or Chromium) window into a tile grid position 2. Release the mouse to snap the window into position, release shift key. 3. Click the window BELOW the title bar without moving the mouse OBSERVED RESULT Window is focused, unsnaps, and restores its original size EXPECTED RESULT Window is focused and stays at the original size and location SOFTWARE/OS VERSIONS Windows: N/A macOS: Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION The mouse changes to a move cursor immediately when clicking. When clicking the title bar, it seems to stay snapped. I originally had the merged Chrome window and title bar to save screen real estate, but disabled that so I at least had somewhere to click. I'm still constantly unsnapping my windows. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #4 from Tony --- I submitted the but report with the compressed attachment. After that I realised I could upload the three files separately, which I did. However, I now see that I cannot delete the compressed attachment, so the files are uploaded twice. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #3 from Tony --- Created attachment 158567 --> https://bugs.kde.org/attachment.cgi?id=158567=edit Demonstration KMyMoney file -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #2 from Tony --- Created attachment 158566 --> https://bugs.kde.org/attachment.cgi?id=158566=edit Incorrect numbers -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #1 from Tony --- Created attachment 158565 --> https://bugs.kde.org/attachment.cgi?id=158565=edit Correct numbers -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469195] New: Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 Bug ID: 469195 Summary: Transaction report in native currency show wrong amount Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: t...@marshall.name Target Milestone: --- Created attachment 158564 --> https://bugs.kde.org/attachment.cgi?id=158564=edit Three files described in the bug report. SUMMARY *** A transaction report showing a transfer from one account into an account having a different currency displays the amount and currency incorrectly when the "from" account is not included in the report. I do not want to include the "from" account in the report, as it includes too many transactions. I'm only interested in the transactions in the "to" account. *** STEPS TO REPRODUCE 1. Create a transaction that transfers from account "A" to account "B", which is in a different currency to "A". 2. Create a "Transactions by account" report and customise it to show only the transactions in account "B". 3. The line in the report that shows the amount transferred from account "A" has the currency of account "A" and the amount in the currency of account "B", but rounded using the decimal points defined for the currency of account "A". 4. Customise the report to include the transactions in account "A". 5. The line described in step 3 now displays correctly. SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION Attached are 3 files: 1. CorrectReport.png shows the report with the correct amount and currency. However, for it to display correctly, I had to include the "transfer from" account in the report, which I don't want to do. 2. IncorrectReport.png shows the report with the incorrect amount and currency. 3. MyTest.kmy shows the problem. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 468939] New: Akregator crashes on exit after marking feeds as read.
https://bugs.kde.org/show_bug.cgi?id=468939 Bug ID: 468939 Summary: Akregator crashes on exit after marking feeds as read. Classification: Applications Product: akregator Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: akregator (5.23.40 alpha (23.07.40)) Qt Version: 5.15.8 Frameworks Version: 5.106.0 Operating System: Linux 6.2.11-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Importing my feed list from quiterss into akregator and marking them all as read and closing it will result in this crash. The crash can be reproduced sometimes. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x31eccb1358d48ff) at /usr/include/c++/13/bits/atomic_base.h:503 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=0x31eccb1358d48ff) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref() (this=0x31eccb1358d48ff) at /usr/include/qt5/QtCore/qrefcount.h:55 #8 QString::QString(QString const&) (other=..., this=0x7ffc84ef1a20, this=, other=) at /usr/include/qt5/QtCore/qstring.h:1094 #9 Akregator::Feed::xmlUrl() const (this=0x562285e48130) at /usr/src/debug/akregator-23.07.70git.20230423T024803~9e78405/src/feed/feed.cpp:463 #10 0x7f2707989823 in Akregator::ArticleGrantleeObject::actionToken() const (this=) at /usr/src/debug/akregator-23.07.70git.20230423T024803~9e78405/src/formatter/articlegrantleeobject.cpp:101 #11 Akregator::ArticleGrantleeObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _id=, _a=, _c=) at /usr/src/debug/akregator-23.07.70git.20230423T024803~9e78405/build/src/akregatorprivate_autogen/CBONX6BG6C/moc_articlegrantleeobject.cpp:121 #12 0x7f270798a529 in Akregator::ArticleGrantleeObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_a=0x7ffc84ef1b30, _id=10, _c=QMetaObject::ReadProperty, _o=0x562286b58080) at /usr/src/debug/akregator-23.07.70git.20230423T024803~9e78405/build/src/akregatorprivate_autogen/CBONX6BG6C/moc_articlegrantleeobject.cpp:181 #13 Akregator::ArticleGrantleeObject::qt_metacall(QMetaObject::Call, int, void**) (this=0x562286b58080, _c=QMetaObject::ReadProperty, _id=10, _a=0x7ffc84ef1b30) at /usr/src/debug/akregator-23.07.70git.20230423T024803~9e78405/build/src/akregatorprivate_autogen/CBONX6BG6C/moc_articlegrantleeobject.cpp:166 #14 0x7f27060fa23a in QMetaProperty::read(QObject const*) const () at /lib64/libQt5Core.so.5 #15 0x7f26fbbb5a56 in Grantlee::MetaType::lookup(QVariant const&, QString const&) () at /lib64/libGrantlee_Templates.so.5 #16 0x7f26fbbc65db in Grantlee::Variable::resolve(Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #17 0x7f26fbbb897f in Grantlee::FilterExpression::resolve(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #18 0x7f26fbbb91af in Grantlee::FilterExpression::resolve(Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #19 0x7f26fbbb9522 in Grantlee::VariableNode::render(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #20 0x7f26fbbb3df0 in Grantlee::NodeList::render(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #21 0x7f26d40e19f3 in () at /usr/lib64/grantlee/5.3/grantlee_defaulttags.so #22 0x7f26fbbb3df0 in Grantlee::NodeList::render(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #23 0x7f26d40e1d0d in () at /usr/lib64/grantlee/5.3/grantlee_defaulttags.so #24 0x7f26d40e034e in () at /usr/lib64/grantlee/5.3/grantlee_defaulttags.so #25 0x7f26fbbb3df0 in Grantlee::NodeList::render(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #26 0x7f26fbbb3df0 in Grantlee::NodeList::render(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #27 0x7f26fbbc1fcf in Grantlee::TemplateImpl::render(Grantlee::OutputStream*, Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #28 0x7f26fbbc447e in Grantlee::TemplateImpl::render(Grantlee::Context*) const () at /lib64/libGrantlee_Templates.so.5 #29 0x7f2705439be0 in GrantleeTheme::GenericFormatter::render(QHash const&) const (this=this@entry=0x56228638eb40, mapping=...) at
[systemsettings] [Bug 426047] Various KCMs randomly crash in their destructors when switching to a different KCM
https://bugs.kde.org/show_bug.cgi?id=426047 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430465] Add Crop option in annotation tool
https://bugs.kde.org/show_bug.cgi?id=430465 --- Comment #18 from Tony Murray --- (In reply to Dan Dascalescu from comment #16) > Almost a year later, I still don't see cropping in Spectacle :-/ > > Probably not surprising, as Help -> About shows v21.12.3, copyright 2015? > I'm on Kubuntu 22.04, up to date. Additional information: (In reply to Prajna Sariputra from comment #17) > (In reply to Dan Dascalescu from comment #16) > > Almost a year later, I still don't see cropping in Spectacle :-/ > > > > Probably not surprising, as Help -> About shows v21.12.3, copyright 2015? > > I'm on Kubuntu 22.04, up to date. > > As per the "Version Fixed In" field of the bug you need Spectacle 22.04 and > kImageAnnotator 0.6.0. (In reply to Prajna Sariputra from comment #17) > (In reply to Dan Dascalescu from comment #16) > > Almost a year later, I still don't see cropping in Spectacle :-/ > > > > Probably not surprising, as Help -> About shows v21.12.3, copyright 2015? > > I'm on Kubuntu 22.04, up to date. > > As per the "Version Fixed In" field of the bug you need Spectacle 22.04 and > kImageAnnotator 0.6.0. Additional information for Dan: (from personal investigation): Kubuntu 22.10 (with backports repository) does have the kImageAnnotator with the cropping tool. KDE Neon has the latest Spectacle version (currently 22.12.3), but it relies on Ubuntu LTS (22.04) which has kImageAnnotator 0.5.3 (/usr/lib/x86_64-linux-gnu/libkImageAnnotator.so.0.5.3) The next Ubuntu LTS is due April 2024, and then Neon might be upgraded several months after that - October 2024, going by last time. When using Neon, I instead export to Gwenview which has both crop and annotate operations. (you may need to customize toolbar/editing tools) Hope this helps! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467822] SMS messages are sent but not acknowledged and replies are not received on CalyxOS
https://bugs.kde.org/show_bug.cgi?id=467822 --- Comment #1 from Tony Schmidt --- Sorry, I guess I can't grok how to edit a ticket description in Bugzilla, so adding as a comment: Desktop KDEConnect Version: GSConnect 50 (Also tried with latest KDE-Connect version) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467822] New: SMS messages are sent but not acknowledged and replies are not received on CalyxOS
https://bugs.kde.org/show_bug.cgi?id=467822
Bug ID: 467822
Summary: SMS messages are sent but not acknowledged and replies
are not received on CalyxOS
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Android
OS: Unspecified
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: t...@opensourceit.org
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
SUMMARY
SMS messages are sent but not acknowledged and replies are not received on
Pixel 4a5g running CalyxOS 4.7.5.
STEPS TO REPRODUCE
1. Pair phone with computer.
2. Send an SMS to a contact from the computer.
OBSERVED RESULT
Messages are sent to contact but the message appears gray (unacknowledged?) in
desktop UI and replies from the contact are only received on the phone and not
the computer.
EXPECTED RESULT
Sent messages should turn black and replies from contact should be received
(tested and works on Pixel 6 running stock Android).
SOFTWARE/OS VERSIONS
Desktop OS: PopOS 22.04
Mobile OS: CalyxOS 4.7.5
Android KDE Connect 1.23.2
ADDITIONAL INFORMATION
Several warnings are posted in the attached Android logs, but I'm unsure which
warning is the primary issue or what configuration the CalyxOS system may be
missing to support the SMS message acknowledgement and receiving functions.
Some of the suspect warnings and logs include:
* W ContextImpl: Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1222
com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3085
com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1616
com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:492
android.os.Binder.execTransactInternal:1285
* W BroadcastQueue: Permission Denial: receiving Intent {
act=android.intent.action.SERVICE_STATE flg=0x110 (has extras) } to
ProcessRecord{df2db07 2591:com.android.systemui/u0a171} (pid=2591, uid=10171)
requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid
1001)
* I QImsService: ImsSmsImpl : onSendSmsResult:: token:6 smsResponse:{
mMessageRef = 6, mSendSmsResult = 1, mSendSmsReason = 0, mNetworkErrorCode =
-1}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 467365] New: Plasma resets display position each time "Extend to left/right" is used
https://bugs.kde.org/show_bug.cgi?id=467365 Bug ID: 467365 Summary: Plasma resets display position each time "Extend to left/right" is used Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: wladys...@outlook.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY System has two screens - primary (external monitor) and secondary (built-in, laptop). I re-arrange them inside "Display Configuration" and save changes. Whenever "Extend to ..." option is used, position of secondary smaller screen gets reset to default one. STEPS TO REPRODUCE 1. Inside "Display Configuration" re-arrange screen position and save changes (move smaller screen to bottom) 2. Disable secondary (built-in) screen: Meta+P > "Switch to external screen" (primary one) 3. Use "Extend to left" option OBSERVED RESULT Screen position is reset. Screenshot 1 EXPECTED RESULT Screen position should be saved. Screenshot 2 SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (Arch Linux) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: X11 SCREENSHOTS https://imgur.com/a/B1sel9g -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 466818] kio-gdrive: Expired or missing access tokens
https://bugs.kde.org/show_bug.cgi?id=466818 tony changed: What|Removed |Added CC||ard...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466818] New: KIO GDrive does not work
https://bugs.kde.org/show_bug.cgi?id=466818 Bug ID: 466818 Summary: KIO GDrive does not work Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ard...@gmx.com Target Milestone: --- Expired or missing access tokens for account google7 STEPS TO REPRODUCE 1. create new online account goto network in dolphin Directory structure of My google drive is shown OBSERVED RESULT error message - Expired or missing access tokens for account google7 Unable to write to directory EXPECTED RESULT 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.
[ark] [Bug 425965] Please add support for zpaq and lrzip
https://bugs.kde.org/show_bug.cgi?id=425965 --- Comment #11 from Tony --- https://github.com/libarchive/libarchive/issues/1432 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464189] Sometimes when I activate the second monitor, the night color sets itself as temperature of the night
https://bugs.kde.org/show_bug.cgi?id=464189 Tony changed: What|Removed |Added CC||wladys...@outlook.com --- Comment #11 from Tony --- Can confirm this bug. Selecting "Extend to left/right" screen layout option turns on blue light on primary monitor if it was off, or turns it off if it already was on. Holding mouse button pressed on "Night color temperature" slider in order to preview temperature inside System Settings fixes issue. Some system info Operating System: EndeavourOS (Arch Linux) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1-lts (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465214] Add "Closed" flag to an account
https://bugs.kde.org/show_bug.cgi?id=465214 --- Comment #2 from Tony --- "How hard did you look for this feature?" Obviously not hard enough. To be honest, it didn't occur to me that it'd be a menu option. I just assumed that it would be a status flag, just like "Preferred Account", that appeared in the Edit Account dialog window. IMO it's more suitable to make it a status field, but the important thing is that the ability exists to close the account. Thank you for replying. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465214] New: Add "Closed" flag to an account
https://bugs.kde.org/show_bug.cgi?id=465214 Bug ID: 465214 Summary: Add "Closed" flag to an account Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: t...@marshall.name Target Milestone: --- SUMMARY *** It would be nice to be able to mark an account as closed. Then, in the Reports filter, one closed accounts are by default excluded, unless one chooses to include them by clicking a a "Include closed accounts" checkbox. Microsoft Money used to have this feature and it was useful. I have over 25 years' of accounts in KMyMoney, and so I have accumulated a lot of closed accounts over time (due to moving country, banks etc.) *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464852] Closing single window among grouped ones through a thumbnail often crashes whole task bar/panel
https://bugs.kde.org/show_bug.cgi?id=464852 Tony changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464852] Closing single window among grouped ones through a thumbnail often crashes whole task bar/panel
https://bugs.kde.org/show_bug.cgi?id=464852 --- Comment #5 from Tony --- (In reply to Vlad Zahorodnii from comment #4) > It sounds like plasmashell crashes. Can you get the backtrace of the crash? > Run > >coredumpctl list plasmashell > > find the relevant entry, usually the last one and use its PID in > > coredumpctl gdb > > when gdb loads, type "bt" and post its output here Here it is. Hopefully I did this correct: (gdb) bt #0 0x7fd71a234448 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #1 0x7fd71a2643b0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #2 0x7fd71a24d38e in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #3 0x7fd71a250bee in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #4 0x7fd71a2556b1 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #5 0x7fd71a23d0a5 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #6 0x7fd71a23d544 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #7 0x7fd71a296ac5 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #8 0x7fd71a2f0fd1 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #9 0x7fd71a2a1096 in () at /usr/lib/libQt5Quick.so.5 #10 0x7fd71a2a5fa4 in () at /usr/lib/libQt5Quick.so.5 #11 0x7fd71883732a in () at /usr/lib/libQt5Core.so.5 #12 0x7fd7183ba8fd in () at /usr/lib/libc.so.6 #13 0x7fd71843cd20 in () at /usr/lib/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464852] Closing single window among grouped ones through a thumbnail often crashes whole task bar/panel
https://bugs.kde.org/show_bug.cgi?id=464852 Tony changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #3 from Tony --- (In reply to Vlad Zahorodnii from comment #1) > When the panel disappears, do other windows disappear? Also is it x11 or > wayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464852] Closing single window among grouped ones through a thumbnail often crashes whole task bar/panel
https://bugs.kde.org/show_bug.cgi?id=464852 Tony changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Tony --- (In reply to Vlad Zahorodnii from comment #1) > When the panel disappears, do other windows disappear? Also is it x11 or > wayland? My bad - it's X11. Other windows do not disappear but what I also noticed: in addition to panel, wallpaper disappears as well. Basically when it happens - all I see for a split second is a black screen and remaining window/s -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455380] With n screens, Lock screen requires n fingerprint scans to unlock
https://bugs.kde.org/show_bug.cgi?id=455380 --- Comment #11 from Tony Murray --- Update after further research: In the pam.d configuration file, I changed the line: authsufficient pam_u2f.so to: authsufficient pam_u2f.so cue And the fingerprint reader now works as expected (enter once, and no need to click enter). You can also add the following for a prompt: authsufficient pam_u2f.so cue [cue_prompt=Please enter your fingerprint.] Ref from vendor: https://authentrend.com/secure-a-ubuntu-linux-login-using-u2f-with-atkeys/ The line was added to the file /etc/pam.d/other (which I use only for the lock screen, on KDE Neon) If anyone knows why adding 'cue' here works, or knows a good user-friendly up-to-date guide to pam.d configuration, please provide a link! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455380] With n screens, Lock screen requires n fingerprint scans to unlock
https://bugs.kde.org/show_bug.cgi?id=455380 Tony Murray changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||subscripti...@ruadesign.org --- Comment #10 from Tony Murray --- I am using KDE Plasma 5.26.5 with dual monitors, and the problem is still present - enter fingerprint twice to unlock. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 440762] Kamoso crashes after stoppping video recording.
https://bugs.kde.org/show_bug.cgi?id=440762 Tony changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Tony --- With version 22.11 i do not get this crash. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 460089] Blue screen after conection
https://bugs.kde.org/show_bug.cgi?id=460089 --- Comment #12 from Tony Murray --- Might be worthwhile to file a bug there to make sure it will be pushed out. On Tue, Nov 22, 2022 at 8:29 AM Mike Russo wrote: > https://bugs.kde.org/show_bug.cgi?id=460089 > > --- Comment #11 from Mike Russo --- > Can confirm Qt 5.15.7 fixes this. Compiled it on Ubuntu 22.10 with KDE > patches > as documented in > https://www.linuxfromscratch.org/blfs/view/svn/x/qt5.html > (I didn't skip QtWebEngine and so ran into a few problems with it, as > documented in > > https://www.reddit.com/r/QtFramework/comments/vpo4sf/compiling_qt_5154_using_gcc_12/ > and > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013025 > patch for that at : > > https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/commit/32198a3e0694401b745b4d01add18cdcddf658b4 > but I'm not sure QtWebEngine is necessary for KRDC anyway? > ) > then installed to /opt/qt5 set my LD_LIBRARY_PATH to /opt/qt5/lib and > created a > symlink to the KRDC plugins directory in /opt/qt5/lib and now KRDC works > correctly. So I hope Qt 5.15.7 is in the pipeline for Ubuntu 22.10! > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 460089] Blue screen after conection
https://bugs.kde.org/show_bug.cgi?id=460089 Tony Murray changed: What|Removed |Added CC||murrayt...@gmail.com --- Comment #8 from Tony Murray --- I was not able to reproduce this on Arch with 22.08.3 (Frameworks 5.100.0 and Qt 5.15.7). I was able to reproduce it on Ubuntu 22.10. It is not clear where the issue, if anyone can pinpoint it, that would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 366739] 2nd monitor is not being forgotten after turning it off and reboot.
https://bugs.kde.org/show_bug.cgi?id=366739 Tony changed: What|Removed |Added CC||jodr...@live.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 366739] 2nd monitor is not being forgotten after turning it off and reboot.
https://bugs.kde.org/show_bug.cgi?id=366739 Tony changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460346] Plasmashell crashing randomly
https://bugs.kde.org/show_bug.cgi?id=460346 --- Comment #3 from Tony Murray --- I switched to X11 graphics for now: and the crashes no longer occur. Here is some info about the Graphics card/driver. Computer is an intel NUC. $sudo lshw -c video *-display description: VGA compatible controller product: Iris Graphics 540 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0a width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:132 memory:de00-deff memory:8000-bfff ioport:f000(size=64) memory:c-d I think the graphic drivers are in the kernel? Is any further info or actions that would be useful from my side? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460346] New: Plasmashell crashing randomly
https://bugs.kde.org/show_bug.cgi?id=460346 Bug ID: 460346 Summary: Plasmashell crashing randomly Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: subscripti...@ruadesign.org Target Milestone: 1.0 Created attachment 152763 --> https://bugs.kde.org/attachment.cgi?id=152763=edit debug 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. Version 5.26.0 - (not on list, upgraded yesterday 12 Oct 2022) 2. Plasma shell is crashing repeatedly, randomly (as far as I can tell - no common actions, applications open prior to crash) 3. Losing certain amount of current work - need to save regularly OBSERVED RESULT Crash, black screen. plasmashell --replace, restarts the desktop (though all applications need restarted) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.26.0 (available in About System) KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Using dual-screens -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 390288] KIO/KDirModel: Kate crash while trying to save a new file to a Samba share
https://bugs.kde.org/show_bug.cgi?id=390288 --- Comment #8 from Tony --- Unfortunately I no longer use Samba shares and can not test this. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 410092] Ark crashes if you close it while decompressing a file.
https://bugs.kde.org/show_bug.cgi?id=410092 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 458250] 22.08.0 flatpak crashes on fresh AlmaLinux 9.0 install
https://bugs.kde.org/show_bug.cgi?id=458250 Tony Diep changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Tony Diep --- Installed debug version and kde SDK to get crash report and now Kdenlive starts properly. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 458250] New: 22.08.0 flatpak crashes on fresh AlmaLinux 9.0 install
https://bugs.kde.org/show_bug.cgi?id=458250 Bug ID: 458250 Summary: 22.08.0 flatpak crashes on fresh AlmaLinux 9.0 install Product: kdenlive Version: 22.08.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: tonyd...@tonydiep.com Target Milestone: --- SUMMARY Kdenlive 22.08.0 flatpak shows startup screen, then crashes, does not start. Tried both Wayland and Xorg. This is a fresh AlmaLinux 9.0 install. STEPS TO REPRODUCE 1. Install AlmaLinux 9.0 2. Install Kdenlive 22.08.0 flatpak 3. Start Kdenlive OBSERVED RESULT Startup screen appears. Program does not start. EXPECTED RESULT Program starts SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: AlmaLinux 9.0 (Emerald Puma) (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.
[plasmashell] [Bug 355588] Switching between alternative widgets makes them lose settings
https://bugs.kde.org/show_bug.cgi?id=355588 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 433968] Failed to contact bugs.kde.org: bugs.kde.org: Socket operation timed out
https://bugs.kde.org/show_bug.cgi?id=433968 Tony changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Tony --- Long time since i got this, plus can't reproduce with the recent changes made to drkonqui. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422424] kwin_wayland crashes when I change global theme
https://bugs.kde.org/show_bug.cgi?id=422424 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414834] Plasma crashes in QWaylandClientExtensionPrivate::handleRegistryGlobal() on Wayland when I change global theme
https://bugs.kde.org/show_bug.cgi?id=414834 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #20 from Tony Stipanic --- Created attachment 149846 --> https://bugs.kde.org/attachment.cgi?id=149846=edit Debug logs from script with MR -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #19 from Tony Stipanic --- I have tried running with the currently merged MR from the Plasma/5.25 branch but unfortunately, it doesn't seem to have fixed the issue. I've run the script with that version. The only useful logs I've got were from dmesg. The kwin one is just empty -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455319] Flood of "Restart the system now" notifications
https://bugs.kde.org/show_bug.cgi?id=455319 --- Comment #3 from tony den haan --- (In reply to Nate Graham from comment #1) > > 2. wait for something to go wrong > What does this mean exactly? The notification question is typically sent by > Discover. Under what condition does it appear multiple times like this? This is just one example, and it's not just this particular notification. Point is that in such case i get multiple notifications of same issue. I remember a case where i got over 100 :) Pretty sure i'll be able to provide another screenshot soon enough. Sadly no idea what condition causes this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #11 from Tony Stipanic --- I can also confirm reproducing this issue on both the 5.24.90 beta and the 5.25.0 release. Reverting back to 5.24.5 fixes this issue. Both USB-C DP and HDMI do not work for my laptop (ASUS ProArt Studiobook 16). Maybe important to note: The laptop is AMDGPU+NVIDIA. Nvidia must be turned on with nvidia-drm.modeset=1 so that the external monitor works on any version. I will try to get useful logs and attach it asap. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455331] New: Windows preview of task manager not working on 5.25.0
https://bugs.kde.org/show_bug.cgi?id=455331 Bug ID: 455331 Summary: Windows preview of task manager not working on 5.25.0 Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: antonio.dimarti...@gmail.com Target Milestone: 1.0 SUMMARY Hello, after the upgrade to KDE 5.25.0 windows preview on Icons only Task Manager doesn't work anymore on my system. STEPS TO REPRODUCE 1. Hover an open, non minimized application with mouse pointer 2. Wait for window preview to appear OBSERVED RESULT An icon of the application appears. EXPECTED RESULT A preview of the window should appear. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-48-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO System Version: ThinkPad X230 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 455319] New: KDE notification floods
https://bugs.kde.org/show_bug.cgi?id=455319 Bug ID: 455319 Summary: KDE notification floods Product: frameworks-knotifications Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kdeb...@tuxick.net CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 149734 --> https://bugs.kde.org/attachment.cgi?id=149734=edit kde flood screenshot STEPS TO REPRODUCE 1. use KDE 2. wait for something to go wrong OBSERVED RESULT Screen fills up with alerts. I've been seeing this on KDE for quite a while already. EXPECTED RESULT a single alert SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24 KDE Frameworks Version: About KDE no longer shows this Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 Tony Stipanic changed: What|Removed |Added CC||tony+...@stipanic.ch -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 440135] cli7zplugin: add support for original 7-zip
https://bugs.kde.org/show_bug.cgi?id=440135 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #7 from Tony --- (In reply to Max from comment #6) > Turned out p7zip and 7-Zip are not one to one compatible, there are minor > differences. I've updated patches, so that all autotests are now passed with > 7-Zip, but 2 out of 17 fail with p7zip. Unfortunately, I know nothing about > autotests to dig into fixing these errors, besides I'm not sure if it's > worth it considering p7zip status. Right now in opensuse tumbleweed ark is unable to open or compress to 7z. P7zip has been removed from the main tumbleweed repos for a while already, replaced by 7zip, not having this puling is a big regresion. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451800] Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell
https://bugs.kde.org/show_bug.cgi?id=451800 --- Comment #6 from Tony Green --- (In reply to Nate Graham from comment #2) > Hmm, the crash backtrace doesn't contain any KDE code in it. Not sure how to > proceed. Fresh backtrace created and attached. I hope this will help. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451800] Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell
https://bugs.kde.org/show_bug.cgi?id=451800 --- Comment #5 from Tony Green --- Created attachment 147819 --> https://bugs.kde.org/attachment.cgi?id=147819=edit Tarball containing WebSlice files -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451800] Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell
https://bugs.kde.org/show_bug.cgi?id=451800 --- Comment #4 from Tony Green --- Created attachment 147818 --> https://bugs.kde.org/attachment.cgi?id=147818=edit Crash report caused by WebSlice widget crashing Plasmashell By temporarily restoring from a pre-upgrade backup I have forced my Plasmashell to crash, thus recreating the original crash report I had previously lost. I hope this will be more useful at diagnosing the problem. My clue that it may have been WebSlice came from the line showing a problem in /usr/lib/libQt5WebEngineCore.so.5 (a lucky find/guess). The version of WebSlice which caused this problem was installed in 2018. This may be what's available as the "legacy" version when adding new widgets, but in case it's useful in diagnosing this problem I will upload a tarball of the widget's files as installed on the problem setup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451800] Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell
https://bugs.kde.org/show_bug.cgi?id=451800 --- Comment #3 from Tony Green --- (In reply to Nate Graham from comment #2) > Hmm, the crash backtrace doesn't contain any KDE code in it. Not sure how to > proceed. Probably my fault for not reading what the other user posted. I should be able to restore my config from a backup and get a fresh crash which (hopefully) will be more useful. Leave it with me and I'll sort that out as soon as time permits. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451800] Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell
https://bugs.kde.org/show_bug.cgi?id=451800 --- Comment #1 from Tony Green --- Something I forgot to mention. The most recent version of Webslice *doesn't* crash the desktop (though it doesn't seem to work). I assume what's available as the "legacy" version when downloading widgets is the problematic one, though as I've had that widget on my desktop for some years it could be an even older one. I can dig through my backups to find out the date it was installed if necessary. However, the fact that a newer version doesn't cause the problem doesn't mitigate this problem as other people will also have had similarly long-installed widgets and may not know how to recover from a crashed desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451800] New: Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell
https://bugs.kde.org/show_bug.cgi?id=451800 Bug ID: 451800 Summary: Changes between 5.24.2 and 5.24.3 cause some widgets to crash, bringing down Plasmashell Product: plasmashell Version: 5.24.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: k...@web-brewer.co.uk Target Milestone: 1.0 Created attachment 147669 --> https://bugs.kde.org/attachment.cgi?id=147669=edit Crash report from Reddit user SUMMARY *** When I upgraded to 5.24.3 and re-started, my desktop crashed, throwing out a crash report (which sadly I failed to file a bug for at the time). After analysing the report I discovered that the Webslice widget was crashing and with it, taking down plasmashell. Removing that widget allowed me to continue. A poster on Reddit (https://www.reddit.com/r/kde/comments/tjx3uq/kde_desktop_crashing_on_startup/) today posted a similar problem and with my guidance was able to get their desktop working. This time it turned out to be the Digital Clock widget. As that user posted their crash backtrace I'm adding that here. So it seems that some (API?) change in 5.24.3 is causing some widgets to crash, fatally for plasmashell. It seems worrying that a crashing widget can do this, but there may well be something in the desktop integration which makes this inevitable... STEPS TO REPRODUCE 1. Use an older Plasma version and add a Webslice widget to the desktop. 2. Upgrade to 5.24.3 and restart OBSERVED RESULT Desktop crashes on startup EXPECTED RESULT Desktop shouldn't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451380] New: Menu and keyboard shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=451380 Bug ID: 451380 Summary: Menu and keyboard shortcuts don't work Product: kdenlive Version: 21.12.3 Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: tonyd...@tonydiep.com Target Milestone: --- SUMMARY In 21.12.3 the menu items do not show after you click on them. Shortcut keys to cut / select, etc., do not work. STEPS TO REPRODUCE 1. Start KDENLIVE 2. Click File 3. OBSERVED RESULT File menu does not show EXPECTED RESULT File menu shows SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: About system does not show because menu is broken ADDITIONAL INFORMATION * happens in both Wayland and X11 * downgrading to previous kdenlive fixed problem flatpak update --commit=0fe16d64f530b03147264f6936fa73df5ce8b37e5f941ee4d07caca51d49f7dc org.kde.kdenlive -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426047] Crash in KQuickAddons::ConfigModule::~ConfigModule() for multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #36 from Tony --- (In reply to Nate Graham from comment #35) > From Bug 450164, it seems that installing the package that provides > qqmldata_p.h may fix it. Is anyone else able to reproduc ethat? Can't find that file on my system nor within a package on tumblewed, i have not hit this bug in a long time though. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 439891] [Feature Request] Allow websites to detect dark or light theme in use
https://bugs.kde.org/show_bug.cgi?id=439891 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 449158] Akregator crashes while removing feeds folder.
https://bugs.kde.org/show_bug.cgi?id=449158 Tony changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Tony --- *** This bug has been marked as a duplicate of bug 428714 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 428714] kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=428714 --- Comment #1 from Tony --- *** Bug 449158 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 428714] kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=428714 Tony changed: What|Removed |Added Product|kontact |akregator Component|general |general CC||jodr...@live.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 449158] New: Akregator crashes while removing feeds folder.
https://bugs.kde.org/show_bug.cgi?id=449158 Bug ID: 449158 Summary: Akregator crashes while removing feeds folder. Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: akregator (5.19.40 alpha (22.03.40)) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.2-xanmod1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.80 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Delete a feed folder, for example the default KDE feeds folder, it will crash soon after. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #4 0x7f5b5796cfc7 in QString::QString (other=..., this=, this=, other=...) at /usr/include/qt5/QtCore/qstring.h:1093 #5 Akregator::Feed::xmlUrl (this=0x55ad159e85e0) at /usr/src/debug/akregator-22.03.70git.20220124T192922~c08296af-ku.28.1.x86_64/src/feed/feed.cpp:463 #6 0x7f5b579556c2 in Akregator::ArticleGrantleeObject::actionToken (this=0x55ad15ae0d60) at /usr/src/debug/akregator-22.03.70git.20220124T192922~c08296af-ku.28.1.x86_64/src/formatter/articlegrantleeobject.cpp:100 #7 Akregator::ArticleGrantleeObject::qt_static_metacall (_o=0x55ad15ae0d60, _id=, _a=, _c=) at /usr/src/debug/akregator-22.03.70git.20220124T192922~c08296af-ku.28.1.x86_64/build/src/akregatorprivate_autogen/CBONX6BG6C/moc_articlegrantleeobject.cpp:121 #8 0x7f5b579564c9 in Akregator::ArticleGrantleeObject::qt_static_metacall (_a=0x7ffeabbcce50, _id=10, _c=QMetaObject::ReadProperty, _o=0x55ad15ae0d60) at /usr/src/debug/akregator-22.03.70git.20220124T192922~c08296af-ku.28.1.x86_64/build/src/akregatorprivate_autogen/CBONX6BG6C/moc_articlegrantleeobject.cpp:181 #9 Akregator::ArticleGrantleeObject::qt_metacall (this=0x55ad15ae0d60, _c=QMetaObject::ReadProperty, _id=10, _a=0x7ffeabbcce50) at /usr/src/debug/akregator-22.03.70git.20220124T192922~c08296af-ku.28.1.x86_64/build/src/akregatorprivate_autogen/CBONX6BG6C/moc_articlegrantleeobject.cpp:166 #10 0x7f5b56254f9a in QMetaProperty::read (this=this@entry=0x7ffeabbcd020, object=object@entry=0x55ad15ae0d60) at kernel/qmetaobject.cpp:3169 #11 0x7f5b4bb99f36 in doQobjectLookUp (property=..., object=0x55ad15ae0d60) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/metatype.cpp:86 #12 Grantlee::MetaType::lookup (object=..., property=...) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/metatype.cpp:113 #13 0x7f5b4bba7cab in Grantlee::Variable::resolve (this=, c=) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/variable.cpp:211 #14 0x7f5b4bb98a9f in Grantlee::FilterExpression::resolve (this=, stream=0x7ffeabbcd330, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/filterexpression.cpp:213 #15 0x7f5b4bb99310 in Grantlee::FilterExpression::resolve (this=0x55ad1766cf78, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/filterexpression.cpp:260 #16 0x7f5b4bb99693 in Grantlee::VariableNode::render (this=0x55ad1766cf60, stream=0x7ffeabbcd900, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/nodebuiltins.cpp:37 #17 0x7f5b4bb959c0 in Grantlee::NodeList::render (this=this@entry=0x55ad166c3928, stream=stream@entry=0x7ffeabbcd900, c=c@entry=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/node.cpp:180 #18 0x7f5ad40f6cae in IfNode::render (this=, stream=0x7ffeabbcd900, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/defaulttags/if.cpp:99 #19 0x7f5ad40f1556 in ForNode::renderLoop (c=, stream=, this=) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/defaulttags/for.cpp:122 #20 ForNode::render (this=0x55ad167049f0, stream=, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/defaulttags/for.cpp:214 #21 0x7f5b4bb959c0 in Grantlee::NodeList::render (this=this@entry=0x55ad1668f578, stream=stream@entry=0x7ffeabbcd900, c=c@entry=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/node.cpp:180 #22 0x7f5ad40f6cae in IfNode::render (this=, stream=0x7ffeabbcd900, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/defaulttags/if.cpp:99 #23 0x7f5b4bb959c0 in Grantlee::NodeList::render (this=0x55ad165fd7e8, stream=0x7ffeabbcd900, c=0x7ffeabbcd968) at /usr/src/debug/grantlee5-5.2.0-ku.8.3.x86_64/templates/lib/node.cpp:180 #24 0x7f5b4bba334f in Grantlee::TemplateImpl::render (this=, stream=0x7ffeabbcd900, c=0x7ffeabbcd968) at
[kwin] [Bug 448943] Night color not enabled auto after log in
https://bugs.kde.org/show_bug.cgi?id=448943 --- Comment #8 from Tony Evl --- (In reply to galdera from comment #2) > waiting for user to try with 5.23.5 I update fedora from test repos. Also kde plasma updated to 5.23.5 version. The issue is still there... No have issue with fresh install fedora 35 with kde plasma 5.22.x -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto after log in
https://bugs.kde.org/show_bug.cgi?id=448943 Tony Evl changed: What|Removed |Added Summary|Night color not enabled |Night color not enabled |auto when log in|auto after log in -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto when log in
https://bugs.kde.org/show_bug.cgi?id=448943 --- Comment #7 from Tony Evl --- (In reply to galdera from comment #6) > I think so but I would recommend to wait > until Fedora updates the stable repo. > regards Okay, thanks for the answer. I'll try to do it on a test PC or on a main one. In any case, I'll write here when I have news. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto when log in
https://bugs.kde.org/show_bug.cgi?id=448943 --- Comment #5 from Tony Evl --- (In reply to galdera from comment #2) > waiting for user to try with 5.23.5 On stable fedora 35 is 5.23.4. Need I change to testing my repos, right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto when log in
https://bugs.kde.org/show_bug.cgi?id=448943 --- Comment #4 from Tony Evl --- (In reply to galdera from comment #2) > waiting for user to try with 5.23.5 -- You are receiving this mail because: You are watching all bug changes.
