#StackBounty: #unity #gnome #launcher #compiz Unity profile without window decorations or launchpad

Bounty: 50

From one day to another (probably after an automatic update), when I log in to my profile, I do not see window decoration or the start menu. If I use another user, everything works fine. I had this problem before, so I know it is unity and compiz related. Back then, I solved it by moving away the compizconfig directory, but this does not do the trick this time, although it seems to be a profile-related issue.

The error message reads:

Sorry, Ubuntu 16.04 has experienced an internal error.

If you notice further problems, try restarting the computer.

ExecutablePath /usr/lib/x86_64-linux-gnu/unity/compiz-config-profile-setter

Package unity 7.4.5+16.04.20190312-0ubuntu1

ProblemType: Crash

Title: compiz-config-profile-setter crashed with SIGSEGV in cssObjectGetInterface_()

.tmp.unity_support_test.0

ApportVersion: 2.20.1-ubuntu2.21

CompizPlugins: No value set for ‘/apps/compiz-1/general/screen0/options/active_plugins’

[…]

This error message appears only sometimes, the launchpad is never around though.

How do I fix my broken profile with minimal effort?

References


Get this bounty!!!

#StackBounty: #gnome #window-manager Programs are grouped with the program that launched them. How can I change that?

Bounty: 100

This morning, I launched Slack from the program list. Once it was up and running, I clicked a link therein, which launched Firefox. In fact, it launched four Firefox windows, each with many tabs, because Firefox remembers my previous session, and I’m disorganized like that.

However, in the program switcher (Alt+Tab), the Firefox windows are bundled in with the Slack window. So too in the launcher bar, where the Firefox icon shows with no dots underneath, and the Slack icon with five. I visited about:profiles in Firefox and restarted the program, but it’s still associated with Slack.

I often start Firefox by clicking a link in an email, but I’ve never had it grouped in with Thunderbird. I often start Slack from Firefox, by opening the Slack webapp, and selecting the “Open the Slack App” option therein. This sometimes causes Slack to be grouped within the Firefox windows (the opposite of what I have today).

I find this somewhat irritating. Is there an easy way to fix it? Should I be reporting this as a bug instead of / as well as asking about it here?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:    18.04
Codename:   bionic


Get this bounty!!!

#StackBounty: #gnome #usb #android How to prevent gnome pop-ups when drive is (re)connected?

Bounty: 50

MicroUSB cables are extremely finnicky when it comes to having all connectors having contact inside the microUSB female port on the phone. Every time my phone moves even slightly when developing Android apps, my phone disconnects then reconnects, opening up a new gnome window or two. Believe it or not, this is not an issue with the phone, as it happens with multiple phones. It also happens with multiple microUSB cords. The hardware’s disconnect/reconnect is not an Ubuntu issue, but the fact that there is an annoying pop-up of the disk contents every time it happens is an Ubuntu issue, especially since unlike a USB drive, I don’t need to ever use a GUI for an android phone connection. I only need it to use with command line software like adb or third-party guis like android-studio

I still want my device to mount automatically, I just don’t want gnome to issue a pop-up with its contents. Is there any way I can prevent myself from having to close 100 gnome windows after an hour of Android development?

The window is the usual file explorer, like what comes up when you run gnome-open ./


Get this bounty!!!

#StackBounty: #nvidia #gnome #xorg #multiple-monitors Gnome ignoring second monitor Ubuntu 19.10

Bounty: 200

tl;dr: I have an Ubuntu 19.10 setup that recognises both monitors (lspci shows both and I get a cursor on the second one) but xrandr -q and GNOME only see one of them. What might be the problem?


I set up a new system with a pair of GeForce RTX 2080 Ti cards and a 4K monitor connected to each via USB-C.

After installing Ubuntu 19.10, only one monitor came up. Running sudo nvidia-settings gave me a sample xconfig, which I appended to /usr/share/X11/xorg.conf.d/10-nvidia.conf. The result:

Section "OutputClass"
    Identifier "nvidia"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "AllowEmptyInitialConfiguration"
    ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
