The officially official Devuan Forum!

You are not logged in.

#1 Hardware & System Configuration » Webkit & NVIDIA with onedriver » 2024-04-04 19:37:36

felixed
Replies: 0

I got the issue when starting onedriver but found out that it is present in a similar pattern with other programs. The more or less same error message is

KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Keine Berechtigung
Failed to create GBM buffer of size 450x600: Keine Berechtigung
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Keine Berechtigung
Failed to create GBM buffer of size 450x600: Keine Berechtigung
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Keine Berechtigung
Failed to create GBM buffer of size 450x600: Keine Berechtigung
Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1

The web window shows up but remains empty - at the time the access data input is required.

In onedriver it can be circumvented by using the --no-browser option in program call.

In the past it worked. Downgrading NVIDIA drivers to the version it worked with (470.something from 5xx.something) did not solve the problem.

Any ideas what causes the denial of permission and how to fix it?

System: Daedalus on a ryzen7 with NVIDIA GeForce GTX 1650.

#2 Re: Desktop and Multimedia » Wer synchronisiert die Systemuhr? » 2024-03-03 09:45:01

Seems not to do it on my system.

$ whereis ntpdate
ntpdate:

@aluma
Thanks.

Deine Uhr hat exakt die richtige Zeit!Der Unterschied zu Time.is betrug +0,001 Sekunden (±0,089 Sekunden)

I think that's too good to be a coincidence.

#3 Re: Desktop and Multimedia » Wer synchronisiert die Systemuhr? » 2024-02-24 19:17:50

I do not want to know how to synchronize the system clock, because it's perfectly done.

I want to find out which program does it on my system.

By the way:

$ sudo apt-search time
sudo: apt-search: Befehl nicht gefunden

#4 Desktop and Multimedia » Wer synchronisiert die Systemuhr? » 2024-02-24 13:29:13

felixed
Replies: 10

Meine Systemuhr geht sekundengenau. Ich weiß nur nicht, warum. Weder ntp noch chrony ist installiert.

Wer macht das in Devuan? Oder ist's der Browser (Opera)?

Devuan chimaera, permanente Internetverbindung mit Ethernet.

#5 Hardware & System Configuration » [SOLVED] Flickering monitor with NVIDIA GTX1650 » 2023-08-06 08:20:22

felixed
Replies: 0

Just for information:

The symptom were short blackouts in the upper part of the monitor.

The problem was the driver from Nvidia version above 470.

Installing the 470 driver from the Devuan repository led to error messages (but worked without flickering or any other problem).

So I got me the NVIDIA-Linux-x86_64-470.199.02.run from Nvidia download site and installed it by changing to tty1, logging in as root and

service slim stop
apt purge *nvidia*
cd (to the directory with the driver)
sh NVIDIA-Linux-x86_64-470.199.02.run
reboot

Done.

#6 Re: Hardware & System Configuration » NUC Ethernet not found » 2023-07-31 18:58:26

What does lspci say?
Is it disabled by BIOS?

#7 Hardware & System Configuration » [solved] WLAN connects, disconnects, connects ... (Realtek 8821ce) » 2023-07-29 16:41:21

felixed
Replies: 0

To cut it short, device, system and all other things are irrelevant except the WLAN-adapter and it's firmware.

WLAN-adapter: Realtek 8821ce
Firmware: rtw_8821ce

It took me several days to find out, that the kernel firmware in all newer versions since 5.something is faulty.

Replacement with rtl8821ce firmware from Github solved the problem. Blacklist the rtw_8821ce.

Add to /etc/modprobe.d/blacklist.conf

blacklist rtw88_8821ce

Then

su -
apt install module-assistant build-essential dkms bc git linux-headers-$(uname -r)
git clone https://github.com/tomaspinho/rtl8821ce
cd rtl8821ce
chmod +x dkms-install.sh
chmod +x dkms-remove.sh
./dkms-install.sh
reboot

see also https://bbs.archlinux.org/viewtopic.php?id=273440

#8 Re: Hardware & System Configuration » [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected » 2023-07-29 14:24:32

I don't know if it should be termed as a solution or rather a workaround. Finally it works.

