[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #8 from Daniel Boles  ---
Created attachment 96966
  --> https://bugs.kde.org/attachment.cgi?id=96966=edit
screenshot of an edit attempt, just prior to clicking OK

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #6 from Daniel Boles  ---
Created attachment 96964
  --> https://bugs.kde.org/attachment.cgi?id=96964=edit
desktop file created (and unable to edit) by autostart

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #2 from Daniel Boles  ---
Thanks for the move. I did search for System Settings, but it wasn't found due
to the space between the 2 words, which makes (its own kind of!) sense.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #4 from Daniel Boles  ---
Hi David, as mentioned (somewhat cryptically) in my 2nd post, this is by
Program.

And to confirm, I'm definitely attempting to edit the command proper, in the
Application tab - not just the desktop shortcut name on General.

On clicking OK, the KCM pops up a message "Updating system configuration..."
briefly, but it does not change the command.

Should be simple enough for someone else to test. Do you need anything else?

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #10 from Daniel Boles  ---
Thanks for the pointers, added the requested.

Notably the timestamp indicates that indeed the file has not been touched at
all since the date of initial creation (or in this case, recreation since I had
to delete the one without -no-splash and create this one, for obvious reasons)

Hope this helps and let me know anything else required.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #9 from Daniel Boles  ---
Created attachment 96967
  --> https://bugs.kde.org/attachment.cgi?id=96967=edit
screenshot of config and directory after attempted edit, showing no change

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #7 from Daniel Boles  ---
Created attachment 96965
  --> https://bugs.kde.org/attachment.cgi?id=96965=edit
screenshot of autostart configuration and directory prior to attempting edit

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 358701] New: Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

Bug ID: 358701
   Summary: Autostart fails to edit existing entries; they remain
how they were when they were first created
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: db0...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Autostart fails to edit existing entries; they remain how they were when they
were first created. To 'edit' an entry requires creating a new one with the
desired settings and deleting the old one.

Reproducible: Always

Steps to Reproduce:
1. Open Autostart
2. Create an entry (which works)
3. Go back later and try to edit it

Actual Results:  
On saving the entry, changes are not applied: going back into it shows that the
changes have not been saved, and the entry is the same as when it was first
inserted.

Expected Results:  
Changes should be saved, of course!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 358701] Autostart fails to edit existing entries; they remain how they were when they were first created

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358701

--- Comment #1 from Daniel Boles  ---
the exact test case:

entry as created: Program: xscreensaver &
desired edit: xscreensaver -no-splash &

On restarting, the splash was still shown. Opening the Autostart entry showed
that the -no-splash switch had not been added. Trying to change again also
failed. I had to delete the old entry and create a new one with -no-splash
included. I have since replicated this with other commands.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 354028] Konsole crash on exit ( yet another dupe of Bug 346833 et al because Dr. Konqi is broken.)

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354028

--- Comment #3 from Daniel Boles  ---
For me, some intervening update seems to have fixed this. Konsole hasn't been
updated since version "konsole:amd64 (15.08.2-1, 15.08.3-1)" on the 12th,
before I confirmed the bug, but now it does not crash on exit.

Hopefully this has fixed it for other users with this problem, too?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346181

--- Comment #11 from Daniel Boles  ---
Nice to hear, but that unfortunately doesn't help everyone else for whom
KDE 5 is doing all sorts of weird things on multi-display setups.

Are these being worked on for fixing? A similar - but apparently totally
unrelated - issue with notifications was getting a lot of attention, while
this one hasn't even been 'confirmed' yet. What gives? It's hardly an
unimportant detail if a 2nd screen is barely usable without considerable
concessions.


On Sun, Jan 3, 2016 at 2:01 PM, Ian Morgan via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=346181
>
> --- Comment #10 from Ian Morgan  ---
> I found my problem, and it's incredibly stupid. I also can't believe that
> in
> all my quests to find a solution over the last 3+ months, nobody ever
> thought
> to ask "are tooltips turned on?".. !!!
>
> The closest I had come before was someone asking if the "Show Tooltips"
> option
> was turned on ** in Task Manager Settings **.. which it was. And that
> setting
> wouldn't explain why no tooltips would show up for ANY panel item,
> unrelated to
> Task Manager.
>
> Drum roll, please
>
> System Settings -> Workspace/Desktop Behaviour -> Workspace/Workspace
> Behaviour
> -> Show Informational Tips
>
> ARGH!!! All this time, and it was a goddamned option that was turned off!
>
> Problem solved.. Good-day gentlemen.
>
> Recommendation: In the Task Manager settings, grey-out or disable the "Show
> tooltips" option (with a hint saying why it's disabled) if the global "Show
> Informational Tips" option is turned off.
>
> A related question: In what file is the "Show information tips" option
> setting
> stored? One of the things I had done to try to resolve this issue was to
> wipe
> all my kde/qt settings files/folders and start fresh, yet that made no
> difference. Is the fresh-start default for this option on or off? I expect
> that
> on would be the default.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356850

--- Comment #7 from Daniel Boles  ---
Thanks again - good point - it does look to be v4 stuff in there. I nuked all 3
(-daniel, -root, and -kdm) dirs and only the former was recreated. After a
reboot and login, it has these contents:

