[plasmashell] [Bug 372839] New: Laptop gets to hot
https://bugs.kde.org/show_bug.cgi?id=372839 Bug ID: 372839 Summary: Laptop gets to hot Product: plasmashell Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: wellend...@posteo.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Since a while a saw the processor temperature running on critical levels. I use a Thinkpad W520 since three years now. Since I installed Plasma 5 the temperature in idle condition is around 70°, if I am happy 65°. But after using it a while it gets up to 90° or even 95°, with a processor use of maybe 10-20% and doing nothing demanding. I was very reluctant to change anything, but after one year being afraid that running on this high temperatures will not be good for the hardware I finally decided to use Cinnamon to test, if there is the same problem occuring. Here I get temperatures around 60° under more or less idle conditions and it stays around that. Beside the different desktop I use the same software. I try this now a week and never got 90°. I would love to continue to use KDE, which I used to use since 2005, what can I do? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372839] Laptop gets to hot
https://bugs.kde.org/show_bug.cgi?id=372839 Marcus changed: What|Removed |Added CC||wellend...@posteo.de --- Comment #1 from Marcus --- Actually I dont even get 80° with Cinnamon. If there is some load maybe 75°. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440217] New: title clip: glitch with special characters and typewriter effect
https://bugs.kde.org/show_bug.cgi?id=440217
Bug ID: 440217
Summary: title clip: glitch with special characters and
typewriter effect
Product: kdenlive
Version: 21.04.3
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Effects & Transitions
Assignee: vpi...@kde.org
Reporter: kde.b...@nueb.de
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. create a title clip with special characters like "mdash" ("—") and
typewriter effect
2. let kdenlive render
EXPECTED RESULT
all characters (incl. "—") are displayed in typewriter effect
OBSERVED RESULT
when the special characters are to appear, two carets with question marks are
displayed first
SOFTWARE/OS VERSIONS
$ uname -a
Linux red 5.10.52-1-MANJARO #1 SMP PREEMPT Tue Jul 20 20:32:02 UTC 2021 x86_64
GNU/Linux
$ gnome-shell --version
GNOME Shell 40.3
$ qmake --version
QMake version 3.1
Using Qt version 5.15.2 in /usr/lib
ADDITIONAL INFORMATION
text sample to reproduce the glitch: "!"§$%&/()=?öäüß…–—"
You can watch the glitch in this YT video: https://youtu.be/SWxTHxUYyLY
Kdenlive project files:
https://tmp.nueb.net/nopurge/kdenlive_typewriter_glitch.zip (~ 1 MB)
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 428638] 7.2.0 beta1: sorting of images in thumbnail view - german environment and UI
https://bugs.kde.org/show_bug.cgi?id=428638 --- Comment #3 from Marcus --- forgot to mention one thing: All pictures in the folders (that show the odd behaviour) have the exact same name-pattern (IMG_MMDD_hhmmss.jpg - e.g. IMG_20200816_160635.jpg) Therefore i really dont get the difference between those 2 approaches (natural/normal) when reading the explanation from the manual "With the String comparison type setting, you can set the way in which strings are compared inside digiKam. This influences the sorting of the tree views. Natural tries to compare strings in a way that regards some normal conventions. The result will be sort naturally even if they have a different number of digits inside. Normal uses a more technical approach. Use this style if you want to entitle albums with ISO dates (201006 or 20090523) and the albums should be sorted according to these dates." -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 --- Comment #5 from marcus --- I use stock hardware This is copied from system settings. Sorry for language mix. > Betriebssystem: Manjaro Linux > KDE-Plasma-Version: 5.27.9 > KDE-Frameworks-Version: 5.111.0 > Qt-Version: 5.15.11 > Kernel-Version: 6.1.60-1-MANJARO (64-bit) > Grafik-Plattform: X11 > Prozessoren: 16 × 11th Gen Intel® Core™ i7-11700F @ 2.50GHz > Speicher: 15,5 GiB Arbeitsspeicher > Grafikprozessor: NVIDIA GeForce RTX 3060/PCIe/SSE2 > Hersteller: Acer > Produktname: Predator PO3-630 > Systemversion: 1.0 Yesterday I startet a Manjaro system update which might have triggered reindexing. I just don't know. The system was in IDLE state when I noticed the fan going up and down. In KDE Systemmonitor I could see one CPU thread being active while others were inactive which led to ~5% CPU usage. Please let me know if more information is missing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 marcus changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from marcus --- Status changed back to reported. I hope this is correct -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 --- Comment #7 from marcus --- Created attachment 163009 --> https://bugs.kde.org/attachment.cgi?id=163009&action=edit System load during IDLE indexing So this is the ~5% cpu load visualized. It is core 5 and 6 that do stuff the rest is idle -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 476785] New: GPU Ram total show wrong value
https://bugs.kde.org/show_bug.cgi?id=476785 Bug ID: 476785 Summary: GPU Ram total show wrong value Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mar...@kmann.eu CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 163013 --> https://bugs.kde.org/attachment.cgi?id=163013&action=edit System monitor page 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 *** While I have 12 GiB of VRAM it shows me I would have 28 GiB in total > Operating System: Manjaro Linux > KDE Plasma Version: 5.27.9 > KDE Frameworks Version: 5.111.0 > Qt Version: 5.15.11 > Kernel Version: 6.1.60-1-MANJARO (64-bit) > Graphics Platform: X11 > Processors: 16 × 11th Gen Intel® Core™ i7-11700F @ 2.50GHz > Memory: 15.5 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 > Manufacturer: Acer > Product Name: Predator PO3-630 > System Version: 1.0 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.
[Discover] [Bug 477058] New: Flickering Dialog on FullHD
https://bugs.kde.org/show_bug.cgi?id=477058 Bug ID: 477058 Summary: Flickering Dialog on FullHD Classification: Applications Product: Discover Version: 5.27.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: mar...@kmann.eu CC: aleix...@kde.org Target Milestone: --- Created attachment 163192 --> https://bugs.kde.org/attachment.cgi?id=163192&action=edit Video of flicking dialog SUMMARY Dialog window flickers on 1920x1080 monitor. It doesn't do so on 2560x1440. See attached video please. 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.
[frameworks-baloo] [Bug 476752] New: Priorize Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 Bug ID: 476752 Summary: Priorize Baloo File Indexing Process Classification: Frameworks and Libraries Product: frameworks-baloo Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: mar...@kmann.eu 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 *** I am asking for a button (or command) to speed up indexing process. https://forum.manjaro.org/t/priorize-baloo-file-indexing-process/151223 "Baloo_file_extractor is busy indexing files at 5% cpu usage. Because of poor thermal design pc fans are going up and down all the time. Is there a way to get through this process quicker? I would rather have it done fast than being gentle." 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.
[digikam] [Bug 462736] Connection to external Mysql-Server fails
https://bugs.kde.org/show_bug.cgi?id=462736 Marcus changed: What|Removed |Added CC||digikam...@iinet.net.au --- Comment #18 from Marcus --- Created attachment 154595 --> https://bugs.kde.org/attachment.cgi?id=154595&action=edit Screenshot of error message digikam 7.9 on mac - cannot connect to mysql external -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 307645] automatically determine the coordinates of an address
https://bugs.kde.org/show_bug.cgi?id=307645 Marcus changed: What|Removed |Added Version|4.9 |5.16.3 Platform|Ubuntu Packages |Manjaro --- Comment #4 from Marcus --- Would still be nice to have. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488843] Triple buffering causing stuttering
https://bugs.kde.org/show_bug.cgi?id=488843 Marcus changed: What|Removed |Added CC||jjmarco75+...@gmail.com --- Comment #23 from Marcus --- Created attachment 171409 --> https://bugs.kde.org/attachment.cgi?id=171409&action=edit perf stats csv files running KWin with MR 5982 and without I built KWin with the hysteresis MR (https://invent.kde.org/plasma/kwin/-/merge_requests/5982) applied and ran it with logging. I also ran stock 6.1.2 KWin with logging. This was done on a notebook with intel UHD 630 integrated gpu in the 1080@60Hz mode. I didn't notice improvements in either cases on my end, framerate still gets halved until certain types of large screen updates happen (pulling the overview, alt-tabbing, switching vdesktops, etc), at which point it goes back to 60fps for a short time. just like the others, disabling triple-buffering fixes it. This is much less of an issue in 144Hz mode. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488843] Triple buffering causing stuttering
https://bugs.kde.org/show_bug.cgi?id=488843 --- Comment #28 from Marcus --- Thanks for the response! So I tested different values for the extra safety margin on a Plasma/6.1 build, and increasing it does help reduce dropped frames. I need to make it pretty high, closing in on the frame time itself (not counting vblank), to have a noticeable effect though. Anything lower than ~10ms still makes the framerate eventually tank, but above ~14ms the 60fps target is consistently maintained. I also took the liberty of running the analysis tool myself: - 6 000 us > - total of 46008 frames > - dropped 40 frames (0.087%) >- 11 because of too late commits (0.024%) >- 16 because of late rendering start (0.035%) >- 13 because of render times (0.028%) > - 2257us average render time > - 2000us median render time > - 363s total 'unnecessary' latency > - would've estimated render times too low in 59 frames (0.13%) > - would've estimated 50+% too much render time in 40951 frames (89%) - 13 000 us > - total of 48274 frames > - dropped 24 frames (0.05%) >- 8 because of too late commits (0.017%) >- 9 because of late rendering start (0.019%) >- 7 because of render times (0.015%) > - 2224us average render time > - 2000us median render time > - 259s total 'unnecessary' latency > - would've estimated render times too low in 88 frames (0.18%) > - would've estimated 50+% too much render time in 43972 frames (91%) - 15 000 us > - total of 50195 frames > - dropped 23 frames (0.046%) >- 2 because of too late commits (0.004%) >- 14 because of late rendering start (0.028%) >- 7 because of render times (0.014%) > - 2081us average render time > - 2000us median render time > - 183s total 'unnecessary' latency > - would've estimated render times too low in 71 frames (0.14%) > - would've estimated 50+% too much render time in 21862 frames (44%) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488843] Triple buffering causing stuttering
https://bugs.kde.org/show_bug.cgi?id=488843 --- Comment #30 from Marcus --- Increasing the 1ms extra is the same deal; it helps but I need to make it very high. so it doesn't seem to be related to dropped frames. > - total of 42978 frames > - dropped 105 frames (0.24%) > - 87 because of too late commits (0.2%) > - 12 because of late rendering start (0.028%) > - 6 because of render times (0.014%) But my issue isn't stuttering due to dropped frames per se; it's that the frame rate drops to 30fps for long periods of time, like a starved double-buffered vsync, unless I (apparently) add myself a frame of latency or turn off triple-buffering altogether, and only at 60Hz. and somehow this doesn't show in the perf stats. if there's no obvious solution to this I can just disable tb indefinitely, but it's still a weird issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488843] Triple buffering causing stuttering
https://bugs.kde.org/show_bug.cgi?id=488843 --- Comment #31 from Marcus --- looking at RenderLoopPrivate::scheduleRepaint more closely it seems that if I make the safety margin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488843] Triple buffering causing stuttering
https://bugs.kde.org/show_bug.cgi?id=488843 --- Comment #32 from Marcus --- Sorry, ignore that. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 392500] Session crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=392500 Marcus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Marcus --- I'm closing this issue as I switched back to plasma and no more shows up in newer versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375902] rename files linked to activity in folderview delete/move the file and corrupt file name
https://bugs.kde.org/show_bug.cgi?id=375902
Marcus changed:
What|Removed |Added
Version|5.9.0 |5.15.5
Platform|Other |Manjaro
CC||wellend...@posteo.de
--- Comment #7 from Marcus ---
I just run into this problem, too. I have some activities with folder view,
added one Libreoffice spreadsheet from a subfolder of my home folder to one
activity so it was showing up on thaat desktop. Then I renamed it at the
desktop and it disappeared.
I found it after some search with a cryptic name Rk�?�{�.j�Z��l moved into the
home folder. I tested the bug doing the same procedure with a textfile, similar
result, but the file was called ��-��m.
I think for some people that is like a data loss.
--
You are receiving this mail because:
You are watching all bug changes.
[knemo] [Bug 409197] New: Plasmashell takes 50% of the CPU when it can't connect to the Wifi
https://bugs.kde.org/show_bug.cgi?id=409197 Bug ID: 409197 Summary: Plasmashell takes 50% of the CPU when it can't connect to the Wifi Product: knemo Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jst...@mehercule.net Reporter: bio...@gmail.com Target Milestone: --- Created attachment 121150 --> https://bugs.kde.org/attachment.cgi?id=121150&action=edit Wifi trying to connect uses a stable 49% CPU SUMMARY The process plasmashell will will take up to 50% of the CPU when the Wifi network won't connect. It takes either 25% or 50% and it is a stable utilization as if the process went out of control. STEPS TO REPRODUCE The bug is always reproducible: when the Wifi is activate it will start consuming CPU, as soon as I deactivate it, the utilization will go down to 0-2%. 1. Activate Wifi. 1. Find a Wifi connection that won't connect: a connection that will successfully authenticate the user but will not go beyond "applying networks address" phase. 2. Try to connect to that network without any other alternative available. If there are no alternatives the process will go timeout and keep trying to connect to the same network. OBSERVED RESULT Watch CPU utilization jump up and fans start spinning like crazy. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 --- Comment #3 from Marcus --- Created attachment 121152 --> https://bugs.kde.org/attachment.cgi?id=121152&action=edit Docx file inside Google drive folder -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 --- Comment #4 from Marcus --- Just small additional information. The bug is still relevant in Plasma 5.16.1 and KDE Frameworks 5.59.0 .doc files are correctly recognized. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401152] In multi monitor configuration PC start with screen OFF
https://bugs.kde.org/show_bug.cgi?id=401152 Marcus changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409197] Plasmashell takes 50% of the CPU when it can't connect to the Wifi
https://bugs.kde.org/show_bug.cgi?id=409197 Marcus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Marcus --- Maybe it is a Google Drive issue, I see also the web client interpret those files as archives -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410082] New: Artifacts when settings scale effect on closing
https://bugs.kde.org/show_bug.cgi?id=410082 Bug ID: 410082 Summary: Artifacts when settings scale effect on closing Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- Created attachment 121666 --> https://bugs.kde.org/attachment.cgi?id=121666&action=edit Scale settings SUMMARY When settings scale effects on closing windows, it generates visual artifacts on the area that is not being actively refreshed, until those areas gets the focus. STEPS TO REPRODUCE 1. Open system settings 2. Go to Desktop Behavior 3. Select Desktop Effects 4. Activate Scale animation setting the close scale more than 1x 5. Open multiple windows (not fullscreen) so that once you close one, there is at least one inactive window in background. OBSERVED RESULT A flickering visual artifact appears (It may last for long time) EXPECTED RESULT Clean closing animation SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This bug is pretty easy to verify. It happens with both the desktop with an AMD card and a notebook that uses Nvidia proprietary driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410082] Artifacts when settings scale effect on closing
https://bugs.kde.org/show_bug.cgi?id=410082 --- Comment #1 from Marcus --- Created attachment 121667 --> https://bugs.kde.org/attachment.cgi?id=121667&action=edit Video showing the artifacts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410082] Artifacts when settings scale effect on closing
https://bugs.kde.org/show_bug.cgi?id=410082 --- Comment #3 from Marcus --- Created attachment 122383 --> https://bugs.kde.org/attachment.cgi?id=122383&action=edit Video configuration The speed is just sightly faster than standard -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410082] Artifacts when settings scale effect on closing
https://bugs.kde.org/show_bug.cgi?id=410082 --- Comment #4 from Marcus --- Created attachment 122384 --> https://bugs.kde.org/attachment.cgi?id=122384&action=edit Window animation duration 150ms -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410082] Artifacts when settings scale effect on closing
https://bugs.kde.org/show_bug.cgi?id=410082 --- Comment #5 from Marcus --- As to how to reproduce it, it is important that when the window scales on close, it scales to more than 1x (I have 1.2), then it happens basically every time. There are almost always artifacts. Sometimes they flicker in reaction to mouse movement, sometimes they stand still. About the composition, sometimes a whole portion of window remains there (like the upper bar, with the buttons to minimize, maximize, ... sometimes ii's just the shadow of the window that remains there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410082] Artifacts when settings scale effect on closing
https://bugs.kde.org/show_bug.cgi?id=410082 --- Comment #6 from Marcus --- If you haven't seen the video yet, please look at it. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 403893] Wrong escaping written to file
https://bugs.kde.org/show_bug.cgi?id=403893 Marcus changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Marcus --- I'm very sorry. For having wasted your time. The problem when compiling the file with the bib file created by kbibtex was unrelated to the \i inserted. I used a macro called '\i' in some block and somehow the scoping broke. So the \i was not available in the bibliography even though it should have been. So it now works with and without your patch and I think the original version is more correct. Again, my apologies ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419771] New: A possible configuration for automatically scanning for new added pictures?
https://bugs.kde.org/show_bug.cgi?id=419771 Bug ID: 419771 Summary: A possible configuration for automatically scanning for new added pictures? Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: wellend...@posteo.de Target Milestone: --- Using digikam since version two I will soon have 100.000 pictures in my database. If I configure digikam to scan for new pictures at the start it takes quite a long time, some minutes actually. I deactivated the scan at the start and as I sometimes import photographies with rapid-photo-downloader I manually do a scan in the used folders. I just thought: If the scan could get limited to the last 1 (or 2,3,4,10) folders used or for folders used in the last 1 (or 2,3,4,10...) days in the configuration an automatic scan could cover most cases of new added pictures. at least for my usecase it would be great! Thank you for this great peace of software! Marcus -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419771] A possible configuration for automatically scanning for new added pictures?
https://bugs.kde.org/show_bug.cgi?id=419771 Marcus changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Marcus --- Great, that works. Thank you so much! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] New: docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 Bug ID: 401151 Summary: docx files opened as archives in remote folders Product: systemsettings Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_filetypes Assignee: fa...@kde.org Reporter: bio...@gmail.com Target Milestone: --- Created attachment 116375 --> https://bugs.kde.org/attachment.cgi?id=116375&action=edit File association setted It is impossible to set remote files .docx to open with libreoffice. They will always open with Ark. This happen (for me) only on the google drive folder, when moved locally everithing works as expected. STEPS TO REPRODUCE 1. Setup Google drive directory 2. Open Dolphin and go to "gdrive:account/" 3. Copy a .docx file in some folder 4. Open the file with Dolphin (as usual, by double clicking) Ark will open 5. Set the file to be opened with LibreOffice (see the attachment) 6. Go to number 3 OBSERVED RESULT Locally it works as expected EXPECTED RESULT The association of docx -> LibreOffice should be remembered SOFTWARE/OS VERSIONS Kubuntu 18.10 updated KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401152] New: In multi monitor configuration PC start with screen OFF
https://bugs.kde.org/show_bug.cgi?id=401152 Bug ID: 401152 Summary: In multi monitor configuration PC start with screen OFF Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- Created attachment 116376 --> https://bugs.kde.org/attachment.cgi?id=116376&action=edit Screen configuration I have the PC connected to a Samsung TV through an audio amplifier. Usually I do not use the TV so it is disabled in monitor settings (attachment: SAMSUNG). My monitor (attachment: VE248) is set as the main screen. OBSERVED RESULT When the computer starts it start with the screen ON: I can see the mouse on a dark background and it moves correctly. In a few seconds it turns OFF, no matter I move the mouse or randomly press on keyboard, it stays OFF. The turn my monitor ON I have to power ON the amplifier, then it turns ON. After that I can turn the amplifier OFF again, everything keeps working as expected. EXPECTED RESULT The screen should stay ON independently on the amplifier when it is enabled in Screen settings. SOFTWARE/OS VERSIONS OS: Kubuntu 18.10 KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION PC is connected from an AMD GPU through HDMI to the monitor. PC is connected from the integrated Intel HDMI output to a Yamaha audio amplifier (5.1 Home cinema) which is connected through HDMI to a Samsung TV. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401151] docx files opened as archives in remote folders
https://bugs.kde.org/show_bug.cgi?id=401151 --- Comment #2 from Marcus --- I don't have all those opportunities to test remote protocols. In the case of FTP, it works correctly (I used this https://dlptest.com/ftp-test/), it open with LibreOffice (though I cannot read it from that server). I also noted the icon is different when I copy a file to google drive the icon becomes the one of archives (yellow). When a docx file is moved/copied to another location, it changes back to the violet document icon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401317] New: Replace the search system with KFind
https://bugs.kde.org/show_bug.cgi?id=401317 Bug ID: 401317 Summary: Replace the search system with KFind Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- The current search system used by Dolphin is far from being optimal. I wouldn't want to sound rough but the search system, when works, it shows just partial results, sometimes it doesn't work at all so that I ended up replacing search with filter, which is a good compromise most of times. At the same time we have KFind (which is great), it supports all sort of advanced search options, always finds every possible result and, most important, I never seen it crashing. I was wandering, did anyone contemplate the the idea to truly integrate it into Dolphin? (I mean not like it is now: use other search tools or similar) but to get the result from KFind when someone searches using the input text element from Dolphin (starting from the current directory). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392500] New: Session crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=392500 Bug ID: 392500 Summary: Session crashes when an external monitor is connected Product: kwin Version: 5.12.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: bio...@gmail.com Target Milestone: --- This bug happened starting from Plasma 5.12.3 (or maybe .2). I remember perfectly that it worked on the initial version of Plasma 5.12. What happens: With an external monitor the screen will suddently become black and the system will go to the login screen (which is correctly visualized). Now I use the live version of KDE Neon. When I start the system without the external monitor HDMI attached, it correctly loads. As soon as I attach the HDMI the screen becomes black and then loops between the initial white KDE logo on a black background and a total black screen. I use the live distro KDE Neon as downloaded from the website, without any modification. My GPU is: AMD HD 7950, CPU: Intel i5 3570k. The problem is 100% reproducible so I can provide logs if you tell me the command to input in the terminal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392500] Session crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=392500 --- Comment #2 from Marcus --- It is on X11 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #9 from Marcus --- I could go ahead and try testing the new version. 1. I found on the website the page for the new beta version: https://files.kde.org/kdenlive/unstable/kdenlive-18.04-beta2.AppImage.mirrorlist Is that the version you mentioned ? 2. I use gentoo, and there is a kde overlay which provides a Version kdenlive-18.04.49. , see http://gpo.zugaina.org/kde-apps/kdenlive Does this version contain the branch ? If not is it another version on any branch I could install with portage ? 3. If not - where can I read what to do with these AppImage files ? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 Marcus changed: What|Removed |Added CC||liquidni...@gmx.net --- Comment #2 from Marcus --- I see a similar issue on Gentoo64bit, media-libs/mlt-6.4.1-r6 kde-apps/kdenlive-17.12.1 Here I have a project with about 400 video files, about 500 time clips and >100 Speed settings. SOME operations like shifting clips in the time line , or lane-shifting, or something else kills lots of speed settings previously applied to lots of clips in the time line. I see me adding speed effects the 4th time over and over to the same clips :-( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #3 from Marcus --- This might be similiar to bug 385542 . Additional issue 1: When you copy a speed effect from one clip to another, the program forgets it. Additional issue 2: When you copy a color rotation effect from lane1 (with setting) to lane2, the program forgets the setting at lane2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385542] Clips with Speed effect reset when moved back with other clips
https://bugs.kde.org/show_bug.cgi?id=385542 Marcus changed: What|Removed |Added CC||liquidni...@gmx.net --- Comment #1 from Marcus --- Might be similar to bug 385780 - I am affected by this bug, too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #4 from Marcus --- I found steps to reproduce it: 1. create new project 2. add ONE video clip into bin 3. add a color clip 4. place the video clip into time line 5. put the color clip behind the video clip 6. add speed effect to video clip, set it to 200% 7. replay the clip section, check the double speed. 8. save project 9. do a GROUP MOVE of both clips, to the right (also to left) 10. check the replay, speed is gone ! 11. Save, reopen - the speed effect on the clip is gone ! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #5 from Marcus --- As I just tested, that version of kdenlive is affected by this bug: kde-apps/kdenlive-17.08.3 == gentoo-stable@2018-02-04 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #6 from Marcus --- I see on Linux mint, which uses kdenlive-15.12.3, that this bug is already in that old version. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #7 from Marcus --- The bug is also inkde-apps/kdenlive- , from the "kde" overlay, used in gentoo.This version of the ebuild downloads the most recent source and installs it. If the developers fix this bug, I could test it using the kde overlay again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #18 from Marcus --- I just tested kdenlive-19.03.70-b33cb35-x86_64.appimage . Applying speed, saving, closing, reloading, checking the speed works now. Actually this is the first version since some years where I see that feature working so far ;-) -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 403893] New: Wrong escaping written to file
https://bugs.kde.org/show_bug.cgi?id=403893
Bug ID: 403893
Summary: Wrong escaping written to file
Product: KBibTeX
Version: git (master)
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Loading/saving files
Assignee: fisc...@unix-ag.uni-kl.de
Reporter: marcus+...@distos.org
Target Milestone: ---
Created attachment 117806
--> https://bugs.kde.org/attachment.cgi?id=117806&action=edit
Example bibfile to reproduce bug
SUMMARY
When a bibtex entry with a diaeresis is read and then written again an invalid
macro is inserted leading to compilation failure by pdflatex.
STEPS TO REPRODUCE
1. Open attached bibtex file in kbibtex
2. Save the file with default options
OBSERVED RESULT
The resulting file has among others the following text in the author file:
Lo\"{\i}c
EXPECTED RESULT
The output should read
Lo\"ic
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.3
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #12 from Marcus --- I am using kde-apps/kdenlive-18.12.0 on gentoo linux (default/linux/amd64/17.0/desktop) and just tested the current version. The bug still persists and can be recreated by following Comment 4. Here I would note that this bug is not specific to the windows binary. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #14 from Marcus --- Created attachment 117458 --> https://bugs.kde.org/attachment.cgi?id=117458&action=edit Screenshot ofkdenlive-19.03.70-bd12c4f-x86_64.appimage I tested the kdenlive-19.03.70-bd12c4f-x86_64.appimage In the given version, there is no (more) speed effect available. See the screen shot. The former effect that was set with the older kdenlive version is not being represented in the current program. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 --- Comment #16 from Marcus --- I tested the kdenlive-19.03.70-bd12c4f-x86_64.appimage As i just see, the speed effect remains on group move, but disappears on project close , project reopen. Steps to reproduce it: 1. create new project 2. add ONE video clip into bin 3. add a color clip 4. place the video clip into time line 5. put the color clip behind the video clip 6. add speed effect to video clip, set it to 200% 7. replay the clip section, check the double speed. 8. save project 9. close kdenlive 10. start kdenlive, reload the project 10. check the clip in timeline / context menu / speed : the speed effect on the clip is gone. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743
--- Comment #6 from Marcus ---
I did some further research and found here another bug
https://bugs.kde.org/show_bug.cgi?id=280736 which is maybe related to this.
Manjaro provides hugin 2017.0.0-1.
As far as I understood the panoramagui tests which version auf autooptimizer is
installed through a parsing autooptimizer --help. The above mentioned bugs
reporter writes about cpfind:
> I assume it's executing 'cpfind --help' and trying to parse the first line,
> however kubuntu's hugin version does not have version number on the first
> line, but 'ThreadQueue created'.
That would explain that even choosing autooptimizer doesn't work for me.
But I don't know how to check the parsing process.
Starting digikam from the console I get this output when opening the
panoramagui:
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: Testing "cpclean" ...
digikam.general: "cpclean" help header line:
"cpclean version 2017.0.0.eac5e8cc546e"
digikam.general: Found "cpclean" version: "2017.0.0"
digikam.general: Testing "cpfind" ...
digikam.general: "cpfind" help header line:
"Hugin's cpfind 2017.0.0.eac5e8cc546e"
digikam.general: Found "cpfind" version: "2017.0.0"
digikam.general: Testing "enblend" ...
digikam.general: "enblend" help header line:
"enblend 4.2"
digikam.general: Found "enblend" version: "4.2"
digikam.general: Testing "make" ...
digikam.general: "make" help header line:
"GNU Make 4.2.1"
digikam.general: Found "make" version: "4.2.1"
digikam.general: Testing "nona" ...
digikam.general: "nona" help header line:
"nona version 2017.0.0.eac5e8cc546e"
digikam.general: Found "nona" version: "2017.0.0"
digikam.general: Testing "pano_modify" ...
digikam.general: "pano_modify" help header line:
"pano_modify version 2017.0.0.eac5e8cc546e"
digikam.general: Found "pano_modify" version: "2017.0.0"
digikam.general: Testing "pto2mk" ...
digikam.general: Testing "hugin_executor" ...
digikam.general: Found "hugin_executor"
digikam.general: Starting Main Thread
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: All Binaries Found : false
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: All Binaries Found : false
digikam.general: Hugin >= 2015.0 : false
digikam.general: Testing "pto2mk" ...
digikam.general: Testing "autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: All Binaries Found : false
digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ...
digikam.general: All Binaries Found : false
If I manually choose autooptimizer I get this output:
kf5.kio.widgets: No node found for item that was just removed:
QUrl("file:///usr/bin/gdb")
digikam.general: Testing "/usr/bin//autooptimiser" ...
digikam.general: "autooptimiser" help header line:
""
digikam.general: All Binaries Found : false
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #7 from Marcus --- I was writing autooptimizer but it should be autooptimiser! Checking the help file I get this: $ autooptimiser --help autooptimiser: optimize image positions autooptimiser version 2017.0.0.eac5e8cc546e Usage: autooptimiser [options] input.pto To read a project from stdio, specify - as input file. ... Which seems to be ok. ls -l /usr/bin/autooptimiser: -rwxr-xr-x 1 root root 133272 15. Jul 14:57 /usr/bin/autooptimiser -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #8 from Marcus --- Is that maybe a reason, the automatic testing searches here: digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... (autooptimiser inside a folder "autooptimiser") And manually adding the path: digikam.general: Testing "/usr/bin//autooptimiser" ... (two slashes: bin// ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #10 from Marcus --- Dear Gilles, thank you for your question. As far as I have researched the problem it could be a bug because it doesn't work with hugin 2017 or a packaging problem downstream, because it should be packaged with an earlier version of hugin. In the beginning I just saw, that the panorama stitching doesn't work for me. But my understanding now is, that it depends on your definition. Actually I posted at the Manjaro forum after I found out, that there have been similar problems with earlier versions and it might be a wrong packaging. Please let me know if you would say this is a packaging problem downstream and I will forward that to the Manjaro team. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #12 from Marcus --- Great! Looking forward to get the new version. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Marcus changed: What|Removed |Added CC||wellend...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #13 from Marcus --- Just to confirm: After an update to 5.7.0 on Arch the autooptimizer detection is working. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #14 from Marcus --- Sorry, that was on Manjaro, I don't know about Arch. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 385315] New: kipiplugins sendimage not available in digikam and gwenview
https://bugs.kde.org/show_bug.cgi?id=385315 Bug ID: 385315 Summary: kipiplugins sendimage not available in digikam and gwenview Product: kipiplugins Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: imaging-bugs-n...@kde.org Reporter: wellend...@posteo.de Target Milestone: --- I am using Manjaro stable with installed digikam and kipiplugins both version 5.7.0-1 libkipi 5.2.0 (17.08.1) and gwenview 17.08.1 KDE Frameworks 5.38.0 Qt 5.9.1 (compiled with 5.9.1) In Digikam and Gwenview I cant find the sendimage plugin to send an email attached picture anymore. There is no entry in the menues or context menues. I remember in Digikam it was in the tools menu before, in earlier versions in the export menu of the menubar, but neither there nor in the context menu is any entry for it. All other menues I looked through and didn't find anything related. In Digikam settings > plugins there is no email or sendimage plugin listed, like I saw before. There are 15 other plugins listed, I have only one choosen which appears in the menubar Then I opened Gwenview, not sure if there was a menue entry for sending pictures with email before. However, I don't find one now. I checked which files got installed with the kipi plugins in the /usr folder: kipiplugin_sendimages.desktop kipiplugin_sendimages.so kipiplugin_sendimagesui.rc plus a lot of kipiplugin_sendimages.mo files. Shouldn't be there an entry for using the plugin? Thank you for your attention! -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 385315] kipiplugins sendimage not available in digikam and gwenview
https://bugs.kde.org/show_bug.cgi?id=385315 Marcus changed: What|Removed |Added Version|5.8.0 |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379608] New: geo localisation with google and proxy
https://bugs.kde.org/show_bug.cgi?id=379608 Bug ID: 379608 Summary: geo localisation with google and proxy Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-de...@kde.org Reporter: wellend...@posteo.de Target Milestone: --- I am in China where all Google services are blocked. I have to use a proxy to get access to Google maps. Using the geolocation tool in Digikam it is not loading the Google maps, which seems to be because google is blocked, even if I have set the proxy in KDE settings. (Same with the Geolocation menu on the right) Digikam doesn't have proxy settings itself, as far as I found out. What can I do? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] New: cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 Bug ID: 381743 Summary: cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto Product: digikam Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panorama Assignee: digikam-de...@kde.org Reporter: wellend...@posteo.de Target Milestone: --- Running the panorama tool the tool stops after choosing the photographies to be stitched and pressing CONTINUE (with or without celeste) with the message cpfind kann nicht ausgeführt werden: Hugin's cpfind 2016.2.0.be8da0221960 based on Pan-o-matic by Anael Orlinski WARN: 07:24:32.652100 (/build/hugin/src/hugin-2016.2.0/src/hugin_base/panodata/Panorama.cpp:2054) readData(): Failed to read from dataInput. ERROR: couldn't parse panos tool script: 'pano_base.pto'! Detection took 0 seconds. This might have been already with earlier version, I haven't used the panorama tool for quite a time. Any suggestions? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 Marcus changed: What|Removed |Added CC||wellend...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #1 from Marcus --- Created attachment 106477 --> https://bugs.kde.org/attachment.cgi?id=106477&action=edit screenshot software hugin -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #2 from Marcus --- In this window can click "find" and it opens /usr/bin where is installed autooptimiser. But clicking the program it returns to this screen, still not display the version and showing "find", not "change (Ändern)" Similar problem if I press "find" to find pto2mk. Actually pto2mk is not installed later than Hugin 2014, hugin should instead search for hugin_executor, not for pto2mk actually. Manually adding hugin_executor doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #3 from Marcus --- This is running on Manjaro stable. I installed a stable opensuse, digikam 5.2, where it works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381743] cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto
https://bugs.kde.org/show_bug.cgi?id=381743 --- Comment #4 from Marcus --- This is on Manjaro stable. I parallel installed opensuse stable, where everything works fine with digikam 5.2. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 492147] System tray icon shown during recording is blank
https://bugs.kde.org/show_bug.cgi?id=492147 Marcus changed: What|Removed |Added Keywords|wayland | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 492147] System tray icon shown during recording is blank
https://bugs.kde.org/show_bug.cgi?id=492147 --- Comment #5 from Marcus --- (In reply to Noah Davis from comment #4) > Created attachment 175203 [details] > 256-status-media-recording-started.webp > > Can you view this animated webp image in gwenview? No. It says "Loading ‘test.webp’ failed Gwenview cannot display documents of type image/webp." -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 492147] System tray icon shown during recording is blank
https://bugs.kde.org/show_bug.cgi?id=492147 Marcus changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #7 from Marcus --- (In reply to Noah Davis from comment #6) > (In reply to Marcus from comment #5) > > No. > > > > It says "Loading ‘test.webp’ failed Gwenview cannot display documents of > > type image/webp." > > Then you are missing something in your system. Do you have the following two > packages installed? > > - https://archlinux.org/packages/extra/x86_64/libwebp/ > - https://archlinux.org/packages/extra/x86_64/qt6-imageformats/ I have libwebp installed, but not qt6-imageformats. This is a bug in Arch Linux. The qt6-imageformats package should be a dependency of spectacle. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494038] New: Blank networks show up in Networks widget when Wi-Fi is disabled
https://bugs.kde.org/show_bug.cgi?id=494038 Bug ID: 494038 Summary: Blank networks show up in Networks widget when Wi-Fi is disabled Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mar...@marcusspencer.xyz CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 174367 --> https://bugs.kde.org/attachment.cgi?id=174367&action=edit Wi-Fi disabled with a bunch of blank networks SUMMARY STEPS TO REPRODUCE 1. Click on the Networks widget 2. Turn Wi-Fi off OBSERVED RESULT All Wi-Fi networks disappear and wired networks keep showing in the Networks widget. Then a bunch of blank networks appear in the Networks widget. EXPECTED RESULT All Wi-Fi networks disappear and wired networks keep showing, but blank networks don't appear in the Networks widget. SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.11.1-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics NetworkManager version: 1.50.0 Blank networks persist even when Wi-Fi is re-enabled. core-testing, extra-testing and multilib-testing repositories are also enabled. When you *try* to configure these blank networks, it brings up a configuration screen for a network that actually exists. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371831] New: Digikam 5 missing Printer Driver Properties in Image Printing Dialog
https://bugs.kde.org/show_bug.cgi?id=371831 Bug ID: 371831 Summary: Digikam 5 missing Printer Driver Properties in Image Printing Dialog Product: digikam Version: 5.2.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ImageEditor-Print Assignee: digikam-de...@kde.org Reporter: m...@deltagram.eu Target Milestone: --- Created attachment 101883 --> https://bugs.kde.org/attachment.cgi?id=101883&action=edit Image Printing in Digikam 4 vs Digikam 5. I have recently switched to DigiKam 5.1 (and updated to 5.2) and have been quite happy so far. Unfortunately, however, I now found that DigiKam 5 doesn't seem to have all features of version 4 implemented yet. In particular, I'm missing a way to access the printer driver properties, when printing - no matter, if I'm using "Print Image" in the Image Editor or the KIPI-Plugin "Print Images". I added an attachement to illustrate the problem: In version 4 (top) the "Properties" button leads me to a dialog, where I can access a tab for "Advanced" settings. This contains the printer driver settings and this is what I'm looking for. In version 5 (bottom) this option is missing. (By the way: The tab "Job Options" are merely a way to schedule a print job, set a priority etc.) What am I missing? Do I need to install an additional plugin? Or hasn't this been implemented yet? Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368734] Moving a hierarchy of tags (a tag with subtags) doesn't work and can lead to losing the complete hierarchy
https://bugs.kde.org/show_bug.cgi?id=368734 --- Comment #11 from Marcus Christopher --- Any news on this? Can anyone confirm the phenomenon that I'm describing? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371831] Digikam 5 missing Printer Driver Properties in Image Printing Dialog
https://bugs.kde.org/show_bug.cgi?id=371831 --- Comment #2 from Marcus Christopher --- Yes, I have the same problem with all print functions. Do I have to install anything else (like another Qt library) to make this work in Qt5? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371831] Digikam 5 missing Printer Driver Properties in Image Printing Dialog
https://bugs.kde.org/show_bug.cgi?id=371831 --- Comment #4 from Marcus Christopher --- Thanks for your help. I just installed gwenview (based on Qt 5.5.1) for testing this. Yes, indeed, I do have the same problem there. What does that mean for my system? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371831] Digikam 5 missing Printer Driver Properties in Image Printing Dialog
https://bugs.kde.org/show_bug.cgi?id=371831 --- Comment #6 from Marcus Christopher --- I just searched for this issue and found this thread: http://lists.qt-project.org/pipermail/interest/2015-September/018694.html So, sorry for posting this problem here. It seems, this has been a long-standing issue in Qt5. And it seems, nothing has changed at since September 2015. As it is, this will probably keep me from using the new Digikam 5. What a shame. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372306] New: Kate crashes when pressing "0" and "1" while holding alt key
https://bugs.kde.org/show_bug.cgi?id=372306 Bug ID: 372306 Summary: Kate crashes when pressing "0" and "1" while holding alt key Product: kate Version: 16.08 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: marcus.behrendt...@gmail.com Target Milestone: --- Created attachment 102159 --> https://bugs.kde.org/attachment.cgi?id=102159&action=edit GDB output All is said in summary. This is reproducible on 2 computers. I am using Archlinux packages that come without debug symbols. Nevertheless I attached gdb output. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 372758] New: kio_plugins failing to load
https://bugs.kde.org/show_bug.cgi?id=372758 Bug ID: 372758 Summary: kio_plugins failing to load Product: frameworks-kio Version: 5.28.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: fa...@kde.org Reporter: flarel...@gmx.de CC: kdelibs-b...@kde.org Target Milestone: --- Hi I have the latest KDE Neon distribution with the latest updates installed. When I try to use remote:/, fish:/ or smb:/ ... both dolphin and krusader show (sorry for German language version): Prozess kann nicht gestartet werden: Aufruf des Ein-/Ausgabemoduls nicht möglich. klauncher meldet: Fehler beim Laden von „/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_remote.so“ I checked /usr/lib/x86_64-linux-gnu/qt5/plugins$ ll kio* -rw-r--r-- 1 root root 14656 Nov 13 14:42 kio_about.so -rw-r--r-- 1 root root 60656 Nov 13 14:42 kio_activities.so -rw-r--r-- 1 root root 23168 Nov 13 00:47 kio_applications.so -rw-r--r-- 1 root root 101520 Nov 12 00:37 kio_bluetooth.so -rw-r--r-- 1 root root 110400 Nov 13 12:38 kio_fonts.so -rw-r--r-- 1 root root 60688 Nov 13 13:43 kio_iso.so -rw-r--r-- 1 root root 72936 Nov 13 04:43 kio_kamera.so -rw-r--r-- 1 root root 52248 Nov 13 13:24 kio_kdeconnect.so -rw-r--r-- 1 root root 118936 Nov 13 13:43 kio_krarc.so -rw-r--r-- 1 root root 89648 Nov 12 00:37 kio_obexftp.so -rw-r--r-- 1 root root 43880 Nov 13 00:47 kio_remote.so -- so at least kio_remote.so is in place and it is installed from the neon repro. (5.28.0-0neon+16.04+build24) Is there a hack to help the load to find the .so and load it ? Best regrads, Marcus -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 372758] kio_plugins failing to load
https://bugs.kde.org/show_bug.cgi?id=372758 Marcus Menzel changed: What|Removed |Added CC||flarel...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371263] Rendering remaining time 00:00 and then stops
https://bugs.kde.org/show_bug.cgi?id=371263 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454428] New: Touchpad based kinetic scrolling in gtk applications does not work
https://bugs.kde.org/show_bug.cgi?id=454428
Bug ID: 454428
Summary: Touchpad based kinetic scrolling in gtk applications
does not work
Product: kwin
Version: 5.24.5
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: input
Assignee: kwin-bugs-n...@kde.org
Reporter: marcus.gur...@gmail.com
Target Milestone: ---
SUMMARY
Touchpad based kinetic scrolling in gtk applications does not work when using
kwin (wayland). After doing some digging and testing I found that the reason is
the way wl_pointer.axis_stop events are sent to application windows. kwin
(actually kwayland-server before it was merged in kwin) currently sends the
stop event for each axis in its own frame:
```
[13: wl_pointer] frame
[13: wl_pointer] axis_source: 1 (finger)
[13: wl_pointer] axis_stop: time: 1054759; axis: 0 (vertical)
[13: wl_pointer] frame
[13: wl_pointer] axis_source: 1 (finger)
[13: wl_pointer] axis_stop: time: 1054759; axis: 1 (horizontal)
[13: wl_pointer] frame
```
In other compositors (weston, wlroots based like sway, mutter) the stop events
for both axes are bundled in a single frame:
```
[13: wl_pointer] frame
[13: wl_pointer] axis_source: 1 (finger)
[13: wl_pointer] axis_stop: time: 1054759; axis: 0 (vertical)
[13: wl_pointer] axis_stop: time: 1054759; axis: 1 (horizontal)
[13: wl_pointer] frame
```
After patching kwayland-server to behave like sway etc kinetic scrolling works.
The patch needs more work obviously and is only intended to show the bare
minimum of changes to "make it work":
```
diff --git a/src/server/pointer_interface.cpp
b/src/server/pointer_interface.cpp
index b552ac4..128c6d9 100644
--- a/src/server/pointer_interface.cpp
+++ b/src/server/pointer_interface.cpp
@@ -236,7 +236,11 @@ void PointerInterface::sendAxis(Qt::Orientation
orientation, qreal delta, qint32
}
d->send_axis(resource->handle, d->seat->timestamp(),
wlOrientation, wl_fixed_from_double(delta));
} else if (version >= WL_POINTER_AXIS_STOP_SINCE_VERSION) {
-d->send_axis_stop(resource->handle, d->seat->timestamp(),
wlOrientation);
+if (wlOrientation == 0)
+{
+d->send_axis_stop(resource->handle, d->seat->timestamp(), 0);
+d->send_axis_stop(resource->handle, d->seat->timestamp(), 1);
+}
}
}
}
```
STEPS TO REPRODUCE
1. Open some gtk application, e.g. use gedit to display a large text file.
2. Scroll using touchpad and lift fingers while they are moving.
OBSERVED RESULT
The scrolling stops immediately after lifting the fingers.
EXPECTED RESULT
The scrolling goes on after lifting the fingers up.
SOFTWARE/OS VERSIONS
OS: Manjaro 21.2.6
uname -a: Linux marcus-surface 5.17.9-arch1-2-surface #1 SMP PREEMPT Wed, 25
May 2022 15:31:19 + x86_64 GNU/Linux
KDE Plasma Version: KDE Plasma 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 454496] Krita crash on save
https://bugs.kde.org/show_bug.cgi?id=454496 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454496] Krita crash on save
https://bugs.kde.org/show_bug.cgi?id=454496 --- Comment #3 from Marcus Harrison --- Created attachment 149732 --> https://bugs.kde.org/attachment.cgi?id=149732&action=edit New crash information added by DrKonqi krita (5.0.5) using Qt 5.15.4 Using the save dialogue - such as from the "Save As..." or "Export..." menu options - produces the crash. When opening an existing file and using the "Save" menu option, no crash happens. Seems to be confirmed in the backtrace in the `KisPreviewFileDialog` destructor. -- Backtrace (Reduced): #4 0x7f4fcf30ec47 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x2) at /usr/include/c++/9/bits/atomic_base.h:413 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x2) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 [...] #8 QList::~QList (this=0x55849ceed240, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:873 #9 0x7f4fcf39878c in KToolBar::Private::~Private (this=0x55849ceed190, __in_chrg=) at ./libs/widgetutils/xmlgui/ktoolbar.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454496] Krita crash on save
https://bugs.kde.org/show_bug.cgi?id=454496 --- Comment #4 from Marcus Harrison --- Ah, looks like it's solved in the duplicated ticket. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 467270] New: SMTP login not recognizing 334\r\n (example: GMX)
https://bugs.kde.org/show_bug.cgi?id=467270 Bug ID: 467270 Summary: SMTP login not recognizing 334\r\n (example: GMX) Classification: Applications Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: SMTP Assignee: trojita-b...@kde.org Reporter: m...@gmx.de Target Milestone: --- SUMMARY Login to GMX SMTP does not work, Trojita does not recognize the 334 message after its AUTH PLAIN *** 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. Add GMX as SMTP configuration (mail.gmx.net, STARTTLS or TLS) 2. Activate "Authentication" and add pretty much any email and password, hit "Save" 3. Compose a new email 4. Hit "Send" OBSERVED RESULT The progress bar stops at 50% for some time. The app waits for quite some time and finally declares a timeout. Except from console log: --- SMTP >>> "EHLO localhost\r\n" SMTP <<< 220 gmx.net (mrgmx104) Nemesis ESMTP Service ready SMTP <<< 250-gmx.net Hello localhost [84.xxx.xxx.xxx] SMTP <<< 250-8BITMIME SMTP <<< 250-AUTH LOGIN PLAIN SMTP <<< 250 SIZE 69920427 SMTP >>> AUTH PLAIN SMTP <<< 334 None of two regular expressions matched the input "334\r\n" SMTP <<< 421 gmx.net Service closing transmission channel - command timeout --- EXPECTED RESULT Login is successful SOFTWARE/OS VERSIONS Linux/KDE Plasma: Lubuntu 22.04.2 (available in About System) KDE Plasma Version: 5.24.7-0ubuntu0.1 / 5.92.0-0ubuntu1 (?) KDE Frameworks Version: 5.24.7-0ubuntu0.1 / 5.92.0-0ubuntu1 (?) Qt Version: ? ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435690] [Wayland] Kickoff, Krunner, and other applets open in the wrong place
https://bugs.kde.org/show_bug.cgi?id=435690 --- Comment #40 from Marcus Larborg --- Operativsystem: KDE neon 5.25 Version av KDE Plasma: 5.25.5 Version av KDE Ramverk: 5.98.0 Qt-version: 5.15.6 Kärnans version: 5.15.0-48-generic (64-bitar) Grafikplattform: Wayland Processorer: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Minne: 7,3 Gibyte minne Grafikprocessor: Mesa Intel® HD Graphics 4400 Tillverkare: Dell Inc. Produktnamn: XPS13 9333 I have the same issue. Not sure when this started, but have this issue with another user on the same computer. Tested to create a new user, but the issue persist. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468153] New: Changing Repeat Mode using the drop-down menu desynchronizes the toggle-button
https://bugs.kde.org/show_bug.cgi?id=468153 Bug ID: 468153 Summary: Changing Repeat Mode using the drop-down menu desynchronizes the toggle-button Classification: Applications Product: Elisa Version: 22.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY There are two methods of changing the repeat behaviour of Elisa: you can click the button to cycle through Playlist, One and None; or you can click-and-hold to select the play mode from a drop-down menu. If you don't use the drop-down menu at all, just toggling by clicking the button, the three modes work as expected. If you choose the play mode from the drop-down menu, the play mode you selected will be active. However, after choosing from the drop-down menu, the button will no longer reflect the play mode you selected. Changing the play mode by toggling the button no longer works, and the play mode the button displays doesn't reflect the mode selected from the drop-down menu. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.6 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve36-1-neptune (64-bit) Graphics Platform: X11 Processors: 8 × AMD Custom APU 0405 Memory: 14.5 GiB of RAM Graphics Processor: AMD Custom GPU 0405 Manufacturer: Valve Product Name: Jupiter System Version: 1 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468153] Changing Repeat Mode using the drop-down menu desynchronizes the toggle-button
https://bugs.kde.org/show_bug.cgi?id=468153 --- Comment #2 from Marcus Harrison --- Awesome! Thanks, and sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 471134] New: Subtitle settings are not preserved
https://bugs.kde.org/show_bug.cgi?id=471134 Bug ID: 471134 Summary: Subtitle settings are not preserved Classification: Applications Product: Haruna Version: 0.10.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: sund...@iki.fi Target Milestone: --- SUMMARY Some settings are promptly forgotten and must be reset at every launch. STEPS TO REPRODUCE 1. Change Settings->Configure->Allow subtitles in black borders (for example) 2. Close Haruna 3. Open Haruna again. OBSERVED RESULT The setting is reset to the old value when restarting Haruna. EXPECTED RESULT The setting should be persisted if you restart Haruna. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 471134] Subtitle settings are not preserved
https://bugs.kde.org/show_bug.cgi?id=471134 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 471135] New: Add dynamic range compressor audio filter
https://bugs.kde.org/show_bug.cgi?id=471135 Bug ID: 471135 Summary: Add dynamic range compressor audio filter Classification: Applications Product: Haruna Version: 0.10.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: sund...@iki.fi Target Milestone: --- Created attachment 159726 --> https://bugs.kde.org/attachment.cgi?id=159726&action=edit Dedynamicizer-curve SUMMARY In many environments (e.g. noisy) a video with wide dynamic range audio is impossible to listen to; either silent parts are too silent or loud parts get too loud. A dynamic range compressor (or a compressor/limiter) works by boosting low volume and/or lowering high volume. This way you can hear a whisper, and still not damage your hearing by a gunshot in the film. This is one of the most useful filters a movie player can have. It would be nice if the "high volume lowering" would actually keep the peaks where they are, but instead boost everything else, except very low volume. Like in the attached picture of a top-biased S-curve. The filter should have at least one setting: the amount of boosting to do. (Other minor things, like attack, release, and window size, could be hidden as long as they're at least somewhat sensible.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 471135] Add dynamic range compressor audio filter
https://bugs.kde.org/show_bug.cgi?id=471135 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 471134] Subtitle settings are not preserved
https://bugs.kde.org/show_bug.cgi?id=471134 --- Comment #2 from Marcus Sundman --- Thanks for fixing it. I tried to find a newer ubuntu version before reporting (and also searching for existing bug reports), but couldn't. Flatpak is a no. I'm not going to add any snaps or flatpaks or any such messes that run completely contrary to the native packaging system. An AppImage would be fine for testing, as it doesn't install anything or require anything or mess with anything, AFAIK. Otherwise I'll just refrain from reporting bugs. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448952] Choice of Generic 105-key PC keyboard not honored after installation
https://bugs.kde.org/show_bug.cgi?id=448952 --- Comment #1 from Marcus Seyfarth --- This is still an issue on Plasma 5.27.4 / KF 5.105.0 / Qt 5.15.9 / X11. It is not the "generic 86-key PC keyboard" hoewever on every distribution I tested it with, but sometimes the "generic 104-key PC keyboard". But the value is still off-by-one of the originally chosen value. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] New: Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 Bug ID: 459945 Summary: Multiple windows are force-opened in the center of the screen which shouldn't be Classification: Plasma Product: kwin Version: 5.25.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY Various windows which shouldn't open in the center of the screen are being forced to, including KRunner with Top position set, plasma widget pop-outs and plasma notifications. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A6-9220C RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 3.8 GiB of RAM Graphics Processor: AMD STONEY Manufacturer: Google Product Name: Grunt System Version: rev6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 --- Comment #1 from Marcus Harrison --- I just confirmed that this happens with a brand new user account using default settings as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 --- Comment #3 from Marcus Harrison --- (In reply to Vlad Zahorodnii from comment #2) > Can you check whether you have kwayland-integration or any package with > similar name (the naming may differ based on distro package naming > conventions) installed? Looks like I do indeed have that package installed: Installed kwayland-integration-4:5.25.5-0xneon+20.04+focal+release+build59.amd64 (installed:user_focal-focal-main) > Also, if you change the placement policy to > zero-cornered, are those windows placed differently? Interestingly, when I set the policy to zero-cornered, KRunner begins opening in the top-left corner, but the plasma panel pop-ups continue to appear in the center, rising up from the panel, and the notifications still appear in the center of the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 --- Comment #5 from Marcus Harrison --- (In reply to Vlad Zahorodnii from comment #4) > Okay, can you check whether qtwaylandclient has been updated recently and > perhaps try to downgrade it? I suspect that qtwaylandclient had been > updated, but due to a packaging mishap, kwayland-integration was not rebuilt. I did run upgrades yesterday before experiencing this issue, not sure which version I upgraded _from_ though. Current installed version is 5.15.5+p20.04+tunstable+git20220909.1409-0. Using apt to try to downgrade to version 5.15.5+p20.04+tunstable+git20220809.0847-0 gives a resolution that attempts to remove most depending KDE software and some system-critical packages (including neon-desktop), so I'm holding fire on doing that for now. -- You are receiving this mail because: You are watching all bug changes.
