Gentoo Archives: gentoo-user

From: Kai Krakow <hurikhan77@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: Plasma upgrade: Part Deux.
Date: Wed, 21 Sep 2016 05:04:18
Message-Id: 20160921070346.52ad23b9@jupiter.sol.kaishome.de
In Reply to: Re: [gentoo-user] Re: Plasma upgrade: Part Deux. by Daniel Frey
1 Am Tue, 20 Sep 2016 21:03:23 -0700
2 schrieb Daniel Frey <djqfrey@×××××.com>:
3
4 > On 09/20/2016 08:26 PM, Kai Krakow wrote:
5 > >>
6 > >> I've noticed a couple more things. One is after resume from standby
7 > >> the plasma taskbar hangs at 100% cpu for 2-3 minutes, during which
8 > >> time you can't open the K menu, click on open programs in the task
9 > >> bar or start any apps. The tray icons and clock are also frozen.
10 > >> Has anyone experienced this? It only does this after resume, it
11 > >> seems to be fine otherwise.
12 > >
13 > > Any chances you're using calendar access in plasma widgets? I'm
14 > > using calendars via akonadi-ews, and the clock widget has access to
15 > > this (also korgac integrates with the plasma bars and accesses the
16 > > calendar). This leads plasma to blocking for about 1 minute after
17 > > login or resume - but only due to heavy writes of logs about
18 > > zoneinfo that cannot be found. The problem here is that Outlook
19 > > uses very strange time zone names (which even seem to change from
20 > > version to version, I wonder how MS programmers keep track of it).
21 > > The solution was to simply symlink the missing names (which you can
22 > > extract from the X session logs and/or journal)
23 > > to /usr/share/zoneinfo/localtime and now it works and my calendar
24 > > events are even at the correct hour (and not shifted to another
25 > > time zone). For me, blocking of plasma is now gone or at least
26 > > reduced to a very short time.
27 >
28 > Well, I think I might have solved this one for now. I was using the
29 > nouveau driver and I was playing a news clip and had no sound and
30 > when I clicked on the volume control in the tray my computer
31 > hardlocked.
32 >
33 > I was able to ssh in to see that nouveau was crashing constantly
34 > trying to do what plasma was asking of it; I have installed the
35 > recommended nvidia-drivers version that was mentioned on nvidia's
36 > site and now it seems to be okay.
37 >
38 > Six or so months ago I tried both nouveau and nvidia's drivers and
39 > they were both crashing plasma every 10-20 seconds.
40
41 Strange, I never had this and use plasma since 5.2 or something...
42 Always with the proprietary driver (as I also like to play Steam games).
43
44 > >> Is there a way to speed up alt-tab switching? Often I hit alt-tab
45 > >> expecting it to switch to another app but nothing happens. I have
46 > >> to hit it two or sometimes even three (!) times to make it switch.
47 > >> This is really irritating and slows down my work flow.
48 > >
49 > > I wonder about this annoying bug, too. As a programmer this is
50 > > absolutely irritating as I do a lot of alt+tab between editors,
51 > > logs, web browsers, and documentation. :-(
52 > >
53 > > Something similar happens when switching tasks using the mouse:
54 > > Sometimes the first click on a taskbar icon is simply not fully
55 > > recognized, it just switches focus to plasma but doesn't switch the
56 > > application to front.
57 > >
58 > > Sometimes I feel like this may be related to having multiple
59 > > monitors connected.
60 >
61 > I do not have multiple monitors. I haven't seen the mouse issue yet as
62 > when alt+tab isn't working I have to resort to the dang mouse and it
63 > always works.
64
65 Well, I use multi monitor on all setups. Here at home, I use TV and
66 monitor in clone mode. Mouse switching works almost reliably here
67 (only rarely exposing the bug). At work I use two monitors side by side,
68 with a desktop across both screens (no clone mode). Only there, I'm
69 experiencing the mouse problem often, on the other hand my home system
70 is much more capable. It might well be an issue related to
71 performance of the system.
72
73 On the other hand, when using the activity switcher (not the meta+q one
74 but the one that works like alt+tab, I've set it to meta+tab), it is
75 displayed twice - it seems once for each monitor. At work, it is shown
76 on both monitors. It is shown only once as soon as I disable one
77 monitor. I've filed a bug report for it. I think multi monitor is not
78 really tested well.
79
80 https://bugs.kde.org/show_bug.cgi?id=368870
81
82 > However, on the plus side, I disabled the compositor effects on the
83 > alt-tab switching and so now it works as expected.
84 >
85 > I've attached a small screenshot, make sure what I've circled in red
86 > is NOT checked. It's under system settings -> window management ->
87 > task switcher.
88
89 Tried that. Didn't work at all at first, the current window was just
90 flashing on alt+tab. Only after manually switching with the mouse, the
91 keyboard shortcut worked reliably. That makes me think the root cause
92 is to be searched somewhere else and not really related to the
93 compositor effect.
94
95 Anyway, I switched back to the both checkboxes reversed. I prefer that
96 setup much better. I don't like alt+tab hovering the windows, and
97 without the compositor effect that setting disabled makes the hole
98 experience quite useless.
99
100
101 --
102 Regards,
103 Kai
104
105 Replies to list-only preferred.