InvisibleShadowGhost's questions

I own a Dell XPS 9370 laptop with an i7 8550U.

I recently noticed, that my performance decreases quite significantly when my battery percentage drops under 20%. This especially visible on GNOMEs animations, which start to get pretty laggy. This happens in all Ubuntu versions from 18.04 to 19.10 I tested.

I tried to investigate a bit and observed that my CPU frequency does not scale up properly anymore, it does not reach the max frequency of my processor (4 GHz) by far after my battery life falls under 20%. When running with over 20%, it scales properly up to the 4 GHz.

Setting the CPU governor to performance removes that impact but is obviously not a solution, as that has a serious impact on the battery life.

So all in all it feels like a power saving feature of the governor. Is there a possibility to turn it off or move the battery percentage that kicks in? Maybe some kernel parameter?
Any additional ideas to solve that problem?

Cheers in advance

P.S: I uninstalled all additional power saving tools I know of (tlp etc.), but that did not help either.

I own an XPS 9370 and often find the following in my dmesg

[40705.581409] mce: CPU5: Core temperature above threshold, cpu clock throttled (total events = 950)
[40705.581410] mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 950)
[40705.581411] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581412] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581413] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581414] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581445] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581446] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581447] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.581448] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 3843)
[40705.585426] mce: CPU5: Core temperature/speed normal
[40705.585428] mce: CPU4: Package temperature/speed normal
[40705.585428] mce: CPU2: Package temperature/speed normal
[40705.585429] mce: CPU0: Package temperature/speed normal
[40705.585430] mce: CPU6: Package temperature/speed normal
[40705.585431] mce: CPU3: Package temperature/speed normal
[40705.585431] mce: CPU1: Core temperature/speed normal
[40705.585432] mce: CPU7: Package temperature/speed normal
[40705.585433] mce: CPU1: Package temperature/speed normal
[40705.585434] mce: CPU5: Package temperature/speed normal
[41528.582396] mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 1547)
[41528.582397] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1547)
[41528.582398] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582399] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582400] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582400] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582403] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582407] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582416] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.582417] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4112)
[41528.585420] mce: CPU0: Core temperature/speed normal
[41528.585420] mce: CPU4: Core temperature/speed normal
[41528.585421] mce: CPU2: Package temperature/speed normal
[41528.585422] mce: CPU5: Package temperature/speed normal
[41528.585423] mce: CPU1: Package temperature/speed normal
[41528.585442] mce: CPU4: Package temperature/speed normal
[41528.585443] mce: CPU0: Package temperature/speed normal
[41528.585444] mce: CPU6: Package temperature/speed normal
[41528.585445] mce: CPU7: Package temperature/speed normal
[41528.585445] mce: CPU3: Package temperature/speed normal
[42028.738360] mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 977)
[42028.738360] mce: CPU5: Core temperature above threshold, cpu clock throttled (total events = 977)
[42028.738384] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738387] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738389] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738389] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738390] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738391] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738393] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.738393] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4144)
[42028.739359] mce: CPU1: Core temperature/speed normal
[42028.739359] mce: CPU5: Core temperature/speed normal
[42028.739360] mce: CPU1: Package temperature/speed normal
[42028.739360] mce: CPU5: Package temperature/speed normal
[42028.739391] mce: CPU2: Package temperature/speed normal
[42028.739391] mce: CPU6: Package temperature/speed normal
[42028.739393] mce: CPU4: Package temperature/speed normal
[42028.739393] mce: CPU0: Package temperature/speed normal
[42028.739394] mce: CPU7: Package temperature/speed normal
[42028.739394] mce: CPU3: Package temperature/speed normal
[42366.286406] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1589)
[42366.286407] mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 1589)
[42366.286408] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286409] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286411] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286412] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286413] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286414] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286415] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.286417] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 4194)
[42366.289376] mce: CPU0: Core temperature/speed normal
[42366.289377] mce: CPU5: Package temperature/speed normal
[42366.289378] mce: CPU7: Package temperature/speed normal
[42366.289379] mce: CPU3: Package temperature/speed normal
[42366.289379] mce: CPU2: Package temperature/speed normal
[42366.289380] mce: CPU4: Core temperature/speed normal
[42366.289381] mce: CPU1: Package temperature/speed normal
[42366.289381] mce: CPU6: Package temperature/speed normal
[42366.289382] mce: CPU4: Package temperature/speed normal
[42366.289383] mce: CPU0: Package temperature/speed normal

