keddad's questions

I've got a Lenovo IdeaPad 5i 15IIL05 with Intel UHD graphics, running Ubuntu 20.04.1. I want to connect it to an external monitor (Acer Gaming Nitro VG270U) via HDMI.

When connected, it does work - however, the highest possible resolution the system suggests is 1920x1080, when the screen itself supports 2560 x 1440. It is definitely not a problem with a cable or the monitor itself - when connected to another laptop (Lenovo Ideapad 3gen with AMD Renoir iGPU), running Ubuntu 21.04, everything worked well.

I also don't think it is a problem with the installation itself. Before Ubuntu, this laptop was running Arch-based distro (Endeavour OS), where the same problem occurred.

Usually then facing some issues like this I'd start by checking what xrandr tells me about the screens connected. However, the laptop is running Wayland, so it doesn't work - and, as far as I know, there is no tool to replace it. I don't really know what can cause this issue. Here is some system information:

corny@warri:~$ lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation Device 8a56 (rev 07)

corny@warri:/sys/class/drm/card0-HDMI-A-1$ cat modes 
1920x1080
1920x1080
1920x1080
1920x1080i
1920x1080i
1920x1080
1920x1080i
1920x1080
1920x1080
1680x1050
1280x1024
1280x1024
1440x900
1280x960
1152x864
1280x720
1280x720
1280x720
1280x720
1280x720
1024x768
1024x768
1024x768
832x624
800x600
800x600
800x600
800x600
720x576
720x480
720x480
720x480
720x480
720x480
640x480
640x480
640x480
640x480
640x480
640x480
720x400

Where is also a suggestion of manually setting the resolution with video kernel boot parameter. However, I've tried several naming options (card0-HDMI-A-1, HDMI-A-1, HDMI-1), and it doesn't change anything - instead, it causes the internal screen to display some extremely glitched images.

I've also seen a suggestion to create custom edid and make the system use it. I haven't tried it (yet), however, I don't really see how that would help - if another laptop can "generate" valid EDID, this one should too.

What can I do in this situation? What can possibly cause such a problem?

Update: That is probably not a X11/Wayland issue - booting in X11 doesn't help, neither does adding custom resolution with xrandr --newmode.

Update: using custom EDID didn't help, either.

I've wanted to edit some shortcuts, so I added a keybind to my ~/.config/openbox/lxqt-rc.xml, under <keyboard>

<keybind key="W-S-q">
      <action name="Close" />
</keybind>

Sounds pretty simple, but it doesn't apply the changes after openbox --reconfigure, as well as after reboot. XML in the file is not malformed, according to some online checker, so that's not the issue. In fact, I don't see any errors in journalctl. Other keybinds I add there also don't seem to work. It's even weirder since I copied it from my old config which worked fine under Manjaro. The only similar thing I found is this question, but I don't have any keybindings conflicting, so that's not the case. What am I doing wrong here?

I got a fresh Kubuntu 20.04 installation. I've got some snaps out of the box, and one of those confuses me:

Name               Version                     Rev   Tracking       Publisher   Notes
bitwarden          1.18.0                      25    latest/stable  bitwarden✓  -
core18             20200427                    1754  latest/stable  canonical✓  base
gnome-3-28-1804    3.28.0-17-gde3d74c.de3d74c  128   latest/stable  canonical✓  -
gtk-common-themes  0.1-36-gc75f853             1506  latest/stable  canonical✓  -
snapd              2.45.1                      8140  latest/stable  canonical✓  snapd

Why do I have gnome-3-28-1804 snap installed out of the box when I run Kubuntu with KDE Plasma? I'd expect it when running Ubuntu, but seeing it on Kubuntu is weird.

So, I've got this weird Nvidia + Intel combination, where HDMI is wired to Nvidia card, so I can't use HDMI without switching to Nvidia driver. When I was using 19.10, it was as simple as opening Nvidia Settings and enabling Nvidia (Perofrmance mode) in PRIME Profiles. But now it doesn't work! If I switch the GPUs it doesn't enable the screen. It doesn't even show nvidia-specific settings which were there earlier, like GPU frequencies, connected monitors, all that stuff. Here is how it looks like:

Here is lshw -c video output:

