[digikam] [Bug 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 --- Comment #56 from Hugo --- (In reply to caulier.gilles from comment #55) Dear Gilles, Everything works absolutely fine now! Thanks a lot for your efforts and support! 🤗 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465360] New: Can't get blacks or maximum color with my brush!!!
https://bugs.kde.org/show_bug.cgi?id=465360 Bug ID: 465360 Summary: Can't get blacks or maximum color with my brush!!! Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: hgmes...@gmail.com Target Milestone: --- SUMMARY I made a brush and the results of it are not the same! it is a brush I've made in older version and the result isn't the same in the newer one, I can't get the blacks of it when I'm sketching, but when I'm tunning the brush in the Scratchpad de result is normal, I don't know I other brushes suffer the same, but I've made this brush because I like to get darker in my sketces and now I dont have the same feeling of drawing pleasure... sorry for my english STEPS TO REPRODUCE 1. use my brush in krita 2. use the scratchpad to see the diference 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: yes 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.
[krita] [Bug 446470] New: Krita 5 Beta 5, brush strokes are diferent from krita 4
https://bugs.kde.org/show_bug.cgi?id=446470 Bug ID: 446470 Summary: Krita 5 Beta 5, brush strokes are diferent from krita 4 Product: krita Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: hgmes...@gmail.com Target Milestone: --- Created attachment 144210 --> https://bugs.kde.org/attachment.cgi?id=144210&action=edit Dry Brushing not working proprelly Brush storkes are diferent from krita 4 STEPS TO REPRODUCE 1. select (for example) Dry Brushing Brush and use it 2. go to brush edito and uncheck opacity (you may check it again) and use it 3. it goes to it's real brush setting (altought this brush uses to be short paint distance) 4. If you press the restore button it goes to the bugged state OBSERVED RESULT the mask seems not working 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 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 --- Comment #53 from Hugo --- (In reply to caulier.gilles from comment #52) Thanks a lot - can't wait to see it the next build :) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 450426] OFX import is broken on MS-Windows
https://bugs.kde.org/show_bug.cgi?id=450426 --- Comment #21 from Hugo --- Hello, I'm unsure about how to read this bug report, so my apologies if this reply is nonsense : - I certainly can import manualy OFX on my MS-windows KMM (I've just done it) - I can't Direct Connect since OFX Importer Plugin <https://docs.kde.org/stable5/en/kmymoney/kmymoney/details.impexp.ofx.html> seems to be missing in MS-windows KMM This might be the meaning of this bug report, though... Hugo Le mer. 13 avr. 2022 à 08:46, Thomas Baumgart via KMyMoney-devel < kmymoney-de...@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=450426 > > --- Comment #20 from Thomas Baumgart --- > To my knowledge, unfortunately, not yet. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 Hugo changed: What|Removed |Added CC||ze...@soppa.de Version|6.4.0 |7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 --- Comment #46 from Hugo --- Problem persists in version 7.6.0 In my case on Linux. All videos stutter, no matter whether .mov or .mp4 format -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 --- Comment #47 from Hugo --- I can confirm, the audio stream is the problem. When you disconnect audio in the OS, the video plays smoothly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382582] Video stutters when played with MP3 audio track
https://bugs.kde.org/show_bug.cgi?id=382582 --- Comment #49 from Hugo --- (In reply to caulier.gilles from comment #48) > Hi, > > The problem in digiKam is the lack of settings to tune backend to use for > video and audio playback. The default ones are used as well. I plan to add > the relevant code in digiKam to fix the problem. > > Also, you must know that QtAV is not maintained since February 2022. We > (digiKam team and me personalty) have backported all QtAV core codes in > digiKam 8.x and maintain/review/fix these codes for the digiKam uses (and > only these ones). > > See the README here : > https://invent.kde.org/graphics/digikam/-/tree/master/core/libs/video/qtav > > Best > > Gilles Caulier Thank you, looking forward to it very much -- it is such a nice program! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445296] New: Brush Stroke with "v" mypaint brush
https://bugs.kde.org/show_bug.cgi?id=445296 Bug ID: 445296 Summary: Brush Stroke with "v" mypaint brush Product: krita Version: 5.0.0-beta2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: hgmes...@gmail.com Target Milestone: --- SUMMARY MyPaint brushes using the line tool on Brush (pressing "V" to make line stroke) doesn't end on the end point. STEPS TO REPRODUCE 1. select a pencil with Mypaint engine on it 2. Make a stroke with "V" 3. Select a pencil with old version and try the same OBSERVED RESULT Brush stroke doesn't end on the cursor EXPECTED RESULT Brush stroke should end on the cursor SOFTWARE/OS VERSIONS Windows: Yes 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.
[kdeconnect] [Bug 432502] Unable to send files to the computers: "Failed sending file to COMPUTERNAME" #1048
https://bugs.kde.org/show_bug.cgi?id=432502 HUGO changed: What|Removed |Added CC||ibanezh...@iesremedios.es --- Comment #1 from HUGO --- Hello papanito, we are sorry for your problem, have you made sure that the two devices are connected to the same wify network? you have tried to restart the app or the device try that and if not contact us again. a greeting hugo. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432502] Unable to send files to the computers: "Failed sending file to COMPUTERNAME" #1048
https://bugs.kde.org/show_bug.cgi?id=432502 HUGO changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432502] Unable to send files to the computers: "Failed sending file to COMPUTERNAME" #1048
https://bugs.kde.org/show_bug.cgi?id=432502 --- Comment #3 from HUGO --- Good, it seems that it is not an error of the application, it is a connection error that your device has given, we regret your problem and if the problem continues, report again. The incidence that you present when attaching and downloading attachments from emails to that specific folder is caused by access restrictions (That is if your computer is part of a private or corporate network), Windows user restrictions or malware. Please tell me if you computer is home or belongs to a group or corporate network.While you reply to us, please create a new Windows session with administrator rights and from there try to attach and download attachments. Below I share a link that will help you in the process: How to create user accounts in Windows 10 ?. Tell me the results of this test, I will be attentive to your answer. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 424800] New: K3b crashes when adding a file with only a slash as name to a data project.
https://bugs.kde.org/show_bug.cgi?id=424800 Bug ID: 424800 Summary: K3b crashes when adding a file with only a slash as name to a data project. Product: k3b Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: h...@buddelmeijer.nl CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY K3b crashes when adding a file with only a slash as name to a data project. The file that caused this problem for me is from 2009. I'm fairly certain that I have burned this file to disc with K3b before in the last decade. Probably even with this operating system. Nevertheless, the filename was a mistake, so my immediate problem is fixed by renaming the file. STEPS TO REPRODUCE 1. Create a file with a slash as name. E.g. `echo "hello" >> "\\"`. 2. Start a new data project. 3. Drag the file into the project. OBSERVED RESULT K3b crashes: ASSERT: "i >= 0" in file /usr/include/qt4/QtCore/qstring.h, line 885 KCrash: Application 'k3b' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/hugo/.kde/socket-ubuntu32/kdeinit4__1 EXPECTED RESULT K3b should burn the file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 16.04.6 LTS (available in About System) KDE Plasma Version: ? KDE Frameworks Version: ? Qt Version: ? ADDITIONAL INFORMATION About K3b: Version 2.0.3 Using KDE Development Platform 4.14.16 Yeah this version is probably pretty old, but it seems this problem has been introduced only recently, so I thought it might be worthwhile to mention anyway. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 424800] K3b crashes when adding a file with only a slash as name to a data project.
https://bugs.kde.org/show_bug.cgi?id=424800 --- Comment #2 from Hugo --- 2.0.3 is the latest k3b version of the oldest Ubuntu LTS (16.04). But that is not your problem, maybe I should file the bug with Ubuntu. (And apparently Kubuntu 16.04 is not supported anymore, that would make the problem a bit more relevant.) It could be interesting to know what made this problem suddenly appear though. But well, not really worth it to dig into this if other versions are not affected. Thanks for checking and resolving Albert. I didn't know how to easily install a newer k3b version without breaking everything. Thanks for this wonderful piece of software. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 423190] Dropdown menus are drawn way right
https://bugs.kde.org/show_bug.cgi?id=423190 --- Comment #2 from Hugo --- Do you know if there's an issue tracking this upstream? (I did a bit of searching on the Qt bug tracker but didn't find anything on the topic). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410623] New: Crashing PlasmaShell on startup with Raven Ridge 2500u
https://bugs.kde.org/show_bug.cgi?id=410623 Bug ID: 410623 Summary: Crashing PlasmaShell on startup with Raven Ridge 2500u Product: plasmashell Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: omnicr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.3) Qt Version: 5.13.0 Frameworks Version: 5.60.0 Operating System: Linux 5.2.4-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: PlasmaShell frequently crashes upon login to Plasma - Unusual behavior I noticed: PlasmaShell frequently crashes upon login to Plasma. I manually start it using krunner which I have mapped to a keyboard shortcut. After 2-6 attempts, plasmashell will succeed and the full plasma sessions finished loading the desktop, panels and widgets successfully. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa0d9030880 (LWP 1645))] Thread 18 (Thread 0x7fa0a3fff700 (LWP 2447)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0ddd3e5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa0ddd3e692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa0dfb1e7bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa0dfb1ea6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa0ddd38520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fa0b085c700 (LWP 2445)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fa0b105d700 (LWP 2444)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fa0b8ff9700 (LWP 2346)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fa0b97fa700 (LWP 2345)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fa0b9ffb700 (LWP 2344)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fa0ba7fc700 (LWP 2343)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa0b3fff700 (LWP 2342)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa0dd20757f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa0dd9c70e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa0baffd700 (LWP 2341)): #0 0x7fa0dd20d415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa0c764973c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa0c7649338 in () at /usr/lib/dri/radeonsi_dri.so #3 0x000
[plasmashell] [Bug 410623] Crashing PlasmaShell on startup with Raven Ridge 2500u
https://bugs.kde.org/show_bug.cgi?id=410623 Hugo changed: What|Removed |Added CC||omnicr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 423190] New: Dropdown menus are drawn way right
https://bugs.kde.org/show_bug.cgi?id=423190 Bug ID: 423190 Summary: Dropdown menus are drawn way right Product: kolourpaint Version: 20.04 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: h...@barrera.io Target Milestone: --- Created attachment 129503 --> https://bugs.kde.org/attachment.cgi?id=129503&action=edit Screenshot SUMMARY The menubar menus are drawn far right of where the menubar and mouse are. At a small window size, it's just off-screen, at a larger window size, they're further right. Oddly, I've had no similar offset issues with actually drawing on kolourpaint. STEPS TO REPRODUCE 1. Click on any menubar item. OBSERVED RESULT Menubar is far on the right, or not visible with a smaller window size. EXPECTED RESULT Menubar should be right where the menubar and mouse are. SOFTWARE/OS VERSIONS - Linux 5.7.2-arch1-1 x86_64 GNU/Linux - sway version 1.4 - kolourpaint 20.04.2 - Qt 5.15.0-3 ADDITIONAL INFORMATION Apparently the icon files are missing in my distribution's package, or something is wrong there, but I don't think that should be relevant to this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpeople] [Bug 372463] Plasma crash
https://bugs.kde.org/show_bug.cgi?id=372463 Hugo changed: What|Removed |Added CC||ubuntufire...@yandex.ru --- Comment #2 from Hugo --- Created attachment 113019 --> https://bugs.kde.org/attachment.cgi?id=113019&action=edit Plasmashell crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpeople] [Bug 372463] Plasma crash
https://bugs.kde.org/show_bug.cgi?id=372463 --- Comment #3 from Hugo --- My crash was in Debian 9 (Testing). -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 496931] New: Notification and scrolling mouse in Version 1.10.24083 Linux
https://bugs.kde.org/show_bug.cgi?id=496931 Bug ID: 496931 Summary: Notification and scrolling mouse in Version 1.10.24083 Linux Classification: Applications Product: konversation Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: mxte...@hotmail.com Target Milestone: --- Hi, In in Version 1.10.24083 on Linux two bugs annoying: 1) Notification when anyone or anything cause it 2) No notification yet when someone open a private dialog + message 3) Scroll is broken, difficult -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371978] New: kwin segfaults when opening a new window
https://bugs.kde.org/show_bug.cgi?id=371978 Bug ID: 371978 Summary: kwin segfaults when opening a new window Product: kwin Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: hugo.klep...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: This bug has happened to me >10 times, usually ~1 a day. When it happens, it is always when I am opening a new window of some kind (ie, a gnome-terminal window, or a libreoffice document) It does not always occur when opening a new window. When it crashes, I see my desktop wallpaper for a split second then kwin reopens with all windows (including new one) present. - Unusual behavior I noticed: When kwin reopens, it seems it doesn't know where it had focus. Alt-tabbing and selecting windows with the mouse works strangely until I select a window explicitely. After it crashes if I had a workspace with a fullscreen youtube video then the browser must be restarted as I cannot un-fullscreen the video afterwards. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa398043840 (LWP 6135))] Thread 6 (Thread 0x7fa367fff700 (LWP 6624)): #0 0x7fa397a96551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa395148ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa39514a3b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3950f723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa394f1a0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa38faa02d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fa394f1ed78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa390d45454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa397a9f7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fa3677fe700 (LWP 6238)): #0 0x7fa390d4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa39408fac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fa39408fb09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fa390d45454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa397a9f7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa375230700 (LWP 6188)): #0 0x7fa397a96551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa395148ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa39514a3b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3950f723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa394f1a0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa38faa02d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fa394f1ed78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa390d45454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa397a9f7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fa377957700 (LWP 6162)): #0 0x7fa397a96551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa395148ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa39514a3b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3950f723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa394f1a0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa38ec6ae55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fa394f1ed78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa390d45454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa397a9f7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa37d8cf700 (LWP 6136)): #0 0x7fa397a9648d in poll () at /usr/lib/libc.so.6 #1 0x7fa396bdb8e0 in () at /usr/lib/libxcb.so.1 #2 0x7fa396bdd679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fa37e37b449 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fa394f1ed78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fa390d45454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa397a9f7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa398043840 (LWP 6135)): [KCrash Handler] #6 0x7fa38fa8b810 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /usr/lib/libQt5Qml.so.5 #7 0x7fa38fa8c775 in QQmlBinding::update(QFlags) () at /usr/lib/libQt5Qml.so.5 #8 0x7fa38fa96405 in () at /usr/lib/libQt5Qml
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Hugo Klepsch changed: What|Removed |Added CC|hugo.klep...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467500] New: Configuration for optional window outline
https://bugs.kde.org/show_bug.cgi?id=467500 Bug ID: 467500 Summary: Configuration for optional window outline Classification: Plasma Product: Breeze Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: hugor...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- SUMMARY It would be nice to have an option to make the new window outline optional. It is a nice feature for some use cases (e.g., dark themes), but there are other scenarios in which it creates visual noise (e.g., light themes with only a few dark windows, such as konsole). Also, it is kind of confusing with the general option "Window border size" = "No borders" within "Window Decorations". I know technically this new feature is not a border but an outline of another element, but the problem is most users don't understand the difference. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 482138] New: Bug when trying to shut down, restart or log out of the computer
https://bugs.kde.org/show_bug.cgi?id=482138 Bug ID: 482138 Summary: Bug when trying to shut down, restart or log out of the computer Classification: Applications Product: Discover Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: hugolfsim...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click the shutdown, restart or log out button OBSERVED RESULT After updating to the new version, the shutdown, restart and end session buttons do not work. I can only shut down the computer with command lines. EXPECTED RESULT When clicking on the buttons (shut down, restart or end session), they perform their actions SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION It started to occur after the update made on 03/01/2024 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451580] New: Titlebar buttons configuration KCM render error when not default settings
https://bugs.kde.org/show_bug.cgi?id=451580 Bug ID: 451580 Summary: Titlebar buttons configuration KCM render error when not default settings Product: kwin Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: hugor...@gmail.com Target Milestone: --- Created attachment 147531 --> https://bugs.kde.org/attachment.cgi?id=147531&action=edit Applied configuration vs configuration mockup SUMMARY In the "Titlebar Buttons" config on KCM "Window Decorations" there is a render problem when buttons are not in the default config. Drag and drop behaves strange and not all buttons are visible nor the same order. This was a fresh installation using Kubuntu 21.10 STEPS TO REPRODUCE 1. Open KCM "Window Decoration" 2. In the "Titlebar Buttons" tab modify the default button arrangement or add new buttons. 3. The behavior is not the expected, specially on drag and drop but also in the render. OBSERVED RESULT Render errors in buttons config mockup. There is an attachment with an example. EXPECTED RESULT Buttons in configuration mockup should appear in the same order of applied configuration. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451580] Titlebar buttons configuration KCM render error when not default settings
https://bugs.kde.org/show_bug.cgi?id=451580 Hugo Ortega_H changed: What|Removed |Added CC||plasma-b...@kde.org Component|decorations |kcm_kwindecoration Product|kwin|systemsettings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] New: KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 Bug ID: 427490 Summary: KDE Neon (user edition) freezes in the presentation screen after log-in. Product: plasmashell Version: 5.19.5 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: luckyfdga...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 132240 --> https://bugs.kde.org/attachment.cgi?id=132240&action=edit The system completely frozen in this screen. SUMMARY: I've installed KDE neon (user edition, with default themes, no extensions or customization). I updated my system, and when i restarted the system i logged-in, then plasma opened a black screen asking my kdewallet (i don't have one) and my wifi password. After i insert the wifi password, the system crashes and stucks in the presentation screen. My setup is: Intel Core i5-8265U, 8GB of RAM, 1tb (HD), 256GB (blitzwolf's ssd) <--- where the system is installed, Intel UHD Graphics 620. I tried to reinstall the system, but the same thing happened again STEPS TO REPRODUCE: 1. Install KDE Neon (user edition) in a ssd, with 400 MiB for boot, 8,5 GiB of SWAP and the /home installed in a HD 2. Update the system 3. Restart and Login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #1 from Victor Hugo --- Edit:In the steps to reproduce i said to put 400 MiB for the boot, but i tested it now and this bug happen with any quantity for boot, i'm not sure if it happen installing the /home in the same drive, cais i didn't tested it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #3 from Victor Hugo --- (In reply to David Edmundson from comment #2) > Can you VT switch(control+alt+f2) when this happens? > > If so can you get a snapshot of what's running > and ~/.local/share/sddm/xorg-session.log No, i can't do it. Nothing happens when i press those keys. Anyway, it's a clean installation, i didn't even downloaded my things or changed any system settings. I think the services that are ruinning in background are the standard of the system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #5 from Victor Hugo --- Oh just a thing: when you finish the installation of the system and it asks you to restart you can login normally, the bug happens when you update the system and restart by the second time after you've finish the installation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427490] KDE Neon (user edition) freezes in the presentation screen after log-in.
https://bugs.kde.org/show_bug.cgi?id=427490 --- Comment #6 from Victor Hugo --- (In reply to David Edmundson from comment #4) > >No, i can't do it. Nothing happens when i press those keys. > > Then I'm afraid that strongly implies your bug is lower level than Plasma > and there won't be much we can do. X handles those keys directly. > > You should be able to VT switch whilst on the login screen, from there you > can install openbox or some such to have a session you can log into. > > `journalctl -b -1 ` > might list something interesting. It'll show logs of the last boot. Ah, i really don't know if in the login screen i can do it. I can't test it anymore cause i've aready installed another distro instead KDE Neon (OpenSUSE) in my computer to i be able to use it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439695] New: fade transition apply in preview but not in render
https://bugs.kde.org/show_bug.cgi?id=439695 Bug ID: 439695 Summary: fade transition apply in preview but not in render Product: kdenlive Version: 21.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: hugo.trentes...@lilo.org Target Milestone: --- Created attachment 139976 --> https://bugs.kde.org/attachment.cgi?id=139976&action=edit minimal (non)working example SUMMARY Previewing a fade transition works as expected, but the render result is different. STEPS TO REPRODUCE 1. open minimal kdenlive file 2. render project 3. watch result OBSERVED RESULT Fade transition do not appear. A direct break is observed. EXPECTED RESULT Fade transition should appear as well as in project preview. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411643] krunner crash
https://bugs.kde.org/show_bug.cgi?id=411643 Hugo Klepsch changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Hugo Klepsch --- I don't recall this being an issue for a while. This was probably just a weird state that plasmashell was in. You can close if you like :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 Hugo Ortega_H changed: What|Removed |Added CC||hugor...@gmail.com --- Comment #337 from Hugo Ortega_H --- How can I help to re-implement these features? I have experience with Qt framework and QML. Personally, I'm more interested in different widgets per VD, but the wallpaper per VD would be nice. Years ago I made some patches for Kile and Umbrello applications, but I have no experience with Plasma core. Any suggestion would be welcome. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 Hugo Ortega_H changed: What|Removed |Added CC||hugor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 472302] Text in input doesn't wrap and become a multi-line string after hitting Shift+Enter
https://bugs.kde.org/show_bug.cgi?id=472302 Hugo Ortega_H changed: What|Removed |Added CC||hugor...@gmail.com --- Comment #5 from Hugo Ortega_H --- I just upgraded my Linux distribution and came here to see if someone had reported the problem. Also, there is no way to put a background color in the text, something that was possible in previous versions. But maybe this should be another issue report. Aside from that, I really liked the new UI. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429726] Kwin crashes while starting up after logout and login again
https://bugs.kde.org/show_bug.cgi?id=429726 Victor Hugo changed: What|Removed |Added CC||victor.makeav...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429726] Kwin crashes while starting up after logout and login again
https://bugs.kde.org/show_bug.cgi?id=429726 --- Comment #1 from Victor Hugo --- Created attachment 136266 --> https://bugs.kde.org/attachment.cgi?id=136266&action=edit New crash information added by DrKonqi kwin_x11 (5.19.5) using Qt 5.14.2 - What I was doing when the application crashed: how do i send u my log because there was nothing particular going on pretty standard stuff + this happens all the time i dont think its a behaviour-based kinda crash idk - Unusual behavior I noticed: - Custom settings of the application: -- Backtrace (Reduced): #5 0x7fdc124c50aa in QQmlValueTypeFactory::isValueType(int) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 [...] #9 0x7fdc12467a9d in QQmlDataBlob::tryDone() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fdc124b9ef9 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fdc124ba2d9 in QQmlTypeLoader::setData(QQmlDataBlob*, QByteArray const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 [...] #15 0x7fdc14735013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411643] New: krunner crash
https://bugs.kde.org/show_bug.cgi?id=411643 Bug ID: 411643 Summary: krunner crash Product: krunner Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: hugo.klep...@gmail.com Target Milestone: --- Application: krunner (5.16.5) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 5.2.11-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Trying to search for an installed application. - Unusual behavior I noticed: The keyboard shortcut to open krunner did not open the search window. I was able to search and open the application by just typing on an open desktop, which opened krunner and ran the search. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94b9d89840 (LWP 3269))] Thread 24 (Thread 0x7f9445ffb700 (LWP 3292)): #0 0x7f94be2b4415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f94bef505a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f94bef50692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f94c09747bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f94c0974a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f94bef4a520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f94be2ae57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f94bebd70e3 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f94467fc700 (LWP 3291)): #0 0x7f94be2b4415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f94bef505a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f94bef50692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f94b0334309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f94b0337d8b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f94b0337de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f94b03334fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f94b0335ecc in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7f94bef4a520 in () at /usr/lib/libQt5Core.so.5 #26 0x7f94be2ae57f in start_thread () at /usr/lib/libpthread.so.0 #27 0x7f94bebd70e3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f9446ffd700 (LWP 3290)): #0 0x7f94be2b4415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f94bef505a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f94bef50692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f94b0334309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrW
[plasmashell] [Bug 366284] Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 --- Comment #8 from Hugo Rens --- (In reply to Alexander Mentyu from comment #7) > @Hugo Rens is this bug still relevant for you after updates? Sorry for my lack of feedback, I didn't actually encountered the bug after a few updates (as far as I can remember) and I'm afraid I can't tell you exactly what update solved the issue. So no, the bug isn't relevant for me anymore. Can I (and should I) do something to close/delete the issue ? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 497614] New: OpenSSL vulnerabilities
https://bugs.kde.org/show_bug.cgi?id=497614 Bug ID: 497614 Summary: OpenSSL vulnerabilities Classification: Applications Product: kdiff3 Version: 1.12.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: h...@hugo-dias.com.pt Target Milestone: --- SUMMARY The KDiff3 is being distrubuted with openssl version 3.1.4 and it has multiple vulnerabilities STEPS TO REPRODUCE OBSERVED RESULT EXPECTED RESULT No vulnerabilities from OpenSSL SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION Having vulnerabilities has contraints in my computer due to company policies. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 497528] The procedure entry point DnsQueryEx could not be located in the dynamic link library DNSAPI.dll
https://bugs.kde.org/show_bug.cgi?id=497528 hugo lavia changed: What|Removed |Added CC||laviahug...@gmail.com Platform|Microsoft Windows |KDE Linux Component|windows-application |messaging-application OS|Microsoft Windows |Linux Version|24.02.0 |unspecified Assignee|piyushaggarwal...@gmail.com |si...@ergotech.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467143] New: No icons by default on non-KDE
https://bugs.kde.org/show_bug.cgi?id=467143 Bug ID: 467143 Summary: No icons by default on non-KDE Classification: Applications Product: Tokodon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Created attachment 157168 --> https://bugs.kde.org/attachment.cgi?id=157168&action=edit Statusbar screenshot SUMMARY I'm running tokodon on a non-KDE setup (specifically, on swaywm, a standalone compositor). Icons are not rendering. It might be something with my setup. I only have one other Qt application (neochat, also QML) and it has the same issue. I just don't know exactly where these applications read icons though. I have the following icon-related packages installed on this host: arc-icon-theme kiconthemes adwaita-icon-theme moka-icon-theme hicolor-icon-theme I'm not trying to rice, or be picky or have specific icons -- I mostly want ANY readable icons to render. STEPS TO REPRODUCE The easiest way to repro this is probably to install an Arch or Alpiine VM, install sway and tokodon and just run that. It's a non-trivial amount of effort, so I'm happy to provide further debugging information. OBSERVED RESULT Out-of-the-box, no icons are rendered. EXPECTED RESULT Out-of-the-box, icons should render OR some clear indication of what's missing. SOFTWARE/OS VERSIONS Linux Plasma: Alpine Linux, swaymw (standalone wayland compositor) Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467143] No icons by default on non-KDE
https://bugs.kde.org/show_bug.cgi?id=467143 --- Comment #1 from Hugo Osvaldo Barrera --- Created attachment 157169 --> https://bugs.kde.org/attachment.cgi?id=157169&action=edit Screenshot of a toot -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467143] No icons by default on non-KDE
https://bugs.kde.org/show_bug.cgi?id=467143 --- Comment #2 from Hugo Osvaldo Barrera --- Created attachment 157170 --> https://bugs.kde.org/attachment.cgi?id=157170&action=edit Screenshot of hover menu on message in conversation -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467143] No icons by default on non-KDE
https://bugs.kde.org/show_bug.cgi?id=467143 --- Comment #3 from Hugo Osvaldo Barrera --- Suggestions online indicate that setting `QT_QPA_PLATFORMTHEME=gtk` would make Qt use the same icon theme as GTK, but setting that variable does not show any improvements. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467162] New: UX: Focus textarea for new toot
https://bugs.kde.org/show_bug.cgi?id=467162 Bug ID: 467162 Summary: UX: Focus textarea for new toot Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- When I click "toot" on the upper right, the interface to type a new toot shows up. It would make sense for its textarea to be focused by default. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467163] New: Chat view scrolls when selecting text vertically
https://bugs.kde.org/show_bug.cgi?id=467163 Bug ID: 467163 Summary: Chat view scrolls when selecting text vertically Classification: Applications Product: NeoChat Version: 23.01.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu Target Milestone: --- SUMMARY In the main chat window,I can click-and-drag to select text horizontally (e.g.: left to right). However, if I try to drag vertically (e.g.: to select multiple lines of text), dragging the mouse actually moves the chat window up and down. This shouldn't happen when the click-drag was initiated on text. STEPS TO REPRODUCE 1. Send a multi-line message on a chat. 2. Click-and-hold on the first line and move the mouse to the second or third line. OBSERVED RESULT Chat area moves vertically and can't select more than one line. EXPECTED RESULT Area shouldn't move in this case. SOFTWARE/OS VERSIONS Linux: swaywm/wayland Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467164] New: UX: Ctrl+enter to submit new toot
https://bugs.kde.org/show_bug.cgi?id=467164 Bug ID: 467164 Summary: UX: Ctrl+enter to submit new toot Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- When drafting a new toot, pressing Ctrl+Enter should submit. Tab doesn't work on this screen, so there's no keyboard-only way to submit the toot. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467198] New: Opening files in terminal fails but opening a terminal works
https://bugs.kde.org/show_bug.cgi?id=467198 Bug ID: 467198 Summary: Opening files in terminal fails but opening a terminal works Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: h...@whynothugo.nl CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If I right click anywhere and pick "Open terminal here", it opens my default terminal, foot. If I double click on a text file (which opens in vim, in a terminal), dolphin errors: "Terminal konsole not found while trying to run /usr/share/appliations/nvim.desktop." OBSERVED RESULT Depending no the action, dolphin uses a different mechanism to spawn the default terminal, and one is broken. EXPECTED RESULT The mechanism to determine the current terminal should be consistent despite what action I'm performing. SOFTWARE/OS VERSIONS Linux: Alpine Linux, Linux 6.2.2-0-edge x86_64 Linux Qt Version: qt5-5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467205] New: -v doesn't print anything if tokodon is already running
https://bugs.kde.org/show_bug.cgi?id=467205 Bug ID: 467205 Summary: -v doesn't print anything if tokodon is already running Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY tokodon --version doesn't work either. STEPS TO REPRODUCE 1. tokodon --version or tokodon -v OBSERVED RESULT Nothing is printed, exit code success. EXPECTED RESULT The version SOFTWARE/OS VERSIONS Linux: Alpine Qt Version: 5.15.8 ADDITIONAL INFORMATION My guess is that the single-instance check kicks in before checking if --version was specified -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467206] New: UX: search says "no results found" before anything loads
https://bugs.kde.org/show_bug.cgi?id=467206 Bug ID: 467206 Summary: UX: search says "no results found" before anything loads Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY I find it hard to distinguish these two states: - The search has not begun. - The search is done and yielded no results. STEPS TO REPRODUCE 1. Just search for anything. Bonus points if your internet is slow. OBSERVED RESULT The original message "no results found" is wrong. EXPECTED RESULT It should say "searching...". SOFTWARE/OS VERSIONS Linux: Alpine Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457581] [non-KDE] no icons unless a theme is explicitly configured
https://bugs.kde.org/show_bug.cgi?id=457581 --- Comment #2 from Hugo Osvaldo Barrera --- Installing the "breeze" icon theme works (e.g.: it gets used automatically). It seems that dolphin tries to use Breeze by default, even if it's not installed. I think the issue here is that dolphin tries to use breeze even if it's not installed, rather than falling back to any of the installed icon themes. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467724] New: Feature: allow refreshing an open toot
https://bugs.kde.org/show_bug.cgi?id=467724 Bug ID: 467724 Summary: Feature: allow refreshing an open toot Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY I have a toot open, and I'd like to refresh it since I know there are more recent replies. A "refresh" button on top would be very handy (bonus points for a "fetched at..." label). Mentioned on IRC: > C: Ideally we should try to use websockets update for that > R: i searched around the api, but i dont think you can actually subscribe to > a thread or a toot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467752] New: Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 Bug ID: 467752 Summary: Dolphin uses black text over black background when using the BreezeDark theme Classification: Applications Product: dolphin Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: h...@whynothugo.nl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 157546 --> https://bugs.kde.org/attachment.cgi?id=157546&action=edit screenshot SUMMARY When using the "BreezeDark" theme, the main panel uses black background with black text. This is unreadable. See screenshot. STEPS TO REPRODUCE 1. `ln -s /usr/share/color-schemes/BreezeDark.colors ~/.config/kdeglobals -f` 2. `dolphin` Note that changing the theme has a different procedure in KDE since it's handled by a dedicated daemon. OBSERVED RESULT Black text on black background. EXPECTED RESULT Good contrast in text. SOFTWARE/OS VERSIONS Linux : Linux 6.2.2-0-edge x86_64 Linux Qt Version: 5.15.8 ADDITIONAL INFORMATION I'm using dolphin on swaywm (a standalone compositor). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 --- Comment #2 from Hugo Osvaldo Barrera --- I'm already following the issue you mention and have already commented there on a separate item there already. However, I don't feel that this bug falls under its scope. The main topic on that issue is about KDE applications adopting the theme of other DEs, and how they can integrate better into Gnome and similar DEs. I'm not really trying to make Dolphin look like other applications on my desktop or trying to integrate it with any DE in any way. I don't have a strong preference on which theme it uses, or what type of widgets it draws either. I'm using Dolphin with the default theme (Breeze) with the dark colour preference. Both of these are part of KDE; there's nothing about a different DE involved in this scenario (though I'll clarify I'm also not using KDE; I have a single no-DE setup). The issue at hand is black text on black background, which is simply totally unreadable, and not really a matter of "appearance" (please do check out the screenshot if you haven't). I expect the outcome of the issue you link to be some mechanism whereby a DE can tell KDE applications to render using a different theme or something alike. I've no interest in this mechanism; the ideal fix for _this_ issue would be that applications render readable out-of-the-box without any such additional customization mechanism. It's also worth mentioning, Neochat and Tokodon render text white (or is it light gray?) text on black background on this same host and are perfectly readable; this issue is specifically about Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 --- Comment #3 from Hugo Osvaldo Barrera --- Oh, I'm enabling the BreezeDark variant by simply: ln -s /usr/share/color-schemes/BreezeDark.colors ~/.config/kdeglobals -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 456647] When opening a read room, neochat scrolls somewhere randomly up
https://bugs.kde.org/show_bug.cgi?id=456647 Hugo Osvaldo Barrera changed: What|Removed |Added CC||h...@whynothugo.nl -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 456647] When opening a read room, neochat scrolls somewhere randomly up
https://bugs.kde.org/show_bug.cgi?id=456647 Hugo Osvaldo Barrera changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470302] New: Dolphin se cierra
https://bugs.kde.org/show_bug.cgi?id=470302 Bug ID: 470302 Summary: Dolphin se cierra Classification: Applications Product: dolphin Version: 23.04.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hugorafael1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) (Compiled from sources) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.1.30-1-lts x86_64 Windowing System: X11 Distribution: EndeavourOS DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Dolphin se cierra para abrir en modo administracion, siempre toca cerrar las pestañas que tengas abiertas en el Dolphin para poder accerder al Dolphin en modo Administracion. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f020769aa98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #5 0x7f02083cd664 in ?? () from /usr/lib/libQt5Widgets.so.5 #6 0x7f02083cec27 in ?? () from /usr/lib/libQt5Widgets.so.5 #7 0x7f020837893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7f020769ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7f0207b4121c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #10 0x7f0207b2a955 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #11 0x7f020152f710 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #12 0x7f020550f53b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #13 0x7f020556c219 in ?? () from /usr/lib/libglib-2.0.so.0 #14 0x7f020550e1a2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #15 0x7f02076e9f2f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #16 0x7f0207699824 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #17 0x7f020769acc3 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #18 0x55f46fe80da8 in ?? () #19 0x7f0206e39850 in ?? () from /usr/lib/libc.so.6 #20 0x7f0206e3990a in __libc_start_main () from /usr/lib/libc.so.6 #21 0x55f46fe81565 in ?? () [Inferior 1 (process 12487) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470304] New: Dolphin Chrass
https://bugs.kde.org/show_bug.cgi?id=470304 Bug ID: 470304 Summary: Dolphin Chrass Classification: Applications Product: dolphin Version: 23.04.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hugorafael1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) (Compiled from sources) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.1.30-1-lts x86_64 Windowing System: X11 Distribution: EndeavourOS DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Se me cierra y demora mucho la respuesta, de algunas aplicaciones. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f37c2ac0c08 in QObject::thread() const () from /usr/lib/libQt5Core.so.5 #5 0x7f37c2ac692f in QObject::QObject(QObjectPrivate&, QObject*) () from /usr/lib/libQt5Core.so.5 #6 0x7f37c3efb0ad in QDBusPendingCallWatcher::QDBusPendingCallWatcher(QDBusPendingCall const&, QObject*) () from /usr/lib/libQt5DBus.so.5 #7 0x7f37c4a8257b in ?? () from /usr/lib/libKF5KIOWidgets.so.5 #8 0x7f37c2acffe7 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f37c376bbb7 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #10 0x7f37c377160b in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #11 0x7f37c38f3b4b in ?? () from /usr/lib/libQt5Widgets.so.5 #12 0x7f37c38f3c6d in ?? () from /usr/lib/libQt5Widgets.so.5 #13 0x7f37c37af1e1 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f37c377893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f37c377ddef in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f37c2a9ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x7f37c377c12a in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f37c37cd9d4 in ?? () from /usr/lib/libQt5Widgets.so.5 #19 0x7f37c37cec27 in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x7f37c377893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x7f37c2a9ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #22 0x7f37c2f4121c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #23 0x7f37c2f2a955 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #24 0x7f37bd04d710 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #25 0x7f37c090f53b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x7f37c096c219 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0x7f37c090e1a2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0x7f37c2ae9f0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #29 0x7f37c2a99824 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #30 0x7f37c38fb3f8 in ?? () from /usr/lib/libQt5Widgets.so.5 #31 0x7f37c38fb513 in QMenu::exec(QPoint const&, QAction*) () from /usr/lib/libQt5Widgets.so.5 #32 0x5641ffb0b9f0 in ?? () #33 0x7f37c2acffe7 in ?? () from /usr/lib/libQt5Core.so.5 #34 0x7f37c4d37289 in DolphinView::requestContextMenu(QPoint const&, KFileItem const&, KFileItemList const&, QUrl const&) () from /usr/lib/libdolphinprivate.so.5 #35 0x7f37c4da7b84 in DolphinView::slotViewContextMenuRequested(QPointF const&) () from /usr/lib/libdolphinprivate.so.5 #36 0x7f37c2acffe7 in ?? () from /usr/lib/libQt5Core.so.5 #37 0x7f37c4d34bea in KItemListController::viewContextMenuRequested(QPointF const&) () from /usr/lib/libdolphinprivate.so.5 #38 0x7f37c4d6f22a in KItemListController::onPress(QPoint const&, QPointF const&, QFlags, QFlags) () from /usr/lib/libdolphinprivate.so.5 #39 0x7f37c4d6f69e in KItemListController::mousePressEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /usr/lib/libdolphinprivate.so.5 #40 0x7f37c4d72eeb in KItemListController::processEvent(QEvent*, QTransform const&) () from /usr/lib/libdolphinprivate.so.5 #41 0x7f37c4d7608e in KItemListView::event(QEvent*) () from /usr/lib/libdolphinprivate.so.5 #42 0x7f37c377893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #43 0x7f37c2a9ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #44 0x7f37c3a948c0 in ??
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 --- Comment #4 from Hugo Osvaldo Barrera --- Still an issue in dolphin-24.02.0. Dolphin renders black text on black background with the dark Breeze theme. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 --- Comment #6 from Hugo Osvaldo Barrera --- Thanks for your reply. I was unaware on the distinction between theme and color scheme. I have breeze installed locally on my system, and have configured nothing Qt/KDE related. It was my understanding that Breeze was the default theme, so I assumed this was the currently applied theme. I don't see any output on stdout from dolphin. I'm not sure that it is failing to apply the default theme and using a fallback. I can't find any references to Fusion anywhere on my system, so I'm also unsure whether it is installed. I checked some of the paths were breeze includes files,and it's the only one present. E.g.: ``` $ ls /usr/share/color-schemes/ BreezeClassic.colors BreezeDark.colors BreezeLight.colors $ ls /usr/lib/qt5/plugins/styles/ breeze.so $ ls /usr/share/QtCurve/ Breeze.qtcurve ``` Assuming that the error is in how I am applying the color-scheme, what is the correct approach to tell dolphin to use a dark variant of the current theme? I don't really care much which theme is used, I just don't want a white screen when I switch to it in the middle of the night. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483033] New: Stuck in accounts screen with no path forward
https://bugs.kde.org/show_bug.cgi?id=483033 Bug ID: 483033 Summary: Stuck in accounts screen with no path forward Classification: Applications Product: NeoChat Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: h...@whynothugo.nl CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166826 --> https://bugs.kde.org/attachment.cgi?id=166826&action=edit screenshot of neochat SUMMARY I'm stuck in the account screen (see screenshot). Apparently I can log out, but can't continue past this screen. Clicking on my username or on the arrow to its right does nothing. Compete terminal output: > neochat qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" Reading access token from the keychain for "@whynothugo:matrix.org" file:///usr/lib/qt6/qml/org/kde/kirigami/templates/private/PassiveNotificationsManager.qml:171:19: QML Control: Binding loop detected for property "implicitHeight" file:///usr/lib/qt6/qml/org/kde/kirigami/templates/private/PassiveNotificationsManager.qml:171:19: QML Control: Binding loop detected for property "implicitHeight" 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.
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 --- Comment #8 from Hugo Osvaldo Barrera --- >From where does Dolphin read the current theme? -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483033] Stuck in accounts screen with no path forward
https://bugs.kde.org/show_bug.cgi?id=483033 --- Comment #2 from Hugo Osvaldo Barrera --- Clocking on the red "X" next to the account does not delete it. I wanted to try simply wiping all settings, but I don't see neochat's data files in ~/.local/share/neochat or ~/.local/state/neochat or ~/.cache/neochat. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483033] Stuck in accounts screen with no path forward
https://bugs.kde.org/show_bug.cgi?id=483033 --- Comment #3 from Hugo Osvaldo Barrera --- I tried picking "Login" and adding the same account again but it simply freezes after I provide a password. I restarted neochat and after a third time it did work; I got two successive requests from keepassxc to disclose secrets (looks like neochat tried to read them multiple times at startup this time?) and then it worked. Not sure if I'm seeing a flaky issue or what. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483033] Stuck in accounts screen with no path forward
https://bugs.kde.org/show_bug.cgi?id=483033 Hugo Osvaldo Barrera changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Hugo Osvaldo Barrera --- I think the root of the issue here was a mis-configuration on my part; keepassxc was prompting for consent to disclose a secret, but due to some local configuration those prompts are very frequently not visible (see also: https://github.com/keepassxreboot/keepassxc-browser/issues/1980 ). It's possible that I was not running KPXC some of the times I had tried. It seems that neochat provides no indication when the secret service is not running. I do think that printing a bit more information to stdout would help. Especially when the secret service is not running. I'll close this though, since this seems to be resolved. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 415927] Impossible to pick a screen color on Wayland
https://bugs.kde.org/show_bug.cgi?id=415927 Hugo Parente Lima changed: What|Removed |Added Assignee|hugo...@gmail.com |unassigned-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 415927] Impossible to pick a screen color on Wayland
https://bugs.kde.org/show_bug.cgi?id=415927 Hugo Parente Lima changed: What|Removed |Added CC||hugo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457581] New: [non-KDE] no icons unless a theme is explicitly configured
https://bugs.kde.org/show_bug.cgi?id=457581 Bug ID: 457581 Summary: [non-KDE] no icons unless a theme is explicitly configured Product: dolphin Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: h...@whynothugo.nl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 151160 --> https://bugs.kde.org/attachment.cgi?id=151160&action=edit Screenshot of what dolphin looks like out-of-the-box SUMMARY When running dolphin on a non-KDE setup (in my case, swaywm), dolphin will render no icons by default. This is kind of a "known issue", and Arch's wiki describes a workaround: installing qt5ct, picking an icon theme and then setting an environment variable whenever running Dolphin. While the workaround works, it provides a very poor out-of-the-box experience. If a user has not explicitly chosen an icon theme, using _any_ icon theme would be better than none. The initial impression is otherwise very poor, and even using the wrong icons would give a better impression (those not using KDE shouldn't be surprised by a theme mismatch anyway). OBSERVED RESULT All icons are blank. See screenshot. EXPECTED RESULT Render using any icon theme.. SOFTWARE/OS VERSIONS Linux: Linux 5.19.0-rc7-asahi-2-1-ARCH aarch64 GNU/Linux KDE Plasma Version: this issue is specific to non-KDE setups Qt Version: qt5-base is 5.15.5+kde+r174-1, though this is not a new issue at all ADDITIONAL INFORMATION It's possible the issue at hand is not Dolphin-specific an actually in some dependency/framework that's in use here. If so, please let me know which component that is and I can report to the correct place. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457581] [non-KDE] no icons unless a theme is explicitly configured
https://bugs.kde.org/show_bug.cgi?id=457581 --- Comment #1 from Hugo Osvaldo Barrera --- Oh, QT_QPA_PLATFORMTHEME is unset. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473415] New: Cannot see any signature information for a signed PDF
https://bugs.kde.org/show_bug.cgi?id=473415 Bug ID: 473415 Summary: Cannot see any signature information for a signed PDF Classification: Applications Product: okular Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: h...@whynothugo.nl Target Milestone: --- Created attachment 160980 --> https://bugs.kde.org/attachment.cgi?id=160980&action=edit PDF mentioned in the issue description SUMMARY I have received a signed PDF document. This document is signed with a certificate that is signed by a CA operate by the Argentinian government (and is not bundled by default on any distribution or browser). When I open the PDF on Okular, it merely states "Some of the signatures could not be validated properly". The reason that I am opening the file with Okular is to check the signature, but no details are shown anywhere. E.g.: Okular validates the signature for me, but won't display it, nor the certificate associated with it, nor any information related to it. The main issue here is that the "View certificate" button is disabled, but there is no indication why (am I missing an optional dependency?). The only output that okular is providing is unrelated: > okular Afirmar_signed.pdf kf.windowsystem: Could not find any platform plugin QWidget::setMinimumSize: (okular_sidebar/Sidebar) Negative sizes (0,-1) are not possible qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x7fdc917f5670) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x7fdc82abea90) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents OBSERVED RESULT No details on the PDF's signature are visible. No details on the certificate that signed it are visible. EXPECTED RESULT I should be able to see the PDF and details on its signature. SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: no KDE Plasma Version: no KDE Frameworks Version: no Qt Version: qt5-qtbase-5.15.10 I'm using okular 23.04.3 on Alpine-Edge. Originally reported at: https://invent.kde.org/graphics/okular/-/issues/82 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473415] Cannot see any signature information for a signed PDF
https://bugs.kde.org/show_bug.cgi?id=473415 --- Comment #1 from Hugo Osvaldo Barrera --- Created attachment 160981 --> https://bugs.kde.org/attachment.cgi?id=160981&action=edit Screenshot of Okular -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473415] Cannot see any signature information for a signed PDF
https://bugs.kde.org/show_bug.cgi?id=473415 --- Comment #3 from Hugo Osvaldo Barrera --- The PDF is already attached to this issue. See https://bugs.kde.org/attachment.cgi?id=160980 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473415] Cannot see any signature information for a signed PDF
https://bugs.kde.org/show_bug.cgi?id=473415 --- Comment #5 from Hugo Osvaldo Barrera --- Thanks for narrowing that down for me. I've rebuilt poppler with nss support (and then rebuilt okular) and not it works. I've sent an MR adding nss-dev as a build dependency: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/50095 -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 413691] Color picker picks color from the wrong place when monitors are configured using xrandr (using --scale, --pos and --panning parameters)
https://bugs.kde.org/show_bug.cgi?id=413691 --- Comment #1 from Hugo Parente Lima --- Hi, KColorchooser is just a QColorDialog with extra buttons injected, so you must file this bust to Qt5[1], since there's not much we can do on KDE side. Thanks! [1] https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 379596] New: Cannot create the folder /Logical_View Please check the access rights
https://bugs.kde.org/show_bug.cgi?id=379596 Bug ID: 379596 Summary: Cannot create the folder /Logical_View Please check the access rights Product: umbrello Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: task Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: dnhu...@hotmail.com Target Milestone: --- Created attachment 105375 --> https://bugs.kde.org/attachment.cgi?id=105375&action=edit Project with prints of environment and error I just did create a class with two attributes (int type, both) and ask to generate a C ++ code. But in the last step (the effective button to generate) report this error. Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 506085] Dolphin crashes when trying to play audio file in information panel
https://bugs.kde.org/show_bug.cgi?id=506085 Hugo F. Meira changed: What|Removed |Added Component|general |panels: information -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 506085] New: Dolphin crashes when trying to play audio file in information panel
https://bugs.kde.org/show_bug.cgi?id=506085 Bug ID: 506085 Summary: Dolphin crashes when trying to play audio file in information panel Classification: Applications Product: dolphin Version First 25.04.2 Reported In: Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hugofranciscome...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (25.04.2) ApplicationNotResponding [ANR]: false Qt Version: 6.9.1 Frameworks Version: 6.15.0 Operating System: Linux 6.15.3-1-cachyos x86_64 Windowing System: Wayland Distribution: CachyOS DrKonqi: 6.4.0 [CoredumpBackend] -- Information about the crash: When trying to preview .mp3 or .flac audio files in dolphin's information panel, the application freezes then crashes. This happens every time you click to play an audio file in the info panel. No other odd behaviour was observed in the application aside from this The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping note processing warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping note processing warning: Can't open file anon_inode:i915.gem during file-backed mapping note processing [New LWP 6833] [New LWP 6987] [New LWP 6992] [New LWP 6841] [New LWP 6996] [New LWP 6990] [New LWP 6993] [New LWP 6834] [New LWP 6843] [New LWP 6858] [New LWP 6989] [New LWP 6837] [New LWP 6840] [New LWP 6844] [New LWP 6862] [New LWP 6994] [New LWP 6835] [New LWP 6836] [New LWP 6842] [New LWP 6857] [New LWP 6861] [New LWP 6988] [New LWP 6995] [New LWP 7005] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/dolphin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7f1d69b43a80 (LWP 6833))] Cannot QML trace cores :( [Current thread is 11 (Thread 0x7f1d0c7fd6c0 (LWP 6989))] Thread 24 (Thread 0x7f1d08ff66c0 (LWP 7005)): #0 __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 #1 0x7f1d6fea1fda in __internal_syscall_cancel (a1=, a2=, a3=, a4=, a5=a5@entry=0, a6=a6@entry=0, nr=232) at cancellation.c:49 #2 0x7f1d6fea2024 in __syscall_cancel (a1=, a2=, a3=, a4=, a5=a5@entry=0, a6=a6@entry=0, nr=232) at cancellation.c:75 #3 0x7f1d6ff29475 in epoll_wait (epfd=, events=, maxevents=, timeout=) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #4 0x7f1d0ec49a2a in ?? () from /usr/lib/spa-0.2/support/libspa-support.so #5 0x0001 in ?? () #6 0x in ?? () Thread 23 (Thread 0x7f1d097f76c0 (LWP 6995)): #0 __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 #1 0x7f1d6fea1fda in __internal_syscall_cancel (a1=, a2=, a3=, a4=, a5=a5@entry=8, a6=a6@entry=0, nr=271) at cancellation.c:49 #2 0x7f1d6fea2024 in __syscall_cancel (a1=, a2=, a3=, a4=, a5=a5@entry=8, a6=a6@entry=0, nr=271) at cancellation.c:75 #3 0x7f1d6ff1c5a6 in __GI_ppoll (fds=, nfds=, timeout=, sigmask=) at ../sysdeps/unix/sysv/linux/ppoll.c:42 #4 0x7f1d4832fa55 in ?? () from /usr/lib/libmpv.so.2 #5 0x000a in ?? () #6 0x in ?? () Thread 22 (Thread 0x7f1d0cffe6c0 (LWP 6988)): #0 __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 #1 0x7f1d6fea1fda in __internal_syscall_cancel (a1=, a2=, a3=, a4=, a5=a5@entry=0, a6=a6@entry=4294967295, nr=202) at cancellation.c:49 #2 0x7f1d6fea264c in __futex_abstimed_wait_common64 (private=0, futex_word=0x55ea63b9301c, expected=, op=, abstime=0x0, cancel=true) at futex-internal.c:57 #3 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55ea63b9301c, expected=, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #4 0x7f1d6fea26af in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55ea63b9301c, expected=, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #5 0x7f1d6fea4d1e in __pthread_cond_wait_common (cond=0x55ea63b92ff8, mutex=0x55ea63b92fd0, clockid=0, abstime=0x0) at pthread_cond_wait.c:426 #6 ___pthread_cond_wait (cond=0x55ea63b92ff8, mutex=0x55ea63b92fd0) at pthread_cond_wait.c:458 #7 0x7f1d48295351 in ?? () from /usr/lib/libmpv.so.2 #8 0x in ?? () Thread 21 (Thread 0x7f
[Breeze] [Bug 371068] yakuke / konsole with breeze color schema htop has some part unreadable
https://bugs.kde.org/show_bug.cgi?id=371068 Hugo Pereira Da Costa changed: What|Removed |Added Component|QStyle |general CC||hugo.pereira.da.costa@gmail ||.com Assignee|hugo.pereira.da.costa@gmail |plasma-de...@kde.org |.com| -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369627] [Frameworks] unexpected background color
https://bugs.kde.org/show_bug.cgi?id=369627 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #6 from Hugo Pereira Da Costa --- There are two issues reported here. The one in the description is definitely an "Okular" thing. The color used by the background is a mix between colors from the palette, which explains the behavior you describe. To double check, can you veryfy that you get the same colors when changing widget style ? okular -style plastique or okular -style fusion (depending on whether you use the kde4 or the kf5 version of okular) For the 'issues' reported in comment1, could you post a screenshot ? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371489] Breeze style elements are looking too big
https://bugs.kde.org/show_bug.cgi?id=371489 Hugo Pereira Da Costa changed: What|Removed |Added Severity|normal |wishlist CC||hugo.pereira.da.costa@gmail ||.com --- Comment #2 from Hugo Pereira Da Costa --- Hi, Thanks for reporting and sorry for the delay for answering. We are aware of the complain about breeze being too space consuming (although in general one does get use to it). There are plans to have a "compact" breeze mode. It just needs some time to implement. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369627] [Frameworks] unexpected background color
https://bugs.kde.org/show_bug.cgi?id=369627 Hugo Pereira Da Costa changed: What|Removed |Added Assignee|hugo.pereira.da.costa@gmail |okular-de...@kde.org |.com| Component|QStyle |general Product|Breeze |okular --- Comment #8 from Hugo Pereira Da Costa --- (In reply to rasq37 from comment #7) > Yes, the problem remains when using a different widget style. > > The issues I mentioned in comment 1 are shown in the screenshots I posted > earlier. Look at the top two color boxes on the right side of System > Settings main window. The border is the same color as the background in > Okular, dark in the first image and light in the second. Well if you are talking of the button 'outline', this is different, and intended. It is a mix and is a mix between the "button" and the "buttonText" color. This is to make it stick out. The fact that it resemble the okular background is probably just a coincidence. So bottomline: the issue with the okular background (about which this bug report originally is), and the fact that it is not using the "View" color, has nothing to do with breeze. Reassigning to Okular, and sorry for the back and forth. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369627] [Frameworks] unexpected background color
https://bugs.kde.org/show_bug.cgi?id=369627 --- Comment #10 from Hugo Pereira Da Costa --- I guess I misunderstood which colors you refer to. If we are talking about the 1 pixel outline that surrounds buttons, then this one does not change from one screenshot to the other and this is the intended behavior I am talking about If we are talking about the "shadow" around the color square, in the color buttons, then I have no idea how this one is calculated and this is again unrelated to breeze (and okular) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369627] [Frameworks] unexpected background color
https://bugs.kde.org/show_bug.cgi?id=369627 Hugo Pereira Da Costa changed: What|Removed |Added CC|hugo.pereira.da.costa@gmail | |.com| -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 372081] misinterpretation of system information
https://bugs.kde.org/show_bug.cgi?id=372081 --- Comment #7 from Hugo Pereira Da Costa --- (In reply to Christoph Feck from comment #4) > Adding Hugo for the KCapacityBar issue. > > The default rendering of KCapacityBar is visible on > https://api.kde.org/frameworks/kwidgetsaddons/html/classKCapacityBar.html > > "inline text" mode draws the text inside the bar > "outline text" mode draws the text below the bar > > KInfoCenter uses the "outline text" mode. > > KCapacityBar::minimumSizeHint() assumes this layout. > > With Fusion style (which does not customize the rendering), the text is > correctly drawn below the bar, and elided with trailing dots, if it does not > fit completely. > > With Breeze style, the text is rendered to the right of the bar, and the bar > and leading text characters vanish when it does not fit completely. > > Can KCapacityBar respect the different layout, in other words, is there some > QStyle::sizeFromContents() for this custom ControlElements implemented in > Breeze? Hello Christoph Thanks for adding me to the bug report. So, first, this is not really a bug, right ? i mean, all the information is displayed, provided there is enough space for it. More seriously, in the current kcapacity bar implementation, the drawTextMode you mention is only used when internal rendering is called, it is not known to the style at all. I guess one could pass it via a property on the widget, at the minimum. And then you are right, there is the minimumSizeHint. It basically works only if internal rendering is used. In principle the class should also call a style-implemented minimumSizeHint (some sizeFromContents with the right elements), in case of styled rendering. All in all there seems there is a need for some reworking of the kcapacitybar class if we want to really support sized rendering -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 370733] QtQuick Controls ComboBox popup rendering broken
https://bugs.kde.org/show_bug.cgi?id=370733 Hugo Pereira Da Costa changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/oxyg ||en/397f7baa2ea45033acfcd0a8 ||1c6afca690e07734 --- Comment #1 from Hugo Pereira Da Costa --- Git commit 397f7baa2ea45033acfcd0a81c6afca690e07734 by Hugo Pereira Da Costa. Committed on 07/11/2016 at 14:30. Pushed by hpereiradacosta into branch 'master'. Draw full rect in qtquick menu frames (as in, e.g. comboboxes) M +13 -0kstyle/oxygenstyle.cpp http://commits.kde.org/oxygen/397f7baa2ea45033acfcd0a81c6afca690e07734 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407989] Maximized windows can be resized on multi monitor setups
https://bugs.kde.org/show_bug.cgi?id=407989 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #12 from Hugo Pereira Da Costa --- for oxygen and breeze at least, this is probably due to the "extended window borders", the ability to resize windows from "outside" the window. It is enabled only when there is no border drawn. It is not disabled for maximized windows it seems. When you have only one monitor, this is not an issue because outside of the window for a maximized window means outside of the screen. This is not the case in multimonitor setup. I think it can be disabled inside the window decoration code itself. But should it not better be disabled upstream ? (in kdecoration or kwin) ? Hugo -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407989] Maximized windows can be resized on multi monitor setups
https://bugs.kde.org/show_bug.cgi?id=407989
--- Comment #13 from Hugo Pereira Da Costa ---
Patch for breeze:
diff --git a/kdecoration/breezedecoration.cpp
b/kdecoration/breezedecoration.cpp
index 10686506..d5526ce2 100644
--- a/kdecoration/breezedecoration.cpp
+++ b/kdecoration/breezedecoration.cpp
@@ -423,10 +423,10 @@ namespace Breeze
int extBottom = 0;
if( hasNoBorders() )
{
-extSides = extSize;
-extBottom = extSize;
+if( !isMaximizedHorizontally() ) extSides = extSize;
+if( !isMaximizedVertically() ) extBottom = extSize;
-} else if( hasNoSideBorders() ) {
+} else if( hasNoSideBorders() && !isMaximizedHorizontally() ) {
extSides = extSize;
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 407989] Maximized windows can be resized on multi monitor setups
https://bugs.kde.org/show_bug.cgi?id=407989 --- Comment #15 from Hugo Pereira Da Costa --- > > > Heh, it's more simpler than the one I proposed. Perhaps we need to unset > resize-only borders for shaded clients too, so there is no dead zone around > each shaded client. Interesting: right now, in breeze, if I set the window borders to no-sides or no-borders, in fact the extended sides do not apply to the decoration title (whether the window is shaded or not), and shaded windows cannot be resized at all. Not from the top or bottom, by construction, but also not on the sides, because there is no extended sides. So: I don't see a dead zone around shaded clients, but there is no way to resize them either. This is true whether or not you allow resizing maximized windows. Do you confirm ? Should this be considered a bug ? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407989] Maximized windows can be resized on multi monitor setups
https://bugs.kde.org/show_bug.cgi?id=407989 --- Comment #17 from Hugo Pereira Da Costa --- (In reply to Vlad Zagorodniy from comment #16) > Not exactly, you cannot resize shaded windows because kwin doesn't allow > that. Right ! confirmed. (I thought it was possible with non zero side borders, but indeed it is not, even in that case) > Perhaps kwin could reset the decoration input window for shaded > clients without relying on the decoration theme to update resize-only > borders accordingly... > > In either case, your patch is good to go. :-) ok. I'll push for both oxygen and breeze. Sorry if I missed some existing review requests on this: I don't automatically get the notificatiosn of those anymore after having stepped down from maintainership (and because of being annoyed by some people commenting excessively on those in the past). Hugo -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407989] Maximized windows can be resized on multi monitor setups
https://bugs.kde.org/show_bug.cgi?id=407989 --- Comment #18 from Hugo Pereira Da Costa --- Git commit c95b7652b7afbcc1bfc54f9185d2be4953acc119 by Hugo Pereira Da Costa. Committed on 03/06/2019 at 10:25. Pushed by hpereiradacosta into branch 'master-kde'. Disable extended resize borders for maximized windows M +3-3kdecoration/breezedecoration.cpp https://commits.kde.org/breeze/c95b7652b7afbcc1bfc54f9185d2be4953acc119 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407989] Maximized windows can be resized on multi monitor setups
https://bugs.kde.org/show_bug.cgi?id=407989 --- Comment #20 from Hugo Pereira Da Costa --- Git commit 72a70ceacc0434c04ddd795b5f2c093cba588b26 by Hugo Pereira Da Costa. Committed on 03/06/2019 at 10:38. Pushed by hpereiradacosta into branch 'master'. Disable extended resize borders for maximized windows M +3-3kdecoration/oxygendecoration.cpp https://commits.kde.org/oxygen/72a70ceacc0434c04ddd795b5f2c093cba588b26 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408845] Clicking on separator closes context menu
https://bugs.kde.org/show_bug.cgi?id=408845 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #1 from Hugo Pereira Da Costa --- This is a valid issue/concern, however this is not a breeze bug. Happens with any widget style. In fact, mouse event handling is not done (in general) by the style, but upstream, by Qt. Issue should be reported and possibly fixed there. In principle, this could also be addressed in the style itself, but that would only be a hack, that should then be duplicated to any widget style. Not the right way to go. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407833] Add option to use the icon theme's titlebar icons
https://bugs.kde.org/show_bug.cgi?id=407833 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 393238] Reduce shadow size/strength for background windows
https://bugs.kde.org/show_bug.cgi?id=393238 --- Comment #12 from Hugo Pereira Da Costa --- Just two cents on the different shadow strength. In principle no objection. However please note that (as in oxygen), the transition between active and inactive window is animated (you can see the animation in action if you increase the animation duration in the breeze config. from e.g. 15Omsec to 500). The shadow transition from strong to light between active and inactive should then be animated too, as is the glow in oxygen. Hopefully this will not be too resource consuming. If it turns out it is, I would be in favor of keeping the shadow size the same for the two states. Hugo -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 393238] Reduce shadow size/strength for background windows
https://bugs.kde.org/show_bug.cgi?id=393238 --- Comment #16 from Hugo Pereira Da Costa --- It is not so much a question of what one likes or not but of consistency. All transitions in breeze are animated, so this one should be too (for people who like smooth transition). Then, if you don't like them, you can disable them, just like you do now. Not having it upfront would be a consistency break (for breeze). -- You are receiving this mail because: You are watching all bug changes.
