[konsole] [Bug 480196] FreeBSD: konsole: broken tabs/session title
https://bugs.kde.org/show_bug.cgi?id=480196 Ole changed: What|Removed |Added Summary|FreeBSD: broken |FreeBSD: konsole: broken |tabs/session title |tabs/session title -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480196] FreeBSD: broken tabs/session title
https://bugs.kde.org/show_bug.cgi?id=480196 Ole changed: What|Removed |Added Summary|broken tabs/session title |FreeBSD: broken ||tabs/session title -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480196] New: broken tabs/session title
https://bugs.kde.org/show_bug.cgi?id=480196 Bug ID: 480196 Summary: broken tabs/session title Classification: Applications Product: konsole Version: 24.01.90 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: olev...@ya.ru Target Milestone: --- Created attachment 165143 --> https://bugs.kde.org/attachment.cgi?id=165143&action=edit broken tabs title STEPS TO REPRODUCE 1. run 'konsole' 2. ssh XXX@remote host 3. add second tabs 4. keep doing some activity and after a while you may see garbage (see screenshot) instead of the normal title. OBSERVED RESULT 1) in a local session tabs I only see '/' , instead of the usual title ( my settins: Tab title format: %d : %n ) 2) in a remote session tabs I can see random garbage (buffer overflow ? ). I once saw this as a tab name: ``` '/ : ze Name[it]=Brezza N' ``` (it looks like part of i18n content? po/it/konsole.po:msgstr "Brezza" ) ( behavior does not depend on the user shell ( /bin/sh, /bin/csh )) Possibly a 'sysctl' processing/parsing problem in src/UnixProcessInfo.cpp ( UnixProcessInfo::getProcInfoStruct ) src/ProcessInfo.cpp ( readProcInfo ) ? EXPECTED RESULT Username/path/remote host info as a tabs title SOFTWARE/OS VERSIONS OS: FreeBSD 15.0-CURRENT KDE Plasma Version: 5.92.0 KDE Framework Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 15.0-CURRENT (64-bin) Graphics Platform: X11 ADDITIONAL INFORMATION Tabs settings: Tab title format: %d : %n Remote tab title format: (%u) %H konsole version: 24.01.90 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 477441] New: Hi, I are given an error report each time I start the application, and each time I try too update
https://bugs.kde.org/show_bug.cgi?id=477441 Bug ID: 477441 Summary: Hi, I are given an error report each time I start the application, and each time I try too update Classification: Applications Product: Discover Version: 5.27.8 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: oleaa...@gmail.com CC: aleix...@kde.org Target Milestone: --- This is the error report: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu mantic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: http://us.archive.ubuntu.com/ubuntu mantic InRelease is not (yet) available (The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C) W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.ubuntu.com/ubuntu mantic-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: http://security.ubuntu.com/ubuntu mantic-security InRelease is not (yet) available (The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C) W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu mantic-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: http://us.archive.ubuntu.com/ubuntu mantic-updates InRelease is not (yet) available (The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 463149] Pipewire loopback devices do not show up anymore in audio widget
https://bugs.kde.org/show_bug.cgi?id=463149 --- Comment #2 from Niels Ole Salscheider --- (In reply to Nicolas Fella from comment #1) > The applet has a "Show virtual devices" option that is off by default, > presumably if you enable that your devices will appear Thanks, that solves my issue! Maybe the option is a bit difficult to discover, but it does what I want. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 463149] New: Pipewire loopback devices do not show up anymore in audio widget
https://bugs.kde.org/show_bug.cgi?id=463149 Bug ID: 463149 Summary: Pipewire loopback devices do not show up anymore in audio widget Classification: Plasma Product: plasma-pa Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: niels_...@salscheider-online.de CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 154644 --> https://bugs.kde.org/attachment.cgi?id=154644&action=edit Config for virtual sinks SUMMARY I have split my sound card into two virtual ones using libpipewire-module-loopback. This way, I can move individual applications from my headphones to my speakers or the other way around. In the past I could see these loopback devices in the plasma-pa widget. But since a few releases they are gone and I can only see the "Audio Pro" devices. The audio settings in system settings still also list the loopback devices. I would like to get the loopback devices back to the plasma-pa widget in order to move applications around easily. STEPS TO REPRODUCE 1. You need to use pipewire as audio server 2. Copy the attached config to ~/.config/pipewire/pipewire.conf.d/ OBSERVED RESULT The loopback devices do not show up in the plasma-pa widget. EXPECTED RESULT The loopback devices should show up in the plasma-pa widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #10 from Niels Ole Salscheider --- (In reply to Niels Ole Salscheider from comment #8) > (In reply to Zamundaaa from comment #7) > > Did you check if the env var was applied correctly? You can check the > > actually used format in dmesg (it's printed on resolution changes iirc) or > > with drm_info (https://gitlab.freedesktop.org/emersion/drm_info). It'll be > > ARGB2101010 for 10bpc and ARGB for 8bpc > > I didn't check yet but I will check in the afternoon. The output of drm_info says that the environment variable is taken into account. The max bpc setting of the connectors changes to 8 and the FBs now have type ARGB. But unfortunately this does not help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #9 from Niels Ole Salscheider --- You can find the log here: https://stuff.salscheider.org/gpu.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #8 from Niels Ole Salscheider --- (In reply to Zamundaaa from comment #7) > Did you check if the env var was applied correctly? You can check the > actually used format in dmesg (it's printed on resolution changes iirc) or > with drm_info (https://gitlab.freedesktop.org/emersion/drm_info). It'll be > ARGB2101010 for 10bpc and ARGB for 8bpc I didn't check yet but I will check in the afternoon. > Also, does the output work with Xorg or Weston? I checked, it does not work with Xorg either. > > It seems strange though that kwin again and again removes the frame buffer > > after the atomic mode set and then tries to add a new frame buffer? > That's entirely normal. A new buffer gets added and presented, the old one > gets removed afterwards. Ah, ok. Dmesg didn't show anything else in the log buffer anymore, but it is there in the journal. I will upload a full log for enabling and disabling the projector (without the env var set). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #6 from Niels Ole Salscheider --- Created attachment 154466 --> https://bugs.kde.org/attachment.cgi?id=154466&action=edit Repeating part of dmesg with drm.debug=0x1ff -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #5 from Niels Ole Salscheider --- (In reply to Zamundaaa from comment #4) > > Dez 06 22:57:36 OleDesktop kwin_wayland_wrapper[1304]: Mesa: 5 similar > > errors > > Dez 06 22:57:36 OleDesktop kwin_wayland_wrapper[1304]: Mesa: User error: > > GL_INVALID_OPERATION in glGetFramebufferAttachmentParameteriv(invalid pname > > GL_FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING) > > That seems odd, even if it's probably unrelated. If you set the > KWIN_DRM_PREFER_COLOR_DEPTH=24 env var, does that make the display work at > 4k60? No, unfortunately it does not help. I thought this would be the cause because the projector reported 10bpc / yuv444, but now it still fails. I tried to get debug information with drm.debug=0x1ff (see attachment), - but I can't tell from it what's going on and if it is a driver bug. It seems strange though that kwin again and again removes the frame buffer after the atomic mode set and then tries to add a new frame buffer? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #3 from Niels Ole Salscheider --- > The display driver is supposed to (and in the case of amdgpu does) use chroma > subsampling and reduced bpc to make the given mode work. If it can't make it > work, it should reject attempts to use the output, so that the compositor can > react accordingly. Ok, then it might be a driver bug. I somehow assumed that user space would know about it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 --- Comment #2 from Niels Ole Salscheider --- Created attachment 154386 --> https://bugs.kde.org/attachment.cgi?id=154386&action=edit log of plasma kwin_wayland This is the requested log. I changed the refresh rate from 30 Hz to 60 Hz at 22:57 which resulted in a black screen. Unfortunately the output does not seem too helpful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462712] New: DRM: Allow to specify the output BPC
https://bugs.kde.org/show_bug.cgi?id=462712 Bug ID: 462712 Summary: DRM: Allow to specify the output BPC Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: niels_...@salscheider-online.de Target Milestone: --- SUMMARY *** I have a projector connected to my RX480 over HDMI which I use with kwin_wayland. When I connect the projector, kwin_wayland configures the output with the following settings: - 3840 x 2160 resolution - 60 Hz refresh rate - 10 bpc (instead of 8 bpc) - No chroma subsampling (YUV444 instead of YUV420) The HDMI port of the GPU supports HDMI 2.0b. I think the bandwidth of that output is enough to support any 3 of the 4 settings, but not all 4 at once. With the default settings the display stays just black (it works fine with another computer that has a newer GPU). If I reduce the resolution or the refresh rate the display lights up. I would however prefer to reduce the BPC of the connection since my input anyway only has 8 bpc. Please make this configurable. *** STEPS TO REPRODUCE 1. Connect a display that supports 4K, 60Hz, 10bpc to an HDMI 2.0b port. OBSERVED RESULT The default configuration results in a black screen, I can only change the resolution or refresh rate to fix it. EXPECTED RESULT The default configuration should work. The BPC of the output configuration should be adjustable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421173] Removal of e-mail attachments without removing entire e-mail
https://bugs.kde.org/show_bug.cgi?id=421173 Ole Reier Ulland changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Ole Reier Ulland --- I can see that this has been solved. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421172] Folder column width out of control
https://bugs.kde.org/show_bug.cgi?id=421172 Ole Reier Ulland changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Ole Reier Ulland --- After a new clean installation of Mageia linux, the bug is no more there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 397191] Some button labels are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=397191 Niels Ole Salscheider changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Niels Ole Salscheider --- This bug had been fixed in the meantime. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421173] New: Removal of e-mail attachments without removing entire e-mail
https://bugs.kde.org/show_bug.cgi?id=421173 Bug ID: 421173 Summary: Removal of e-mail attachments without removing entire e-mail Product: kmail2 Version: 5.11.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: ole.reier.ull...@gmail.com Target Milestone: --- SUMMARY A few years ago it was possible to remove an attached file from an e-mail without removing the entire e-mail. That is no longer possible. That is so extremely impractical to me that I have attempted to migrate to an other e-mail client, but I came up short. If you are not willing to fix this, that I find to be a major bug in KMail, please tell me of a way to migrate all my e-mails to an other e-mail client. # uname -a Linux HP-Compaq 5.5.9-desktop-1.mga7 #1 SMP Thu Mar 12 08:02:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux KDE Plasma Version: It should have been on top of the start menu. But I can not find that information anywhere I have thought of looking. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421172] New: Folder column width out of control
https://bugs.kde.org/show_bug.cgi?id=421172 Bug ID: 421172 Summary: Folder column width out of control Product: kmail2 Version: 5.11.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: ole.reier.ull...@gmail.com Target Milestone: --- SUMMARY In KMail on the left side, for e-mail folders, I have three columns, Name, Total and Size. Somehow the size column has become extremely wide, I am talking about many many display widths, I strongly suspect by ifself. The same happens sometimes when I start KMail to a smaller extent by itself in the right section also where the e-mails are. There I can just drag the column more narrow so it can be contained on the display. But for the left section that does not work. # uname -a Linux HP-Compaq 5.5.9-desktop-1.mga7 #1 SMP Thu Mar 12 08:02:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux KDE Plasma Version: It should have been on top of the start menu. But I can not find that information anywhere I have thought of looking. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 349512] Konsole and other KDE Apps Crash during KWindowSystemPrivateX11::viewportToDesktop
https://bugs.kde.org/show_bug.cgi?id=349512 Ole Langbehn changed: What|Removed |Added CC|ole.langb...@googlemail.com | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 397502] Problems install of Wine in KDE NEON Bionic
https://bugs.kde.org/show_bug.cgi?id=397502 Ole changed: What|Removed |Added CC||o...@gidderikke.no --- Comment #4 from Ole --- I found using aptitude easier to get wine-staging installed, I must admit it is a bit annoying that you must do this to make wine-staging work. Using wine-staging is way too common these days. Could maybe check for a snap package or something thoug. Install aptitude if it isn't already, then type: sudo aptitude install wine-staging Then skip to the solution where it want to downgrade the -one- package "libblkid1" - if you accidentally bypass it, just exit aptitude and start over. Install "wine-staging-compat" if wine-staging is your only Wine and you want it to be the default. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399032] New: kdevelop crashes when focusing a new tab and place the cursor in the text editor
https://bugs.kde.org/show_bug.cgi?id=399032 Bug ID: 399032 Summary: kdevelop crashes when focusing a new tab and place the cursor in the text editor Product: kdevelop Version: 5.2.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: o...@gidderikke.no Target Milestone: --- Application: kdevelop (5.2.4) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.4.0-136-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: This has happened several times and I can't find the root cause of this error. But occasionally when I select another tab and click on the line where I want to edit, it might suddenly crash. After reopening kdevelop, it seems to work quite fine rest of the session. Tried to reset all config files, which had no effect. I usually use UTF-8 encodings for my files, and tried different temp and save directories (like local and over NFS), so doesn't seem to be related to this either. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e45044940 (LWP 20179))] Thread 8 (Thread 0x7f0df0d49700 (LWP 20400)): #0 0x7f0e4171074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0e386a638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e386a649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e420280bb in QEventDispatcherGlib::processEvents (this=0x7f0de40032e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0e41fcf5ba in QEventLoop::exec (this=this@entry=0x7f0df0d48c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f0e41e045e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f0de200e255 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #7 0x7f0e41e0f727 in QThreadPrivate::start (arg=0x42ac7b0) at thread/qthread_unix.cpp:367 #8 0x7f0e3af6a6ba in start_thread (arg=0x7f0df0d49700) at pthread_create.c:333 #9 0x7f0e4171c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f0df25e9700 (LWP 20192)): #0 0x7f0e386a58c3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0e386a62bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e386a649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e420280bb in QEventDispatcherGlib::processEvents (this=0x7f0dec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0e41fcf5ba in QEventLoop::exec (this=this@entry=0x7f0df25e8c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f0e41e045e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f0e41e0f727 in QThreadPrivate::start (arg=0x276f8c0) at thread/qthread_unix.cpp:367 #7 0x7f0e3af6a6ba in start_thread (arg=0x7f0df25e9700) at pthread_create.c:333 #8 0x7f0e4171c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f0df91af700 (LWP 20185)): #0 0x7f0e4171074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0e386a638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e386a649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e420280bb in QEventDispatcherGlib::processEvents (this=0x7f0df40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0e41fcf5ba in QEventLoop::exec (this=this@entry=0x7f0df91aec70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f0e41e045e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f0e41e0f727 in QThreadPrivate::start (arg=0x7f0e2f2076b8) at thread/qthread_unix.cpp:367 #7 0x7f0e3af6a6ba in start_thread (arg=0x7f0df91af700) at pthread_create.c:333 #8 0x7f0e4171c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f0dfa06a700 (LWP 20184)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0e41a9291c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7f0e02c100ee in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f0e02c10209 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7f0e41a97c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7f0e3af6a6ba in start_thread (arg=0x7f0dfa06a700) at pthread_create.c:333 #6 0x7f0e4171
[frameworks-qqc2-desktop-style] [Bug 397191] New: Some button labels are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=397191 Bug ID: 397191 Summary: Some button labels are not displayed correctly Product: frameworks-qqc2-desktop-style Version: 5.48.0 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: niels_...@salscheider-online.de CC: k...@davidedmundson.co.uk Target Milestone: --- If I use qqc2-desktop-style with Qt Quick Components 2 then some button labels are not displayed correctly. For example "*" or emojis like "😀" as the complete label result in empty buttons. If I add a normal letter (e.g. "a😀") to the label then it is displayed correctly. With the fusion style everything works as expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 397191] Some button labels are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=397191 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 377038] Spectacle crashes when the option "Rectangular Region" is selected.
https://bugs.kde.org/show_bug.cgi?id=377038 Ole Christensen changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #8 from Ole Christensen --- Hmm, just tried to reproduce the issue again. Works... The only thing I just changed some minutes ago is the nVidia driver. I upgraded from 390.48 to 396.18. Sorry for the noise. Highly probable the nVidia stuff is the causer. Maybe Dylan could also give the latest driver a try. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 377038] Spectacle crashes when the option "Rectangular Region" is selected.
https://bugs.kde.org/show_bug.cgi?id=377038 Ole Christensen changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||ole.christen...@web.de Resolution|WORKSFORME |--- --- Comment #6 from Ole Christensen --- Same behavior here on Gentoo. It used to work until I upgraded from 17.08.3 to 17.12.3. Qt version is 5.9.4. Error message is: QGLXContext: Failed to create dummy context Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Aborted The X driver is the proprietary nVidia driver as well. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388482] New: Startup trouble
https://bugs.kde.org/show_bug.cgi?id=388482 Bug ID: 388482 Summary: Startup trouble Product: kmail2 Version: 5.4.3 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ole.reier.ull...@gmail.com Target Milestone: --- Application: kmail (5.4.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-desktop-1.mga6 i686 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I attempted to start KMail. Since Plasma is too heavy I run Cinnamon. It is a 32 bit computer without sse2 support. When I attempt to run KMail from a remote computer KMail crashes. When I run it locally the KMail window is just black. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/i686/libthread_db.so.1". [Current thread is 1 (Thread 0xa63fdb00 (LWP 7755))] Thread 21 (Thread 0x95688b40 (LWP 7804)): #0 0xb774ecd5 in __kernel_vsyscall () #1 0xb395960b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb5e122bd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libc.so.6 #3 0xad5b9cec in base::ConditionVariable::Wait() () from /lib/libQt5WebEngineCore.so.5 #4 0xad4d9641 in mojo::system::Waiter::Wait(unsigned long long, unsigned int*) () from /lib/libQt5WebEngineCore.so.5 #5 0xad4c42c8 in mojo::system::Core::WaitManyInternal(unsigned int const*, unsigned int const*, unsigned int, unsigned long long, unsigned int*, mojo::system::HandleSignalsState*) () from /lib/libQt5WebEngineCore.so.5 #6 0xad4c4488 in mojo::system::Core::WaitMany(mojo::system::UserPointer, mojo::system::UserPointer, unsigned int, unsigned long long, mojo::system::UserPointer, mojo::system::UserPointer) () from /lib/libQt5WebEngineCore.so.5 #7 0xad4c059b in MojoWaitMany () from /lib/libQt5WebEngineCore.so.5 #8 0xaeb8b0d7 in mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState const&, bool) () from /lib/libQt5WebEngineCore.so.5 #9 0xaeb8b30e in mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*, base::MessagePump::Delegate*) () from /lib/libQt5WebEngineCore.so.5 #10 0xaeb8b46e in mojo::common::MessagePumpMojo::Run(base::MessagePump::Delegate*) () from /lib/libQt5WebEngineCore.so.5 #11 0xad59756a in base::MessageLoop::RunHandler() () from /lib/libQt5WebEngineCore.so.5 #12 0xad5acedf in base::RunLoop::Run() () from /lib/libQt5WebEngineCore.so.5 #13 0xad597052 in base::MessageLoop::Run() () from /lib/libQt5WebEngineCore.so.5 #14 0xad5c5f12 in base::Thread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #15 0xad5c1efd in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/libQt5WebEngineCore.so.5 #16 0xb39544a5 in start_thread () from /lib/i686/libpthread.so.0 #17 0xb5e0481e in clone () from /lib/i686/libc.so.6 Thread 20 (Thread 0x967d3b40 (LWP 7802)): #0 0xb774ecd5 in __kernel_vsyscall () #1 0xb395960b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb5e122bd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libc.so.6 #3 0xad5b9cec in base::ConditionVariable::Wait() () from /lib/libQt5WebEngineCore.so.5 #4 0xad5c5248 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib/libQt5WebEngineCore.so.5 #5 0xad5c57d3 in base::SequencedWorkerPool::Worker::Run() () from /lib/libQt5WebEngineCore.so.5 #6 0xad5c59dd in base::SimpleThread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #7 0xad5c1efd in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/libQt5WebEngineCore.so.5 #8 0xb39544a5 in start_thread () from /lib/i686/libpthread.so.0 #9 0xb5e0481e in clone () from /lib/i686/libc.so.6 Thread 19 (Thread 0x95fd2b40 (LWP 7801)): #0 0xb774ecd5 in __kernel_vsyscall () #1 0xb395960b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb5e122bd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libc.so.6 #3 0xad5b9cec in base::ConditionVariable::Wait() () from /lib/libQt5WebEngineCore.so.5 #4 0xad5ba779 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib/libQt5WebEngineCore.so.5 #5 0xad5ba881 in base::WaitableEvent::Wait() () from /lib/libQt5WebEngineCore.so.5 #6 0xad59acfe in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /lib/libQt5WebEngineCore.so.5 #7 0xad59756a in base::MessageLoop::RunHandler() () from /lib/libQt5WebEngineCore.so.5 #8 0xad5acedf in base::RunLoop::Run() () from /lib/libQt5WebEngineCore.so.5 #9 0xad597052 in base::MessageLoop::Run() () from /lib/libQt5WebEngineCore.so.5 #10 0xad5c5f12 in base::Thread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #11 0xad5c1efd in base::(anonymous
[plasmashell] [Bug 388029] New: Checking "Show week numbers in Calander" made Plasma crash
https://bugs.kde.org/show_bug.cgi?id=388029 Bug ID: 388029 Summary: Checking "Show week numbers in Calander" made Plasma crash Product: plasmashell Version: 5.8.7 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ole.reier.ull...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.7) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: I checked "Show week numbers in Calander" pushed "Apply" then Plasma crashed. I am running Mageia 6. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5aab227800 (LWP 18054))] Thread 14 (Thread 0x7f59b2015700 (LWP 18769)): #0 0x7f5aa287261a in g_main_context_check () from /lib64/libglib-2.0.so.0 #1 0x7f5aa2872c38 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f5aa2872d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f5aa6214e2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5aa61c049a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5aa5ffa3bc in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f5aa5ffeff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f5aa510866d in start_thread () from /lib64/libpthread.so.0 #8 0x7f5aa5917e4d in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f59a51b4700 (LWP 18758)): #0 0x7f5aa510dc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5aa5fffdfb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f5aa927eb1d in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f5aa927f395 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7f5aa5ffeff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5aa510866d in start_thread () from /lib64/libpthread.so.0 #6 0x7f5aa5917e4d in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f59a27a2700 (LWP 18757)): #0 0x7f5aa5ff748a in QMutex::lock() () from /lib64/libQt5Core.so.5 #1 0x7f5aa62145f9 in postEventSourceCheck(_GSource*) () from /lib64/libQt5Core.so.5 #2 0x7f5aa28726d1 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f5aa2872c38 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f5aa2872d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f5aa6214e2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5aa61c049a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f5aa5ffa3bc in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f5aa888b205 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f5aa5ffeff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f5aa510866d in start_thread () from /lib64/libpthread.so.0 #11 0x7f5aa5917e4d in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f59a1fa1700 (LWP 18726)): #0 0x7f5aa510dc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5aa5fffdfb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f5aa927eb1d in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f5aa927f395 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7f5aa5ffeff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5aa510866d in start_thread () from /lib64/libpthread.so.0 #6 0x7f5aa5917e4d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f59dc440700 (LWP 18665)): #0 0x7f5aa510dc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5aa5fffdfb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f5aa927eb1d in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f5aa927f395 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7f5aa5ffeff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5aa510866d in start_thread () from /lib64/libpthread.so.0 #6 0x7f5aa5917e4d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f59dbc3f700 (LWP 18560)): #0 0x7f5aa510dc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5aa5fffdfb in QWaitCondition::wait(QMutex*, unsign
[kmail2] [Bug 380179] Regression kMail 5.5.1: Moving messages (DnD) does not work reliably any more
https://bugs.kde.org/show_bug.cgi?id=380179 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380182] deleting a message thread doesn't remove it from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #28 from Niels Ole Salscheider --- > * EffectWatcher constructor for "_KDE_NET_WM_BACKGROUND_CONTRAST_REGION" > atom is often !isNull() Does "often" mean that you observed it to be Null sometimes? Because often is not always... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 366032] plasma-pa should allow to select the sink for volume control
https://bugs.kde.org/show_bug.cgi?id=366032 --- Comment #1 from Niels Ole Salscheider --- Or maybe it would be enough to recursively query the master sink starting from the default sink and then adjust the volume of the sink you end up with eventually. That would fix my use-case at least but I do not know about others... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 366032] New: plasma-pa should allow to select the sink for volume control
https://bugs.kde.org/show_bug.cgi?id=366032 Bug ID: 366032 Summary: plasma-pa should allow to select the sink for volume control Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: niels_...@salscheider-online.de CC: plasma-b...@kde.org Currently, plasma-pa just sets the volume of the default sink when the volume keys on the keyboard are pressed. This is not necessarily what the user wants if he has a bit more complex setup. It would therefore be good if the sink for the volume control could be configured in plasma-pa's KCM. For example, I have this in my default.pa: load-module module-remap-sink sink_name=headphones channels=2 master_channel_map=front-left,front-right channel_map=front-left,front-right remix=0 sink_properties=device.description=Headphones load-module module-virtual-surround-sink sink_name=vsurround master=headphones hrir=/home/olesalscheider/.ir.wav sink_properties=device.description=VirtualSurround set-default-sink vsurround This splits two channels of the sound card and creates a "headphone" sink from them. The other channels could for example be connected to a surround sound system but I do not use them currently. Then it creates another sink (vsurround) with the "headphone" sink as master. This sink computes virtual surround sound from its input signals and passes the generated signal to the master. I have set "vsurround" as my default sink because I want all new streams to go there by default. But I have moved some manually to "headphones" where I do not want the virtual surround effect (e. g. for music). When I now press the volume keys I want them not to change the volume of the "vsurround" sink but the volume of the master sink. Because otherwise the volume of the streams that I moved to "headphones" is not changed. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 349512] Konsole and other KDE Apps Crash during KWindowSystemPrivateX11::viewportToDesktop
https://bugs.kde.org/show_bug.cgi?id=349512 --- Comment #9 from Ole Langbehn --- I am still able to reproduce this issue. It actually breaks my workflow, so I am heavily interested in getting this fixed. If I can help, please tell me how. I have full debugging symbols on my box. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362257] spectacle.khotkeys: The specified file is empty or not a configuration file
https://bugs.kde.org/show_bug.cgi?id=362257 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de --- Comment #11 from Niels Ole Salscheider --- I can confirm that this is in fact a bug! The source code of libkhotkeysprivate (Settings::isConfigFileValid to be precisely) clearly states that only version 2 is supported. Therefore, spectacle.khotkeys should be adjusted accordingly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #3 from Niels Ole Salscheider --- Created attachment 98784 --> https://bugs.kde.org/attachment.cgi?id=98784&action=edit Plasma after being restarted (with transparency) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #2 from Niels Ole Salscheider --- Created attachment 98783 --> https://bugs.kde.org/attachment.cgi?id=98783&action=edit Plasma right after login (no transparency) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] New: Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 Bug ID: 362531 Summary: Plasma panels are not transparent after login Product: plasmashell Version: 5.6.3 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: niels_...@salscheider-online.de When plasmashell starts after logging in, the panels are not transparent. Restarting plasmashell fixes this. I think this might be because of a race condition with kwin: plasmashell will only enable the background contrast if the _KDE_NET_WM_BACKGROUND_CONTRAST_REGION atom is registered. But this only happens when kwin loads the backgroundcontrast plugin which seems to happen too late for me. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 362142] New: The session does not finish cleanly / startkde exits too early?
https://bugs.kde.org/show_bug.cgi?id=362142 Bug ID: 362142 Summary: The session does not finish cleanly / startkde exits too early? Product: frameworks-kinit Version: 5.20.0 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: niels_...@salscheider-online.de CC: kdelibs-b...@kde.org When I try to log out or power down my computer, the current kde session stays in the closing state. In this case, loginctl session-status prints something similar to this: - olesalscheider (1000) Since: Sat 2016-04-23 15:56:16 CEST; 8min ago Leader: 1121 Seat: seat0; vc1 Display: :0 Service: sddm; type x11; class user Desktop: KDE State: closing Unit: session-1.scope �~T~\�~T~@1292 /usr/x86_64-pc-linux-gnu/bin/pulseaudio --start --log-target=syslog �~T~\�~T~@1494 gpg-agent --homedir /home/olesalscheider/.gnupg --use-standard-socket --daemon �~T~\�~T~@1616 kdeinit4: kio_http_cache_cleaner [kdeinit] �~T~T�~T~@1827 /usr/x86_64-pc-linux-gnu/libexec/kf5/kio_http_cache_cleaner Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kactivitymanagerd[1231]: The X11 connection broke (error 1). Did the X11 server die? Apr 23 16:02:51 OleDesktop kdeinit5[1191]: The X11 connection broke: I/O error (code 1) Apr 23 16:02:52 OleDesktop drkonqi[2550]: QXcbConnection: Could not connect to display :0 Apr 23 16:02:52 OleDesktop kdeinit5[2555]: QXcbConnection: Could not connect to display :0 It seems that the problem is that the X server is terminated before kdeinit5 finishes and before it can terminate all children. But AFAIK the X server should only be terminated once startkde finishes and that can only happen when the kdeinit5_shutdown wrapper for kdeinit returns. Therefore it seems likely that the bug is either in kdeinit or the wrapper. The session can be cleanly terminated by running "loginctl terminate-session". Reproducible: Always Steps to Reproduce: 1. Log out 2. Run loginctl list-sessions / loginctl session-status Actual Results: Session stays in closing state Expected Results: Session finishes cleanly -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360967] The breeze-plymouth theme contains subdirectories
https://bugs.kde.org/show_bug.cgi?id=360967 --- Comment #2 from Niels Ole Salscheider --- plymouth-populate-initrd is part of plymouth, though, and is only used by dracut. This means it is either a plymouth bug or that it was an intentional decision by the plymouth developers... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360967] New: The breeze-plymouth theme contains subdirectories
https://bugs.kde.org/show_bug.cgi?id=360967 Bug ID: 360967 Summary: The breeze-plymouth theme contains subdirectories Product: Breeze Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: niels_...@salscheider-online.de The breeze-plymouth theme does not have a flat structure but contains sub-directories for the images. The plymouth-populate-initrd does not support this so that the images do not end up in the initramfs when using dracut. This obviously breaks the theme. However, I'm not sure if plymouth themes must not contain sub-directories or it this is a bug in plymouth. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 --- Comment #7 from Niels Ole Salscheider --- Please ignore what I said. The real problem is that the window is not visible because of setFixedSize(minimumSize()); where minimumSize() returns (0, 0). -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105
Niels Ole Salscheider changed:
What|Removed |Added
CC||niels_ole@salscheider-onlin
||e.de
--- Comment #6 from Niels Ole Salscheider ---
It seems that kcalc polls on a socket in "/tmp/.ICE-unix/". The relevant output
from strace is:
[...]
socket(PF_LOCAL, SOCK_STREAM, 0)= 6
getsockopt(6, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
uname({sysname="Linux", nodename="OleDesktop", ...}) = 0
connect(6, {sa_family=AF_LOCAL, sun_path=@"/tmp/.ICE-unix/1317"}, 22) = 0
fcntl(6, F_SETFD, FD_CLOEXEC) = 0
[...]
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
And then the last two lines are repeated.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #27 from Niels Ole Salscheider --- Yes, this would be sufficient. For mesa at least, since it queries the environment variable in eglGetDisplay. We already use EGL_PLATFORM for the hwcomposer backend and the wayland QPA, so it should be fine to also use it here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #24 from Niels Ole Salscheider --- (In reply to Thomas Lübking from comment #23) > The relevant code (initEGL()) is in platform agnostic in libkwineffects - > we'd either have to transfer it into the platform implementations to make us > of eglGetPlatformDisplayEXT (or pass it down alongside the EGL_EXT_platform* > tests incl. an explicit query for client extensions on EGL_NO_DISPLAY) Yes, that's why I haven't proposed a patch yet... > => Simply setting EGL_PLATFORM avoids the crash? The crash is already avoided by the patch I sent to mesa-dev. But simply setting EGL_PLATFORM makes mesa choose another platform that uses render nodes instead of /dev/dri/card0 so that I do not see "radeon: Failed to get PCI ID, error number -13" anymore. Also, it would avoid the crash even when my patch was not applied to mesa. EGL_PLATFORM was a workaround by mesa for this problem when eglGetPlatformDisplayEXT was not yet around. It still works but I think that the latter is the cleaner solution. > I'm however not sure whether that's a general solution to the problem (see > eglinfo situation) I'm afraid that there is not really a general solution, because unfortunately eglGetDisplay made it into the standard in its current form without considering that there might be drivers with multiple platforms. Applications should probably use glGetPlatformDisplayEXT when possible. And for all that don't, distributions should set a sane default backend that will hopefully not fail (surfaceless?). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #22 from Niels Ole Salscheider --- Or even better, use eglGetPlatformDisplayEXT to get a display for the right platform (if available). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #21 from Niels Ole Salscheider --- Maybe KWin should set EGL_PLATFORM to x11 or wayland, depending on where it runs. This is at least what other compositors do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #20 from Niels Ole Salscheider --- No, the current code tries all EGL drivers (which is only drm), but it only tries one platform for each driver. This platform is either what is set by the EGL_PLATFORM env var or if that is empty what was the first passed to the configure script in --with-egl-platforms. In my case this was drm and I was not aware that the order matters. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #18 from Niels Ole Salscheider --- > The code in question looks like it unconditionally tries /dev/dri/renderD0, > that one's likely occupied and in return it resorts to card0 > > What *should* (probably, I'm no expert) happen is to try all available > render nodes (ie. loop from 0-128?) until one available is found?! The current code just tries to open /dev/dri/card0 twice (on Linux), because "int n = snprintf(buf, sizeof(buf), DRM_DEV_NAME, DRM_DIR_NAME, 0);" just copies that string into buf. So it does not use render nodes at all. Of course, the path of the render node could be calculated in a similar way - the hardcoded path was mostly just to see if it works. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #16 from Niels Ole Salscheider --- Created attachment 96909 --> https://bugs.kde.org/attachment.cgi?id=96909&action=edit Mesa patch to prefer rendernodes Ok, I get significantly more output and no error with the attached patch. But I am not sure if this is the right thing to do or if it is supposed to work with /dev/dri/card0... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #15 from Niels Ole Salscheider --- The output seems to be missing? I wonder if the problem has something to do with rendernodes. The platform code opens /dev/dri/card0 when no display is supplied but the pipe-loader code seems to open a render node (/dev/dri/renderD*). The RADEON_INFO ioctl that fails has DRM_AUTH|DRM_RENDER_ALLOW as access restrictions. This means that the ioctl can be called from render nodes, but I am not completely sure what DRM_AUTH implies and if that can cause it to fail when using /dev/dri/card0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #13 from Niels Ole Salscheider --- It seems so, this is the output I get: radeon: Failed to get PCI ID, error number -13 EGL API version: 1.4 EGL vendor string: Mesa Project EGL version string: 1.4 (DRI2) EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 EGL extensions string: EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_create_context EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context EGL_MESA_configless_context EGL_MESA_image_dma_buf_export EGL client extensions string: EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_wayland EGL_EXT_platform_x11 EGL_KHR_client_get_all_proc_addresses EGL_MESA_platform_gbm Configurations: bf lv colorbuffer dp st msvis cav bi renderable supported id sz l r g b a th cl ns bid eat nd gl es es2 vg surfaces - 0x01 32 0 8 8 8 8 0 0 0 0 0x34325241-- y y y win 0x07 32 0 8 8 8 8 16 0 0 0 0x34325241-- y y y win 0x0d 32 0 8 8 8 8 24 0 0 0 0x34325241-- y y y win 0x13 32 0 8 8 8 8 24 8 0 0 0x34325241-- y y y win 0x19 32 0 8 8 8 8 32 0 0 0 0x34325241-- y y y win 0x1f 24 0 8 8 8 0 0 0 0 0 0x34325258-- y y y win 0x25 24 0 8 8 8 0 16 0 0 0 0x34325258-- y y y win 0x2b 24 0 8 8 8 0 24 0 0 0 0x34325258-- y y y win 0x31 24 0 8 8 8 0 24 8 0 0 0x34325258-- y y y win 0x37 24 0 8 8 8 0 32 0 0 0 0x34325258-- y y y win 0x79 16 0 5 6 5 0 0 0 0 0 0x36314752-- y y y win 0x7f 16 0 5 6 5 0 16 0 0 0 0x36314752-- y y y win 0x85 16 0 5 6 5 0 24 0 0 0 0x36314752-- y y y win 0x8b 16 0 5 6 5 0 24 8 0 0 0x36314752-- y y y win 0x91 16 0 5 6 5 0 32 0 0 0 0x36314752-- y y y win I'm not sure if it is ok to fail or not. I will have to look into it a bit more... Just for reference, a link to the patch: http://lists.freedesktop.org/archives/mesa-dev/2016-January/106102.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #11 from Niels Ole Salscheider --- Thank you for your patience. I have sent a patch to mesa-dev that fixes the crash. I still see "radeon: Failed to get PCI ID, error number -13" (both with KWin and eglinfo) but apart from that, both seem to work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #10 from Niels Ole Salscheider --- It segfaults in the same function. So it really seems to be a driver issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #8 from Niels Ole Salscheider --- I have only tried with mesa master. I can also compile the latest stable version but this will take a bit since I will have to downgrade llvm, clang and maybe some other first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 Niels Ole Salscheider changed: What|Removed |Added Attachment #96907|0 |1 is obsolete|| --- Comment #6 from Niels Ole Salscheider --- Created attachment 96908 --> https://bugs.kde.org/attachment.cgi?id=96908&action=edit Backtrace with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #4 from Niels Ole Salscheider --- Created attachment 96907 --> https://bugs.kde.org/attachment.cgi?id=96907&action=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #5 from Niels Ole Salscheider --- (In reply to Thomas Lübking from comment #3) > From the mesa troubleshooting guide: > > If see this error message: radeon: Failed to get PCI ID, error number -13, > make sure you have permissions to access the device (usually > /dev/dri/card0), and get the latest version of mesa from git. Prior to this > commit: 044de40cb0c6af54d99252f55145972780362afa, you would have seen this > error message when running compute programs and X at the same time. Yes, I know. It's not a permission problem though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de --- Comment #1 from Niels Ole Salscheider --- Created attachment 96906 --> https://bugs.kde.org/attachment.cgi?id=96906&action=edit Output of "qdbus org.kde.KWin /KWin supportInformation" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] New: KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 Bug ID: 358750 Summary: KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755 Product: kwin Version: 5.5.4 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: niels_...@salscheider-online.de Since commit e641022bf9482a11209577b5654cd43231be0755, KWin crashes during startup when compositing is enabled. The crash is caused by the addition of if (dpy == EGL_NO_DISPLAY) dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY); in libkwineffects/kwinglutils.cpp. When reverting the commit or removing these two lines, everything works fine again. Right before the crash, I see "radeon: Failed to get PCI ID, error number -13" which comes from mesa (more precisely from do_winsys_init in src/gallium/winsys/radeon/drm/radeon_drm_winsys.c when RADEON_INFO_DEVICE_ID is queried). Reproducible: Always Steps to Reproduce: 1. Start KWin with compositing enabled -- You are receiving this mail because: You are watching all bug changes.