*-display                 
       description: VGA compatible controller
       product: GP107M [GeForce GTX 1050 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:16 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:4000(size=128) memory:b4080000-b40fffff
  *-display
       description: VGA compatible controller
       product: HD Graphics 630
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 04
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:133 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff

lspci reports I'm using Nvidia driver:

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:591b] (rev 04)
    DeviceName: Intel Kabylake HD Graphics GT2
    Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:836b]
    Kernel driver in use: i915
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1)
    DeviceName: NVIDIA GeForce GTX 1050
    Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:836b]
    Kernel driver in use: nvidia

Software and updates window tells me same thing: I'm running nvidia-driver-440. What is broken here and how do I fix it?

UPD: It wasn't an upgrade from older system, I made a clean install

I'm running Kubuntu 18.04, and I want to do some system profiling. My main goals are to improve startup speed and power usage. What instruments can I use to profile daemons/processes to get the time they took on system startup or see their usage of CPU during normal operation? It would also be great if I had some tools to monitor disk/network usage, since these operations are pretty battery-hungry too.

When I do

apt-get install chromium-browser

it downloads some .deb file, and then installs a snap package:

Selecting previously unselected package chromium-browser.
(Reading database ... 227048 files and directories currently installed.)
Preparing to unpack .../chromium-browser_77.0.3865.120-0ubuntu1~snap1_amd64.deb
...
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
Warning: /snap/bin was not found in your $PATH. If you've not restarted your
         session since you installed snapd, try doing that. Please see
         https://forum.snapcraft.io/t/9469 for more details.

chromium 78.0.3904.70 from Canonical✓ installed
=> Snap installation complete
Unpacking chromium-browser (77.0.3865.120-0ubuntu1~snap1) ...
Setting up chromium-browser (77.0.3865.120-0ubuntu1~snap1) ...
Processing triggers for mime-support (3.63ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
(base) keddad@keddad:~$

But I didn't ask it to get me chromium via snap, I wanted to get a normal .deb package. It works, after all, but it just feels wrong. If I want to get a snap, I use snap, not apt. Why such behavior is considered normal?

I've recently found out that running

apt list --installed | grep i386 | wc -l

Says that I've got 186 i386 packages. Since my system is 64bit, it is probably better to install 64 bit versions instead. So, how do I automatically install amd64 packages instead of my i386 ones, where possible? If there are any way to automatically build the rest which doesn't have prebuilt binaries? I guess some packages can not really be changed, like wine32 or steam, but I suppose most of them can be changed.

Running Ubuntu 19.10 with i3wm, I've got these lines it me /etc/default/grub which should theoretically make GRUB to wait for 5s without showing up and then booting the OS:

GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5
GRUB_HIDDEN=1

Thing is, it still shows up and has a load timeout (Time to load a default boot option) of 30s. How do I fix this behavior?

UPD: I added

GRUB_RECORDFAIL_TIMEOUT=5

to my config, and now load timeout is 5s, so I suppose grub just thinks that boot failed even though it was OK. Don't really know how to fix it.

When I was using GNOME, my bluetooth devices worked fine. But now I've moved to i3 and use blueman. When I try to connect to any headphone, blueman throws

blueman.bluez.errors.DBusFailedError: Protocol not available.

In logs there are pretty similar errors:

сен 09 21:00:45 keddad-pc bluetoothd[916]: a2dp-sink profile connect failed for FC:A8:9A:90:B

The only fix I could find is to install pulseaudio-module-bluetooth, but it is already installed. What might cause this problem?

I tried adding

load-module module-bluetooth-policy
load-module module-bluetooth-discover

to /etc/pulse/system.pa as in Arch Wiki, but it didn't fix anything

This gist didn't help either.

I'm looking for a reason for freezes of the system. Just before the freeze I've got such lines in the logs:

cен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
сен 06 09:03:31 keddad-pc org.gnome.Shell.desktop[1896]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).

What are these? What kind of binding does it overwrite and why? Can it cause be the reason for freezes? UPD: These things appear to happen after each boot

I'm running Ubuntu 18.04.2 LTS, faced with an issue: when I connect headphones through a Type-C dongle, the system doesn't see it. Both port and headphones are working, but the headphones aren't seen by OS. Is there a way to fix it? When connected, they don't even appear in audio settings, so I'm a bit out of ideas.