[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.
https://bugs.kde.org/show_bug.cgi?id=356899 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #16 from Heiko Tietze --- Still an issue under 5.8 Environment: Notebook with external display, one with folder view the other desktop. Background image (happens always) and layout (desktop/wallpaper configuration) is lost after restart. Happens when I wait until final shutdown; but since this takes some seconds my expectation is to have a reliable setup also when I close the lid after clicking shutdown. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369037] Gradient at LibreOffice toolbar
https://bugs.kde.org/show_bug.cgi?id=369037 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #3 from Heiko Tietze --- The issue has been fixed. It will be available in 5.3 as well the nightly builds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368772] Can't access the plasmoids' context menu
https://bugs.kde.org/show_bug.cgi?id=368772 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #1 from Heiko Tietze --- Isn't the long press the only means on desktop environment? Why shouldn't it work on touch screens. (+bug -usability imho) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368459] Group menu steals focus, cannot hide window
https://bugs.kde.org/show_bug.cgi?id=368459 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #3 from Heiko Tietze --- The context menu for grouped objects should affect all items. But I agree with Christoph that we should keep the focus where it is. Microsoft Windows shows a menu on left click where the active window is highlighted (focus goes from the window itself to this menu entry). When the user right clicks a menu item the respective window comes into foreground and the common window menu pops up with the option to minimize etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360289] open new task with right click on empty space
https://bugs.kde.org/show_bug.cgi?id=360289 --- Comment #6 from Heiko Tietze --- (In reply to Kai Uwe Broulik from comment #5) > "Run Command" *is* KRunner. And the default short-cut is Alt+F2. While users may deduct the functionality we should have the same label on all places (either KRunner or Run Command). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360289] open new task with right click on empty space
https://bugs.kde.org/show_bug.cgi?id=360289 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #4 from Heiko Tietze --- >From our HIG [1]: "A context menu is a list of functions or options (respectively menu items) available to users in the current context... Provide a context menu for inherent functions... Use context menus for well known functions only... Do not use context menus as the only way..." The context of Plasma is _global_ so all well known functions of Plasma should be replicated within the context menu. And "KRunner [Alt+F2]" is such a function, but not "Run command [Shift+Space]". The question is whether the task manager is seen as a program with own context (I agree with Thomas that this is true), and should then provide different functions. Having a context menu improves accessibility and allows the user to explore functionality. Observe yourself: you will most likely read the context menu in new applications and check what's available there (beyond the copy/paste stuff). Putting all together I would rather refuse the idea. [1] https://community.kde.org/KDE_Visual_Design_Group/HIG/ContextMenu -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353029] Shuting down the system with notebook lid closed changes KScreen settings to not enabled
https://bugs.kde.org/show_bug.cgi?id=353029 --- Comment #6 from Heiko Tietze --- (In reply to Sebastian Kügler from comment #5) > Aand fixed. Thanks for helping to identify the problem! Best comment ever. Thanks for all your work! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Heiko Tietze changed: What|Removed |Added CC|tietze.he...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365346] Screen configuration never restored on startup
https://bugs.kde.org/show_bug.cgi?id=365346 --- Comment #7 from Heiko Tietze --- (In reply to Peter Mattern from comment #6) > Maybe the OP will drop another note. Neither arrangement nor resolution was restored well. Plasma adds the trouble with panels, while LXQt is even worse with background not fitting the original setup. Meanwhile I found a workaround, namely to configure the montor file in /etc/X11/xorg.onf/ properly. There are too many issues to track it down, IMHO. There are enough other bugs open. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365346] Screen configuration never restored on startup
https://bugs.kde.org/show_bug.cgi?id=365346 --- Comment #1 from Heiko Tietze --- Same issue when running LXQt https://github.com/lxde/lxqt/issues/1096#issuecomment-233173103 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365749] Kscreen Display Configuration Advanced Settings
https://bugs.kde.org/show_bug.cgi?id=365749 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #1 from Heiko Tietze --- There are data from a survey that support this request: http://user-prompt.com/kscreen-results-of-the-user-survey/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365659] Icons-only task manager isn't refreshed
https://bugs.kde.org/show_bug.cgi?id=365659 --- Comment #2 from Heiko Tietze --- (In reply to Eike Hein from comment #1) > There have been various changes since 5.7.1 that fix things in Icontasks. > Are you able to test the 5.7 branches of plasma-desktop or plasma-workspace? It's a productive system, well more or less since I still run KDE (scnr). I will install what Arch offers - and try to observe if the issue persists. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365657] Spactacle's selection mode works unreliable
https://bugs.kde.org/show_bug.cgi?id=365657 --- Comment #2 from Heiko Tietze --- Created attachment 100093 --> https://bugs.kde.org/attachment.cgi?id=100093&action=edit Screenshot of current screen Full screen related to the screenshot with 'window under cursor'. My system has a second screen, kwin reports 700,300/1217,754 (x,y topleft and bottomright) on moving this dialog. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365657] Spactacle's selection mode works unreliable
https://bugs.kde.org/show_bug.cgi?id=365657 --- Comment #1 from Heiko Tietze --- Created attachment 100092 --> https://bugs.kde.org/attachment.cgi?id=100092&action=edit Result from taking a screenshot Result from taking a screenshot for 'window under the cursor', clicking the compress image dialog in the middle of the screen (next attachment shows the full screen). Obviously, spectacle creates the screenshot at 0,0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365659] New: Icons-only task manager isn't refreshed
https://bugs.kde.org/show_bug.cgi?id=365659 Bug ID: 365659 Summary: Icons-only task manager isn't refreshed Product: plasmashell Version: 5.7.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: tietze.he...@gmail.com CC: plasma-b...@kde.org The icon-only taskmanager does sometimes not show new apps or updates existing. Hard to track down in what situation this happens. But reliable it keeps the last icon active when all programs are closed. In all unclear situations it helps when I change the panel height and thereby it is refreshed. Reproducible: Always plasmashell 5.7.1 Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 365657] New: Spactacle's selection mode works unreliable
https://bugs.kde.org/show_bug.cgi?id=365657 Bug ID: 365657 Summary: Spactacle's selection mode works unreliable Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: tietze.he...@gmail.com Rectangular Region, Delay 2s (or 1s or on click): It happens often (>80% of my trys) that my screen remains bright, only the cursor changes into the crosshair (or whatever) shape. There is no visual feedback for the selection, moving the mouse over the area changes the cursor into NW/SW etc. meaning I could extend the selection, if it would be visual. I can end the procedure with enter (not double click!) and get what I want, but without visual feedback it's hard to define precise rectangles. Sometimes it also happens that Window Under Cursor and Active Screen result in some weird rectangle, at least not the window I see. But this issue is not easy to reproduce. Reproducible: Always Arch Linux Spectacle: v16.04.3 KDE: 5.23.0 Qt: 5.7 (Thanks for making the version info not selectable. Who needs to copy/paste when typing in the numbers is also possible.) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365346] New: Screen configuration never restored on startup
https://bugs.kde.org/show_bug.cgi?id=365346 Bug ID: 365346 Summary: Screen configuration never restored on startup Product: KScreen Version: 5.7.0 Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: kded Assignee: se...@kde.org Reporter: tietze.he...@gmail.com With the latest update to 5.7 I have to reconfigure my screens after every start. It's a laptop (MSI GE40 2OC) right of a full hd screen (ASUS VX238H) connected via HDMI. Both have panels on top and bottom. Before 5.7 I had issues when the lid is closed and the system was shutdown. Now it always happens that all panels are overlaid on the Full HD screen, which I set-up as primary. I have placed some widgets on the secondary screen and use different wallpapers. It's not easy to get back to this arrangement, switching primary/secondary on/off, closing the lid, and doing this back and forth ends up eventually in what I defined, but not always. There is no error message. I tried to disable KScreen but with no success: same problems (didn't do much investigations though). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363959] New: Always the same identiy is chosen
https://bugs.kde.org/show_bug.cgi?id=363959 Bug ID: 363959 Summary: Always the same identiy is chosen Product: kmail2 Version: unspecified Platform: Other URL: https://forum.kde.org/viewtopic.php?f=215&t=133244 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: tietze.he...@gmail.com My setup contains of a (default) IMAP and a POP3 account. Both are associated with separate identities. When I set the IMAP account as the default I'm not able to compose a new message for the POP3 account. Switching the default allows to compose messages based on the account that is currently being selected. KMail 5.2.1, Arch Linux Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363210] desktop right click show Activities (when you only have one activity)
https://bugs.kde.org/show_bug.cgi?id=363210 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #3 from Heiko Tietze --- https://techbase.kde.org/Projects/Usability/HIG/ContextMenu * Disable menu items that don't apply to the current context, instead of removing them. * Hide menu items completely if they are permanently unavailable on the user's system (e.g. due to missing hardware capabilities or missing optional dependencies). The background of these guidelines is that users aren't aware of hidden features. It may be clear for expert users, but novices who never heard about a function and don't see how to interact with it will not become familiar with the underlying concept. So -1 from my side as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362970] System tray refreshes not reliable
https://bugs.kde.org/show_bug.cgi?id=362970 --- Comment #2 from Heiko Tietze --- Both, KTelepathy and KMail? Sometimes it works, sometimes not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362970] New: System tray refreshes not reliable
https://bugs.kde.org/show_bug.cgi?id=362970 Bug ID: 362970 Summary: System tray refreshes not reliable Product: plasmashell Version: 5.6.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: tietze.he...@gmail.com I have two panels placed on my desktop, and use the upper to show notifications. The issue is annoying for KMail where the icon remains with a number after all messages are read. But as well the KTelepathy keeps its initial icon with the throbber until a refreh is pushed from somewhere else, e.g. me by changing the height. As far as I remember it was a regression from 5.6.2, but not sure. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353029] Shuting down the system with notebook lid closed changes KScreen settings to not enabled
https://bugs.kde.org/show_bug.cgi?id=353029 --- Comment #2 from Heiko Tietze --- Mostly it does. Me have to wait until the system is fully shut down until the lid can be closed safely. Playing with the lid is very error-prone in respect to Plasma in general. I have control bars on bottom and top of the desktop at both screens. On the notebook there are also some plasmoids showing the system state (i.e. load, hard disc, network). It happens often that the control bars are placed on the first screen after lid close. The plasmoids never move. Sometimes screens are reversed, left/right. So from what you say, moving config files around, which sounds weird, I'd confirm your diagnosis. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 358957] laptop won't hybrid-suspend when Plasma is running
https://bugs.kde.org/show_bug.cgi?id=358957 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #7 from Heiko Tietze --- My first thought was to agree with the checkbox. But actually it's an intermediate method suspending to both RAM and disk. If you could place the checkbox at either hibernate or suspend it makes no sense. By the way: I like the description in the Arch wiki with "Suspend to RAM/disk/both". From the usability POV even a third option (aka radio button) is not a good solution. Strictly speaking it's not an exclusive setting. "Both" implies rather to have checkboxes for RAM (or hibernate) and disk (aka suspend, I may have mixed the terms), and checking both means hybrid-suspense. If I understand the underlying functionality right it works exactly in this way: you have the current state in both RAM and on disk allowing to wake-up quickly from RAM with the safety of a backup on disk when you run of of battery. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357210] Red close icon does not work on colored backgrounds
https://bugs.kde.org/show_bug.cgi?id=357210 Heiko Tietze changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Heiko Tietze --- Likely fixed, see https://git.reviewboard.kde.org/r/126523/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 359830] New: KMail stops silently working because of error "Unable to fetch item from backend"
https://bugs.kde.org/show_bug.cgi?id=359830 Bug ID: 359830 Summary: KMail stops silently working because of error "Unable to fetch item from backend" Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: tietze.he...@gmail.com CC: kdepim-b...@kde.org, vkra...@kde.org The error "Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." is shown in the status bar. It happens on synchronizing the Google trash folder. The really awkward is that KMail silently stops working (except from the status bar info) until I restart per "akonadictl restart" (without any error). It helps when I cleanup the trash but it's not a solution. My suggestion is to a) fix the bug and b) show a plasma notification on error that prevent KMail from receiving emails. Reproducible: Always KMail 5.1.2 akonadictl -v: "Akonadi 5.1.51" plasmashell -v: "plasmashell 5.5.4" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358069] Browse mode pointer should be an arrow not an hand to improve precision
https://bugs.kde.org/show_bug.cgi?id=358069 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #2 from Heiko Tietze --- The cursor shape is not relevant for the actual precision. However it gives a feeling of an exact position, in particular the crosshairs for the selection. But the shape is much more relevant to illustrate the underlying function. The hand shaped cursor shows the grab functionality (BTW: how the cursor looks depends on the cursor theme) and changes to grabbing with left mouse button pressed. The arrow is the default pointer and well suited to the zoom mode. If we would change the browse mode cursor it rather adds confusion since the arrow is used unspecifically. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358351] plasma crashes when manipulating with systray
https://bugs.kde.org/show_bug.cgi?id=358351 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #1 from Heiko Tietze --- Why do you flag VisualDesign? Sounds like an ordinary bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 353026] KRunner closes when focus is lost
https://bugs.kde.org/show_bug.cgi?id=353026 Heiko Tietze changed: What|Removed |Added CC||tietze.he...@gmail.com --- Comment #4 from Heiko Tietze --- I wouldn't add complexity. If something has to be sticky it should be implemented as plasmoid. Floating forms should be kept as such. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357763] clipboard widget delete history button
https://bugs.kde.org/show_bug.cgi?id=357763 --- Comment #4 from Heiko Tietze --- (In reply to Kai Uwe Broulik from comment #3) > > But take into consideration that the input field and the icon next to it > > are overloaded with the QR functionality > What? Click the barcode icon of an entry: the input becomes a button to go back and the clear all icon is replaced by a menu with QR types. > > 'remove this clipboard' (who came up with the idea to delete a clipboard?!) > Remove this clipboard widget. Sure, that's how it should be called. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357763] clipboard widget delete history button
https://bugs.kde.org/show_bug.cgi?id=357763 --- Comment #2 from Heiko Tietze --- I think you agree with the need for a function to delete all items. And this feature might be frequently used. If you care about the position next to the input field, which is usually taken by the clear-input-button, I agree. But take into consideration that the input field and the icon next to it are overloaded with the QR functionality (terrible solution). And if your intention is safety, a confirmation dialog could help. However, if you believe that a delete-all function is not that frequently used your suggestion makes sense. Perhaps another menu entry could offer the function. But actually the context menus are not contextual because it comes either from the panel with system tray and panel options or the desktop/folder settings and 'remove this clipboard' (who came up with the idea to delete a clipboard?!). All context menus need a context section for the plasmoid itself and another for the parent, clearly separated of course. It's conceptual broken on many places. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357210] Red close icon does not work on colored backgrounds
https://bugs.kde.org/show_bug.cgi?id=357210 --- Comment #2 from Heiko Tietze --- The URL shows all three types of message panels. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357210] New: Red close icon does not work on colored backgrounds
https://bugs.kde.org/show_bug.cgi?id=357210 Bug ID: 357210 Summary: Red close icon does not work on colored backgrounds Product: Breeze Version: 5.5.1 Platform: Other URL: https://git.reviewboard.kde.org/r/126523/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: uri_herr...@nitrux.in Reporter: tietze.he...@gmail.com CC: kain...@gmail.com The message panel has a colored background that jars with the red close icon. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356863] Blur when docked/maximized
https://bugs.kde.org/show_bug.cgi?id=356863 Heiko Tietze changed: What|Removed |Added Product|Breeze |kwin Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356863] Blur when docked/maximized
https://bugs.kde.org/show_bug.cgi?id=356863 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Heiko Tietze --- "Drop shadow" is the perfect keyword to dig the web and to find this thread https://www.reddit.com/r/kde/comments/2nshc1/panel_shadow_in_plasma_5/ with the solution: |For anyone coming across this thread, this is what worked for me: |(1) xprop -remove _KDE_NET_WM_SHADOW |(2) click the panel from which you want to remove the shadow I'm too lazy to read all the posts about drop shadows but obviously I'm not the only one who dislike this "feature". No idea for what it is good for. So I vote for removing it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356863] Blur when docked/maximized
https://bugs.kde.org/show_bug.cgi?id=356863 --- Comment #2 from Heiko Tietze --- Created attachment 96166 --> https://bugs.kde.org/attachment.cgi?id=96166&action=edit KMail free floating KMail free floating -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356863] Blur when docked/maximized
https://bugs.kde.org/show_bug.cgi?id=356863 --- Comment #1 from Heiko Tietze --- Created attachment 96165 --> https://bugs.kde.org/attachment.cgi?id=96165&action=edit KMail docked to the (upper) panel KMail docked to the (upper) panel -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356863] New: Blur when docked/maximized
https://bugs.kde.org/show_bug.cgi?id=356863 Bug ID: 356863 Summary: Blur when docked/maximized Product: Breeze Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: tietze.he...@gmail.com The edge of windows get a blur when docked to a panel. This blur looks unprecise, I always catch myself checking if the form isn't placed underneath the panel. The issue is illustrated in the screen shot. Reproducible: Always >qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation Version === KWin version: 5.5.1 Qt Version: 5.5.1 Qt compile version: 5.5.1 XCB compile version: 1.11.1 Operation Mode: X11 only Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 2 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 showGeometryTip: true condensedTitle: false electricBorderMaximize: false electricBorderTiling: false electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 112 glPlatformInterface: 2 Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: HDMI1 Geometry: 0,0,1920x1080 Refresh Rate: 60 Screen 1: - Name: eDP1 Geometry: 1920,180,1600x900 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL version string: 3.3 (Core Profile) Mesa 11.0.7 OpenGL platform interface: EGL OpenGL shading language version string: 3.30 Driver: Intel GPU class: Haswell OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 11.0.7 X server version: 1.18 Linux kernel version: 4.2.5 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom slidingpopups kwin4_effect_login slide screenshot minimizeanimation kwin4_effect_windowaperture flipswitch desktopgrid coverswitch kwin4_effect_fade kwin4_effect_maximize presentwindows highlightwindow kwin4_effect_dialogparent blur contrast logout windowgeometry startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: slide: screenshot: minimizeanimation: kwin4_effect_windowaperture: flipswitch: tabBox: true tabBoxAlternative: false duration: 200 angle: 30 xPosition: 0.3301311302185 yPosition: 1 windowTitle: true desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true coverswitch: animationDuration: 200 animateSwitch: true animateStart: true animateStop: true reflection: true windowTitle:
[Breeze] [Bug 356365] Progress bar has no good zero state
https://bugs.kde.org/show_bug.cgi?id=356365 --- Comment #5 from Heiko Tietze --- oxygen-demo5 looks okay here (blue on grey and nothing at 0% but with a smaller bar and label at the side). It might be a problem of Qt4 since my own program is linked against it and KMail afaik as well. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356365] Progress bar has no good zero state
https://bugs.kde.org/show_bug.cgi?id=356365 --- Comment #1 from Heiko Tietze --- Created attachment 95924 --> https://bugs.kde.org/attachment.cgi?id=95924&action=edit Example of zero percent progress bar taken from KMail -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356365] New: Progress bar has no good zero state
https://bugs.kde.org/show_bug.cgi?id=356365 Bug ID: 356365 Summary: Progress bar has no good zero state Product: Breeze Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: QStyle Assignee: hugo.pere...@free.fr Reporter: tietze.he...@gmail.com At zero percent the progress bar still shows a small blue line. This looks broken Reproducible: Always Expected Results: There should be no fill at zero, i.e. nothing blue. And I would also think about of hiding the text. -- You are receiving this mail because: You are watching all bug changes.