EndSection

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 435.21

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" RightOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG HDR 4K"
    HorizSync       30.0 - 135.0
    VertRefresh     56.0 - 61.0
    Option         "DPMS"
EndSection

Section "Monitor"
    # HorizSync source: unknown, VertRefresh source: unknown
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG HDR 4K"
    HorizSync       0.0 - 0.0
    VertRefresh     0.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce RTX 2080 Ti"
    BusID          "PCI:10:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce RTX 2080 Ti"
    BusID          "PCI:4:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-6"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "metamodes" "nvidia-auto-select +0+0 {AllowGSYNC=Off}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

After rebooting, I still get GNOME on the one monitor. The other monitor, however, is a black screen with just the default X cursor (the glow on the right is just reflections on the monitor):

enter image description here

I also noticed two gdm3 sessions in htop, one running:

/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3

The other running the same command line but with vt1 instead of vt2. Killing the vt2 one killed my GNOME session. Killing the other one, however, seemed to do nothing. I can even still see a cursor on the second monitor.

Afaict from Settings | Devices | Screen Display, only one monitor is present:

enter image description here

Some additional data:

$ lspci | grep -i nvidia
04:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] (rev a1)
04:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio Controller (rev a1)
04:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Controller (rev a1)
04:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU102 UCSI Controller (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] (rev a1)
0a:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio Controller (rev a1)
0a:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Controller (rev a1)
0a:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU102 UCSI Controller (rev a1)
$ xrandr -q
Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
USB-C-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   3840x2160     60.00*+  30.00  
   2560x1440     59.95  
   1920x1080     60.00    59.94  
   1600x900      60.00  
   1280x1024     60.02  
   1280x800      59.81  
   1280x720      60.00    59.94  
   1152x864      59.96  
   1024x768      60.00  
   800x600       60.32  
   720x480       59.94  
   640x480       59.94    59.93  
$ nvidia-smi
Sun Dec  8 14:19:03 2019       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 435.21       Driver Version: 435.21       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 208...  Off  | 00000000:04:00.0  On |                  N/A |
| 25%   32C    P8     6W / 260W |     39MiB / 11019MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 208...  Off  | 00000000:0A:00.0  On |                  N/A |
| 32%   41C    P8     4W / 260W |    571MiB / 11016MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      7142      G   /usr/lib/xorg/Xorg                            37MiB |
|    1      7142      G   /usr/lib/xorg/Xorg                           268MiB |
|    1      7351      G   /usr/bin/gnome-shell                         260MiB |
|    1      9360      G   gnome-control-center                           6MiB |
|    1     10505      G   ...no-sandbox --gpu-preferences=IAAAAAAAAA    34MiB |
+-----------------------------------------------------------------------------+

Question: Why is only one of my monitors being picked up by GNOME and what can I do to fix this?

UPDATE: I’ve uploaded my /var/log/Xorg.0.log. No smoking gun there, afaict.


Get this bounty!!!

#StackBounty: #ubuntu #gnome #gnome-panel #favorites Stop GNOME from randomizing window locations in its pop-out?

Bounty: 100

I’m working on Ubuntu 18.04, fully patched with dist-upgrade. I layout 4 terminals as shown below. The order of the favorite pop-out is top-to-bottom: (a) is (1) top left, (b) is (2) bottom left, (c) is (3) top right, and (d) is (4) bottom right.

enter image description here

After the favorite pop-out window closes, GNOME will randomize the order. The top-to-bottom order of the pop-out is randomized. (a) in the pop-out may become terminal (3), and (d) in the pop-out may become terminal (1). It is incredibly annoying behavior since I can’t quickly jump back to the terminal (1) by clicking the (a) pop-out.

How do I tell GNOME to stop randomizing the window layouts in the favorite pop-out?


For me, each terminal is used for a specific task. I usually have 8 or 10 terminals open. I might have Emacs open in Terminal (1), a cp command in terminal (2), and a compiler in terminal (3). I just rotate among them to get the work done.

