[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #7 from Thomas Weissel --- so i tried to clean up everything kscreen related.. it didn't help. i just figured out that the problem is most likely related to "ACTIVITIES" when i hit "meta+tab" in a working VM the "activity bar" shows up on the left side of the screen. in the faulty VW nothing happens. the "activity bar" shows up when i use the desktop context menu and for some reason it is empty (screenshot) the "default" activity is still visible in the activity settings but it seems to be unused -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #6 from Thomas Weissel --- Created attachment 132552 --> https://bugs.kde.org/attachment.cgi?id=132552=edit activity switcher on the left side there is no activity visible even if the "default" activity is still there in the activity settings dialog -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 Thomas Weissel changed: What|Removed |Added CC||xapi...@gmx.net --- Comment #14 from Thomas Weissel --- i created a bug report that obviously describes the same bug forget about the first post - it DOES change the configuration.. it completely removes the "desktop containment" section and replaces it with the default "folder" section https://bugs.kde.org/show_bug.cgi?id=423421 you can use my iso file in a virtualbox vm to recreate it - just reset is until you see it as others have already postet - it happens in 2 out of 10 cases .. completely random -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #5 from Thomas Weissel --- https://bugs.kde.org/show_bug.cgi?id=421498 this bug is related to thx to the live image i created you can replay this as often as you want (just reset the virtualbox vm as long as neccesary to reproduce the behaviour - then analyze ;-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #4 from Thomas Weissel --- https://bugs.kde.org/show_bug.cgi?id=356899 this bug seems to be related -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 Thomas Weissel changed: What|Removed |Added CC||xapi...@gmx.net --- Comment #3 from Thomas Weissel --- Created attachment 132120 --> https://bugs.kde.org/attachment.cgi?id=132120=edit xsession-errors from a failed plasma start org.kde.plasma: requesting config for "Arbeitsfläche" without a containment! this is one thing that seems to be related :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #2 from Thomas Weissel --- i have to add information about the configuration: [Containments][2] stays exactly the same.. (the panel) [Containments][7] stays exactly the same.. (systemtray) [Containment][22] org.kde.desktopcontainment (which holds all of the widgets and the desktop wallpaper) is replaced by [Containment][49] org.kde.folder (wallpaper only) The activityId also stays the same.. so the question is.. what in the world makes plasma think it can switch from desktop containment to folderview RANDOMLY ??? it is also resultion independend.. it happens on vga, svga, hd, fullhd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #1 from Thomas Weissel --- Created attachment 129626 --> https://bugs.kde.org/attachment.cgi?id=129626=edit 3 identical virtual machines boot the same iso -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] New: Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 Bug ID: 423421 Summary: Plasmashell occasionally 'forgets' to load widgets and wallpaper Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: xapi...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129625 --> https://bugs.kde.org/attachment.cgi?id=129625=edit both states side by side SUMMARY Plasmashell occasionally forgets to load widgets (folderview and application launchers) and displays the default desktop wallpaper. opposed to what can be found in the configuration file "plasma-org.kde.plasma.desktop-appletsrc" this should be reproducable with the following image (basically kubuntu 20.04 with extra applications) https://life-edu.eu/public/life-2004-0.iso (https://life-edu.eu/download.html) no need to copy this on a flashdrive - it's also reproducable in virtualbox STEPS TO REPRODUCE 1. new virtual machine (ubuntu 64, no disk) - add iso as live cd (i made 3 vms in order to test faster) 2. start virtual machine 3. observe OBSERVED RESULT PARTS of the "plasma-org.kde.plasma.desktop-appletsrc" are ignored (they stay in the configfile but they are ignored) desktop starts with default desktop wallpaper - without widgets in the containment plasma panel has the correct configuration as defined in the config and widgets in the plasma panel also work as expected EXPECTED RESULT load configured desktop with all widgets and launchers SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION it is absolutely not reproducable.. first it happend when booting macs with the live usb flashdrive without acpi it made no sense then i tried in virtualbox and played with the settings.. nothing came up.. it happens absolutely RANDOM i have 3 identical virtual machines.. if i start them one after the other.. at least one of them will display only half of the configuration correctly i already deleted the configuration files und started from scratch with a fresh config.. same thing happend so it shouldn't be a bug in the config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417753] New: Folderview doesn't refresh on content change on remote smb:/ locations
https://bugs.kde.org/show_bug.cgi?id=417753 Bug ID: 417753 Summary: Folderview doesn't refresh on content change on remote smb:/ locations Product: plasmashell Version: 5.18.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: xapi...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Mounting a samba share into a folder that is currently displayed in a folderview widget doesn't trigger a content refresh in this widget. the title of the widget changes to "xy at 10.0.0.100" but i need to manually trigger a "refresh" in order to see the content of the remote share STEPS TO REPRODUCE 1. add folderview widget to desktop 2. show a specific folder A in folderview 3. mount samba share into folder A OBSERVED RESULT the title changes but the content is not displayed EXPECTED RESULT titel and content refresh -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414101] kiosk: action/shell_access=false causes dolphin to crash on exit
https://bugs.kde.org/show_bug.cgi?id=414101 Thomas Weissel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Thomas Weissel --- (In reply to Kai Uwe Broulik from comment #4) > Patch: https://phabricator.kde.org/D25297 > However, it appears there won't be another 19.08 release :/ wow.. that was fast... thank you very much !!! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414101] kiosk: action/shell_access=false causes dolphin to crash on exit
https://bugs.kde.org/show_bug.cgi?id=414101 --- Comment #1 from Thomas Weissel --- plasma version: 5.17.2 frameworks version: 5.63.0 qt version: 5.13.1 kernel: 5.3.6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414101] New: kiosk: action/shell_access=false causes dolphin to crash on exit
https://bugs.kde.org/show_bug.cgi?id=414101 Bug ID: 414101 Summary: kiosk: action/shell_access=false causes dolphin to crash on exit Product: dolphin Version: 19.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: xapi...@gmx.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123901 --> https://bugs.kde.org/attachment.cgi?id=123901=edit all action restrictions i use in one file SUMMARY STEPS TO REPRODUCE 1. create the file /etc/kde5rc 2. create an action restriction for shell access [KDE Action Restrictions][$i] shell_access=false 3. restart desktop to make action restriction active OBSERVED RESULT when you close dolphin it crashes EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385961] using xrandr --transform in order to display a black bar on skylake leads to weird bugs
https://bugs.kde.org/show_bug.cgi?id=385961 --- Comment #6 from Thomas Weissel <xapi...@gmx.net> --- qdbus org.kde.KWin /KWin supportInformation -- KWin-Unterstützungsinformationen: Benutzen Sie die folgenden Informationen, wenn Sie nach Unterstützung fragen, z. B. auf http://forum .kde.org. Sie enthalten Informationen über die momentan laufende Instanz, welche Optionen verwendet werden, welcher OpenGL-Treiber verwendet wird und welche Effekte laufen. Bitte geben Sie die unten stehenden Informationen bei einem Pastebin-Dienst wie http://paste.kde.org ein, anstatt sie direkt in die Hilfediskussionen zu schreiben. == Version === KWin version: 5.9.2 Qt Version: 5.7.1 Qt compile version: 5.7.1 XCB compile version: 1.11.1 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11804000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: false closeOnDoubleClickOnMenu: false decorationButtonsLeft: 9 decorationButtonsRight: 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: true focusStealingPreventionLevel: 1 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: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.1000149011612 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 2 useCompositing: false compositingInitialized: false hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 97 glPlatformInterface: 1 windowsBlockCompositing: true 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: no Number of Screens: 2 Screen 0: - Name: HDMI-1 Geometry: 0,0,1024x768 Refresh Rate: 75.0286 Screen 1: - Name: DP-2 Geometry: 0,0,1024x768 Refresh Rate: 60.0038 Compositing === Compositing is not active xrandr - Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00 + 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x720 60.00 1024x768 75.03* 70.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-2 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 8
[kwin] [Bug 385961] using xrandr --transform in order to display a black bar on skylake leads to weird bugs
https://bugs.kde.org/show_bug.cgi?id=385961 --- Comment #2 from Thomas Weissel <xapi...@gmx.net> --- good question.. it was just a hunch.. because plasma resized accordingly, the mouse area (where i can move my mouse) did resize too.. but my windows are drawn over the whole screen when maximized - therefore i thought that the windowmanager probably is a good start to search for a reason / bug -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385962] kate indention jumps to next level on specific letters when it shouldn advance to next level
https://bugs.kde.org/show_bug.cgi?id=385962 --- Comment #2 from Thomas Weissel <xapi...@gmx.net> --- 5.39.0 cheers -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 385965] New: krunner aka run command interface ignores the entry in /etc/kde5rc to not show up if only plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=385965 Bug ID: 385965 Summary: krunner aka run command interface ignores the entry in /etc/kde5rc to not show up if only plasmashell is restarted Product: frameworks-krunner Version: 5.39.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: xapi...@gmx.net Target Milestone: --- as simple as this.. i place an entry in /etc/kde5rc run_command=false action/run_command=false and krunner does not show up if i restart Xorg... if i only restart plasmashell and kwin it will not work. it worked in 5.10 and stopped working in 5.11 thx in advance -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385962] New: kate indention jumps to next level on specific letters when it shouldn advance to next level
https://bugs.kde.org/show_bug.cgi?id=385962 Bug ID: 385962 Summary: kate indention jumps to next level on specific letters when it shouldn advance to next level Product: kate Version: 17.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: xapi...@gmx.net Target Milestone: --- i don't know how to put it in easier words.. i write a lot of python code in kate and in the recent version it's making me crazy! def test: if this is that: print "same" else: <<< here lies the problem print "different" if i manually decrease indention by using "backspace" kate will jump back to the same indention level as "print" - i hit backspace again.. start writing "else" and it jumps again .. i hit enter in order to make a line break - decrease the indention level manually and write "else" and it advances again one level.. lets put it short: if i manually decrease the indention level - kate has to follow my lead NO MATTER WHAT.. it must not indent automatically after i hit "backspace" (and i'm sure this behaviour is new to kate) probably i'm just "holding it wrong" so please tell me what the preferred workflow with indention should be it actually works if i hit backspace - then enter and then write a line.. but i don't think an extra blankline between the if block and the else block is python pep8 compliant thx in advance -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385961] New: using xrandr --transform in order to display a black bar on skylake leads to weird bugs
https://bugs.kde.org/show_bug.cgi?id=385961 Bug ID: 385961 Summary: using xrandr --transform in order to display a black bar on skylake leads to weird bugs Product: kwin Version: 5.11.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: xapi...@gmx.net Target Milestone: --- on different testcomputers i manage to use --transform to avoid stretching a 4:3 image to a 16:9 screen.. it properly moves the image to the left edge and displays a black bar on the right side. --set 'scaling mode' Center is not working in these cases because the option is not recognized on external screens .. this only works on laptops (embedded displays for me) therefore i use --transform! i testet it on a new pc in our school with an intel skylake cpu and it made the screen flash like crazy once and most of the time it properly scales plasma and the area where i can move my mouse but i can still maximize all my windows to the whole sceenarea it looks really weird - everything is contained to the correct rectangle, i see a black bar on the right sight but windows can cover this area nevertheless... this is the line i am using and i don't think the line is the problem - as i said it works on all the other computers: echo "exec xrandr --output $DISPLAY1 --mode $RESOLUTION --primary $TRANSFORM --output $DISPLAY2 --mode $RESOLUTION --same-as $DISPLAY1 &" where TRANSFORM="--transform 1.3330078125,0,0,0,1,0,0,0,1" for example in order to scale the image proportionally to a 1024x768 image on a full hd screen i tried several other transformations and the result is always the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 Thomas Weissel <xapi...@gmx.net> changed: What|Removed |Added Version|5.9.1 |5.9.2 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #18 from Thomas Weissel <xapi...@gmx.net> --- @christoph feck this bug is resolved in 5.9.2 so i would leave it closed! thx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376679] New: chaning mimeapps.list is not respected by folderview unless you restart Xorg
https://bugs.kde.org/show_bug.cgi?id=376679 Bug ID: 376679 Summary: chaning mimeapps.list is not respected by folderview unless you restart Xorg Product: plasmashell Version: 5.9.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: xapi...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 i tried changing the fileassociation for odt from libreoffice to calligrawords and it is working everywhere except in the folder view widget. even restarting plasmashell did not change this faulty behaviour after i restart Xorg it also works in the folder view widget i made sure that all tree locations /usr/share/applications/ .config/ and .local/share/applications/ had the same mimeapps.list file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #17 from Thomas Weissel <xapi...@gmx.net> --- Unfortunately i have to report that in 5.9.1 this is NOT fixed :) plasma behaves as follows: (starting with a blank new setup) there is only one containment in plasma-org.kde.plasma.desktop-appletsrc [Containments][1] activityId=86868fa6-a85a-4e74-a8d2-8abda1d6ae3e formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.desktopcontainment wallpaperplugin=org.kde.image >> Then i add an Applet - the applet part gets added to the config file to >> containment [1] >> Then i attach a beamer - a new containment [21] is added to the config file: (the beamer is placed right of the mainscreen with the maincontainment) >> then i "clone" the two screens by using xrandr (or the kscreen configuration >> tool (it doesn't matter)) and the containment [21] covers containment [1] >> -> all widgets are hidden. hitting alt+tab (with no applications open) still makes the switch to the maincontainment rebooting the system always shows the unconfigured new containment :-( this is a real showstopper.. bug still there or did the patch miss 5.9.1 ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #15 from Thomas Weissel <xapi...@gmx.net> --- I just tried the setup on kde plasma 5.9.0 (neon packages) i deleted all of the old config files first, setup the desktop containment with widgets and then tried to "clone" the desktop to the beamer... unfortunately nothing changed ! the moment i plug in a beamer and call >> xrandr --output LVDS --mode 1024x768 --primary --set "scaling mode" Center >> --output VGA-0 --mode 1024x768 --same-as LVDS & a new containment is created and used as primary containment on top of the one i configured before... i still can switch to the original one by pressing meta+tab did the fix make it to 5.9 in time ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #14 from Thomas Weissel <xapi...@gmx.net> --- thanx a lot ! i'm definitely going to test it... is there any chance that this fix is going to be in 5.8.6 ? (because for my classrooms im betting on the LTS ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #8 from Thomas Weissel <xapi...@gmx.net> --- Created attachment 103658 --> https://bugs.kde.org/attachment.cgi?id=103658=edit output of kscreen-console -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #7 from Thomas Weissel <xapi...@gmx.net> --- well.. what you can't see in the video is that the screenmanagment tool in systemsettings says [0,0] in the corner (so it thinks they are exactly overlapping) but as seen in the video there is an offset nevertheless.. i changed that in the video immediately so that both windows are precicely on top of each other.. in my classroom installations i'm not doing it manually.. i use.. exec xrandr --output LVDS --mode 1024x768 --primary --set "scaling mode" Center --output VGA-0 --mode 1024x768 --same-as LVDS & this should do it right? i've got no kscreen-doctor.. where can i find that? meanwhile i attach the output of kscreen-console thx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #5 from Thomas Weissel <xapi...@gmx.net> --- here is a more detailed video that shows attaching the beamer and the handling of the applets you can see how the current containment is replaced with a blank new one and how applets are placed on the initial containment and disappear to the new one the moment you try to move them. https://www.youtube.com/watch?v=7bREB1tOf8M -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #4 from Thomas Weissel <xapi...@gmx.net> --- Created attachment 103647 --> https://bugs.kde.org/attachment.cgi?id=103647=edit plasmashell config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #3 from Thomas Weissel <xapi...@gmx.net> --- Created attachment 103646 --> https://bugs.kde.org/attachment.cgi?id=103646=edit plasma applets config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373312] In mirrored display widgets disappear when moved
https://bugs.kde.org/show_bug.cgi?id=373312 Thomas Weissel <xapi...@gmx.net> changed: What|Removed |Added CC||xapi...@gmx.net --- Comment #3 from Thomas Weissel <xapi...@gmx.net> --- looks like we found the same bug ? https://bugs.kde.org/show_bug.cgi?id=375507 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #2 from Thomas Weissel <xapi...@gmx.net> --- oke.. i think i can describe it a little bit better now: the moment you add a second display your plasma-org.kde.plasma.desktop-appletsrc gets a new entry > a new containment for the same activity id that looks like this: [Containments][73] activityId=95dec76c-3e71-47af-a064-cbd5a50957de formfactor=0 immutability=1 lastScreen=2 <<<<< ! location=0 plugin=org.kde.desktopcontainment wallpaperplugin=org.kde.image this containment has no "applets" and therefore is empty that is ok for the default setup where the new display extends the first one to the left or to the right (big desktop) BUT the moment you move the first display over the second (in systemsettings or with xrandr) in order to "clone" the displays (display the same content on both screens) it becomes a problem.. plasma seems to randomly chose which containment is shown on the screens!! new widgets are placed on the primary screen1 containment (and you can see that if you are lucky and this is the one containment that is currently displayed) but the moment you move them they switch to the secondary (empty) contaiment for screen2 (somehow behind the current containment) by pressing meta+tab you can switch between those two contaiments and change the "stack" order.. it seems that sometimes (in my case after every boot) the containment of screen2 acts as overlay over screen1 containment. IMHO they should always have the same content in "clone" mode and the user should never be able to see (or even switch) between those to.. OR.. the containment of any other screens that are not marked as primary should be rigorously ignored -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 --- Comment #1 from Thomas Weissel <xapi...@gmx.net> --- oh.. and if you try to add widgets to a fresh installation (new config file) already cloned - they appear on the screen but then dissappear to the "hidden" second containment the moment you try to move them.. only after a reboot it is possible to add widgets to the current visible screen AND move them without changing to the other conainment... weird !? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 Thomas Weissel <xapi...@gmx.net> changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375507] New: blank plasmadesktop containment is created when cloning display
https://bugs.kde.org/show_bug.cgi?id=375507 Bug ID: 375507 Summary: blank plasmadesktop containment is created when cloning display Product: plasmashell Version: 5.8.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: xapi...@gmx.net Target Milestone: 1.0 steps to reproduce: # configure desktop and fill it with widgets # attach projector # clone display to projector # restart xserver the file: plasma-org.kde.plasma.desktop-appletsrc gets a new entry like this: [Containments][73] activityId=95dec76c-3e71-47af-a064-cbd5a50957de formfactor=0 immutability=1 lastScreen=2 location=0 plugin=org.kde.desktopcontainment wallpaperplugin=org.kde.image >> all desktop widgets are gone the old entry : [Containments][1] activityId=95dec76c-3e71-47af-a064-cbd5a50957de formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.desktopcontainment wallpaperplugin=org.kde.image and all it's associated [Applets] are still there but not shown. pressing "meta+tab" or accessing the activity switcher (or pressing "alt+tab" without running applications) immediately switches back to containment #1 instead of containment #73 and all widgets are visible again. i switched the lastScreen values so that containment #73 has lastScreen=0 > restarted the desktop > everything worked.. all my widgets are here (i'm still able to switch to the empty containment from the parallel universe with meta+tab) the problem is that the moment i disconnect the projector and restart the desktop the containment with lastScreen=0 is shown (ergo the empty one) it seems i can't have both.. there is no other desktop configured and no other activity - plasmashell is doing this automatically but this new "hidden" containment does not show up anywhere except in the config file.. reproduceable: ALWAYS! here is a short video of this strange behaviour: https://www.youtube.com/watch?v=95z7yuZQLCo IMHO creating another desktop containment entry in the config file is fine for big-desktop but clone-desktop should not do this - it should just clone the current one! is there a quick fix for that? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 345871] Solid::Backends::UDisks2::DeviceBackend::checkCache() causes crash after partition changes
https://bugs.kde.org/show_bug.cgi?id=345871 --- Comment #34 from Thomas Weissel <xapi...@gmx.net> --- well.. i understand that starting gparted causes this crash and using parted from bash (my bug-duplicate) also crashes plasma.. but could it be possible that changing settings for a virtualbox vm also causes "the same" crash? (happens to me all the time..) or should i report this somewhere else ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372954] New: Plasmashell Crash when changing several partitions with parted and formatting them
https://bugs.kde.org/show_bug.cgi?id=372954
Bug ID: 372954
Summary: Plasmashell Crash when changing several partitions
with parted and formatting them
Product: plasmashell
Version: 5.8.4
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Device Notifier
Assignee: plasma-b...@kde.org
Reporter: xapi...@gmx.net
Target Milestone: 1.0
every time i run a script that formats my usb flashdrives with 3 partitions
(fat32, fat32, ext4) plasmashell crashes.
reproducable : 99%
this is the script:
echo "# PARTITIONING DEVICE #"
LIFESIZEEND=$(( $WINSHARESIZE + $LIFESIZE ))
sudo partprobe $SDX
sudo parted -s $SDX mktable MSDOS
sleep 1
sudo partprobe $SDX
sudo parted -s $SDX mkpart primary fat32 0% $WINSHARESIZE
sudo parted -s $SDX mkpart primary fat32 $WINSHARESIZE $LIFESIZEEND
sudo parted -s $SDX mkpart primary ext4 $LIFESIZEEND 100%
echo "# setting boot flag to second partition #"
sudo parted -s $SDX set 2 boot on
sudo parted -s $SDX print
echo ""
echo " WAITING FOR DEVICE TO SETTLE .. "
echo ""
sleep 4
sudo partprobe $SDX
echo ""
echo "#CREATING FILESYSTEMS#"
echo ""
sudo mkfs.vfat -F 32 -n WINSHARE ${SDX}1
sleep 1
sudo mkfs.vfat -F 32 -n LIFECLIENT ${SDX}2
sleep 1
echo "mkfs.ext4"
sudo mkfs.ext4 -L casper-rw ${SDX}3 > /dev/null 2>&1 #hide output
sleep 1
#sudo mkfs.ext2 -b 4096 -L home-rw ${SDX}3
sudo partprobe
echo "#Finished Partitioning #"
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 372849] New: davfs2 is treated as local filesystem
https://bugs.kde.org/show_bug.cgi?id=372849 Bug ID: 372849 Summary: davfs2 is treated as local filesystem Product: frameworks-kio Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: xapi...@gmx.net CC: kdelibs-b...@kde.org Target Milestone: --- Dolphin 17.03.70 Plasma 5.8.90 Frameworks 5.29.0 Qt 5.7.0 The problem is best reproduced in dolphin filemanager. A remote share (owncloud) mounted with davfs2 seems to be treated as local filesystem. Therfore the setting "don't create thumbnails for remote files bigger than.." is not honored and previews of files and folders are being created. Deactivating folder previews works as quickfix for the critical situations but files bigger than 10 MB still completely stall dolphin. The davfs2 option "gui_optimize" also improves the situation a little bit but the problem remains. Also giving the thumbnailcreator more power did not really help. /usr/share/kservices5/thumbnail.protocol maxInstances=4 Entering any folder that contains even very small videos almost kills dolphin. It takes forever until you gain control again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 --- Comment #11 from Thomas Weissel <xapi...@gmx.net> --- ok.. it seems this bug is fixed in 5.8.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365617] pinned chromium launcher disappears
https://bugs.kde.org/show_bug.cgi?id=365617 --- Comment #31 from Thomas Weissel <xapi...@gmx.net> --- sorry forgot to add using plasma: 5.8.90 frameworks: 5.28.0 qt: 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365617] pinned chromium launcher disappears
https://bugs.kde.org/show_bug.cgi?id=365617 --- Comment #30 from Thomas Weissel <xapi...@gmx.net> --- (In reply to xkmalikx from comment #25) > What I discovered is that chromium launcher disappears only if I have 3 or > more opened and modified (non blank) tabs. i tried this an i can reproduce it every time... (with a little addition) 1) open chrome 2) open at least 3 nonblank tabs 3) switch to one of these tabs !important 4) close chrome ---> chrome launcher is gone 1) open chrome from the application launcher 2) close chrome ---> chrome launcher is back and btw. i managed to get GIMP launcher removed to.. but i don't know how :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 --- Comment #10 from Thomas Weissel <xapi...@gmx.net> --- i can confirm that in plasma 2.8.90 frameworks 2.28.0 Qt 5.7.0 this bug is still unresolved. it just changes a little bit... kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up brings back my messed up icons in the panel (different bug) but this time screen number 2 stays black.. so it keeps the problem alive now even if i kill it ! btw. why is this bug still "unconfirmed"? is there no developer with a multiscreen setup experiencing the same thing? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 --- Comment #6 from Thomas Weissel <xapi...@gmx.net> --- i dare to say that this problem is fixed now by changing my own hardware setup. what i had: 1x hdmi out (connected to the hdmi port of my first display) 1x dvi out (connected to the hdmi port of my second dislay ) what i have now: 1x hdmi out (conneted to the dvi port of my first display) 1x dvi out (connected to the dvi port of my second dislay) my screens went to sleep at least 5 times now without any problems... attention!! this bug is not fixed ! it just seems to work for my current (new) setup now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 --- Comment #5 from Thomas Weissel <xapi...@gmx.net> --- yet another interesting observation: i added clock widgets to the screens... one of the screens went dark after sleep (no background - no rightclick contextmenu) but the widget remained visible (it still displayed the time when the screens went to sleep) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 Thomas Weissel <xapi...@gmx.net> changed: What|Removed |Added Version|5.7.2 |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 --- Comment #4 from Thomas Weissel <xapi...@gmx.net> --- re-tested with kde neon on kubuntu plasma: 5.8.0 Qt: 5.7.0 the onlything new is that sometimes only the wallpaper is gone but the contextmenu is still there, adding a widget gets everything back to normal.. also when one of the screens went black the last time plasma seemed to restart automatically after 2 or 3 seconds.. what can i do to narrow down the reason for this ? i want this bug gone! -- You are receiving this mail because: You are watching all bug changes.
