[dolphin] [Bug 368582] New: Hover display effect makes the marked file name unreadable.
https://bugs.kde.org/show_bug.cgi?id=368582 Bug ID: 368582 Summary: Hover display effect makes the marked file name unreadable. Product: dolphin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: markus.elfr...@web.de Created attachment 101031 --> https://bugs.kde.org/attachment.cgi?id=101031&action=edit Excerpt from a screenshot showing a file display annoyance I am using the file management application "dolphin 16.08.0-1.2" also in sessions of the desktop environment "XFCE 4.12.1" for a while. I observe that a special display is generated when I move the mouse pointer over an entry in the file list. If this file name is already selected (or marked), the text becomes white and is obviously unreadable therefore in my graphic theme configuration. How are the chances to fix this strange software behaviour for the hover handling that I would usually expect? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 359449] New: Selected channel name is unreadable.
https://bugs.kde.org/show_bug.cgi?id=359449 Bug ID: 359449 Summary: Selected channel name is unreadable. Product: konversation Version: 1.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: markus.elfr...@web.de Created attachment 97238 --> https://bugs.kde.org/attachment.cgi?id=97238&action=edit Excerpt from a screenshot showing an unreadable channel selection I am running the program from the software package "konversation 1.6-17.19" within a session by the desktop environment "XFCE 4.12.1" for some days. If I switch entries in the left list widget, the marked channel name becomes unreadable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #20 from Markus Elfring --- (In reply to Martin Klapetek from comment #19) A better error message will help during the initialisation checks by the KDE software. Another way is also to improve the selection of a desired OpenGL implementation for the configuration of a X server like "Ephyr". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #18 from Markus Elfring --- (In reply to Martin Klapetek from comment #17) I am curious on how the next software improvement will look like. How do you think about to collaborate also with an approach like the GL Vendor-Neutral Dispatch library? https://github.com/NVIDIA/libglvnd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #16 from Markus Elfring --- (In reply to Martin Klapetek from comment #15) Should the software "plasma workspace 5.5.4" work better for the discussed implementation details than the version I am using usually so far? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #14 from Markus Elfring --- (In reply to Martin Klapetek from comment #13) Which functions are responsible for the determination of desired OpenGL support? Can they provide a more user-friendly error message (instead of the attached software "crash" report)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #12 from Markus Elfring --- (In reply to Martin Klapetek from comment #11) How much are corresponding feature detection functions involved? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #10 from Markus Elfring --- (In reply to Martin Klapetek from comment #9) How are the chances to improve OpenGL usability also around the Ephyr X server? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #8 from Markus Elfring --- (In reply to Martin Klapetek from comment #6) > Your OpenGL installation is possibly broken. Does the software situation look interesting if I try commands out like the following. elfring@Sonne:~> Xephyr -screen 1280x980 -host-cursor :1 & elfring@Sonne:~> DISPLAY=:1 dbus-launch /usr/bin/startkde & > Can you verify glxgears works for you? Xephyr KDE session: elfring@Sonne:~> glxinfo … Xlib: extension "GLX" missing on display ":1". Error: couldn't find RGB GLX visual or fbconfig … elfring@Sonne:~> glxgears Xlib: extension "GLX" missing on display ":1". Error: couldn't get an RGB, Double-buffered visual Can a software like Mesa provide appropriate OpenGL support in such a simple test environment (while my regular desktop session display is performed by a proprietary graphic driver)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #7 from Markus Elfring --- (In reply to Martin Klapetek from comment #6) > Your OpenGL installation is possibly broken. A command like "glxinfo" gives me an other impression. > Can you verify glxgears works for you? Yes. - This graphic application is working as expected at the moment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 Markus Elfring changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED --- Comment #3 from Markus Elfring --- (In reply to David Edmundson from comment #1) > QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) Can it be that OpenGL support can not be appropriately detected if anybody (like me) is trying a KDE desktop session out which should be displayed by the X server "Xephyr" from the software package "xorg-x11-server-extra 7.6_1.18.0-430.5"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 --- Comment #2 from Markus Elfring --- (In reply to David Edmundson from comment #1) > Your graphic drivers are missing It seems that this feedback does not really fit to my system configuration. The graphic driver is provided by the script "NVIDIA-Linux-x86_64-352.79.run" here since a few days. The reported error message can still be reproduced if I reactivate the desired OpenGL/GLX support once more. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358869] New: Fix error source for a start failure
https://bugs.kde.org/show_bug.cgi?id=358869 Bug ID: 358869 Summary: Fix error source for a start failure Product: plasmashell Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: markus.elfr...@web.de CC: bhus...@gmail.com, plasma-b...@kde.org Created attachment 96954 --> https://bugs.kde.org/attachment.cgi?id=96954&action=edit Function call trace for an abort of a program from the package "plasma5-workspace 5.5.3-2.1" I am curious when I can use a KDE 5 desktop session again on my openSUSE Tumbleweed system without the attached start failure. -- You are receiving this mail because: You are watching all bug changes.
