How to debug two things

[Mitch Golden]

On Wed, 9 Mar 2016, Valorie Zimmerman wrote:

> On Tue, Feb 9, 2016 at 8:16 PM, Mitch Golden <mgolden at mitchgolden.com> wrote:
>> On Tue, 2 Feb 2016, Achim Bohnet wrote:
>>
>>> Valorie reminded me ...
>>>
>>> On Monday 18 Jan 2016 11:42:48 Mitch Golden wrote:
>>>>
>>>> I have been using KDE5 since the 14.10 dual release, and there are two
>>>> bugs that persist that I would like to tackle.
>>>>
>>>> 1) Most though not all of the time when I log out/shut down and then log
>>>> in again, if I had a konsole open in the old session it will not be there
>>>> in the new.  I am fairly sure that this is due to a crash in konsole when
>>>> it receives the shutdown signal.  I believe this because once or twice I
>>>> have seen the crash reporter open just before the system turned off.
>>>
>>>
>>> I've once read a long analysis what goes wrong with konole session
>>> management
>>> and session management in general.  Worth reading, saves you lots of time
>>> I'm
>>> sure but could not find it right now. Good luck with google ;-)
>>
>>
>> Wow, I figured out how to reproduce the problem, and I think I know why no
>> one else might have seen this.
>>
>> To start with, I should note that my machine has an nVidia card (a GEForce
>> GTX 560M) and I use the nVidia proprietary driver.
>>
>> I have long noticed that for some reason, Firefox (my preferred browser)
>> makes the graphics card spin up all the time.  The slightest touch on the
>> scroll bar, for example, sends the GPU clock to the highest rate, which
>> causes the GPU to run quite hot and the fan to spin up.
>>
>> To counter this, I add this to the xorg.conf
>>
>> Section "Device"
>>     Identifier     "Device0"
>>     Driver         "nvidia"
>>     VendorName     "NVIDIA Corporation"
>>     Option         "RegistryDwords" "PowerMizerEnable=0x1;
>> PerfLevelSrc=0x2222; PowerMizerDefault=0x3; PowerMizerDefaultAC=0x3"
>>     Option         "Coolbits" "9"
>>     Option         "UseEdidDpi" "FALSE"
>>     Option         "DPI" "96 x 96"
>> EndSection
>>
>> This pegs the clock speed to its lowest level, which is fine except for
>> watching videos.
>>
>> So, when these powermizer settings are in effect WHEN THE MACHINE IS
>> STARTING UP (!) and there is a full screen firefox open, konsole fails to
>> reopen - even if the settings were not in effect when the machine was shut
>> down.  It will often, though not always, fail to reopen even if konsole is
>> the only thing on the desktop.
>>
>> This is new to kde5 - everything was fine in kde4.
>>
>> So, my question is: anyone know where should I report this bug? Is it a
>> konsole problem or a plama problem?
>>
>>   - Mitch Golden
>
> Mitch if this is still happening, report it -- upstream. It seems
> clear from your explanation that this is not a packaging bug, so just
> go to bugs.kde.org and report against Konsole. If that is the wrong
> component, the devels will move it. This could be a problem in session
> management too, and I think but am not sure that is covered by Plasma.
> In any case, just put the information you gave us to the KDE devels in
> your bug report.
>
> It is best to always report, even if you aren't precisely sure where
> it should be. One note: the single-sign-on system for KDE does not yet
> cover bko, so if you've never logged in there, you will need to create
> a login.
>
> Valorie
>
> PS: There is no KDE5. Plasma 5, please!

Agreed, it's not a packaging problem - and I already reported it upstream. 
It's really weird bug.  I hope that it has other manifestations than mine, 
because otherwise it'll probably never get fixed.  I can't even figure out 
what to look at to point out what the problem is.

   - Mitch