[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 Trevor Parsons changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 480926] New: Get Hot New Stuff - file not found
https://bugs.kde.org/show_bug.cgi?id=480926 Bug ID: 480926 Summary: Get Hot New Stuff - file not found Classification: Applications Product: kstars Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: tbry...@mts.net Target Milestone: --- Version 3.6.9 Trying to download the Star Catalogues and images from Get Hot New Stuff. Keeps saying "Could not install "_": file not found. Affected Tycho-2 Star Catalogue USNO NOMAD Catalogue Inline thumbnail images NGC Images IC Images Common Images -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480542] Appimage looking for PyQt5.QtTest in the wrong place
https://bugs.kde.org/show_bug.cgi?id=480542 --- Comment #1 from Trevor Noble --- My old login details point to a defunct email address which I no longer have access to. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480542] New: Appimage looking for PyQt5.QtTest in the wrong place
https://bugs.kde.org/show_bug.cgi?id=480542
Bug ID: 480542
Summary: Appimage looking for PyQt5.QtTest in the wrong place
Classification: Applications
Product: krita
Version: unspecified
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: * Unknown
Assignee: krita-bugs-n...@kde.org
Reporter: technicalgraph...@eircom.net
Target Milestone: ---
There appears to be a bug in all appimage versions since 5.1.4. It is also
projecting forward in all the nightly builds. The bug does not occur however in
the current Flatpak 5.2.2 version
from PyQt5.QtTest import QTest
QTest.qWait(2000)
print('I was waiting for two seconds')
returns the following:
ImportError: /lib/x86_64-linux-gnu/libQt5Test.so.5: undefined symbol:
_Z32qt_register_signal_spy_callbacksRK21QSignalSpyCallbackSet, version Qt_5
-
System:Kernel: 5.4.0-167-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1
dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04
focal
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial:
UEFI: American Megatrends v: 5603
date: 10/14/2020
Memory:RAM: total: 15.62 GiB used: 3.27 GiB (21.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges
required.
CPU: Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP
arch: Zen L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
svm bogomips: 114985
Speed: 2212 MHz min/max: 2200/3600 MHz boost: enabled Core speeds
(MHz): 1: 2185 2: 2208 3: 2185 4: 2196 5: 2200
6: 2196 7: 2196 8: 2195 9: 2219 10: 2195 11: 2195 12: 2196 13: 2198
14: 2196 15: 2199 16: 2196
Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: ASUSTeK driver:
nvidia v: 535.154.05 bus ID: 07:00.0
chip ID: 10de:1c81
Display: x11 server: X.Org 1.20.13 driver: nvidia unloaded:
fbdev,modesetting,nouveau,vesa
resolution: 2560x1440~60Hz
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 475029] Rendering crashes when rendering to webp.
https://bugs.kde.org/show_bug.cgi?id=475029 --- Comment #6 from Trevor --- I was able to get webm to work. webp is a picture format to my understanding. So, maybe that's the problem? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475029] New: Rendering crashes when rendering to webp.
https://bugs.kde.org/show_bug.cgi?id=475029 Bug ID: 475029 Summary: Rendering crashes when rendering to webp. Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: trevorvance...@gmail.com Target Milestone: --- SUMMARY I cannot render any projects as webp. It always crashes. STEPS TO REPRODUCE 1. Select 'webp' preset. 2. Press "Render to File". OBSERVED RESULT Rendering of C:/Users/owner/Videos/untitled_%05d.webp crashed [consumer avformat] video codec libwebp unrecognised - ignoring EXPECTED RESULT Output rendered webp file. SOFTWARE/OS VERSIONS Windows: 10 Kdenlive: 23.08.1 ADDITIONAL INFORMATION I looked up the error, "video codec libwebp unrecognised" and found the following, https://stackoverflow.com/questions/67904563/unknown-encoder-libwebp So, I figured it was probably an ffmpeg issue. I downloaded the Windows version from the link and pointed FFmpeg, FFplay, and FFprobe to those but I got the same error so I changed back to the ones installed with kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467590] Cannot crop screenshots from annotation view in main window anymore
https://bugs.kde.org/show_bug.cgi?id=467590 Trevor Parsons changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 468267] Wayland warnings
https://bugs.kde.org/show_bug.cgi?id=468267 Trevor Whitney changed: What|Removed |Added CC||trevorjwhit...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Trevor Whitney --- I am seeing this same behavior. SOFTWARE/OS VERSIONS Operating System: NixOS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.1.38 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 550 / 550 Series I also am running 2x screens with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471644] digiKam: some Mac computers are unable to export any Tag data (under TagList column for Exif).
https://bugs.kde.org/show_bug.cgi?id=471644 --- Comment #6 from Trevor Eakes --- (In reply to Maik Qualmann from comment #2) > If the issue only occurs in exported photos, which camera brand and model is > it affecting? Which image format is used (JPG/RAW). As a test, activate the > writing of metadata with ExifTool in the digiKam settings under Metadata. > > Maik Between our Macs (some unable to export, some able) the camera models are all the same. To be clear, the photos all export and contain all their metadata except for the Tag info. I am trying to figure out how to salvage the issue by identifying under what metadata field DigiKam is storing Tag data and figuring out how to copy that information to a new metadata field. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471644] digiKam: some Mac computers are unable to export any Tag data (under TagList column for Exif).
https://bugs.kde.org/show_bug.cgi?id=471644 --- Comment #5 from Trevor Eakes --- (In reply to Maik Qualmann from comment #2) > If the issue only occurs in exported photos, which camera brand and model is > it affecting? Which image format is used (JPG/RAW). As a test, activate the > writing of metadata with ExifTool in the digiKam settings under Metadata. > > Maik Between our Macs (some unable to export, some able) the camera models are all the same. To be clear, the photos all export and contain all their metadata except for the Tag info. I am trying to figure out how to salvage the issue by identifying under what metadata field DigiKam is storing Tag data and figuring out how to copy that information to a new metadata field. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471644] digiKam: some Mac computers are unable to export any Tag data (under TagList column for Exif).
https://bugs.kde.org/show_bug.cgi?id=471644 --- Comment #4 from Trevor Eakes --- (In reply to Maik Qualmann from comment #1) > Please take a screenshot of the error message. I don't fully understand the > bug report either. The message " [minor] Unrecognized MakerNotes" cannot > appear in the Metadata Viewer in digiKam in the Exif tab, because it is a > message from ExifTool. > Problems under macOS are usually rights problems, i.e. digiKam does not have > the necessary access rights to the directory in which the images are > located. Give digiKam all appropriate rights in the macOS security settings. > > Maik Apologies, the message is just what we see in R in the exif metadata after we try to export the photos and read their metadata. Digikam does not generate this message. Within Digikam tags are functioning normally, but the information is not being exported. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471644] New: DigiKam: some Mac computers are unable to export any Tag data (under TagList column for Exif). All other metadata seems to transfer just fine. Instead the column appears as
https://bugs.kde.org/show_bug.cgi?id=471644 Bug ID: 471644 Summary: DigiKam: some Mac computers are unable to export any Tag data (under TagList column for Exif). All other metadata seems to transfer just fine. Instead the column appears as "Warning" and in the field: [minor] Unrecognized MakerNotes. Classification: Applications Product: digikam Version: 8.0.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: trevore.at...@gmail.com 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 *** On a few of my students Mac computers we are unable to get any Tag data (under TagList column for Exif) exported. All other exif data seems to transfer just fine. Instead the column appears as "Warning" and in the field: [minor] Unrecognized MakerNotes. I assume that is the broken TagList. Students tag thousands of photos as part of a class project so a few computers unable to share their results is a serious issue for analyzing our photos. A positive short term solution is if we could batch copy the Tag metadata into another field such as comments or other similar text field, but we don't know how to get Digikam to do that. STEPS TO REPRODUCE 1. Unknown how to reproduce as it seems to work on some Macs and not on others. 2. Students have followed the same procedure for downloading and installing Digikam. Tag data appears in Digikam but not in exported photos. 3. Not an issue on windows operating systems. Suspect an error formatting tags. OBSERVED RESULT 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.
[kstars] [Bug 457923] New: Supernova database Internal Server Error
https://bugs.kde.org/show_bug.cgi?id=457923 Bug ID: 457923 Summary: Supernova database Internal Server Error Product: kstars Version: 3.6.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: tbry...@mts.net Target Milestone: --- SUMMARY When you go to update the Supernova data, it gives an Internal Server Error. I believe website withe the data has closed down. 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. 2. 3. OBSERVED RESULT 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.
[kstars] [Bug 449363] Align module in Ekos all greyed out when using profile with guide camera
https://bugs.kde.org/show_bug.cgi?id=449363 Trevor Gainey changed: What|Removed |Added CC||tre...@gainey.me.uk -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 449363] New: Align module in Ekos all greyed out when using profile with guide camera
https://bugs.kde.org/show_bug.cgi?id=449363 Bug ID: 449363 Summary: Align module in Ekos all greyed out when using profile with guide camera Product: kstars Version: 3.5.7 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: tre...@gainey.me.uk Target Milestone: --- SUMMARY I was successfully using 3.5.6 on a RPi with a main scope and guide scope in a profile. Yesterday I upgraded to 3.5.7 via the astroberry server and now when I connect to the same Ekos profile the Align module is all greyed out so I cannot use plate solving or polar align options. If I disconnect from that profile and connect to another profile not using a guide scope, then the align module works as normal. So if I want to polar align and plate solve I need to connect to a non-guiding profile, polar align, plate solve then connect to the profile that includes the guide camera to take photos. STEPS TO REPRODUCE 1. Connect to profile that includes a guide camera 2. Move to align module and see it all greyed out and not working 3. OBSERVED RESULT Align module greyed out and impossible to use EXPECTED RESULT Align module ready for use to plate solve and/or polar align SOFTWARE/OS VERSIONS Raspbian GNU/Linux version 10 (buster) ADDITIONAL INFORMATION Problem profile includes ZWO CCD camera on main telescope, QHY CCD camera on guider (guiding on RA axis only), Skywatcher Star Adventurer mount, filter simulator, OpenWeatherMap Working profile as above but without QHY CCD guider -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 448563] New: crash when playing another file *.mt2
https://bugs.kde.org/show_bug.cgi?id=448563 Bug ID: 448563 Summary: crash when playing another file *.mt2 Product: dragonplayer Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: d...@homebrewtrainers.com CC: myr...@kde.org, sit...@kde.org Target Milestone: --- Application: dragon (19.12.3) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-94-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: playing *.mt2 files if you drag & drop or play another file player crashes. reproducable evrey time The crash can be reproduced every time. -- Backtrace: Application: Dragon Player (dragon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f211c2ce800 (LWP 7975))] Thread 4 (Thread 0x7f20e2b1c700 (LWP 8186)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f211e85f623 in g_cond_wait () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f211e83cf4c in g_thread_pool_free () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f21185aaeed in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #4 0x7f21185ab446 in gst_task_cleanup_all () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #5 0x7f211852b87c in gst_deinit () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #6 0x7f211868f287 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so #7 0x7f211868f4bd in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so #8 0x7f21215c67f3 in () at /lib/x86_64-linux-gnu/libphonon4qt5.so.4 #9 0x7f21215c6a5d in () at /lib/x86_64-linux-gnu/libphonon4qt5.so.4 #10 0x7f211f808a27 in __run_exit_handlers (status=1, listp=0x7f211f9aa718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #11 0x7f211f808be0 in __GI_exit (status=) at exit.c:139 #12 0x7f211f1b70a3 in _XDefaultIOError () at /lib/x86_64-linux-gnu/libX11.so.6 #13 0x7f211bc1385e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #14 0x7f211f1b7352 in _XIOError () at /lib/x86_64-linux-gnu/libX11.so.6 #15 0x7f211f1b531c in () at /lib/x86_64-linux-gnu/libX11.so.6 #16 0x7f211f1b07f1 in XSync () at /lib/x86_64-linux-gnu/libX11.so.6 #17 0x7f211f19134f in XCloseDisplay () at /lib/x86_64-linux-gnu/libX11.so.6 #18 0x7f211811e8a0 in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstxvimagesink.so #19 0x7f211811a8f8 in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstxvimagesink.so #20 0x7f211855b9f2 in gst_element_change_state () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #21 0x7f211855c139 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #22 0x7f21185381b8 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #23 0x7f211855b9f2 in gst_element_change_state () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #24 0x7f211855c139 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #25 0x7f21185381b8 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #26 0x7f211855b9f2 in gst_element_change_state () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #27 0x7f211855c139 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #28 0x7f20fcdf7694 in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstplayback.so #29 0x7f211857236e in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #30 0x7f211e801996 in g_hook_list_marshal () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f21185719ee in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #32 0x7f2118574f84 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #33 0x7f21185755da in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #34 0x7f2118573020 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #35 0x7f211857dd71 in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #36 0x7f211857e2eb in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #37 0x7f211857a60e in gst_pad_forward () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #38 0x7f211857a755 in gst_pad_event_default () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #39 0x7f2118574bb4 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #40 0x7f2118575164 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #41 0x7f21185755da in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #42 0x7f2118573020 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #43 0x7f211857dd71 in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #44
[kdenlive] [Bug 440937] New: Unable to add video (including audio) to timeline
https://bugs.kde.org/show_bug.cgi?id=440937 Bug ID: 440937 Summary: Unable to add video (including audio) to timeline Product: kdenlive Version: 21.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: trevor.t...@gmail.com Target Milestone: --- SUMMARY An video file (with audio) cannot be placed onto a pair of tracks on the timeline. STEPS TO REPRODUCE 1. Create new project. Place 3 a/v files into the project bin. 2. Add an a/v pair of tracks and drag one a/v file onto the timeline. This works perfectly. 3. Repeat for the second a/v file. Again, this works. 4. Delete the audio track for the second file so now there are two video tracks (V1 and V2) and one audio track (A1). 5. Create a new a/v track pair (V3 and A2). 6. Attempts to drag the third a/v file onto V3/A2 now fail. OBSERVED RESULT See above. EXPECTED RESULT The a/v file should occupy V3/A2. This is fixed by adding in audio tracks until the "A" track number matches the "V" track number. In the example above, add in a new audio track (now A3). The drag operation now succeeds. An alternative solution is to use the project bin clip properties to mute the audio. The video now drops on to V3. This is only suitable if the audio is not needed. SOFTWARE/OS VERSIONS Ubuntu 20.04, Gnome 3.38. KDEnlive 21.04.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first
https://bugs.kde.org/show_bug.cgi?id=440128 --- Comment #1 from Trevor Parsons --- Created attachment 140647 --> https://bugs.kde.org/attachment.cgi?id=140647=edit Window rule settings for Yakuake to appear on all activities Workaround by setting a window rule... -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first
https://bugs.kde.org/show_bug.cgi?id=440128 Trevor Parsons changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429427] Unable to authenticate gmail via proxy
https://bugs.kde.org/show_bug.cgi?id=429427 Trevor Pearman changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429457] Cannot set proxy server with IPv6 address
https://bugs.kde.org/show_bug.cgi?id=429457 --- Comment #1 from Trevor Pearman --- It doesn't matter if a numeric IPv6 address or a host name referring to an IPv6 address is used -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429427] Unable to authenticate gmail via proxy
https://bugs.kde.org/show_bug.cgi?id=429427 --- Comment #2 from Trevor Pearman --- Actually, the problem is that setting SOCKS proxy to IPv6 address fails It is not a kmail2 problem but a system settings problem Filed bug 429457 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429457] New: Cannot set proxy server with IPv6 address
https://bugs.kde.org/show_bug.cgi?id=429457 Bug ID: 429457 Summary: Cannot set proxy server with IPv6 address Product: systemsettings Version: 5.19.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_networkmanagement Assignee: jgrul...@redhat.com Reporter: trevorpear...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When setting a manual proxy socks proxy server with an IPv6 address, the address is ignored STEPS TO REPRODUCE 1. Open system settings 2. Open network settings 3. Set a valid SOCKS proxy with an IPv6 address 4. Apply and close system settings 5. Open system settings 6. Open network settings 7. SOCKS proxy field is blank and port is reset to 0 OBSERVED RESULT After closing and repopening system setting and entering network settings, the proxy field and port have been reset to blank and 0, respectively EXPECTED RESULT Should be able to access a SOCKS proxy with IPv6 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.19.5 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429427] Unable to authenticate gmail via proxy
https://bugs.kde.org/show_bug.cgi?id=429427 --- Comment #1 from Trevor Pearman --- Never mind Problem is with proxy setup in network settings ... operator error Apologies -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429427] New: Unable to authenticate gmail via proxy
https://bugs.kde.org/show_bug.cgi?id=429427 Bug ID: 429427 Summary: Unable to authenticate gmail via proxy Product: kmail2 Version: 5.15.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: trevorpear...@gmail.com Target Milestone: --- SUMMARY Trying to add a gmail account with 2FA ... system uses remote socks server STEPS TO REPRODUCE 1. Create google account with a valid proxy in the system network settings 2. 3. OBSERVED RESULT Browser opens (titled Google") to accounts.google.com/oauth2/auth?clientid=... and a "No internet" message is returned The following is also displayed on the web page ... There is something wrong with the proxy server, or the address is incorrect. Try: Contacting the system admin Checking the proxy address ERR_PROXY_CONNECTION_FAILED Proxy works normally for all other applications EXPECTED RESULT Connection to the Google oauth2 system SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415871] Maximize window on second monitor does not expand window to whole screen
https://bugs.kde.org/show_bug.cgi?id=415871 --- Comment #6 from Trevor Allen --- Created attachment 129081 --> https://bugs.kde.org/attachment.cgi?id=129081=edit Screenshot of problem Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.4.43-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 23.4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Trevor Allen changed: What|Removed |Added CC||m...@trev.xyz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415871] Maximize window on second monitor does not expand window to whole screen
https://bugs.kde.org/show_bug.cgi?id=415871 Trevor Allen changed: What|Removed |Added CC||m...@trev.xyz --- Comment #3 from Trevor Allen --- Still a problem as of 06/05/2020 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421309] New: Display Configuration does not show screen numbers
https://bugs.kde.org/show_bug.cgi?id=421309 Bug ID: 421309 Summary: Display Configuration does not show screen numbers Product: systemsettings Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: kdeb...@trevorparsons.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 128348 --> https://bugs.kde.org/attachment.cgi?id=128348=edit Screenshot of Display Configuration module showing no screen numbers, in context with a Window Rules setting where the screen number is needed SUMMARY For each connected monitor, the display configuration module helpfully provides the make and model and interface-related identifiers (eg HDMI2, VGA-1-0, HDMI-1-0). Those pieces of information are shown both in the draggable preview of the screen screen layout and in the on-screen identifiers which appear on each screen when you click the Identify button. However, the module does not show what screen number is associated with each monitor. STEPS TO REPRODUCE 1. Look at details shown in screen layout preview. 2. Look at on-screen identifiers which appear when you press the Identify button. OBSERVED RESULT No screen numbers are associated with the monitors in either case. EXPECTED RESULT I would expect the screen number of each monitor to be shown. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.4.39-1-lts OS Type: 64-bit EXAMPLE OF WHY KNOWING THE SCREEN NUMBER IS USEFUL In the System Settings Window Rules module, under the Size & Position tab, it's possible to set "Screen" (which might be more helpfully called "Screen Number") as a property which can be forced or applied to a matched window. But to set this, one needs to know which screen number applies to which physical monitor. The Display Configuration Module is the obvious place to look for that information. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 421308] Non-bound keystroke in month view spawns add event dialog
https://bugs.kde.org/show_bug.cgi?id=421308 Trevor Parsons changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 421308] New: Non-bound keystroke in month view spawns add event dialog
https://bugs.kde.org/show_bug.cgi?id=421308 Bug ID: 421308 Summary: Non-bound keystroke in month view spawns add event dialog Product: korganizer Version: 5.14.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: kdeb...@trevorparsons.com Target Milestone: --- SUMMARY In the month view of Korganizer, if you press a key that is not a function or modifier key, not part of a key combination, and not a key that is bound to a keyboard shortcut, the add event dialog is spawned, unwantedly. STEPS TO REPRODUCE 1. Switch to month view. 2. Press any single unbound non-function / non-modifier key / non-shortcut key. OBSERVED RESULT An add event dialog is spawned with the corresponding character already entered into the Title field. EXPECTED RESULT Nothing, unless the key is set as a keyboard shortcut. The current behaviour prevents the binding of single letter keys to switch quickly between day, week and month view (comparable to the very handy shortcut keys in Google Calendar web interface). Indeed, all that happens if you set a single key, such as 'd' for day, is that that prevents the pressing of 'd' from spawning the add event dialog. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.4.39-1-lts OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 375060] week / day / month view not making sense
https://bugs.kde.org/show_bug.cgi?id=375060 Trevor Parsons changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418231] New: 5619916-x86_64.appimage fails at load UI
https://bugs.kde.org/show_bug.cgi?id=418231 Bug ID: 418231 Summary: 5619916-x86_64.appimage fails at load UI Product: krita Version: nightly build (please specify the git hash!) Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: technicalgraph...@eircom.net Target Milestone: --- SUMMARY krita-4.3.0-prealpha-369d552-x86_64 is last build to start STEPS TO REPRODUCE 1. Start appimage in term window 2. Loads to main window 3. then fail OBSERVED RESULT Term output: mugwah@mugwah-asus ~/app_images/krita_nightly $ ./krita-4.3.0-prealpha-5619916-x86_64.appimage krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 krita.lib.widgets: MD5sum and filename point to different resources -- was the resource renamed? We go with md5 QObject::startTimer: Timers cannot have negative intervals Could not find platform independent libraries Consider setting $PYTHONHOME to [:] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = (not set) program name = 'python3' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/bin/python3' sys.base_prefix = '' sys.base_exec_prefix = '' sys.executable = '/usr/bin/python3' sys.prefix = '' sys.exec_prefix = '' sys.path = [ '/home/mugwah/.local/share/krita/', '/tmp/.mount_krita-jcL3lg/usr/share/krita/', '/home/mugwah/.local/share/krita/pykrita/', '/tmp/.mount_krita-jcL3lg/usr/share/krita/pykrita/', '/tmp/.mount_krita-jcL3lg/usr/share/pykrita/', '/tmp/.mount_krita-jcL3lg/usr/lib/krita-python-libs', '/lib-dynload', '/site-packages', '/site-packages/PyQt5', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x7f4d54aa1900 (most recent call first): krita.general: Warning: some tiles have leaked: krita.general: Tiles in memory: 4 Total tiles: 4 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.
[korganizer] [Bug 412833] Monthview shows comma in year
https://bugs.kde.org/show_bug.cgi?id=412833 --- Comment #3 from Trevor Parsons --- (In reply to Allen Winter from comment #2) > patch is up for review at https://phabricator.kde.org/D24638 Looks good to my untutored eye. Thanks for such quick work, Allen! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412833] New: Monthview shows comma in year
https://bugs.kde.org/show_bug.cgi?id=412833 Bug ID: 412833 Summary: Monthview shows comma in year Product: korganizer Version: 5.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: kdeb...@trevorparsons.com Target Milestone: --- Created attachment 123140 --> https://bugs.kde.org/attachment.cgi?id=123140=edit Screenshot of part of korganizer window showing comma in year in monthview SUMMARY In the month view of Korganizer, the year contains a comma, as if it were a normal numeral. STEPS TO REPRODUCE 1. Start Korganizer 2. Switch to month view OBSERVED RESULT The year contains a comma. For example, at the time of reporting the month and year are shown as "October 2,019". EXPECTED RESULT The year should not contain a comma. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.5-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.14.0 (built against 5.13.1) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353810] Suggest bringing 'Activities' to the top of the appmenu above 'Move To Screen'
https://bugs.kde.org/show_bug.cgi?id=353810 Trevor Parsons changed: What|Removed |Added Resolution|INTENTIONAL |FIXED --- Comment #2 from Trevor Parsons --- I'm pleased to see that now (kwin 5.16.90) the appmenu has adopted the order I suggested in this bug, i.e. the Activities item, now written as "Show in Activities", has been moved to the top of the menu, and "Move to Screen" has been demoted in the list. Changing status from Resolved Intentional to Resolved Fixed. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 411849] RSA4096 option disabled in Kleopatra on newer smartcards
https://bugs.kde.org/show_bug.cgi?id=411849 --- Comment #5 from Trevor B --- Thanks for the super-fast fix! I'll contact you via e-mail about getting keys. There is a new DO in version 3.4 of the spec, called "Algorithm Information", which returns a table of supported algorithms. That would be the most correct way to determine what is supported. But I think it still needs to be plumbed through GPG, and most devices probably don't support it yet. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 411849] RSA4096 option disabled in Kleopatra on newer smartcards
https://bugs.kde.org/show_bug.cgi?id=411849 Trevor B changed: What|Removed |Added CC||tre...@yubico.com -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 411849] RSA4096 option disabled in Kleopatra on newer smartcards
https://bugs.kde.org/show_bug.cgi?id=411849 --- Comment #1 from Trevor B --- Whoops, I mean Kleopatra 3.1.8 as part of Gpg4win 3.1.10. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 411849] RSA4096 option disabled in Kleopatra on newer smartcards
https://bugs.kde.org/show_bug.cgi?id=411849 Trevor B changed: What|Removed |Added Version|unspecified |3.1.8 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 411849] New: RSA4096 option disabled in Kleopatra on newer smartcards
https://bugs.kde.org/show_bug.cgi?id=411849
Bug ID: 411849
Summary: RSA4096 option disabled in Kleopatra on newer
smartcards
Product: kleopatra
Version: unspecified
Platform: Other
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: aheine...@gnupg.org
Reporter: tre...@yubico.com
CC: kdepim-b...@kde.org, m...@kde.org
Target Milestone: ---
SUMMARY
I used Kleopatra 3.1.10 installed as part of the Gpg4Win package on Windows 10.
When generating a new key on a smartcard, Kleopatra presents a drop-down box of
available RSA key sizes. The "4096" option is gated behind an incorrect
version check, checking that the OpenPGP smartcard's version is exactly "2.1":
```
mIs21 = version == QLatin1String("2.1");
```
```
sizes.push_back(1024);
sizes.push_back(2048);
sizes.push_back(3072);
// There is probably a better way to check for capabilities
if (mIs21) {
sizes.push_back(4096);
}
```
This means the option doesn't show up on smartcards implementing later versions
of the OpenPGP on ISO Smart Card spec, which is up to version 3.4. This
affects the latest YubiKey 5, which reports version 3.4.
STEPS TO REPRODUCE
1. Open Kleopatra
2. Insert YubiKey 5
3. Select 'Manage Smartcards' from menu
4. Click "Generate new Keys" button
OBSERVED RESULT
"4096" not listed as an option
EXPECTED RESULT
"4096" should be listed as an option
SOFTWARE/OS VERSIONS
Windows: Windows 10
macOS: untested
Linux/KDE Plasma: untested
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 407456] New: Tile and Cascade do not appear in the window menu.
https://bugs.kde.org/show_bug.cgi?id=407456 Bug ID: 407456 Summary: Tile and Cascade do not appear in the window menu. Product: krita Version: nightly build (please specify the git hash!) Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: technicalgraph...@eircom.net Target Milestone: --- SUMMARY krita-4.2.0-alpha-220be8f-x86_64.appimage Tile and Cascade no show STEPS TO REPRODUCE Window>New View creates a duplicate view. OBSERVED RESULT Tile and Cascade do not appear in the window menu. EXPECTED RESULT Tile and Cascade should appear in the window menu. SOFTWARE/OS VERSIONS Linux Mint Mate, 18.3 Sylvia Athlon X4 950 8 Gig DDR4. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382311] Photos in collapsed groups are incorrectly excluded if first photo in group does not match filter.
https://bugs.kde.org/show_bug.cgi?id=382311 --- Comment #2 from Trevor Giddings --- The bug is resolved in the 6.1.0 pre-release. However, groups with no matching photos now remain in the album view. While I would not classify that as a bug, it is a user-experience regression. (In reply to caulier.gilles from comment #1) > After 3 weeks of work, i finally completed the compilation of AppImage using > Qt > 5.11.3 + QWebkit 5.212. > > New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the > moment) : > > https://files.kde.org/digikam/ > > Please check if this bugzilla entry still valid. > > Thanks in advance > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 Trevor <ve9cb...@gmail.com> changed: What|Removed |Added CC||ve9cb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 --- Comment #25 from Trevor <ve9cb...@gmail.com> --- Created attachment 110349 --> https://bugs.kde.org/attachment.cgi?id=110349=edit New crash information added by DrKonqi plasma-discover (5.11.5) using Qt 5.9.3 - What I was doing when the application crashed: Was trying to search for an application when it crashed. Regretfully I didn't wait for the search result for the last search; I suspect that's probably why it crashed on me. -- Backtrace (Reduced): #6 0x7f75f4725d84 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #8 0x7f75f7794f23 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f75f7795185 in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f75f5d12b9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f75f5d1a5a7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 346565] A photo whose orientation I've corrected (rotated) subsequently becomes inverted
https://bugs.kde.org/show_bug.cgi?id=346565 --- Comment #14 from Trevor Parsons <kdeb...@trevorparsons.com> --- (In reply to Nate Graham from comment #13) > Is anybody able to reproduce this with Gwenview 16.x or 17.x? I can't. With Gwenview 17.08.2 I'm no longer able to reproduce this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382311] New: Photos in collapsed groups are incorrectly excluded if first photo in group does not match filter.
https://bugs.kde.org/show_bug.cgi?id=382311 Bug ID: 382311 Summary: Photos in collapsed groups are incorrectly excluded if first photo in group does not match filter. Product: digikam Version: 5.6.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: AlbumsView-Group Assignee: digikam-de...@kde.org Reporter: tgiddings...@gmail.com Target Milestone: --- When a filter is set in the "filters" tab on the right sidebar, and the first photo in a collapsed group does not match the filter, all photos in the group are excluded from album view. Expected behaviour: The group appears in album view if any of its photos match the filter, and when expanded, only photos matching the filter are shown. The expected behaviour described above is identical to the actual behaviour of DigiKam when the first photo matches the filter. Steps to reproduce: place two pictures in an album mark one picture with the "rejected" label group the pictures selecting the "rejected" picture last in the filters tab, click the black flag expected behaviour: the album view shows one group with the photo that was not marked rejected as the thumbnail. Expanding the group does not show any more photos. actual behaviour: the album view is empty. This occurs in the thumbnails view if the group is collapsed (I.e, the "show grouped images" button was not clicked) and in the table view if the "ignore grouping" option is not checked. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 312919] high CPU usage for copying notification
https://bugs.kde.org/show_bug.cgi?id=312919 Trevor Parsons <kdeb...@trevorparsons.com> changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #56 from Trevor Parsons <kdeb...@trevorparsons.com> --- As others have observed, copying files in Dolphin, particularly across the network, results in this plasmashell CPU overload. But it turns out that, for me, the most frequent source of this problem is the tray icon of Amarok (the audio player). A few days ago, I disabled Amarok's (very useful but oh well) tray icon in Settings > Configure Amarok > General. Since then, plasmashell's CPU overload problem has not recurred. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Trevor Parsons <kdeb...@trevorparsons.com> changed: What|Removed |Added CC||kdeb...@trevorparsons.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349519] plasmashell occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=349519 Trevor <tdip...@hotmail.com> changed: What|Removed |Added CC|tdip...@hotmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 354046] Use the previous save* action as the default in a new session
https://bugs.kde.org/show_bug.cgi?id=354046 --- Comment #8 from Trevor Parsons <kdeb...@trevorparsons.com> --- (In reply to Boudhayan Gupta from comment #7) > Sure. File a new bug and I'll get around to it. But do file a new bug, or > I'll forget. Albert has file the suggested bug as https://bugs.kde.org/show_bug.cgi?id=358641 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 357533] Cannot load icon for activities
https://bugs.kde.org/show_bug.cgi?id=357533 Trevor <trevab...@hotmail.com> changed: What|Removed |Added CC||trevab...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 355972] Double-clicking a track in the playlist results in unexpected behaviour
https://bugs.kde.org/show_bug.cgi?id=355972 Trevor Parsons <kdeb...@trevorparsons.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #4 from Trevor Parsons <kdeb...@trevorparsons.com> --- (In reply to Myriam Schweingruber from comment #3) > Very weird, I don't see what could have been changed that causes this, there > have been no changes in current git affecting the playlist or the playback. > Could you try with a new user? I should have tried the new user test before reporting this. It did the trick. I've therefore removed/renamed the majority of the KDE and Plasma settings files from my own user account and now have a refreshed desktop, in which Amarok does not exhibit the reported problem behaviour. For interest, I think this was also related to the fact that double-clicking on a word in, for example, Konsole, would not result in the normal behaviour of that word becoming selected, because this has also been resolved. I suppose this kind of hard-to-identify problem is liable to happen after lots of upgrades. Thanks for your help Myriam, and sorry for troubling you unnecessarily! -- You are receiving this mail because: You are watching all bug changes.