The problem seems to be that the device presents itself in three modes, connected to ppp0 (ppp), ttyACM0 (mobile broadband) and usb0 (ethernet). Network manager seems to try each one and disconnect the others. I'm not sure about that, but to prevent network manager from handling the devices and giving the job to ifupdown solved the problem. Strange enough, nm-applet then shows this connections icon in the tray.

What to do:
Add to /etc/network/interfaces

allow-hotplug usb0
iface usb0 inet dhcp
iface usb0 inet6 auto

Create / add to /etc/NetworkManager/conf.d/unmanaged-devices.conf

[keyfile]
unmanaged-devices=interface-name:ppp0;interface-name:ttyACM0;interface-name:usb0

Make it happen as root by:

service network-manager restart
ifup usb0

#9 Re: Hardware & System Configuration » [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected » 2023-07-04 15:53:32

There are isc-dhcp-client and conman installed.

conmand is running.

How can I find out which programs are managing network devices / connections?

#10 Re: Hardware & System Configuration » [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected » 2023-07-03 18:22:13

Is it a overconnection connection kill? On a cable-only system I

- uninstall network-manager. Still get connected.

- disable anything in /etc/network/interfaces. Still get connected.

- reinstall network-manager and disable ifupdown / keyfile in /etc/NetworkManager/NetworkManager.conf

#[main]
#plugins=ifupdown,keyfile

#[ifupdown]
#managed=false

Still get connected after reboot.

Who the hell does control the network connections?

#11 Hardware & System Configuration » [SOLVED] USB LTE Stick ASRMICRO KuWfi LTE wingle not reliably connected » 2023-07-02 17:31:02

felixed
Replies: 4