But at the same time, sensors returns the following at the same moment when I get those logs

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +55.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +54.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +53.0°C  (high = +100.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +25.0°C  (crit = +107.0°C)

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +47.5°C  

which is far away from critical temperatures. Can somebody clear this up fro me?

Edit: Added the turbostat startup information

turbostat version 18.07.27 - Len Brown <[email protected]>
CPUID(0): GenuineIntel 0x16 CPUID levels; 0x80000008 xlevels; family:model:stepping 0x6:8e:a (6:142:10)
CPUID(1): SSE3 MONITOR - EIST TM2 TSC MSR ACPI-TM HT TM
CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, HWPepp, No-HWPpkg, EPB
cpu6: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH TURBO)
CPUID(7): SGX
cpu6: MSR_IA32_FEATURE_CONTROL: 0x00040005 (Locked SGX)
CPUID(0x15): eax_crystal: 2 ebx_tsc: 166 ecx_crystal_hz: 0
TSC: 1992 MHz (24000000 Hz * 166 / 2 / 1000000)
CPUID(0x16): base_mhz: 2000 max_mhz: 4000 bus_mhz: 100
cpu6: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination DISable-EPB DISable-OOB)
RAPL: 17476 sec. Joule Counter Range, at 15 Watts
cpu6: MSR_PLATFORM_INFO: 0x4043df1011400
4 * 100.0 = 400.0 MHz max efficiency frequency
20 * 100.0 = 2000.0 MHz base frequency
cpu6: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
cpu6: MSR_TURBO_RATIO_LIMIT: 0x25252828
37 * 100.0 = 3700.0 MHz max turbo 4 active cores
37 * 100.0 = 3700.0 MHz max turbo 3 active cores
40 * 100.0 = 4000.0 MHz max turbo 2 active cores
40 * 100.0 = 4000.0 MHz max turbo 1 active cores
cpu6: MSR_CONFIG_TDP_NOMINAL: 0x00000012 (base_ratio=18)
cpu6: MSR_CONFIG_TDP_LEVEL_1: 0x00080050 (PKG_MIN_PWR_LVL1=0 PKG_MAX_PWR_LVL1=0 LVL1_RATIO=8 PKG_TDP_LVL1=80)
cpu6: MSR_CONFIG_TDP_LEVEL_2: 0x001400c8 (PKG_MIN_PWR_LVL2=0 PKG_MAX_PWR_LVL2=0 LVL2_RATIO=20 PKG_TDP_LVL2=200)
cpu6: MSR_CONFIG_TDP_CONTROL: 0x00000000 ( lock=0)
cpu6: MSR_TURBO_ACTIVATION_RATIO: 0x00000011 (MAX_NON_TURBO_RATIO=17 lock=0)
cpu6: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3, UNdemote-C1, demote-C3, demote-C1, locked, pkg-cstate-limit=8 (unlimited))
cpu6: cpufreq driver: intel_pstate
cpu6: cpufreq governor: powersave
cpufreq intel_pstate no_turbo: 0
cpu6: MSR_MISC_FEATURE_CONTROL: 0x00000000 (L2-Prefetch L2-Prefetch-pair L1-Prefetch L1-IP-Prefetch)
cpu0: MSR_PM_ENABLE: 0x00000001 (HWP)
cpu0: MSR_HWP_CAPABILITIES: 0x01081228 (high 40 guar 18 eff 8 low 1)
cpu0: MSR_HWP_REQUEST: 0x80002804 (min 4 max 40 des 0 epp 0x80 window 0x0 pkg 0x0)
cpu0: MSR_HWP_INTERRUPT: 0x00000000 (Dis_Guaranteed_Perf_Change, Dis_Excursion_Min)
cpu0: MSR_HWP_STATUS: 0x00000000 (No-Guaranteed_Perf_Change, No-Excursion_Min)
cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x00000006 (balanced)
cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.000061 Joules, 0.000977 sec.)
cpu0: MSR_PKG_POWER_INFO: 0x00000078 (15 W TDP, RAPL 0 - 0 W, 0.000000 sec.)
cpu0: MSR_PKG_POWER_LIMIT: 0x420198009c80d8 (UNlocked)
cpu0: PKG Limit #1: ENabled (27.000000 Watts, 24.000000 sec, clamp DISabled)
cpu0: PKG Limit #2: DISabled (51.000000 Watts, 0.002441* sec, clamp DISabled)
cpu0: MSR_DRAM_POWER_LIMIT: 0x5400de00140000 (UNlocked)
cpu0: DRAM Limit: DISabled (0.000000 Watts, 1.000000 sec, clamp DISabled)
cpu0: MSR_PP0_POLICY: 0
cpu0: MSR_PP0_POWER_LIMIT: 0x00000000 (UNlocked)
cpu0: Cores Limit: DISabled (0.000000 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_PP1_POLICY: 0
cpu0: MSR_PP1_POWER_LIMIT: 0x00000000 (UNlocked)
cpu0: GFX Limit: DISabled (0.000000 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x02640000 (100 C)
cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x8828080a (60 C)
cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x00000003 (100 C, 100 C)
cpu6: MSR_PKGC3_IRTL: 0x0000884e (valid, 79872 ns)
cpu6: MSR_PKGC6_IRTL: 0x00008876 (valid, 120832 ns)
cpu6: MSR_PKGC7_IRTL: 0x00008894 (valid, 151552 ns)
cpu6: MSR_PKGC8_IRTL: 0x000088fa (valid, 256000 ns)
cpu6: MSR_PKGC9_IRTL: 0x0000894c (valid, 339968 ns)
cpu6: MSR_PKGC10_IRTL: 0x00008bf2 (valid, 1034240 ns)

Edit2: Added stress test

I am currently running Ubuntu 19.04 (Gnome 3.32) and experience that some programs (e.g. Chrome and OBS) don't show a tray icon. Rambox or Skype e.g. work perfectly.

Does anybody have an idea?

Does anybody have an idea how to get the TAB-completion for zsh working for the snap command? According to the answer in How can I enable auto-completion for the snap command? it should be working right now but it does not complete at all for me for the snap command

I would like to prevent my PC from going to sleep while Spotify is playing a song. If Spotify is open but does not play a song, the PC should go to sleep regularly.
So is it possible to add a lock using systemd-inhibt (or is there a better alternative) whenever Spotify starts a song and remove it when the song is stopped?

Does anyone know whether there is an Ubuntu equivalent to the ms-office-online package from the AUR ms-office-online 20.1.0-2?

Even though I set git config --global diff.ignoreSubmodules git status does not ignore changes in submodules and still shows them as modified content. My git version is 2.20.1.
Does anybody know what I'm doing wrong?

I have a Dell XPS 9370, which is known to have only one camera. But ls /dev/video* results in /dev/video0 /dev/video1 /dev/video2 /dev/video3, so four different camera devices.
These four cameras bubble up to the applications, e.g. Skype which lists four cameras, but just the first one (/dev/video0) works.

Does anybody know where the other entries come from? Or how to hide them from higher layers?

I run Ubuntu 18.10 with Gnome 3.30.1 on an XPS 9370.
If I have music playing (via the built-in speakers) and connect my docking station (a Dell WD15) the music automatically transitions to the speakers connected to the dock (it has a line-out output). The problem is, that Gnome does not recognize it: Even if Gnome shows the line-out output in the sound devices overview, it still has the internal speakers selected and the multimedia keys still adjust the internal speaker.

Has anyone an idea how to fix it?

I want Ctrl-Alt-T to focus (bring back to front) an existing terminal window if there is no running process in it (e.g. top). If there is no terminal window without a running process, a new window should be opened. Is that possible?

Edit: It's not a duplicate. The further going idea is the following:
I do not want to get a terminal where I can not execute a command right now because it's busy (a process is running in it, e.g top). So my wish was to get only a already opened terminal if there is no process in it.

I'm using Ubuntu 18.10 with Gnome. Sometimes, all two or three days, Gnome crashes after resuming from idle screensaver or suspend. I manually have to press "Strg + Alt + F1" and login again to be able to continue because I only see a purple screen. The last output of journalctl -b /usr/bin/gnome-shell is

Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0fb60' has no handler with id '215849'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0fb60' has no handler with id '215850'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a73350' has no handler with id '215851'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a73350' has no handler with id '215852'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a72b90' has no handler with id '215853'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a72b90' has no handler with id '215854'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44440' has no handler with id '215855'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44440' has no handler with id '215856'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287b340' has no handler with id '215857'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287b340' has no handler with id '215858'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a723d0' has no handler with id '215861'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a723d0' has no handler with id '215862'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287a3c0' has no handler with id '215863'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287a3c0' has no handler with id '215864'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287ab80' has no handler with id '215865'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287ab80' has no handler with id '215866'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287bb00' has no handler with id '215867'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e19287bb00' has no handler with id '215868'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44c00' has no handler with id '215869'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b44c00' has no handler with id '215870'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b453c0' has no handler with id '215871'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192b453c0' has no handler with id '215872'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929af3f0' has no handler with id '215875'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929af3f0' has no handler with id '215876'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929afbb0' has no handler with id '215877'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e1929afbb0' has no handler with id '215878'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0e420' has no handler with id '215879'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: ../../../../gobject/gsignal.c:2641: instance '0x55e192a0e420' has no handler with id '215880'
Nov 10 17:05:42 XPS-9370 gnome-shell[6953]: Object Meta.WindowActor (0x55e192a0ebe0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from 
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: == Stack trace for context 0x55e19092c210 ==
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #0   7fff6ed0b640 b   resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f8be5bcc040 @ 25)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #1   7fff6ed0b6e0 b   /usr/share/gnome-shell/extensions/[email protected]/theming.js:416 (7f8bb2e65040 @ 20)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #2   7fff6ed0b7d0 b   self-hosted:261 (7f8be5bc1dc0 @ 223)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #3   7fff6ed0b890 b   /usr/share/gnome-shell/extensions/[email protected]/theming.js:415 (7f8bb2e60f70 @ 172)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #4   7fff6ed0c510 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #5   55e198282308 i   /usr/share/gnome-shell/extensions/[email protected]/theming.js:424 (7f8bb2e650d0 @ 17)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #6   7fff6ed0d480 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #7   55e198282288 i   /usr/share/gnome-shell/extensions/[email protected]/theming.js:89 (7f8bb2e60790 @ 42)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #8   7fff6ed0e3f0 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #9   55e198282200 i   /usr/share/gnome-shell/extensions/[email protected]/docking.js:456 (7f8bb2e565e0 @ 82)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #10   7fff6ed0f360 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #11   55e198282168 i   /usr/share/gnome-shell/extensions/[email protected]/docking.js:1784 (7f8bb2e5c9d0 @ 116)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #12   7fff6ed102d0 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #13   55e1982820e8 i   /usr/share/gnome-shell/extensions/[email protected]/docking.js:1903 (7f8bb2e5cdc0 @ 37)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #14   7fff6ed11240 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #15   55e198282068 i   /usr/share/gnome-shell/extensions/[email protected]/extension.js:31 (7f8bb2e4ad30 @ 12)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #16   55e198281fa8 i   resource:///org/gnome/shell/ui/extensionSystem.js:83 (7f8be585a040 @ 436)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #17   55e198281f28 i   resource:///org/gnome/shell/ui/extensionSystem.js:354 (7f8be585ab80 @ 13)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #18   7fff6ed123b0 b   self-hosted:261 (7f8be5bc1dc0 @ 223)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #19   55e198281ea8 i   resource:///org/gnome/shell/ui/extensionSystem.js:353 (7f8be585aaf0 @ 64)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #20   55e198281e28 i   resource:///org/gnome/shell/ui/extensionSystem.js:371 (7f8be585ac10 @ 87)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #21   7fff6ed134f0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7f8be5bc18b0 @ 386)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #22   7fff6ed14340 b   resource:///org/gnome/shell/ui/sessionMode.js:208 (7f8be5541ca0 @ 254)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #23   7fff6ed14fc0 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #24   55e198281c10 i   resource:///org/gnome/shell/ui/sessionMode.js:177 (7f8be5541af0 @ 100)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #25   7fff6ed15f40 b   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #26   55e198281b68 i   resource:///org/gnome/shell/ui/screenShield.js:1210 (7f8be55288b0 @ 105)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #27   55e198281ac0 i   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #28   55e198281a40 i   resource:///org/gnome/shell/ui/screenShield.js:1200 (7f8be5528790 @ 73)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #29   55e198281998 i   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #30   55e198281908 i   resource:///org/gnome/shell/ui/screenShield.js:627 (7f8be5527040 @ 83)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #31   55e198281860 i   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #32   55e1982817a8 i   resource:///org/gnome/shell/ui/screenShield.js:687 (7f8be55271f0 @ 415)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #33   55e198281700 i   resource:///org/gnome/gjs/modules/_legacy.js:82 (7f8be5bb0b80 @ 71)
Nov 10 17:05:42 XPS-9370 org.gnome.Shell.desktop[6953]: #34   55e198281640 i   self-hosted:979 (7f8be5bf01f0 @ 440)
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_dir_open_with_errno: assertion 'path != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_dir_open_with_errno: assertion 'path != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Nov 10 17:05:58 XPS-9370 gnome-shell[7295]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1564]: reference to undefined property "MetaWindowXwayland"
Nov 10 17:06:12 XPS-9370 gnome-shell[7295]: Connection to xwayland lost

Can someone help?

Edit 1: I think I see connection with the connecting/disconnecting of an external monitor. At least, this seems to make the problem appear more often.

Edit 2: sudo blkid returns

/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/nvme0n1: PTUUID="4ac6dcee-933c-449a-983f-b0ede0f24c5d" PTTYPE="gpt"
/dev/nvme0n1p1: SEC_TYPE="msdos" UUID="15E7-DD98" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="1d435577-b51a-4491-b78e-b33b18783cfc"
/dev/nvme0n1p2: LABEL="OS" UUID="15F8-5108" TYPE="vfat" PARTLABEL="fat32" PARTUUID="266e101c-75bc-4d67-82b4-33dfda5d4cf6"
/dev/nvme0n1p3: UUID="7ea246ac-cdde-4c3f-acc0-40ab63d8dd47" TYPE="ext4" PARTUUID="4bd55ae7-f76f-4c8e-a8fd-3dd795e29eef"
/dev/nvme0n1p4: UUID="71013368-e9f9-4063-b176-fd9d4a73e524" TYPE="swap" PARTUUID="bf879d7d-66cf-419d-99a6-e09b192cd5eb"
/dev/nvme0n1p5: UUID="aef0d414-56c5-44ba-9dd2-55935e35b816" TYPE="ext4" PARTUUID="e9b8805d-c543-4abd-935d-2a5cff34968c"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"

cat /etc/fstab returns

# <file system> <mount point> <type> <options> <dump> <pass>

UUID=7ea246ac-cdde-4c3f-acc0-40ab63d8dd47   /   ext4    errors=remount-ro   0   1
UUID=15E7-DD98  /boot/efi   vfat    umask=0077  0   1
UUID=71013368-e9f9-4063-b176-fd9d4a73e524   none    swap    sw  0   #0
UUID=aef0d414-56c5-44ba-9dd2-55935e35b816   /home   ext4    defaults 0  2

cat /etc/initramfs-tools/conf.d/resume returns

RESUME=UUID=71013368-e9f9-4063-b176-fd9d4a73e524

and free -h returns

              total        used        free      shared  buff/cache   available
Mem:           15Gi       6,3Gi       4,3Gi       1,1Gi       4,7Gi       7,6Gi
Swap:          31Gi        11Mi        31Gi

Probably nobody can give me a definite answer, but does anybody if we are going to see qt5-default 5.11.2 in the official repositories of Ubuntu 18.10 at some point?

Thunderbird doesn't show the unread counter on its symbol in the dock for me on Ubuntu 18.04 and 18.10 (both with gnome). Is that normal? If not, does anybody know what the problem could be?

I have thunderbird with the lightning and the google calendar extension. It works almost perfect, which means that the tasks and events are imported correctly, the calendars synchronizes properly and so on. The only thing that does not get imported are the so called google reminders. Can someone help how to get them imported as well? I tested with the newest version of thunderbird provided in the repos (52.9.1) on Ubuntu 18.04 and Ubuntu 18.10.

My external mouse scrolls very slow (it's a MX Anywhere 2) but the scrolling of my internal touchpad is absolutely fine (for me). Therefore I want to change the scroll speed of my external mouse only which means that imwheel is not an alternative for me. I looked a bit further and found the following post (Increase mouse wheel scroll speed) with the following solution

libinput seems to be included with Wily Werewolf (15.10) where you need to install the package xserver-xorg-input-libinput. After you installed libinput with

$ sudo apt-get install xserver-xorg-input-libinput it should be used for every input after you restarted the Xorg (logout would be sufficient). Now that you are using libinput you are able to adjust the settings of your mouse. You can find a full tutorial in the file /lib/udev/hwdb.d/70-mouse.hwdb. Let me cover here only the basics.

The following steps are need to be done as root. Because of that I am friendliy reminding you that everything you do you need to take responibility.

First get the vendor id and the product id using lsusb. Here with a MX 518 Logitech Mouse as example. If you have the following line in the output of lsusb.

Bus 005 Device 002: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse The is 046d and the is c051.

Then create a File that looks like the following with gksudo gedit /etc/udev/hwdb.d/71-mouse-local.hwdb

mouse:usb:vp:name:*: MOUSE_WHEEL_CLICK_ANGLE=?? For example this file for the Logitech MX 518 example above:

mouse:usb:v046dpc051:name:*: MOUSE_WHEEL_CLICK_ANGLE=30 This file sets the mouse wheel click angle to 30° (default is usually 15). To use this setting, update the hwdb with the following commands:

udevadm hwdb --update udevadm trigger /dev/input/event${id} One can figure out the ${id} using xinput (look out for the id of your mouse) and then run xinput list-props ${xinput_id}.

For some reason that does not affect my scrolling at all. Does anybody have an idea how to fix it?

is it possible to set different blank screen timeouts in Ubuntu 18.04 with Gnome when on battery or ac? The power settings menu provides only one field which is applied always, no matter of the current mode.

This question was already asked for the Unity desktop a while ago (How can I set a different screen timeout time when on battery than if I am plugged in?) and they did not find a solution but I had the hope that that might have changed with Gnome now.

I have a Dell XPS 13 9370 with an i7-8550u CPU which should handle Gnome without any issues. The Ubuntu version is 18.04. But now experience the following problem: When setting the scaling governor to powersave the activity overview animation is very laggy (that one you access by pressing the Super key only). Furthermore it feels a bit strange for me that my system idles with a CPU frequency of 800 MHz but the CPU specification says that the base frequency is 1.8 GHz. If I set the governor to performance those animations are absolutely smooth. The problem is that the CPU now idles at around 3 GHz which results in a high battery consumption.

So what's exactly my question: Is it normal that exactly that Gnome animation is laggy? If so, can we expect an improvement in upcoming versions? Are the configurations with the intel_pstate driver correct? Why is the CPU not able to increase the frequency fast enough to make this animation smooth? Could I maybe disable this specific animation? Is it normal that my CPU idles with a lower frequency than its description says?

Best regards

Is there a way/extension to add a suspend entry (besides the Cancel, Restart and Power Off buttons) to the interactive menu when the physical power button is pressed in gnome?

Edit: I am not looking for the suspend button in the menu in the top right corner where suspend can be accessed using the Alt button.

The output of ifconfig is the following

wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 192.168.178.43  netmask 255.255.255.0  broadcast 192.168.178.255
    inet6 xxxx::xxxx  prefixlen 64  scopeid 0x0<global>
    inet6 yyyy::yyyy  prefixlen 64  scopeid 0x0<global>
    inet6 zzzz::zzzz  prefixlen 64  scopeid 0x20<link>
    ether aa:bb:cc:dd:ee:ff txqueuelen 1000  (Ethernet)
    RX packets 10043888  bytes 13826164373 (13.8 GB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 3274278  bytes 382981422 (382.9 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Why does one interface need/have three ip v6 addresses?

/etc/init.d/cpufrequtils has the following comment

 and which limits to set. Both MIN_SPEED and MAX_SPEED must be values
 listed in:
   cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
 a value of 0 for any of the two variables will disabling the use of 
 that limit variable.

But the file /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies does not exist for me? Do you have it? Where could I get a fitting frequency?

Best regards