GNOME’s behavior is incredibly annoying because I have to chase down the proper window after its been subjected to their randomization. I swear to Christ I believe they are on drugs for some of the idiotic decision they make. The whole bunch should be drug tested and fired.


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:        18.04
Codename:       bionic

$ apt-cache show ubuntu-gnome-desktop
Package: ubuntu-gnome-desktop
Architecture: amd64
Version: 0.83
Priority: optional
Section: universe/metapackages
Source: ubuntu-gnome-meta
Origin: Ubuntu
...


Get this bounty!!!

#StackBounty: #ubuntu #debian #keyboard-shortcuts #gnome #xkb How to revert keyboard layout switching shortcuts after setting them with…

Bounty: 50

I wanted to have two keyboard layouts (one for english and one for spanish), and add a shortcut for switching between them.

The solution I chose was to set the following lines in my /etc/default/keyboard file:

XKBLAYOUT="us,es"
XKBOPTION="grp:ctrl_shift_toggle"

This has turned out to be a mistake because the ctrl_shift shortcut interfers and takes precedence over all other application level shortcuts like browser’s ctrl+shift+tab and vi’s ctrl+shift+insert.

I haven’t found a way to revert this change and have it persist in between shutdowns.

Here are the methods I have tried:
1) Removing the XKBOPTION line from /etc/default/keyboard
2) Running the command dpkg-reconfigure keyboard
3) Running the command setxkbmap -option. This works but is reset upon restarting.
4) Configuring one single layout by adding the line XKBLAYOUT and adding the alternative layout via GNOME and using the GNOME shortcut (Super space). The switch has no effect and is reset upon restarting.

I don’t know where these changes are stored in between installs, I have ran grep with searching for terms like XKBOPTION,ctrl_shift_toggle but I can’t seem to find it. All I can find is that the setxkbmap -print command shows the ctrl_shift_toggle option:

xkb_keymap {
    xkb_keycodes  { include "evdev+aliases(qwerty)" };
    xkb_types     { include "complete"  };
    xkb_compat    { include "complete"  };
    xkb_symbols   { include "pc+us+es:2+us:3+inet(evdev)+grp(ctrl_shift_toggle)"    };
    xkb_geometry  { include "pc(pc105)" };
};

However, as mentioned, I cannot find the file responsible for the ctrl_shift_toggle configuration.

Note: The question is looking for an answer that can revert the state of the keyboard setting either to the original setting, or to the desired configuration. Reinstalling the OS or a solution that starts from a clean install is not considered an optimal solution. The reason for this is that, as a superuser, I want to have deep control of my system.

Thank you for your time.


Get this bounty!!!

#StackBounty: #gnome #keyboard #shortcut-keys #keyboard-layout remap Caps + L to dash

Bounty: 100

I want to remap the four keys ()-= to Caps+jkl; respectively.
The idea is to not leave the home row for typing these characters which are very common in programming.

Any ideas how to go about it?

What I’ve tried already:

  1. https://github.com/simos/keyboardlayouteditor – Installation has syntax error
  2. https://www.bedroomlan.org/projects/evrouter/ – No support for multi keys
  3. editing /usr/share/X11/xkb/symbols/pc – I don’t see an option for combinations, and couldnn’t figure it out from the docs
  4. evdevremapkeys – no support as described in this issue
  5. xdotool – works but it’s very slow …
  6. Mapping directly in vim – that would be my fallback, tho I want this available system-wide

Any help appreciated, probably some guidance would be enough for me to crack this one.

Thanks!


Get this bounty!!!

#StackBounty: #gnome #power-management #lock-screen #gdm How to disable screen power saving in GDM3 login screen?

Bounty: 50

On the desktop login screen (GDM3) my computer will put the screens into power saving mode after 15 seconds of inactivity. I would ideally like to disable power saving in this situation, or at least lengthen the period.

I have tried disabling all power saving options that I can find in gsettings, both for my user and for root, but this has not affected the 15 second timeout.

What else can I try?

I’m running Ubuntu 19.04 with Gnome Shell 3.32.2. I have found various older questions concerned with the same issue, but they all relate to LightDM:


Get this bounty!!!