*+daniel@v3-771g:~$ ls /var/tmp/kdecache-daniel/
total 176328
drwx-- 2 daniel daniel 4096 Dec 22 18:36 ./
drwxrwxrwt 7 root   root   4096 Dec 22 18:36 ../
-rw-r--r-- 1 daniel daniel 10547304 Dec 22 18:36 icon-cache.kcache
-rw-r--r-- 1 daniel daniel  1221311 Dec 22 18:36 ksycoca4
-rw-r--r-- 1 daniel daniel  536 Dec 22 18:36 ksycoca4stamp
-rw--- 1 daniel daniel   48 Dec 22 18:36 Personal Calendarrc
-rw--- 1 daniel daniel  910 Dec 22 18:36 plasma-svgelements-slim-glow
-rw-r--r-- 1 daniel daniel 84377704 Dec 22 18:36
plasma_theme_internal-system-colors.kcache
-rw-r--r-- 1 daniel daniel 84377704 Dec 22 18:36 plasma_theme_slim-glow.kcache
+daniel@v3-771g:~$ 

I don't know whether these components should still be  installed? Happy to
remove them if not. Also, I haven't a clue where Slim Glow is coming from,
since I use Breeze as my Desktop Theme - Slim Glow rings a bell; I might've
used it under v4, but it's not even presented as an option now. The only change
I made to the Breeze Desktop Theme was to apply Oxygen colours - in case that's
relevant to the old stuff floating around (as it was the main v4 theme).

Still, these legacy components don't seem to obey the old KDEVARTMP as
otherwise I would've seen kdecache-daniel being recreated in /tmp on prior
logins, but it always went into /var/tmp

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 354028] Konsole crash on exit ( yet another dupe of Bug 346833 et al because Dr. Konqi is broken.)

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354028

--- Comment #2 from Daniel Boles  ---
oh, should've said: for me this happens every time Konsole is closed: simply
open a window, do absolutely nothing, then close using your choice of "exit" or
the GUI button or the File menu. Each time, same result

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356850

--- Comment #4 from Daniel Boles  ---
I'm away from this PC at the moment but will confirm later whether/what it
currently has TMPDIR set to, and whether changing it affects the location of
kdecache-* stuff. I assume/hope it will but will post back either way.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356850

--- Comment #3 from Daniel Boles  ---
Thanks, David. That makes sense and is quicker than me browsing source for days
to reach the same conclusion! Before I look at updating the wiki, can you
advise whether any other variables therein (especially the closely related
KDETMP, which I admit I haven't checked yet) have also been superseded in KDE5?
That way I can cover them all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #27 from Daniel Boles  ---
Hi,

Will that also cover these problems with various panel popups appearing on the
wrong screen (in a random location) or not at all?
https://bugs.kde.org/show_bug.cgi?id=346181

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356850] New: KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356850

Bug ID: 356850
   Summary: KDEVARTMP environment variable is ignored after
upgrade from KDE 4 to 5
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: db0...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I previously used a .sh file in ~/.kde/env to mkdir a folder in my /tmp
ramdrive and set KDEVARTMP to that folder. This resulted in KDE caching
everything in RAM and seemed to have no ill effects. I have since upgraded from
KDE 4 to 5, moved the .sh script to the new corresponding location -
~/.config/plasma-workspace/env - and noticed that although it is executed and
the environment variable set, that variable is seemingly no longer used. KDE
continues to use its default path in /var/tmp

Is this intentional and the documentation outdated, or has KDEVARTMP been
deprecated, or is something else stopping this from working with the folder I
designate? Thanks in advance.

Reproducible: Always

Steps to Reproduce:
1. export KDEVARTMP from a startup env script, e.g. as /tmp/KDEVARTMP (prefaced
by the required mkdir so this folder exists in advance)

Actual Results:  
2. KDEVARTMP is set
3. It does not have the documented effect, i.e. changing kdecache-* directories
to be placed in the KDEVARTMP path

Expected Results:  
3. kde-cache-* et al should be placed in the KDEVARTMP path as claimed in the
documentation

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356850

Daniel Boles  changed:

   What|Removed |Added

   Keywords||regression, usability

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356850

--- Comment #1 from Daniel Boles  ---
Created attachment 96155
  --> https://bugs.kde.org/attachment.cgi?id=96155=edit
~/.config/plasma-workspace/env/kwin_env.sh (formerly in ~/.kde/env/)

This is the script that gets run, exports the KDEVARTMP file, but does not have
the previous/desired effect. chmod permissions are 755 and it's executable.
/tmp is mounted as a tmpfs in RAM and previously worked fine as the path for
KDEVARTMP stuff (kde-cache etc) in v4

-- 
You are receiving this mail because:
You are watching all bug changes.

[khotkeys] [Bug 345252] khotkeys can not save custom shortcut actions

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345252

Daniel Boles  changed:

   What|Removed |Added

 CC||db0...@gmail.com

