[Bluedevil] [Bug 425941] unable to connect PS3/PS4 bluetooth controllers
https://bugs.kde.org/show_bug.cgi?id=425941 James Th changed: What|Removed |Added Summary|unbale to connect PS3/PS4 |unable to connect PS3/PS4 |bluetooth controller|bluetooth controllers -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 425941] unbale to connect PS3/PS4 bluetooth controller
https://bugs.kde.org/show_bug.cgi?id=425941 --- Comment #3 from James Th --- what you say makes total sense! :) So, I used buetoothctl, and this was the result: luetoothctl Agent registered [NEW] Device 28:C1:3C:A2:91:02 Wireless Controller [bluetooth]# scan on Discovery started [CHG] Controller D4:6D:6D:53:46:06 Discovering: yes [bluetooth]# devices Device 28:C1:3C:A2:91:02 Wireless Controller [CHG] Device 28:C1:3C:A2:91:02 Trusted: yes [bluetooth]# pair 28:C1:3C:A2:91:02 Attempting to pair with 28:C1:3C:A2:91:02 Failed to pair: org.bluez.Error.ConnectionAttemptFailed [bluetooth]# So it must be failing earlier in the stack. So I know this is no longer a KDE issue, but do you have any ideas at all please? Here's my output from: journalctl | grep Blue* Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: Core ver 2.22 Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: HCI device and connection manager initialized Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: HCI socket layer initialized Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: L2CAP socket layer initialized Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: SCO socket layer initialized Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: hci0: Firmware revision 0.1 build 50 week 12 2019 Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Starting Bluetooth service... Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Bluetooth daemon 5.54 Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Started Bluetooth service. Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Reached target Bluetooth. Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: BNEP filters: protocol multicast Aug 29 16:54:24 yshtola.chilli.ai kernel: Bluetooth: BNEP socket layer initialized Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Bluetooth management interface 1.17 initialized Aug 29 16:54:37 yshtola.chilli.ai systemd[588]: Starting Bluetooth OBEX service... Aug 29 16:54:37 yshtola.chilli.ai systemd[588]: Started Bluetooth OBEX service. Aug 29 16:54:37 yshtola.chilli.ai kernel: Bluetooth: RFCOMM TTY layer initialized Aug 29 16:54:37 yshtola.chilli.ai kernel: Bluetooth: RFCOMM socket layer initialized Aug 29 16:54:37 yshtola.chilli.ai kernel: Bluetooth: RFCOMM ver 1.11 Aug 29 16:54:37 yshtola.chilli.ai kded5[666]: bluedevil: Bluetooth operational changed true Here's what appears in systemctl status bluetooth: Aug 29 16:54:24 yshtola.chilli.ai systemd[1]: Started Bluetooth service. Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Starting SDP server Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Bluetooth management interface 1.17 initialized Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: sixaxis: compatible device connected: Wireless Controller (054C:09CC /sys/devices/pci:00/:00:14.0> Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: sixaxis: setting up new device Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Authentication attempt without agent Aug 29 16:54:24 yshtola.chilli.ai bluetoothd[423]: Add Device complete for unknown device 28:C1:3C:A2:91:02 Aug 29 16:55:05 yshtola.chilli.ai bluetoothd[423]: sixaxis: compatible device connected: Wireless Controller (054C:09CC /sys/devices/pci:00/:00:14.0> Aug 29 16:55:05 yshtola.chilli.ai bluetoothd[423]: sixaxis: setting up new device -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 425941] unbale to connect PS3/PS4 bluetooth controller
https://bugs.kde.org/show_bug.cgi?id=425941 --- Comment #1 from James Th --- Here's some (hopefully) useful info for you: lsmod | grep sony hid_sony 36864 0 ff_memless 20480 1 hid_sony hid 143360 5 hidp,usbhid,hid_sony,hid_generic,hid_jabra ls /dev/input/by-id/ Permissions Size User Group Date Modified Name lrwxrwxrwx10 root root 29 Aug 14:35 usb-GN_Netcom_A_S_Jabra_EVOLVE_LINK_MS_0002C5EF3EF207-event-if03 -> ../event10 lrwxrwxrwx 9 root root 29 Aug 14:35 usb-Microsoft_Wired_Keyboard_600-event-if01 -> ../event7 lrwxrwxrwx 9 root root 29 Aug 14:35 usb-Microsoft_Wired_Keyboard_600-event-kbd -> ../event5 lrwxrwxrwx 9 root root 29 Aug 14:35 usb-PixArt_Microsoft_USB_Optical_Mouse-event-mouse -> ../event4 lrwxrwxrwx 9 root root 29 Aug 14:35 usb-PixArt_Microsoft_USB_Optical_Mouse-mouse -> ../mouse0 lrwxrwxrwx10 root root 29 Aug 14:39 usb-Sony_Interactive_Entertainment_Wireless_Controller-event-if03 -> ../event12 lrwxrwxrwx@ 10 root root 29 Aug 14:39 usb-Sony_Interactive_Entertainment_Wireless_Controller-if03-event-joystick -> ../event13 lrwxrwxrwx10 root root 29 Aug 14:39 usb-Sony_Interactive_Entertainment_Wireless_Controller-if03-event-mouse -> ../event11 lrwxrwxrwx@6 root root 29 Aug 14:39 usb-Sony_Interactive_Entertainment_Wireless_Controller-if03-joystick -> ../js0 lrwxrwxrwx 9 root root 29 Aug 14:39 usb-Sony_Interactive_Entertainment_Wireless_Controller-if03-mouse -> ../mouse1 lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 1576) Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 Bus 001 Device 010: ID 054c:09cc Sony Corp. DualShock 4 [CUH-ZCT2x] Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0b0e:0305 GN Netcom Jabra EVOLVE Link MS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2020-08-29 14:35:06 BST; 1h 6min ago Docs: man:bluetoothd(8) Main PID: 416 (bluetoothd) Status: "Running" Tasks: 1 (limit: 19007) Memory: 3.3M CGroup: /system.slice/bluetooth.service └─416 /usr/lib/bluetooth/bluetoothd Aug 29 14:57:45 yshtola.chilli.ai bluetoothd[416]: sixaxis: compatible device connected: Wireless Controller (054C:09CC /sys/devices/pci:00/:00:14.0> Aug 29 14:57:45 yshtola.chilli.ai bluetoothd[416]: sixaxis: setting up new device Aug 29 14:59:11 yshtola.chilli.ai bluetoothd[416]: sixaxis: compatible device connected: Wireless Controller (054C:09CC /sys/devices/pci:00/:00:14.0> Aug 29 14:59:11 yshtola.chilli.ai bluetoothd[416]: sixaxis: setting up new device Aug 29 14:59:37 yshtola.chilli.ai bluetoothd[416]: 28:C1:3C:A2:91:02: error updating services: Host is down (112) Aug 29 14:59:48 yshtola.chilli.ai bluetoothd[416]: 28:C1:3C:A2:91:02: error updating services: Host is down (112) Aug 29 15:05:01 yshtola.chilli.ai bluetoothd[416]: 28:C1:3C:A2:91:02: error updating services: Host is down (112) Aug 29 15:05:48 yshtola.chilli.ai bluetoothd[416]: 28:C1:3C:A2:91:02: error updating services: Host is down (112) Aug 29 15:37:32 yshtola.chilli.ai bluetoothd[416]: sixaxis: compatible device connected: Wireless Controller (054C:09CC /sys/devices/pci:00/:00:14.0> Aug 29 15:37:32 yshtola.chilli.ai bluetoothd[416]: sixaxis: setting up new device -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 425941] New: unbale to connect PS3/PS4 bluetooth controller
https://bugs.kde.org/show_bug.cgi?id=425941 Bug ID: 425941 Summary: unbale to connect PS3/PS4 bluetooth controller Product: Bluedevil Version: 5.19.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: ja...@thornber.io CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I'm trying to connect either my PS3 or PS4 controller via bluetooth in KDE. STEPS TO REPRODUCE 1. Plug in either my PS3/PS4 controller via USB 2. Device appears in "Available devices" (KDE Bluetooth menu bar) 3. Click 'Connect' and it fails with message: Device is unreachable OBSERVED RESULT As above, I can play e.g Steam, using either of my controllers, but they always need to be connected via USB cable, would be good to use them without a cable! :) EXPECTED RESULT Device connects via bluetooth. Let me know what logs would be useful for you to see, please! Many thanks! :) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.5-arch1-1 OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8500 CPU @ 3.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 422867] New: unable to Alt hover for image previews
https://bugs.kde.org/show_bug.cgi?id=422867 Bug ID: 422867 Summary: unable to Alt hover for image previews Product: konsole Version: 20.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY There's a new feature to be able to alt-hover over an image in konsole, and for it to display mini images of the image file, or image folder contents. I'm using konsole 20.04.2, and I can't see the setting option to enable thumbnails. So do I need to enable this somehow, please? Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.7.2-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418234] New: new feature request: enable/disable individual akonadi plugins?
https://bugs.kde.org/show_bug.cgi?id=418234 Bug ID: 418234 Summary: new feature request: enable/disable individual akonadi plugins? Product: Akonadi Version: 5.13.40 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I don't use all of the Akonadi plugins e.g. those for Kmail, Kjots, kalarm, etc. But I do use some of the functionality, so would it be possible to enable/disable individual Akonadi plugins via the akaonadictl CLI interface? It would save RAM (ok, a little bit), but it would enable me to have a much better granual control over what happens on my laptop. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.5.6-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 7.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 417168] New: can we have the possibility to connect to systemd-netwrokd?
https://bugs.kde.org/show_bug.cgi?id=417168 Bug ID: 417168 Summary: can we have the possibility to connect to systemd-netwrokd? Product: plasma-nm Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I know that I need to have network-manager installed to use the plasma-nm app, but can we also have an app that can interface with systemd-networkd? I know that this is a bit of a big-ask so I appreciate it if it's not possible! It's simply about choice, rather than anything else! Many thanks! :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.17.5 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 413856] option missing: check 'x' minutes after start-up
https://bugs.kde.org/show_bug.cgi?id=413856 --- Comment #2 from James Th --- Ooh! I had no idea that I could even do that! :) thank you! On Tue, Nov 5, 2019 at 9:44 PM +, "Nate Graham" wrote: https://bugs.kde.org/show_bug.cgi?id=413856 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- > manually via the CLI (which is my preferred way of doing updates) Why not just uninstall plasma-pk updates, then? If you're not going to use it, just delete it. :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 413856] New: option missing: check 'x' minutes after start-up
https://bugs.kde.org/show_bug.cgi?id=413856 Bug ID: 413856 Summary: option missing: check 'x' minutes after start-up Product: plasma-pk-updates Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ja...@thornber.io Target Milestone: --- SUMMARY currently as soon as I boot up my linux box within seconds of the network connection becoming available, then the system software update runs. I'd like the option to be able to delay this action by 'x' minutes, this would give me the time to run it manually via the CLI (which is my preferred way of doing updates). Would something like this be possible, please? OBSERVED RESULT System software update runs automatically a few seconds after startup/network connection becoming available. EXPECTED RESULT I should be able to delay the default action by 'x' minutes after startup if possible, please. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 --- Comment #4 from James Th --- Thank you so much - you were correct. I had a look at my repos, and for some unknown reason I had a Leap repo enabled and active, in my TW distro. I disabled that, and it downgraded the kontact versions, when I did a zypper dup! Thanks again, you saved me a complete headache today! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 James Th changed: What|Removed |Added Resolution|DOWNSTREAM |WAITINGFORINFO --- Comment #2 from James Th --- is the wrong version of kcontacts able to stop kmail, korganizer, Akregator, and several other programs from starting, please? Also what should the correct version of kcontact be please? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413466] New: akonadi displaying problems, I can't open applications e.g kontact, kmail etc.
https://bugs.kde.org/show_bug.cgi?id=413466 Bug ID: 413466 Summary: akonadi displaying problems, I can't open applications e.g kontact, kmail etc. Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Created attachment 123490 --> https://bugs.kde.org/attachment.cgi?id=123490&action=edit Akonadictl errors SUMMARY I can't open kmail, korganizer etc. If you look at the attached file, then there's lots of errors happening e.g. /usr/bin/akonadi_sendlater_agent: symbol lookup error: /usr/lib64/libKF5ContactEditor.so.5: undefined symbol: _ZN9KContacts9Addressee16staticMetaObjectE org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_sendlater_agent' returned with exit code 127 (Unknown error) org.kde.pim.akonadicontrol: "/usr/bin/akonadi_sendlater_agent" crashed too often and will not be restarted! I've run akonadictl fsck and also vacuum, no errors reported. I completely reinstalled opensuse last week, so it's still relatively clean I think. No errors appear in journalctl, and I'm unsure where to look tbh. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT As above - kontact, kmail etc don't open. EXPECTED RESULT kontact, kmail opens correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW 20191023 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 413191] New: KDE 5.17 - unable to logon with root password to execute YAST application
https://bugs.kde.org/show_bug.cgi?id=413191 Bug ID: 413191 Summary: KDE 5.17 - unable to logon with root password to execute YAST application Product: kwalletmanager Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I try to run YAST2-Printer and KDE asks me for my root password, when I provide it then it comes up with the following notice: journalctl -b -f The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control Oct 19 13:55:40 alisaie su[15720]: gkr-pam: couldn't unlock the login keyring. I know that the password is correct, but I still receive the above. This has only started happening once I upgraded to KDE 5.17.0 Apologies if this bug is raised against the wrong app! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW 20191016 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413183] New: confusing Login-screen SDDM in System settings
https://bugs.kde.org/show_bug.cgi?id=413183 Bug ID: 413183 Summary: confusing Login-screen SDDM in System settings Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Created attachment 123336 --> https://bugs.kde.org/attachment.cgi?id=123336&action=edit SDDM System Setting confusing icon SUMMARY Apologies in advance, I'm not sure which application this is so I'm probably logging this to the wrong place! Please see the attached screenshot, which shows System Settings -> Start Up and Shutdown option -> Login Screen (SDDM). It has an exclamation mark in the bottom corner. To me this says that there's something wrong in my SDDM start up and shutdown settings, but when I look there I can't see anything wrong! So either: 1) we need another exclamation mark within the settings tabs to hi-light where the issue is, *or* 2) The icon needs to be adapted to not show the exclamation mark, i.e. it's a false report. STEPS TO REPRODUCE 1. open up System Settings -> Start Up and Shutdown option, and see if the exclamation mark is there. If it is, then try to find a corresponding issue within the settings screen. OBSERVED RESULT As above EXPECTED RESULT either: 1) we need another exclamation mark within the settings, to hi-light where the issue is, *or* 2) The logo needs to be adapted to not show the exclamation mark, ie it's a false report. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE TW 20191016 (available in About System) KDE Plasma Version: 5.17 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413183] confusing Login-screen SDDM in System settings
https://bugs.kde.org/show_bug.cgi?id=413183 James Th changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 413041] make package update notification dismissable
https://bugs.kde.org/show_bug.cgi?id=413041 --- Comment #4 from James Th --- Brill! Thanks a lot! On Fri, Oct 18, 2019 at 5:50 PM +0100, "Nate Graham" wrote: https://bugs.kde.org/show_bug.cgi?id=413041 Nate Graham changed: What|Removed |Added Version|5.16.5 |unspecified Resolution|WORKSFORME |--- Assignee|lei...@leinir.dk|jgrul...@redhat.com Status|RESOLVED|REPORTED Component|Updater |general Product|Discover|plasma-pk-updates --- Comment #3 from Nate Graham --- Ah, that thing. That's actually not Discover, it's plasma-pk-updates. Moving there. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413041] make package update notification dismissable
https://bugs.kde.org/show_bug.cgi?id=413041 James Th changed: What|Removed |Added CC||ja...@thornber.io --- Comment #2 from James Th --- Created attachment 123323 --> https://bugs.kde.org/attachment.cgi?id=123323&action=edit screenshot showing CLI update, and software update notification Apologies I tried a screen recording, but it didn't work - hopefully next time though (at least on openSUSE TW we don't need to wait so long for an update)! Anyway, the screenshot shows that I updated via the CLI, but still showing update notification, with no 'X' available to close the notification. Hope this helps, and is a little clearer than my original bug report! :) If I'm being a numpty then please do re-close this ticket! :) -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 413060] New: baloo crashed
https://bugs.kde.org/show_bug.cgi?id=413060 Bug ID: 413060 Summary: baloo crashed Product: BalooWidgets Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: ja...@thornber.io Target Milestone: --- Created attachment 123257 --> https://bugs.kde.org/attachment.cgi?id=123257&action=edit baloo crash report SUMMARY Upgraded to latest openSUSE TumbleWeed, and upon first logon, then I received a baloo crash notification. I've attached the dump file for you. I' sorry but I have no idea what this software does, or is useful for, so I can't be very helpful with this bug report! STEPS TO REPRODUCE 1. upgrade to openSUSE TW (20191014), logon. 2. should/could receive a baloo crash notification. OBSERVED RESULT baloo crashes via a notification. EXPECTED RESULT baloo doesn't crash! :) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE TW (20191014) (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 413041] New: make package update notification dismissable
https://bugs.kde.org/show_bug.cgi?id=413041 Bug ID: 413041 Summary: make package update notification dismissable Product: frameworks-knotifications Version: 5.62.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ja...@thornber.io CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Currently if I get an notification update informing me that I have new packages to install - as I usually update via the CLI I have no way to dismiss the notification unless I open discover app which subsequently finds no updates. It would be great to be able to dismiss it (in the standard way), if I've already updated via the CLI. STEPS TO REPRODUCE 1. wait for standard KDE 'update' notification 2. update via CLI 3. Try to dismiss KDE 'update' notification. OBSERVED RESULT as outlined above EXPECTED RESULT as outlined above SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412725] allow multiple 'to' addresses on the same line in the 'to:' address box
https://bugs.kde.org/show_bug.cgi?id=412725 --- Comment #11 from James Th --- I think you're missing the point. The point is quite simply, you shouldn't have to agree with me, but you should at least listen to what I say. The question is to do with respecting of my ideas, both as an end-user, and as a member of the KDE community. I don't see your role as being Kmail's gate- keeper. I see your role as being a listener to ideas and opinions, and having the common-sense to be able to say "OK, i don't necessarily agree with what this person is proposing, but there might be an idea worth implementing for the good of the end-users." By me asking for the possibility to separate email addresses is really not a silly idea. Outlook, Apple mail, etc do this by default. If I wrote a feature request asking for kmail to default to a pink colour scheme with purple unicorns, i would expect you to use the intelligence that you have, and say 'no'. My only "fault" in all this is to request a feature that so many other email clients use. When you wrote and explained to me, that there was a reason why we have multiple 'To:' boxes, I didn't rubbish your thoughts, or your explanation. I took it onboard, listened to your reasons, and I came up with what I believe to be a reasonable compromise so that we could both have a solution. To be told by someone else that this is 'an exotic feature that is only useful to your workflow" is rude, unnecessary, and unhelpful. Do you know that just like you, I really, really like kmail. It's so much better than Thunderbird, and just like you I want it to succeed. It's the only mail client that I have on my openSUSE TW box, it's the only one that I actually want to use. We have common-ground, I would just like us to build on that, and to build a successful solution that works for all of us. To engage with each other, and to challenge each other is great! To basically piss on my ideas, because people don't believe in them is not democratic, fair, helpful, or professional. > https://bugs.kde.org/show_bug.cgi?id=412725 > > --- Comment #10 from Laurent Montel --- > (In reply to James Th from comment #9) > > > If ever you wonder why people don't use kmail, it's exactly things like > > this that are the reason why. > > > > Poor design, lack of compromise, and etotistical attitudes. > > A bad design because you can't write "f...@kde.org, b...@kde.org" ?:) > Is it not work when we use several line ? if it's the case ok it's a bad > design. > But adding a option only because you prefer having "f...@kde.org, > b...@kde.org" it's not a solution. and I don't think that it's a lack of > compromise when you just want to complexify code only as you want to be > able to write to email separated with a ',' ... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412725] allow multiple 'to' addresses on the same line in the 'to:' address box
https://bugs.kde.org/show_bug.cgi?id=412725 --- Comment #9 from James Th --- If ever you wonder why people don't use kmail, it's exactly things like this that are the reason why. Poor design, lack of compromise, and etotistical attitudes. On 08/10/2019, 18:02, "Christophe Giboudeaux" wrote: https://bugs.kde.org/show_bug.cgi?id=412725 Christophe Giboudeaux changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #8 from Christophe Giboudeaux --- No need for new options for exotic features only useful for your workflow. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412726] integrate whatsapp notifications within kdeconnect - possible?
https://bugs.kde.org/show_bug.cgi?id=412726 --- Comment #2 from James Th --- Hi Nicolas, Yes it does, but just not in the way that I was expecting tbh. From what I see then the ability comes from its own kmail notification system. I was hopeing that it would be possible in the default/main KDE notification system. Does that make sense? So the discussion was about aligning this request with how other KDE apps currently work, rather than having simply a KDE plugin. I think that that is a fair appraisal of the discussion! __ On 08/10/2019, 17:48, "Nicolas Fella" wrote: https://bugs.kde.org/show_bug.cgi?id=412726 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- All of this works when the notification plugin is enabled -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412726] integrate whatsapp notifications within kdeconnect - possible?
https://bugs.kde.org/show_bug.cgi?id=412726 --- Comment #3 from James Th --- Sorry, completely wrong thread! Please ignore my last email! __ I'll have a look at the plugin then! Thank you! On 08/10/2019, 17:48, "Nicolas Fella" wrote: https://bugs.kde.org/show_bug.cgi?id=412726 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- All of this works when the notification plugin is enabled -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412725] allow multiple 'to' addresses on the same line in the 'to:' address box
https://bugs.kde.org/show_bug.cgi?id=412725 James Th changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #7 from James Th --- (In reply to Laurent Montel from comment #6) > Hi, > > The problem is not just adding/removing option. > It's just that we implemented check signature type for email address and we > display an icon on the line. It's for that that Dan modified it. > > So we can't switch back otherwise this feature will not work. > > Regards I've re-opened this ticket. Simply because Perhaps there's a way that could be a good compromise: if 'check signature type' is not enabled (which in my case will probably never happen, and will likely be the use-case for a number of other people), then the code could allow multiple addresses within the same 'to:' box (comma- separated) Once 'check signature type' is enabled, then perform the current code ie 1:1 relationship between email address & 'to:' box. This way I think that we can preserve the hard-work that Dan's done, whilst providing another option. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #21 from James Th --- Hopefully I'm getting the formatting correct! __ Please see my inline comments below. On 08/10/2019, 16:42, "Laurent Montel" wrote: https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #19 from Laurent Montel --- (In reply to Nate Graham from comment #18) > (In reply to Laurent Montel from comment #14) > > For you each feature must be activated by default ?! > > We have plugin when we can or not activate feature as for other apps. > Making everything configurable does not remove the responsibility to set > appropriate defaults. Keep in mind "Simple by default, powerful when needed". > > (In reply to Laurent Montel from comment #15) > > Ah why only show the oldest of the new emails ? > > I don't want to see the oldest I want to see the specific email and it's not > > possible when we have multiple emails. > All right, for the multiple email case, maybe it should just bring KMail to > the front without highlighting any particular email. >>Ok we open kmail great and what we will do ? we don't know where are new >>emails... >>So no really useful. Sorry but I *am* able to see the number of unread emails for each folder when I open kmail. Just because you don’t find this useful, doesn’t mean that it's not useful to others. It's possible to code for this functionality to switch the 'click to open email' function off. That way I think you can be happy, or? > > (In reply to Laurent Montel from comment #16) > > Why it's complicated to click on a button ? > > As I explain if we click on notification for closing it and don't click on > > specific cross we will open email as it's not that I want... > That's out of sync with what every other app does though. The KDE community > has voted for Consistency. This kind of thing is important to our users. We > need to keep that in mind. >> Thunderbird does it for example ? I'm pretty sure that Apple does it, and so does outlook __ -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412725] allow multiple 'to' addresses on the same line in the 'to:' address box
https://bugs.kde.org/show_bug.cgi?id=412725 --- Comment #5 from James Th --- Great, thanks for letting me know that this is the right place to include feature requests! Just don't want to waste your time, if it wasn't! :) > https://bugs.kde.org/show_bug.cgi?id=412725 > > --- Comment #4 from Christophe Giboudeaux --- > Anyway, bugs.kde.org is the right place for feature requests. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412725] allow multiple 'to' addresses on the same line in the 'to:' address box
https://bugs.kde.org/show_bug.cgi?id=412725 --- Comment #2 from James Th --- Ok, many thanks! I understand that this is a feature request - where is the best place to file feature requests please, as I completely understand than bugs.kde.org is perhaps not the correct place? thanks! > https://bugs.kde.org/show_bug.cgi?id=412725 > > Christophe Giboudeaux changed: > >What|Removed |Added > > Status|REPORTED|RESOLVED > Resolution|--- |NOT A BUG > > --- Comment #1 from Christophe Giboudeaux --- > KMail did a different choice, when you enter a comma (or a semicolon) after > an email address, it automatically creates a new "To" line. > > The same thing happens if you paste email addresses (eg: > f...@email.com,b...@email.com) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412726] New: integrate whatsapp notifications within kdeconnect - possible?
https://bugs.kde.org/show_bug.cgi?id=412726 Bug ID: 412726 Summary: integrate whatsapp notifications within kdeconnect - possible? Product: kdeconnect Version: 1.10 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: ja...@thornber.io Target Milestone: --- SUMMARY currently if I receive a whatsapp message, then I don't receive a notification in KDE connect. However, if someone calls me on whatsapp, then I receive an 'unknown caller' message. Is it possible to include better/tighter whatsapp integration within KDE connect please? On a complete whim, would it also be possible to reply to a whatsapp message using KDE connect? STEPS TO REPRODUCE 1. ask someone to whatsapp you - if its a message then you'll receive no notification. if it's a call, then you'll see 'unknown caller' diaplayed in kde connect. OBSERVED RESULT as above. EXPECTED RESULT whatsapp message notification in KDE Connect, and also a separate whatsapp caller notification. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412725] New: allow multiple 'to' addresses on the same line in the 'to:' address box
https://bugs.kde.org/show_bug.cgi?id=412725 Bug ID: 412725 Summary: allow multiple 'to' addresses on the same line in the 'to:' address box Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY currently if i have more than one to: recipient in an email,then kmail creates multiple lines for each address. I would like to have the option of comma separating them so that they are all in the same 'to:' box. STEPS TO REPRODUCE 1. write multiple to: email addresses in kmail. OBSERVED RESULT creates multiple 'to:' address boxes EXPECTED RESULT have them all on the same line SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412637] Panel resets upon restarting Plasma
https://bugs.kde.org/show_bug.cgi?id=412637 --- Comment #3 from James Th --- (In reply to James Th from comment #2) > I also tried to logon using wayland yesterday, and I receive the same > problem. i moved my application bar to the bottom of the screen, and it works correctly. So it might be something to do with it being at the top of the screen, which makes it behave differently. I also noticed that should I have my application launcher at the top left of the screen, when I open something such as Kate, then the icon moves along so that it is always to the right of the kate menus. Happy to screen shot this, if it would be useful? thanks, in advance! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412680] New: thinkpad sound function keys no longer functional
https://bugs.kde.org/show_bug.cgi?id=412680 Bug ID: 412680 Summary: thinkpad sound function keys no longer functional Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY i used to be able to use the thinkpad function keys synonymous with F1, F2,F3, and F4 (microphone) to change the volume. This is no longer possible STEPS TO REPRODUCE 1. try to change the volume on a thinkpad (ensuring Fn key is in-active first). 2. Nothing happens i.e. no icon appears on the screen, nor an actual increase/decrease in audible volume. OBSERVED RESULT Unable to change the volume using the dedicated thinkpad volume keys. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (20191003) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412637] application panel resets upon restarting KDE
https://bugs.kde.org/show_bug.cgi?id=412637 --- Comment #2 from James Th --- I also tried to logon using wayland yesterday, and I receive the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412637] application panel resets upon restarting KDE
https://bugs.kde.org/show_bug.cgi?id=412637 --- Comment #1 from James Th --- Created attachment 123037 --> https://bugs.kde.org/attachment.cgi?id=123037&action=edit journalctl-widget-reset-issue.txt i have tried the following, and the issue still occurs: 1) ctlr+Alt+F1, then ctrl+alt+f7 issue still remains. 2) created a new test user, and issue remians (journalctl -b attached for that user) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412637] New: application panel resets upon restarting KDE
https://bugs.kde.org/show_bug.cgi?id=412637 Bug ID: 412637 Summary: application panel resets upon restarting KDE Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I currently have the application bar at the top of my screen, and I have various widgets e.g. system panel, time, search etc which I manually located to the top right of my screen. My application launcher is located at the top left of my screen. However, When I reboot my laptop, all widgets end up on the left side of the screen, so I need to manually move them back. STEPS TO REPRODUCE 1. move your application bar to the top of the screen, and move widgets manually to the right side of the screen. 2. restart your laptop/PC OBSERVED RESULT system tray, search, calendar etc move to the left of my screen next to my application launcher. EXPECTED RESULT Remain on the top right of my screen upon reboot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412631] calendar widget should connect to Korganizer
https://bugs.kde.org/show_bug.cgi?id=412631 --- Comment #6 from James Th --- working now! For anyone's future reference: Right click on digital-clock in the applications bar, and select "configure digital clock". Click on the calendar tab on the left-hand side, and then enable 'PIM events Plugin'. A new tab will then appear called 'PIM events Plugin', where you can select the calendar to sync too. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412631] calendar widget should connect to Korganizer
https://bugs.kde.org/show_bug.cgi?id=412631 --- Comment #5 from James Th --- (In reply to Antonio Rojas from comment #4) > (In reply to James Th from comment #3) > > (In reply to James Th from comment #2) > > > ok, thanks! > > > > > > I'm guessing it should be a distro decision as to whether or not > > > kdepim-addons is installed by default, or is it a KDE decision as to what > > > should be included in the default KDE install, please? > > > > Actually it's already installed - so I think that this should be re-opened > > as a bug: > > > > > zypper in kdepim-addons > > >Loading repository data... > > >Reading installed packages... > > >'kdepim-addons' is already installed. > > >No update candidate for 'kdepim-addons-19.08.1-1.1.x86_64'. The highest > > >>available version is already installed. > > >Resolving package dependencies... > > > > >Nothing to do. > > And you have enabled the plug-in in the applet settings and selected the > calendars you want to display? Really sorry, but how can I check that please? I'm quite new to KDE! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412631] calendar widget should connect to Korganizer
https://bugs.kde.org/show_bug.cgi?id=412631 --- Comment #3 from James Th --- (In reply to James Th from comment #2) > ok, thanks! > > I'm guessing it should be a distro decision as to whether or not > kdepim-addons is installed by default, or is it a KDE decision as to what > should be included in the default KDE install, please? Actually it's already installed - so I think that this should be re-opened as a bug: > zypper in kdepim-addons >Loading repository data... >Reading installed packages... >'kdepim-addons' is already installed. >No update candidate for 'kdepim-addons-19.08.1-1.1.x86_64'. The highest >>available version is already installed. >Resolving package dependencies... >Nothing to do. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412631] calendar widget should connect to Korganizer
https://bugs.kde.org/show_bug.cgi?id=412631 --- Comment #2 from James Th --- ok, thanks! I'm guessing it should be a distro decision as to whether or not kdepim-addons is installed by default, or is it a KDE decision as to what should be included in the default KDE install, please? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412631] New: calendar widget should connect to Korganizer
https://bugs.kde.org/show_bug.cgi?id=412631 Bug ID: 412631 Summary: calendar widget should connect to Korganizer Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY currently the calendar widget just shows the dates & month information. It should be connected to the korganizer app, so that I can view appointments etc. STEPS TO REPRODUCE 1. install calendar widget onto the application panel. try to view appointments etc. 2. 3. OBSERVED RESULT standalone calendar widget, just shows days/months etc. EXPECTED RESULT to be able to view appointments within my korganiser. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412579] New: kmail notifications, should link back to the actual email.
https://bugs.kde.org/show_bug.cgi?id=412579 Bug ID: 412579 Summary: kmail notifications, should link back to the actual email. Product: frameworks-knotifications Version: 5.62.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ja...@thornber.io CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY if i receive a notification, that i have a new email, i should be able to click on the email subject, and it opens the actual email. It makes the notification interactive then, rather than being passive, if that makes sense? STEPS TO REPRODUCE 1. close kmail, and when you receive a notification that you have new email, try to click on the subject line. It's not possible. OBSERVED RESULT notifications are passive, and not interactive. EXPECTED RESULT click on the kmail notification, and it should open the email directly from the notification screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE TW (20190930) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Could also be expanded to include other KDE applications, i would guess. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412474] KMail should set first account 'inbox' to open by default
https://bugs.kde.org/show_bug.cgi?id=412474 --- Comment #4 from James Th --- Hi, That makes perfect sense to me! :) Thanks for your help! James On Mon, Sep 30, 2019 at 6:00 PM +0100, "Jonathan Marten" wrote: https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Summary|kmail should by default |KMail should set first |open 'inbox', rather than |account 'inbox' to open by |mailbox |default Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WORKSFORME |--- --- Comment #3 from Jonathan Marten --- It should be. The default setting for the check box is on, but for the folder is -1 which means none assigned. Since a folder cannot be assigned until an account has been created, maybe this should be done after a new account creation: if no default folder has yet been assigned, set it to the inbox of the newly created account. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412474] kmail should by default open 'inbox', rather than mailbox
https://bugs.kde.org/show_bug.cgi?id=412474 --- Comment #2 from James Th --- Many thanks for this information! Would it be better do you think, if this was actually the default behaviour? James On 30/09/2019, 11:18, "Jonathan Marten" wrote: https://bugs.kde.org/show_bug.cgi?id=412474 Jonathan Marten changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- The folder to select when starting KMail should be configurable: Settings - Configure KMail - Misc - Folders Turn on "Open this folder at startup" and select the required folder. Please report if this option is not present or does not appear to work. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412474] New: kmail should by default open 'inbox', rather than mailbox
https://bugs.kde.org/show_bug.cgi?id=412474 Bug ID: 412474 Summary: kmail should by default open 'inbox', rather than mailbox Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY Currently if I open kmail, it will open and hi-light the mailbox icon and therefore it doesn't show any emails. I think that it should open the inbox folder, so that my emails are shown. I know that this is a small thing, in the grand scheme of things, but I think it would be beneficial. STEPS TO REPRODUCE 1. close Kmail if already open. 2. open kmail, and you'll notice that the default behaviour is to start with the mailbox name. OBSERVED RESULT by default kmail opens with the mailbox hi-lighted. EXPECTED RESULT by default kmail should open with the Inbox folder hi-lighted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse TW 20190925 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412444] New: can't right click my mouse, to bring up the 'paste' option.
https://bugs.kde.org/show_bug.cgi?id=412444 Bug ID: 412444 Summary: can't right click my mouse, to bring up the 'paste' option. Product: Discover Version: 5.16.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ja...@thornber.io CC: aleix...@kde.org Target Milestone: --- SUMMARY If I copy text from say Akregator, and then try to find the software within discover. If i right click on the search box, then I don't get the option to paste my clipboard into it (the standard right-click menu). I can do ctrl-v to paste it in however, so this bug only relates to the mouse-click. STEPS TO REPRODUCE 1. copy text from an application, and open discover 2. right-click in the search box, and the standard right-click menu option to paste won't appear. OBSERVED RESULT unable to paste using right-click EXPECTED RESULT menu appears, with the option to paste. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse TW (20190925) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412443] New: software update notification doesn't have away of clearing the entries
https://bugs.kde.org/show_bug.cgi?id=412443 Bug ID: 412443 Summary: software update notification doesn't have away of clearing the entries Product: frameworks-knotifications Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ja...@thornber.io CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Currently the software update notification will inform me should I have software updates available. However, if I choose to install the updates via the command line, then the update notification continues to state that I have updates available. There should be a button which I can click on to remove the "available" updates (perhaps the broom icon that's in the clipboard application?), also perhaps the automatic updater should re-run itself automatically after perhaps 30 mins to see if the updates haven't been installed via a different means. STEPS TO REPRODUCE 1. wait for notifications to appear in the software update notification. Update using the command line (sudo zypper dup), and allow the updates to install, try to clear/remove the software update notification from your task bar. OBSERVED RESULT no way to clear the software update notification. EXPECTED RESULT should be able to clear all entries by clicking a button inside the notification window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW 20190925 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 412403] when submitting my first drkonki automated bug report it fails at installing backtrace symbols
https://bugs.kde.org/show_bug.cgi?id=412403 --- Comment #1 from James Th --- Apologies i think it should be 'debug symbols' rather than 'backtrace symbols'! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 412403] New: when submitting my first drkonki automated bug report it fails at installing backtrace symbols
https://bugs.kde.org/show_bug.cgi?id=412403 Bug ID: 412403 Summary: when submitting my first drkonki automated bug report it fails at installing backtrace symbols Product: drkonqi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I just logged a seperate automated bug via drkonki when my Kmail crashed. It suggested that it would be useful to the devs if I installed the backtrace symbols(?). When I attempted to do that I could see that it failed to download them in my terminal. The way around it was to enable the OPENSUE-Tumbleweed-debug repo in YAST2. It would be far better for drkonki to automatically check to see if this repo is enabled, and if not ask the user if it can be enabled (again done automatically), and then try to download the backtrace symbols. This would certainly lead to a smoother interaction with the user, and could potentially increase more useful bug reports to the devs. STEPS TO REPRODUCE 1. invoke drkonki without the debug repos being enabled, and try to log an automated bug report. OBSERVED RESULT As above EXPECTED RESULT As above SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE TW (20190925) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412402] New: Kmail crashes when enabling/disabling favourites folders in kmail settings
https://bugs.kde.org/show_bug.cgi?id=412402 Bug ID: 412402 Summary: Kmail crashes when enabling/disabling favourites folders in kmail settings Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Application: kmail (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.2.14-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was disabling the "Show favourite folders view" after disabling then Kmai crashed. Likewise if I go back and then enable it, then Kmail crashes again. So it seems to occur if I toggle between these two options. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f83bcdbefc0 (LWP 6173))] Thread 25 (Thread 0x7f83837fe700 (LWP 10505)): #0 0x7f83cc0be16c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f83c577a486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f83c577ae53 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f83c577afd1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f83c5733141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f83c5735fdd in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f83c57366d4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f83c577d2c5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f83cc0b7faa in start_thread () from /lib64/libpthread.so.0 #9 0x7f83cfa8673f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f835700 (LWP 6835)): #0 0x7f83cfa7780c in read () from /lib64/libc.so.6 #1 0x7f83cb65870f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f83cb6a4cbe in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f83cb6a6372 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f83cb6a649f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f83ce63899b in QEventDispatcherGlib::processEvents (this=0x7f83580082c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f83ce5e10db in QEventLoop::exec (this=this@entry=0x7f835fffeb20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f83ce419021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f83ce41a1a2 in QThreadPrivate::start (arg=0x55cc358547e0) at thread/qthread_unix.cpp:360 #9 0x7f83cc0b7faa in start_thread () from /lib64/libpthread.so.0 #10 0x7f83cfa8673f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f839700 (LWP 6834)): #0 0x7f83cc0be16c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f83c577a486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f83c577ae53 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f83c577afd1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f83c5733141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f83c573632b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f83c57366d4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f83c577d2c5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f83cc0b7faa in start_thread () from /lib64/libpthread.so.0 #9 0x7f83cfa8673f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f83827fc700 (LWP 6827)): #0 0x7f83cc0be16c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f83c577a486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f83c577ae53 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f83c577afd1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f83c5733141 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f83c573632b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f83c57366d4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f83c577d2c5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f83cc0b7faa in start_thread () from /lib64/libpthread.so.0 #9 0x7f83cfa8673f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f82a587f700 (LWP 6352)): #0 0x7f83cfa7bcbf in poll () from /lib64/libc.so.6 #1 0x7f83c1d0c4f2 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7f83c1cfde39 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7f83c1cfe4bf in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f83c1cfe570 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f83c1
[kde] [Bug 412312] New: document icons not showing correctly in recent documents
https://bugs.kde.org/show_bug.cgi?id=412312 Bug ID: 412312 Summary: document icons not showing correctly in recent documents Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Created attachment 122857 --> https://bugs.kde.org/attachment.cgi?id=122857&action=edit generic icons being shown. SUMMARY Document icons not showing correctly in recent documents STEPS TO REPRODUCE 1. go to the main menu -> History -> scroll down to the end. OBSERVED RESULT I see generic document icons for home, documents, desktop, and downloads. EXPECTED RESULT The relevant document icon being show, which is the same as those that I see on my desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Please see attached screenshot! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412207] kmail should have the option to block email tracking images
https://bugs.kde.org/show_bug.cgi?id=412207 James Th changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 412215] zombie feed link
https://bugs.kde.org/show_bug.cgi?id=412215 --- Comment #7 from James Th --- The feed aggregator that I added was: https://bugs.kde.org/buglist.cgi?f1=reporter&o1=equals&v1=%25user%25&resolution=---&ctype=atom&title=Open%20bugs%20reported%20by%20me Attached a screenshot to help! On 23/09/2019, 11:42, "Christophe Giboudeaux" wrote: https://bugs.kde.org/show_bug.cgi?id=412215 --- Comment #6 from Christophe Giboudeaux --- (In reply to James Th from comment #5) > I just removed the bugs.kde.org link from akregator, and then tried to add > it > once again. It's not adding my link to akregator at all. > So back to my original request, what's the feed URL added to akregator? In akregator, right click on the feed name → "Edit feed" -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 412215] zombie feed link
https://bugs.kde.org/show_bug.cgi?id=412215 --- Comment #5 from James Th --- I just removed the bugs.kde.org link from akregator, and then tried to add it once again. It's not adding my link to akregator at all. should I log this as a 2nd separate bug, do you think? thanks! On Monday, 23 September 2019 11:04:55 BST you wrote: > https://bugs.kde.org/show_bug.cgi?id=412215 > > --- Comment #3 from Christophe Giboudeaux --- > Ah, now I see (but can't reproduce). Was it the first time you used > akregator? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 412215] zombie feed link
https://bugs.kde.org/show_bug.cgi?id=412215 --- Comment #4 from James Th --- On Monday, 23 September 2019 11:04:55 BST you wrote: > https://bugs.kde.org/show_bug.cgi?id=412215 > > --- Comment #3 from Christophe Giboudeaux --- > Ah, now I see (but can't reproduce). Was it the first time you used > akregator? That's great! :) I'm pretty sure it was the second time, as i initially looked to see what akregator actually does, and I read the standard RSS feeds, then later on I thought it would be good to add the bugs.kde.org to akregator, and that's when I noticed it. I'm sorry that I can't be more helpful! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 412215] zombie feed link
https://bugs.kde.org/show_bug.cgi?id=412215 --- Comment #2 from James Th --- Hiya, Sorry, I don't think I explained it so well in the bug report! The actually RSS feed works, but if you look at the screenshot, you'll see that there appears to be another blank RSS feed directly below the working one. It has no RSS info, and there's just a grey line pointing to a blank feed. Does this make more sense please? On Mon, Sep 23, 2019 at 7:46 AM +0100, "Christophe Giboudeaux" wrote: https://bugs.kde.org/show_bug.cgi?id=412215 --- Comment #1 from Christophe Giboudeaux --- No issue. The opened reports I created are visible in akregator after clicking on the feed icon. What's this feed URL for you? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 412215] New: zombie feed link
https://bugs.kde.org/show_bug.cgi?id=412215 Bug ID: 412215 Summary: zombie feed link Product: akregator Version: 5.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Created attachment 122809 --> https://bugs.kde.org/attachment.cgi?id=122809&action=edit dummy rss feed in akregtor SUMMARY I subscribe to the RSS feed of bugs that I log on KDE, and I subscribe to my bug list using the RSS feed in akregator. There appears to be a dummy/zombie feed that's been created in akregator, after clicking on the RSS icon from bugs.kde.org. STEPS TO REPRODUCE 1. ensure you have at least 1 bug created in your name on bugs.kde.org 2. click on the RSS image/icon on this site, and open the RSS feed in akregator. 3. You'll notice the rss feed, and immediately below you'll see a dummy/zombie feed, which is blank and not used at all. (please see the attached screenshot) OBSERVED RESULT dummy rss feed immediately below imported folder/bug list rss feed in akregator. EXPECTED RESULT just to see the one single rss feed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412207] New: kmail should have the option to block email tracking images
https://bugs.kde.org/show_bug.cgi?id=412207 Bug ID: 412207 Summary: kmail should have the option to block email tracking images Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY it's possible for me to switch on 'do not download external images' in the global settings for when i open an email, but often this leads to poorly rendered emails. I would like to be able to download external images within an email but to specifically have email tracking images not downloaded/activated. This will mean that when/where I open an email is not noted by the 3rd party, whilst I am still able to read correctly formatted emails. The do not track functionality should ideally be enabled by default. Is my request even possible?! Perhaps by only downloading images larger than 4-5 pixels - just a guess! STEPS TO REPRODUCE 1. it's currently standard functionality. OBSERVED RESULT all images including the 1px tracking image is downloaded. EXPECTED RESULT All images are downloaded except if the image size is less than e.g. 4/5 pixels. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412206] New: sorting mailbox names (ascending/descending) should not sort sub-folders names in the same way
https://bugs.kde.org/show_bug.cgi?id=412206 Bug ID: 412206 Summary: sorting mailbox names (ascending/descending) should not sort sub-folders names in the same way Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I can currently sort mailbox names by clicking on the up/down icon, which is a good feature. However, sorting the sub-folder names at the same time is not very useful. This functionality should be restricted to sorting mailbox names only. Perhaps a right click on the mailbox should allow for sorting of sub-folder names in ascending or descending order. STEPS TO REPRODUCE 1. open up kmail, and click on the ascending/descending icon in the mailbox folder list. 2. Open up your mailbox, and you'll the sub-folders structure has also been reversed. OBSERVED RESULT as above EXPECTED RESULT just the mailbox names should be changed to be ascending/descending. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412205] New: unable to hide local folders
https://bugs.kde.org/show_bug.cgi?id=412205 Bug ID: 412205 Summary: unable to hide local folders Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I use IMAP/SMTP, and I'm synchronising my emails and folder structure across a number of different devices. I would therefore like to have the possibility of being able to remove/hide local folders. An old bug report exists: 44864 (from 2003-2012) - and most ppl seem to agree with the idea of being able to remove/hide local folders. Perhaps it's time to review this feature request? STEPS TO REPRODUCE 1. open up Kmail, and try to remove local folders by right-clicking on them, or elsewhere. OBSERVED RESULT Local Folders can't be removed/hidden. EXPECTED RESULT I should be able to delete/hide them SOFTWARE/OS VERSIONS Linux/KDE Plasma: Open SUSE TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412190] New: 'HTML Message' or 'plain text message' identifier, could be improved
https://bugs.kde.org/show_bug.cgi?id=412190 Bug ID: 412190 Summary: 'HTML Message' or 'plain text message' identifier, could be improved Product: kmail2 Version: 5.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY The message to denote what kind of email message you have i.e. 'HTML message' or 'Plain text message' is strangely positioned between the mail folder list, and the email body itself. Perhaps we can have an icon instead to denote this in the email header section ie where it shows to, from, and subject header. There's plenty of room on the right hand side, or it can be placed elsewhere. STEPS TO REPRODUCE 1. open up kmail and click on an email, and you'll see the html/plain text notification message between the email folders window and the email body. OBSERVED RESULT As above. EXPECTED RESULT perhaps an icon at the top of the email message as explained above, or in a different more relevant location. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse TW (latest) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 412162] New: deselected pop-up notes in prefs, but popup notes still showing in overview
https://bugs.kde.org/show_bug.cgi?id=412162 Bug ID: 412162 Summary: deselected pop-up notes in prefs, but popup notes still showing in overview Product: kontact Version: 5.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: notes Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- Created attachment 122783 --> https://bugs.kde.org/attachment.cgi?id=122783&action=edit pop-up notes kontact screen SUMMARY I deselected pop-up notes in Kontact, but on the main screen I still see pop-up notes showing. Screen shot attached. STEPS TO REPRODUCE 1. Open Kontact, go to 'settings' -> 'configure kontact' -> ensure that pop-up notes is not selected. Close the settings screen. 2. select the 'summary' screen in Kontact, and you'll see the pop-up notes section stating 'no notes found' OBSERVED RESULT As above. EXPECTED RESULT pop-up notes should not appear on the summary screen at all. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse TW (latest version) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.13.1 ADDITIONAL INFORMATION please see attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 412139] hover over battery icon seems to give time for only 1 battery rather than accounting for the 2 batteries.
https://bugs.kde.org/show_bug.cgi?id=412139 James Th changed: What|Removed |Added Summary|hover over battery icon |hover over battery icon |seems to give time for 1|seems to give time for only |battery rather than |1 battery rather than |accounting for two. |accounting for the 2 ||batteries. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 412139] New: hover over battery icon seems to give time for 1 battery rather than accounting for two.
https://bugs.kde.org/show_bug.cgi?id=412139 Bug ID: 412139 Summary: hover over battery icon seems to give time for 1 battery rather than accounting for two. Product: Powerdevil Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY If i hover over the battery icon at the bottom of my screen then I get the 'time-remaining' for only one battery, rather than it taking into account both internal batteries. STEPS TO REPRODUCE 1. have a laptop with 2 batteries, and hover over the battery icon, and it will show you something like: 2:05 remaining, 76% When it switches to the second internal battery it will then show e.g.5:00 remaining, 49% OBSERVED RESULT As above. EXPECTED RESULT 7:05 remaining, 99% (or whatever the actual combined values are for both batteries) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Opensuse TW (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Happy to send a screenshot if that would be useful? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412137] New: message list behaviour
https://bugs.kde.org/show_bug.cgi?id=412137 Bug ID: 412137 Summary: message list behaviour Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY if i select an email message in kmail, and then press the down arrow key, the action seems to be moving through the email message, rather than selecting the next email. STEPS TO REPRODUCE 1. select an email message so that its hilighted in blue. 2. Press the down/up arrow key, and it will scroll down/up the actual email message OBSERVED RESULT as above EXPECTED RESULT to select the next email message. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: opensuse TW (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411992] New: kmail poorly written notification text if no password entered to collect email
https://bugs.kde.org/show_bug.cgi?id=411992 Bug ID: 411992 Summary: kmail poorly written notification text if no password entered to collect email Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY Currently if Kmail cannot connect to the email server, due to it not remembering the password, then the notification comes up "Resource Mail (james) is broken". It's not broken, it's more that it doesn't have the password. So I think that this is a poorly-written notification text. Something like "KMail is unable to connect to the mail server, as no password has been entered", would perhaps be better. STEPS TO REPRODUCE 1. remove password from Kmail account 2. Restart Kmail, and close the password input screen ie don't enter your password. 3. Look at the notification that comes up within KDE. OBSERVED RESULT Receive notification that "Resource Mail (james) is broken". EXPECTED RESULT Receive notification that "Kmail needs a password to connect to the email server" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed (20190909) (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411992] kmail poorly written notification text if no password entered to collect email
https://bugs.kde.org/show_bug.cgi?id=411992 James Th changed: What|Removed |Added CC||ja...@thornber.io -- You are receiving this mail because: You are watching all bug changes.
