New answers tagged

1

Instead of installing dunst as a service, add it to your i3 config: Edit ~/.config/i3/config and add: exec --no-startup-id dunst


1

Because of the Warning: That basically just means that systemd is trying to start the dunst notification daemon (small program that runs in your user desktop session, listening to libnotify based notifications and displaying them in a very minimal way). That's it. Because of the Error: That has nothing to do with the former. If it can't open your X11 display,...


1

from: https://wiki.archlinux.org/index.php/Dunst#Installation Installation Install the dunst package. An example configuration file is included at /usr/share/dunst/dunstrc. Copy this file to ~/.config/dunst/dunstrc and edit it accordingly.


0

It was solved by creating /etc/X11/xorg.conf.d/20-intel.conf file with this content: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection and rebooting.


0

Just like in xterm or most other terminal emulators: printf '\033]2;%s\033\\' whatever The rest is up to the shell -- for instance, in bash you can use a DEBUG trap: set_title(){ local cmd=$BASH_COMMAND case $cmd in fg) cmd=$(jobs %); cmd=${cmd##"${cmd% *} "};; fg\ *|%*) cmd=$(jobs "${cmd#fg }"); cmd=${cmd##"${cmd% *} ...


0

Your udev-rules are not applied, so your peripherals (and probably much more) are not detected/initialized. If you want to learn, how to make your own distribution or learning Linux in depth, I can recommend Linux from scratch or gentoo first. LFS is targeted at people who want to learn more on linux-basics while gentoo is in fact a distribution-construction-...


1

(based off of clue in comment by blaimi (https://github.com/ryanoasis/nerd-fonts/issues/254)) NOTE: The below can hardly be called a solution per se, or barely even considered a workaround..And it's perhaps only Arch- and/or Manjaro- related.. But i'll leave this here in case it might be of use to others whom might hopefully be able to come up with a better ...


2

This seems to be a problem with resolving ligatures. This can happen if your fontconfig-cache is corrupted. You can clear it by deleting/renaming ~/.cache/fontconfig and reboot. copy&pasting in editors works, because they usually don't use ligatures in mono-fonts.


0

# inxi -Sy System: Host: fi965 Kernel: 5.4.0-26-generic x86_64 bits: 64 Desktop: Trinity R14.0.9 Distro: Ubuntu 20.04 LTS (Focal Fossa) # ls -l /etc/X11/xorg.conf.d/00-keyboard.conf -rw-r--r-- 1 root root 286 May 6 2014 /etc/X11/xorg.conf.d/00-keyboard.conf # cat /etc/X11/xorg.conf.d/00-keyboard.conf # Read and parsed by systemd-localed. It's probably ...


0

In case someone else faces this problem, it connected with Asus keyboards and recent kernel update. The workaround is in this thread https://bbs.archlinux.org/viewtopic.php?pid=1922517#p1922517


0

Yes, the manual page for picom explains how to set opacity rules for specific windows based on their name or class. --opacity-rule OPACITY:'CONDITION' Specify a list of opacity rules, in the format PERCENT:PATTERN, like 50:name *= "Firefox". picom-trans is recommended over this. Note we don’t make any guarantee about possible conflicts ...


0

OK Matrox is the authority and i'm just a wannabe user. But I have different information to offer. My current laptop 17-by0061st was the cheapest Hp laptop also refurbished that i could buy at the time because of personal constraints. I have ran and am running 3 monitors with Matrox triplehead2go DE in Ubuntu 18.04 and now 20.04. I bought the th2g more than ...


0

Power off computer. Power on. Wait till GRUB will show where you can choose which Linux distro you want to run. Choose the one which di not start, press e. Navigate down with the arrow-down key until you can see a line ending with: ro quiet splash $vt_handoff Using your keyboard replace the following keywords. FROM: ro quiet splash $vt_handoff TO: rw ...


4

Unfortunately X is not Amiga - where this was possible :) What you can do, although it's not exactly what you want, is start two X instances on the same machine. One can be 8bit, the other 16bit.


2

You should not use devd (on FreeBSD) or udev (on Linux) for that. Any X11 client can use the XInput/XInput2 extension to monitor when X11 input devices like mice or keyboards are added or removed. No need to run as root from devd/udev, mess up X11 authentication and commit layer violations, cope with devd/udev's limitations, assume that it's a single user ...


3

Carefully. It's easy to jam the operation of devd with a program that doesn't terminate speedily. To avoid that, you should probably run a monitor program that connects to devd's output at /var/run/devd.seqpacket.pipe like volmand does, for example. On the other hand … If you still do want to invoke things from devd directly, then first note that there's ...


1

Are the Alt+Ctl+FN key combinations (aka srvrkeys) hardcoded into Xorg? No, they're not. They can be configured via Xkb. But understanding how to effectively and correctly configure Xkb would take someone more than a lifetime ;-). But as a simple hack, completely client-side, this should allow you to switch with just Alt-F1 instead of Ctrl-Alt-F1 [See the ...


1

The error message is generated by the programming language equivalent of this shell script command: echo "Can't open display: $DISPLAY" >&2 So the fact that you don't see anything after the second colon means the DISPLAY environment variable was not set (or was set to a null value). When starting a X11 server, a session cookie is also ...


0

Assuming that GNOME Maps crashes on startup with this Gdk-Message in Debian 10 under GNOME: Error 71 (Protocol error) dispatching to Wayland display. It means that GDK as the GTK rendering engine fails for some reason to communicate with Mutter, which is the Wayland compositor in GNOME. As a result, your application fails to explain to the system how to ...


1

I thought I'd share the solution I've told you about here for the posterity as it does not require rebuilding of the theme. Similar to your setup, i'm running metacity for single full screen application without any additional UI. Set the correct/desired cursor size in ~/.Xresources Xcursor.size: 22 merge settings using xrdb before starting the WM by adding ...


Top 50 recent answers are included