--- Comment #21 from Daniel Boles  ---
Confirmed in 5.4.3-1 on Debian testing. Rather disruptive. Any other info I can
help with to get it fixed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356804] Breeze Task Switcher fails to visually highlight some windows' thumbnails while tabbing through

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356804

--- Comment #1 from Daniel Boles  ---
Re what I said about the mouse cursor always updating the highlight - this is
not _completely_ consistent as sometimes this doesn't work. It's kinda 50/50.
sometimes the switcher not only won't highlight on hover - but won't even
accept clicks to select certain thumbnails. These are usually - but seemingly
not always - the same windows that get skipped by highlighting using the
Alt+Tab.

These issues are probably related and hopefully simple to fix together. Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356804] Breeze Task Switcher fails to visually highlight some windows' thumbnails while tabbing through

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356804

--- Comment #2 from Daniel Boles  ---
As expected, if I tick on "Show selected window", it brings each window to the
foreground in turn, not skipping any - though the highlight box in the sidebar
still misses some, remaining desynchronised from the actual selection.

The alternative types of Switcher - Cover and Flip - also work as intended,

I find both of these much less aesthetically pleasing than a working Breeze
switcher... though I think ideally I'd have the old centred KDE4 one back :P

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356804] New: Breeze Task Switcher fails to visually highlight some windows' thumbnails while tabbing through

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356804

Bug ID: 356804
   Summary: Breeze Task Switcher fails to visually highlight some
windows' thumbnails while tabbing through
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: db0...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I've got the Switcher set to Breeze them with the usual Alt-Tab as the main
shortcut. When pressing this, the pane appears on the left with thumbnails of
windows oriented vertically. One of these is highlighted by a box (in my case a
light blue colour) as you tab through.

However, certain thumbnails do NOT get highlighted - the highlight box stays on
the previous window. But, if I release Alt on the window I just (blindly)
tabbed to, it then gets focussed as normal. Showing that it _is_ being
'selected' - but not properly visually highlighted to indicate this.

Also, when the selection has moved to a new thumbnail where the highlight
erroneously isn't showing - if I keep Alt held and move my mouse cursor over
the now (invisibly) selected thumbnail, the highlight box then moves to there
where it should have been all along.

Please let me know if I can provide any relevant details to get this resolved.

Reproducible: Always

Steps to Reproduce:
1. Set Task Switcher to Breeze them and open a bunch of windows
2. Press Alt+Tab multiple times and notice that certain windows are not
highlighted when they are selected by the Switcher
3. Releasing Alt gives the right window focus, showing that the window is being
selected, just invisibly - though by moving your mouse cursor over the
thumbnail, it gets highlighted properly as it should have been

Actual Results:  
Certain windows are not highlighted (without manually moving the mouse cursor
over them, clearly not useful behaviour)

Expected Results:  
All windows should be highlighted when selected, as with any other
task-switching widget

Happy to provide any relevant logs etc if required. Can probably record a video
if absolutely necessary though I hope this is reproducible enough.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356804] Breeze Task Switcher fails to visually highlight some windows' thumbnails while tabbing through

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356804

Daniel Boles  changed:

   What|Removed |Added

   Keywords||regression, usability

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346181

--- Comment #8 from Daniel Boles  ---
If I make the left, secondary, external screen primary - everything seems to
work as wanted. However, the laptop screen  is closer to me, so it should be my
primary.

Super simplistic guess without ref to source code: Perhaps the affected widgets
are coded naively to appear on the left screen, regardless of its type or set
role. Obviously, if true, this needs to be changed so that they intelligently
appear in the right (normal) place on the primary screen instead.

Anyway, I'll stop for now. But if anyone wants any more info that could get
this patched ASAP, I'll be more than happy to help provide that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

Daniel Boles  changed:

   What|Removed |Added

 CC||db0...@gmail.com

--- Comment #12 from Daniel Boles  ---
possibly related to wider scale mis-selection of screen as documented in
https://bugs.kde.org/show_bug.cgi?id=346181

I might be able to test your patch within the next couple of days once the rest
of my newly migrated Debian testing installation is stable (relatively
speaking).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346181

Daniel Boles  changed:

   What|Removed |Added

 CC||db0...@gmail.com

--- Comment #6 from Daniel Boles  ---
Confirmed in 5.4.3 (Debian testing). App Launcher is simply missing its popup
when clicked. Taskbar right-clicks and systray hovers, etc appear on the
external secondary (in my case, left) screen. This is nearly unusable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in

[Daniel Boles via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346181

--- Comment #9 from Daniel Boles  ---
Interestingly,  after toggling BACK to the internal laptop screen as primary,
things now appear there where they should: the taskbar is there, and so are all
of its popups/menus.

so the process here - which I hope can somehow help the experts diagnose & fix
this one - was:
* boot with external VGA plugged in - and laptop set as primary on last
shutdown
* = taskbar on laptop screen but popups appear in arbitrary places on secondary
VGA
* switch primary to VGA
* = taskbar and popups on VGA - 'correctly' but not my desired layout
* switch primary BACK to laptop
* = taskbar and popups now magically appear all on laptop primary, which they
should have all along

cheers and hope this helps.

-- 
You are receiving this mail because:
You are watching all bug changes.