system: Devuan Chimaera, amd64, same problem on different laptops, network-manager
lsusb: Bus 001 Device 010: ID 2ecc:3010 Asrmicro Asrmicro (it's the eth mode)

When booting with connected stick it is connected to the internet as mobile broadband. Connection data from nm-applet:

Schnittstelle GSM (ttyACM0)
Treiber cdc_acm, mdis_host
Geschwindigkeit Unbekannt
Ipv4
IP-Adresse 10.38.155.185
Broadcast-Adresse 10.38.155.185
Subnetz-Maske 255.255.255.255
» Weitere Adressen
Vorgaberoute 0.0.0.0
Primärer DNS 10.74.210.210
Sekundärer DNS 10.74.210.211
IPv6
IP-Adresse fe80::d57a:d23:a13c:f9d6/64
» Weitere Adressen
Vorgaberoute fe80:albf:dcea:4ea4:817a

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 48:ba:4e:ad:04:a9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ea:4c:6a:a6:95:1a brd ff:ff:ff:ff:ff:ff permaddr 3c:95:09:78:8e:4b
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:61:2b:59:77:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.208/24 brd 192.168.0.255 scope global dynamic noprefixroute usb0
       valid_lft 7165sec preferred_lft 7165sec
    inet6 fe80::7b53:b95a:c413:a84e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
5: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 3
    link/ppp 
    inet 10.37.206.186 peer 10.64.64.64/32 scope global ppp0
       valid_lft forever preferred_lft forever
    inet 10.37.206.186/32 scope global noprefixroute ppp0
       valid_lft forever preferred_lft forever
    inet6 fe80::6d41:b7f8:7dfb:741 peer fe80::a1bf:dcea:4ea4:817a/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::1a36:4075:1d47:f02f/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

After some minutes the device is disconnected, ppp0 gone:

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 48:ba:4e:ad:04:a9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ea:4c:6a:a6:95:1a brd ff:ff:ff:ff:ff:ff permaddr 3c:95:09:78:8e:4b
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:61:2b:59:77:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.208/24 brd 192.168.0.255 scope global dynamic noprefixroute usb0
       valid_lft 6798sec preferred_lft 6798sec
    inet6 fe80::7b53:b95a:c413:a84e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

After executing

sudo service network-manager restart

several times, the usb device is connected as ethernet device.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 48:ba:4e:ad:04:a9 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 72:f9:66:ad:f0:b6 brd ff:ff:ff:ff:ff:ff permaddr 3c:95:09:78:8e:4b
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 86:61:2b:59:77:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.208/24 brd 192.168.0.255 scope global dynamic noprefixroute usb0
       valid_lft 7108sec preferred_lft 7108sec
    inet6 fe80::a0c1:cdec:e7f8:ada1/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

According to nm-applet now:

Schnittstelle Ethernet (usb0)
Hardware-Adresse 4E:05:1C:E7:24:45
Treiber mdis_host
Geschwindigkeit Unbekannt
Sicherheit Keine
IPv4
IP-Adresse 192.168.0.231
Broadcast-Adresse 192.168.0.255
Subnetz-Maske 255.255.255.0
Vorgaberoute 192.168.0.1
Primarer DNS 192.168.0.1
IPv6
IP-Adresse fe80::6a38:14c2:ad6:48f4/64

Starting network-manager by

sudo service network-manager stop
sudo NetworkManager -d

leads to the following messages:

sudo NetworkManager -d
<info>  [1688297559.5098] NetworkManager (version 1.30.6) is starting... (after a restart)
<info>  [1688297559.5099] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
<info>  [1688297559.5127] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
<info>  [1688297559.5150] manager[0x564e8124c020]: monitoring kernel firmware directory '/lib/firmware'.
<info>  [1688297559.5151] monitoring ifupdown state file '/run/network/ifstate'.
<info>  [1688297559.5164] hostname: hostname: couldn't get property from hostnamed
<info>  [1688297559.5165] hostname: hostname changed from (none) to "lenovo-debian"
<info>  [1688297559.5168] dns-mgr[0x564e81245170]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
<info>  [1688297559.5173] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/ieee80211/phy0/rfkill0) (driver rtw_8821ce)
<info>  [1688297559.5174] manager[0x564e8124c020]: rfkill: Wi-Fi hardware radio set enabled
<info>  [1688297559.5174] manager[0x564e8124c020]: rfkill: WWAN hardware radio set enabled
<info>  [1688297559.5194] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-wwan.so)
<info>  [1688297559.5197] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-adsl.so)
<info>  [1688297559.5201] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-bluetooth.so)
<info>  [1688297559.5204] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-wifi.so)
<info>  [1688297559.5213] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-team.so)
<info>  [1688297559.5216] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
<info>  [1688297559.5217] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
<info>  [1688297559.5218] manager: Networking is enabled by state file
<info>  [1688297559.5219] dhcp-init: Using DHCP client 'internal'
<info>  [1688297559.5222] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-settings-plugin-ifupdown.so")
<info>  [1688297559.5222] settings: Loaded settings plugin: keyfile (internal)
<info>  [1688297559.5222] ifupdown: management mode: managed
<info>  [1688297559.5223] ifupdown:       interface-parser: parsing file /etc/network/interfaces
<info>  [1688297559.5223] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
<info>  [1688297559.5372] device (lo): carrier: link connected
<info>  [1688297559.5375] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
<info>  [1688297559.5383] device (usb0): carrier: link connected
<info>  [1688297559.5386] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
<info>  [1688297559.5413] device (usb0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
<info>  [1688297559.5424] device (usb0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
<info>  [1688297559.5434] device (usb0): Activation: starting connection 'usb0' (e270cee1-1313-40f9-8f45-07bff69db3ca)
<info>  [1688297559.5436] device (wlan0): driver supports Access Point (AP) mode
<info>  [1688297559.5442] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
<info>  [1688297559.5453] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
<info>  [1688297560.0874] device (wlan0): set-hw-addr: set MAC address to 62:CA:32:80:E9:7D (scanning)
<info>  [1688297560.6091] device (usb0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6099] device (usb0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6159] agent-manager: agent[60f2fca35ecc68ce,:1.41/org.freedesktop.nm-applet/1000]: agent registered
<info>  [1688297560.6160] modem-manager: ModemManager available
<info>  [1688297560.6161] device (usb0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6164] device (usb0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6188] device (usb0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6192] device (usb0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
<info>  [1688297560.6197] manager: NetworkManager state is now CONNECTED_LOCAL
<info>  [1688297560.6213] device (usb0): Activation: successful, device activated.
<info>  [1688297560.6225] manager: NetworkManager state is now CONNECTED_GLOBAL
<info>  [1688297560.6630] device (wlan0): supplicant interface state: internal-starting -> disconnected
<info>  [1688297560.6631] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
<info>  [1688297561.1658] manager: startup complete

Surprisingly the device gets connected too when network-manager is stopped.

/etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
#auto lo
#iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

Any ideas who is connecting and cancelling the connections? How can I just connect the stick as ethernet device or leave it in mobile broadband mode?

The laptops are also using WLAN and cable connections as well so I would prefer an automatic solution.

Thanks for any help.

#13 Hardware & System Configuration » [SOLVED] USB-LTE-Stick E3372h-153 very slow » 2023-05-24 14:29:40

felixed
Replies: 1

Stick:

HWDH Technology CO. LTD
Super 4G dongle
Model:E3372h-153
IMEI:351757114905086
S/N:G4FDW3372001517
Lte:B1.B3.B5.B7.B8.B20.B38.B40
3G:B1.B5.B8
Web ID:192.168.8.1
Password:admin

Ausgabe usb-devices

Bus=01 Lev=01 Prnt=01 Port=04 Cnt=03 Dev#=  7 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=19d2 ProdID=0548 Rev=01.00
S:  Manufacturer=ZXIC,Incorporated
S:  Product=ZXIC Mobile Boardband
S:  SerialNumber=1234567890ABCDEF
C:  #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=ff Driver=rndis_host
I:  If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host

It works "out of the box", recognised as eth device. Same under Windows 10 in a VM of that Linux (devuan chimaera 64bit), BUT:

Under Linux it is extremely slow, mostly less than 50 kB/s, under Windows up to around 700 kB/s. Speed is limited to 7.2 Mbit/s by provider congstar. The stick is indicating LTE-connection.

Any idea how to get "full" speed?

#14 Other Issues » update-apt-xapian-index not working » 2022-05-06 22:11:28

felixed
Replies: 0

Devuan chimaera, 64bit

On another computer I experienced in synaptic, that the new kernel version 5.10.0-14 is not displayed using apt-xapian-index, but could be found and installed using a search.

Calling update-apt-xapian-index as root from terminal shows some syntax errors that I can not reproduce on the computer I am using now which is running with a similar Devuan configuration. It was something related to python.

But maybe someone here knows the issue and has a solution.

#15 Re: Installation » how to clone a partition with os installed? » 2021-12-25 19:57:37

Head_on_a_Stick wrote:
felixed wrote:

# install bootloader from within new system, it's important *****!!!!!

grub-install /dev/nvme1n1p6
update-grub

For non-UEFI systems it is strongly recommended to install GRUB's core.img to the block device rather than the partition.

Thanks, my mistake. I changed the command and of course I do not install it to a partition.

#16 Re: Installation » how to clone a partition with os installed? » 2021-12-24 18:24:50

I'm using fsarchiver for years. It's not installed by default, but included in standard sources. Never had any problem.

Some tips to use it (you need tune2fs and a super grub disk too):

# ***  save partition sdb1 to /media/XXX/partition12345.fsa ***
#
# clear trash + apt-get clean
# run maintenance system, unmount sdb1 (safer, but I never had any trouble when saving the running system itself)
#
# save:
# -o (overwrite without question)
# -j2 (use 2 CPU cores)
# -A -a (save mounted partition)
# -v (show process information)
# -z3 (compression strength between 1 and 9, replaced by -Z[x])
#
# as root

fsarchiver savefs -o -j2 -A -a -v -z3 /media/XXX/partition12345.fsa /dev/sdb1

#
# *** restore to /dev/nvme1n1p6 ***
#
# run any Linux with fsarchiver installed or remain within running system
#
# mkfs - partition type, usually unnecessary
#
# as root

fsarchiver restfs -o -j2 -v /media/XXX/partition12345.fsa id=0,dest=/dev/nvme1n1p6

# ,mkfs=ext2
#
# when installing onto the same computer it needs a new UUID before mounting!

tune2fs -U random /dev/nvme1n1p6

# mount
# get UUIDs

blkid

# change UUIDs in /etc/fstab of restored system
# reboot into restored system by super grub disk / Rescatux (did I mention before that you need it?)
# install bootloader from within new system, it's important *****!!!!!

grub-install /dev/nvme1n1
update-grub

# change boot device in BIOS

#17 Desktop and Multimedia » [SOLVED] Kaffeine / VLC stuttering video » 2021-11-22 20:21:35

felixed
Replies: 0

Ryzen7 / NVIDIA GLX 1650 / Chimaera / non-free Nvidia driver 470

From ASCII / kaffeine 1.2.2 (using xine as frontend) I was used to smooth video play on the same hardware.

It changed with chimaera (kaffeine 2.0.18 using libVLC instead of xine). During whole screen video moves in HD (for instance during panning shots) the video was stuttering. No big jumps, just visible a way you don't know if it's stuttering or not - and the more annoying.

Searching the web I found and followed a lot of suggestions (decoder, buffer, hardware accelleration settings...). None of it worked.

The solution was simply to turn off deinterlacing in kaffeine as well as in vlc. It also removed a moiree effect from high contrast edges. No sawtooth patterns at edges (which formerly were removed by deinterlacing).

Obviously less is more. Sometimes.

#19 Re: Hardware & System Configuration » [SOLVED] Display / monitor / mouse freeze after hours - Chimaera, not ASCII » 2021-11-17 22:17:39

No more freezes. Solution once again:

Got rid of all nvidia & nouveau stuff by purge.

Manually installed nvidia 470 driver from nvidia.de download. No remarkable tearing even without composite option.

#20 Re: Desktop and Multimedia » [SOLVED] Is it possible to change GUI title bar color when working as root? » 2021-11-17 22:13:54

Das Problem ist nicht wie gewünscht lösbar. Der Titel wird vom Fenstermanager verwaltet und der verwendet die Einstellungen des angemeldeten Nutzers.

Allerdings habe ich jetzt noch menubar und toolbar auf knallrot gesetzt und alle für mich relevanten Programme haben irgendwas davon (headerbar, menubar oder toolbar).

Meine /root/.config/gtk-3.0/gtk.css sieht jetzt so aus:

headerbar {
    background: #ff0000;
    color: #ffffff; 
    text-shadow: #000000;
}
headerbar:backdrop  {
    background: #800000;
    color: #404040;
    text-shadow: #000000;
} 
menubar,toolbar {
    background: #ff0000;
}

Nicht ganz so elegant wie vorgesehen, aber funktioniert.

#21 Re: Desktop and Multimedia » [SOLVED] Is it possible to change GUI title bar color when working as root? » 2021-11-16 15:34:28

Got so far as caja and other GUI's title backgrond (for instance for theme Menta) is set by

@define-color theme_selected_bg_color #accd8a;

in /usr/share/themes/Menta/gtk-3.0/gtk-main.css .

Other entries in there then refer to  theme_selected_bg_color.

#22 Re: Desktop and Multimedia » [SOLVED] Is it possible to change GUI title bar color when working as root? » 2021-11-12 10:12:36

Little step forward.

With /root/.config/gtk-3.0/gtk.css

headerbar {
    background: #ff0000;
    color: #ffffff; 
    text-shadow: #000000;
}
headerbar:backdrop  {
    background: #800000;
    color: #404040;
    text-shadow: #000000;
} 

it works for some GUI as gedit, but not for caja. In caja there is also no effect from ~/.config/gtk-3.0/gtk.css .

#23 Re: Desktop and Multimedia » [SOLVED] Is it possible to change GUI title bar color when working as root? » 2021-11-11 21:32:23

Xfce4 obviously reads the gtk.css of ~. I change some panel and desktop colors by that.

Maybe it's a syntax error. I wrote the same into the ~/.config/gtk-3.0/gtk.css, restarted, but the title bar didn't change. Maybe the syntax is wrong.

Is there any manual of css syntax used by xfce4? Or by gtk3?

#24 Re: Desktop and Multimedia » [SOLVED] Is it possible to change GUI title bar color when working as root? » 2021-11-11 19:21:31

/root/.config/gtk-3.0/ is empty.

I tried a gtk.css there:

.titlebar {
    background: #ff0000;
    color:#000000; 
}

.titlebar:backdrop  {
    background: #a00000;
    color:#808080;
} 

Not working.

With mate there's at least a comment "(as admin)" in the title.

When logging in as root (bad idea, I know) there's a warning displayed within the caja window, but the title bar is not red.

Board footer

Forum Software