Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
0 answers
2 views
Why can't I increase my screen brightness in Debian 12 basic install on my old Packard Bell Easynote Laptop?
I'm trying to increase the brightness of my screen in order to see well what I'm doing (because the set brightness is so low thay I can't see anything if I have some light behind me). Before asking here I have investigated and found some possible ways that didn't work for me: I tried to increase the...
I'm trying to increase the brightness of my screen in order to see well what I'm doing (because the set brightness is so low thay I can't see anything if I have some light behind me). Before asking here I have investigated and found some possible ways that didn't work for me: I tried to increase the backlight of my laptop (since it's too dark) by using brightnessctl (which teorically worked but didn't actually change anything, since the brightness didn't change) or xbacklight (which didn't work because, as I have understood, it's for intel GPUs), so I tried to change it manually in /sys/class/backlight/[device]. I could find a device called **radeon_bl0** inside the mentioned path, and some subdirectories inside radeon_bl0 such as: actual_brightness, bl_power (set to 0), brightness, device, max_brightness (255), power, scale, subsystem, type and uevent. Seeing that, I tried to do it with echo 200 > /sys/class/backlight/radeon_bl0/brightness. Actually, it changed the number inside the file (the cat command showed the new value), but the actual (physical) backlight was the same. I don't know why does this happen, but I think it could be related to brightnessctl not working. Thanks for reading this, I hope someone can help me :) PD: My GPU is an AMD ATI Mobility Radeon 9550
bueno467
Aug 5, 2025, 04:11 PM • Last activity: Aug 6, 2025, 12:20 AM
0 votes
0 answers
15 views
Unpredictable freezing with Debian 12 on Dell Latitude 7490
I'm having freezing problems with my Debian 12 install on a Dell Latitude 7490 laptop. The screen will freeze and become unresponsive. Moving the mouse during the freeze will cause the keyboard backlight to turn back on if it's off, but nothing happens on the screen. This happens both mid-use and be...
I'm having freezing problems with my Debian 12 install on a Dell Latitude 7490 laptop. The screen will freeze and become unresponsive. Moving the mouse during the freeze will cause the keyboard backlight to turn back on if it's off, but nothing happens on the screen. This happens both mid-use and before login, whether in TTY or GUI, and whether in normal mode or recovery mode. I have LUKS, and I haven't noticed it happening before I enter encryption key, though. The only way around seems to be a force shutdown -> reboot, but the problem will almost always just happen again shortly after next boot. My system is honestly more or less unusable right now because of this. At first, I didn't see this happening when I was plugged into AC at work or at home, but since some of the changes that I've tried (below), freezing now seems to happen regardless of battery or AC. I've tried a number of things: 1) Update kernel from 6.1.* -> 6.12.33 via backports. 2) Update firmware drivers similarly. 3) Change BIOS settings (disabled C-States, disabled Intel SpeedShift, disabled SpeedStep, disabled TurboBoost; basically disabled every intel performance option besides multi core and hyper threading). I also have secure boot turned disabled, but that was to solve a different problem. 4) Set intel_idle.max_cstate=0 also tried setting to 1) and intel_iommu=off in GRUB_CMDLINE_LINUX_DEFAULT. Right now, I'm using bookworm with the 6.12.33 kernel from backports, Wayland, and iwd + Network manager. Here's a link to a journalctl dump from a hang: [https://paste.c-net.org/GoldbergLined](https://paste.c-net.org/GoldbergLined) The problem in [this Mint forum thread](https://forums.linuxmint.com/viewtopic.php?t=432757) seems to be quite similar to mine, but no resolution. Thanks for your help!
user1507246 (1 rep)
Aug 5, 2025, 07:52 PM
3 votes
3 answers
385 views
Is it redundant or useful to add a UFW rule to deny root when ssh already does?
I manage a Debian (Bookworm) host. The sshd config is set to disallow login as root. I've tested that one cannot login as root, as expected. However, I see hundreds of login attempts daily as root in /var/log/auth.log. Even though I have what I think is adequate reason to believe they can't succeed,...
I manage a Debian (Bookworm) host. The sshd config is set to disallow login as root. I've tested that one cannot login as root, as expected. However, I see hundreds of login attempts daily as root in /var/log/auth.log. Even though I have what I think is adequate reason to believe they can't succeed, the constant brute-force attacks make me uneasy. I am considering adding a ufw rule in /etc/ufw/before.rules to block any attempt to connect with ssh as root. Is there any value in adding the proposed rule or something like it? Or would that be redundant and/or potentially cause problems?
Gojira (133 rep)
Aug 5, 2025, 12:33 AM • Last activity: Aug 5, 2025, 05:53 PM
0 votes
2 answers
46 views
transcode movies efficiently when 2 GPUs are available
I have a Kodi video library where each movie is in its own folder because I had to place `.nfo` files with links to TMDB in each folder to ensure correct identification. The movies are in their original Blu-ray resolution, stored on a drive shared over Samba on a gigabit LAN. I need to transcode all...
I have a Kodi video library where each movie is in its own folder because I had to place .nfo files with links to TMDB in each folder to ensure correct identification. The movies are in their original Blu-ray resolution, stored on a drive shared over Samba on a gigabit LAN. I need to transcode all these files with FFmpeg to max. 1334×750 px. Setup: Intel Core i-7 3930K, 2 x NVIDIA GTX 980 6 GB GPU, KDE on Debian Testing, custom FFmpeg compiled with h264_nvenc enabled. Although the GPUs are connected with an SLI bridge, they're not in SLI mode due to NVIDIA's Linux driver limitation (v550.163.01). GPU 0 is used by the system, GPU 1 is idle. How to do it efficiently?
likewise (680 rep)
Aug 4, 2025, 05:21 PM • Last activity: Aug 5, 2025, 09:29 AM
8 votes
3 answers
858 views
Is swap space used for the page cache, or can it be used for that?
From my understanding, accessed files from disk are being kept in the page cache, for as long as there's enough memory left. Is this data also being moved to swap memory, or can this be facilitated? **I have the following case:** A Debian 12 VPS server with limited (4GB) RAM and fairly large SSD sto...
From my understanding, accessed files from disk are being kept in the page cache, for as long as there's enough memory left. Is this data also being moved to swap memory, or can this be facilitated? **I have the following case:** A Debian 12 VPS server with limited (4GB) RAM and fairly large SSD storage. It is accessing files on a mounted SMB share, which is located on another server, over the internet through wireguard (bottleneck). Can I configure my VPS server so, that it caches as many of the files on the SMB share in local swap memory on it's SSD as possible? Or are there other tools to achieve this? **edit** grawity's solution worked flawlessly! 1. apt install cachefilesd 2. Set RUN=yes in /etc/default/cachefilesd 3. Optionally set cache dir in /etc/cachefilesd.conf 4. Restart daemon sudo systemctl restart cachefilesd.service 5. Mount SMB share with -o fsc option 6. Monitor watch cat /proc/fs/fscache/stats
adrifromhh (91 rep)
Aug 3, 2025, 08:04 AM • Last activity: Aug 4, 2025, 11:15 PM
1 votes
4 answers
1876 views
UEFI-installed Debian on a pendrive doesn't want to boot after being removed once
I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled...
I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared. I don't want to lose the debian installation, I want it working again. I need to get it booting again.
Debianoid (11 rep)
Mar 12, 2019, 03:41 PM • Last activity: Aug 4, 2025, 10:03 PM
7 votes
1 answers
2235 views
Debian FIPS Certified
Is Debian OS FIPS certified? Does it support FIPS Validated Cryptographic Modules? What I noticed is that FIPS mode can be enabled with the tool [fips-mode-setup][1]. This tool is developed and can be used for other Linux distributions (SUSE, Oracle Linux, Red Hat, Ubuntu), in case the user wants to...
Is Debian OS FIPS certified? Does it support FIPS Validated Cryptographic Modules? What I noticed is that FIPS mode can be enabled with the tool fips-mode-setup . This tool is developed and can be used for other Linux distributions (SUSE, Oracle Linux, Red Hat, Ubuntu), in case the user wants to enable FIPS mode afterward (not part of OS). Does that mean that Debian can be configured to use FIPS Validated Cryptographic Modules?
Milica (71 rep)
Sep 19, 2022, 09:16 AM • Last activity: Aug 4, 2025, 08:06 PM
6 votes
2 answers
491 views
apt seems to be ignoring Signed-By
I'm trying to install AviSynth+ from yuuki-deb.x86.men. ```text $ cat /etc/apt/sources.list.d/yuuki-deb.sources Types: deb URIs: http://yuuki-deb.x86.men/ Suites: bullseye Components: main Signed-By: /usr/share/keyrings/yuuki-deb.gpg Enabled: yes $ ls -l /usr/share/keyrings/yuuki-deb.gpg -rw-r--r--...
I'm trying to install AviSynth+ from yuuki-deb.x86.men.
$ cat /etc/apt/sources.list.d/yuuki-deb.sources
Types: deb
URIs: http://yuuki-deb.x86.men/ 
Suites: bullseye
Components: main
Signed-By: /usr/share/keyrings/yuuki-deb.gpg
Enabled: yes

$ ls -l /usr/share/keyrings/yuuki-deb.gpg
-rw-r--r-- 1 root root 433 Sep  7 20:23 /usr/share/keyrings/yuuki-deb.gpg

$ gpg --show-keys /usr/share/keyrings/yuuki-deb.gpg
pub   ed25519 2020-03-03 [SCA]
      A9BBA31152359AE080A1DF851F331533ABCDEEA3
uid                      AviSynth+ Yuuki Debian Repository 

# apt update
-*- snip -*-
Err:4 http://yuuki-deb.x86.men  bullseye InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1F331533ABCDEEA3
-*- snip -*-
It seems to be completely ignoring the Signed-By directive. How can I fix this?
wizzwizz4 (702 rep)
Aug 2, 2025, 10:19 AM • Last activity: Aug 3, 2025, 06:32 PM
4 votes
1 answers
3757 views
Wifi with WPA2-EAP MS-CHAPv2 authentication (username and password) during Debian installation
I am currently attempting to install Debian on my laptop computer. During the network configuration stage, I am prompted to "enter a passphrase for WPA/WPA2 PSK authentication". Unfortunately, I am on my school's network which requires both a username and a password, with the [MS-CHAPv2](https://en....
I am currently attempting to install Debian on my laptop computer. During the network configuration stage, I am prompted to "enter a passphrase for WPA/WPA2 PSK authentication". Unfortunately, I am on my school's network which requires both a username and a password, with the [MS-CHAPv2](https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access#MS-CHAPv2) authentication protocol. What should I enter at the prompt? I have an Ubuntu computer which can connect to this network. Here are the contents of /etc/NetworkManager/system-connections/NetworkName: [ipv6] method=auto [connection] id=NetworkName uuid=3e728a68-a877-4681-bc0e-1e64b2ff6434 type=802-11-wireless [802-11-wireless-security] key-mgmt=wpa-eap auth-alg=open [802-11-wireless] ssid=NetworkName mode=infrastructure mac-address=84:A6:C8:A9:67:DA security=802-11-wireless-security [802-1x] eap=ttls; identity=username phase2-auth=mschapv2 password-flags=1 [ipv4] method=auto Curiously enough, the password I enter to connect to NetworkName doesn't appear anywhere. EDIT 2: Screenshot of network connection process (in a live-boot Ubuntu) Screenshot
Alessandro Power (305 rep)
May 25, 2015, 06:34 PM • Last activity: Aug 3, 2025, 11:03 AM
1 votes
0 answers
19 views
Debian Trixie, xorg: No acceleration using intel driver
I used intel xorg driver (xserver-xorg-video-intel) plus i965-va-driver on Debian Bookworm; everything worked fine, 2D, 3D, video acceleration. After updating to Trixie, intel xorg driver (same setup as bookworm) doesn't provide acceleration. glxinfo shows LLVMpipe instead of Mesa Intel(R) HD Graphi...
I used intel xorg driver (xserver-xorg-video-intel) plus i965-va-driver on Debian Bookworm; everything worked fine, 2D, 3D, video acceleration. After updating to Trixie, intel xorg driver (same setup as bookworm) doesn't provide acceleration. glxinfo shows LLVMpipe instead of Mesa Intel(R) HD Graphics 630 (KBL GT2) (that's the graphic device on my laptop). I switched to modesetting as suggested for years on Debian; 2D, 3D acceleration works fine on modesetting, but as expected, I have screen tearing on videos. I'd prefer to avoid xorg compositors. Wayland is not an option for me due to certain apps I use and still don't work well on it. Any ideas how to have acceleration using intel driver on Trixie, as in Bookworm?
Krackout (2887 rep)
Aug 3, 2025, 06:38 AM
1 votes
2 answers
3053 views
Postfix error for office365: TLS library problem - wrong version number
I am trying to reconfigure a (currently working) debian 10 postfix configuration because we have moved to Office365 as SMTP server. The postfix mail configuration is only used for sending out mails that the server itself generates (logcheck mails etc). The only change I thought I had to make was cha...
I am trying to reconfigure a (currently working) debian 10 postfix configuration because we have moved to Office365 as SMTP server. The postfix mail configuration is only used for sending out mails that the server itself generates (logcheck mails etc). The only change I thought I had to make was changing the relayhost setting from: relayhost = some.mail.provider:465 to: relayhost = smtp.office365.com:587 **Problem:** However, that doesn't work. In /var/log/syslog I get Sep 21 15:03:30 pasteur postfix/smtp: SSL_connect error to smtp.office365.com[40.101.137.34]:587: -1 Sep 21 15:03:30 pasteur postfix/smtp: warning: TLS library problem: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:332: Sep 21 15:03:30 pasteur postfix/smtp: EC2809EF92: Cannot start TLS: handshake failure **Question**: Anybody knows a solution? I played around with various postfix settings in /etc/postfix/main.cf but that doesn't work. For example, changing smtp_tls_security_level = encrypt to ... = may results in syslog entries such as smtp_tls_wrappermode requires "smtp_tls_security_level = encrypt" (or stronger) My postfix settings in /etc/postfix/main.cf are: # Ansible managed smtpd_banner = $myhostname ESMTP $mail_name biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html # default to 2 on fresh installs. compatibility_level = 2 # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # Enable SASL authentication smtp_sasl_auth_enable = yes smtp_sasl_password_maps = static::************ smtp_sasl_security_options = noanonymous smtp_tls_wrappermode = yes smtp_use_tls = yes smtp_tls_security_level = encrypt # General myhostname = pasteur..com myorigin = /etc/mailname mydestination = $myhostname localhost.$mydomain localhost pasteur mynetworks = "127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128" alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all relayhost = smtp.office365.com:587
Rabarberski (221 rep)
Sep 21, 2021, 01:21 PM • Last activity: Aug 2, 2025, 10:05 PM
6 votes
3 answers
51625 views
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype
I am running Debian 10. I have been getting following error while updating repositories for long time: $ sudo apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Reading p...
I am running Debian 10. I have been getting following error while updating repositories for long time: $ sudo apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: http://security.debian.org/dists/buster/updates/InRelease : The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype. W: http://deb.debian.org/debian/dists/buster/InRelease : The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype. W: http://deb.debian.org/debian/dists/buster-updates/InRelease : The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported filetype. How do I get read of this warning regarding keys? [Here](https://bin.disroot.org/?4f877d71ea1d713d#ArxxtUUJ1i5hJxYv96ySMhJTGoX7cQ8ufV6gpBTYkiNe) is the content of /etc/apt/sources.list Ask in comment if more information is required.
Pandya (25593 rep)
Apr 29, 2020, 06:49 AM • Last activity: Aug 2, 2025, 06:19 PM
0 votes
1 answers
4355 views
installation of wifi in debian
~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) 00:16.0 Communicat...
~$ lspci -nn 00:00.0 Host bridge : Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) 00:16.0 Communication controller : Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) 00:16.3 Serial controller : Intel Corporation 6 Series/C200 Series Chipset Family KT Controller [8086:1c3d] (rev 04) 00:19.0 Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) 00:1b.0 Audio device : Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) 00:1c.0 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) 00:1c.1 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4) 00:1c.3 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4) 00:1c.4 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4) 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04) 00:1f.0 ISA bridge : Intel Corporation QM67 Express Chipset Family LPC Controller [8086:1c4f] (rev 04) 00:1f.2 SATA controller : Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04) 03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) 0d:00.0 System peripheral : Ricoh Co Ltd PCIe SDXC/MMC Host Controller [1180:e823] (rev 07) As [he was saying](https://unix.stackexchange.com/questions/645901/having-issue-with-debian-installation#comment1210259_645901) . I was following [the Wiki](https://wiki.debian.org/iwlwifi) . root@debian:/home/istiak# apt update && apt install firmware-iwlwifi Hit:1 http://security.debian.org/debian-security buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package firmware-iwlwifi root@debian:/home/istiak# modprobe -r iwlwifi ; modprobe iwlwifi bash: modprobe: command not found bash: modprobe: command not found When I try to run iwconfig or ifconfig I get that command not found. How can I install wifi driver? I have installed(iwlwifi-6000g2a-ucode-18.168.6.1.tgz) from [here](https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html) . When I extracted I got it(iwlwifi-6000g2a-6.ucode). What I have to do with it? Output of /usr/sbin/modprobe --version : kmod version 26 +XZ -ZLIB +OPENSSL -EXPERIMENTAL iwconfig : root@debian:~# /sbin/iwconfig enp0s25 no wireless extensions. wwp0s29u1u4 no wireless extensions. wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off lo no wireless extensions. lspci -knn | grep -i net -A3 : istiak@debian:~$ lspci -knn | grep -i net -A3 00:19.0 Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) Subsystem: Lenovo 82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520) [17aa:21ce] Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) -- 03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1311] Kernel driver in use: iwlwifi Kernel modules: iwlwifi
user467213
Apr 20, 2021, 02:50 PM • Last activity: Aug 2, 2025, 02:06 PM
0 votes
1 answers
2112 views
Apache server sometimes gets stuck for minutes with requests getting backlogged and waiting too much to be processed
I've got a production server with **Apache 2.4.38** on **Debian 10** and sometimes the web server doesn't function properly and doesn't immediately send a response to the HTTP requests it gets (All virtual hosts requests on it are completely unresponsive (no matter what they reverse proxy to)). Afte...
I've got a production server with **Apache 2.4.38** on **Debian 10** and sometimes the web server doesn't function properly and doesn't immediately send a response to the HTTP requests it gets (All virtual hosts requests on it are completely unresponsive (no matter what they reverse proxy to)). After a restart it immediately fixes itself or after being like this a while (seconds or even minutes) and starts sending A LOT of HTTP responses all of a sudden.

CPU and RAM usage seem to be fine, so it's definitely not that. I don't know what exactly is going on and why it's doing this. I've also changed mpm_event.conf settings, they currently are set to this:
StartServers                     2
        ServerLimit 100
        MinSpareThreads          25
        MaxSpareThreads          75
        ThreadLimit                      128
        ThreadsPerChild          25
        MaxRequestWorkers         400
        MaxConnectionsPerChild   5000
There are some errors I've seen in the Apache error log though:
[Tue Mar 22 19:53:38.339703 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 29595 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.339777 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 26190 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.339825 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 27903 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.339889 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 16907 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.339933 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 26880 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.340000 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 15384 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.340041 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 24971 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.340091 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 9780 still did not exit, sending a SIGKILL
[Tue Mar 22 19:53:38.340130 2022] [core:error] [pid 3375:tid 140244229465216] AH00046: child process 26317 still did not exit, sending a SIGKILL
What settings can I change that would fix this issue?
BitMonster (35 rep)
Mar 22, 2022, 06:32 PM • Last activity: Aug 2, 2025, 01:01 AM
1 votes
1 answers
87 views
Debian stopped using my Intel i915 GPU after upgrade to Trixie. How to fix?
My notebook, an older Apple MacBookAir 13" with Intel Core i7 an Intel HD Graphics 5000, used to work fine before the upgrade to Trixie (Debian GNU/Linux 13). Now, after the upgrade, all rendering is done using the CPU instead of the GPU. This is annoying and makes the machine feel slow. I would lik...
My notebook, an older Apple MacBookAir 13" with Intel Core i7 an Intel HD Graphics 5000, used to work fine before the upgrade to Trixie (Debian GNU/Linux 13). Now, after the upgrade, all rendering is done using the CPU instead of the GPU. This is annoying and makes the machine feel slow. I would like to have accelerated hardware rendering back, but I don't know where to start troubleshooting this. All relevant packages seems to be installed. The GPU is detected. But llvmpipe is used for all rendering instead. System info:
#uname -a
Linux mymachine 6.12.38+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.38-1 (2025-07-16) x86_64 GNU/Linux

# ls -l /dev/dri
total 0
drwxr-xr-x  2 root root         80 Jul 28 01:32 by-path
crw-rw----+ 1 root video  226,   0 Jul 30 13:06 card0
crw-rw----+ 1 root render 226, 128 Jul 28 01:32 renderD128

# LANG=C inxi -Fxxxrzc0
(...)
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Apple driver: i915
    v: kernel arch: Gen-7.5 ports: active: DP-1,eDP-1
    empty: DP-2,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0a26
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
    compositor: xfwm4 v: 4.20.0 driver: X: loaded: intel dri: swrast gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3360x1080 s-dpi: 96 s-size: 890x286mm (35.04x11.26")
    s-diag: 935mm (36.8")
  Monitor-1: DP-1 mapped: DP1 pos: right model: Dell P2214H serial: 
    res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 102
    size: 480x270mm (18.9x10.63") diag: 547mm (21.5") modes: max: 1920x1080
    min: 720x400
  Monitor-2: eDP-1 mapped: eDP1 pos: primary,left model: Apple Color LCD
    res: mode: 1440x900 hz: 60 scale: 100% (1) dpi: 126
    size: 290x180mm (11.42x7.09") diag: 341mm (13.4") modes: 1440x900
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
    drv: swrast inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.0.7-2 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 19.1.7 256 bits)
    device-ID: ffffffff:ffffffff
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings gpu: gputop,
    intel_gpu_top, lsgpu wl: wayland-info x11: xdriinfo, xdpyinfo, xprop,
    xrandr
(...)

# grep -e WW -e EE /var/log/Xorg.0.log
[     8.834] Current Operating System: Linux MBAirFronczek 6.12.38+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.38-1 (2025-07-16) x86_64
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     8.905] (II) Initializing extension MIT-SCREEN-SAVER
[     8.907] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object file: No such file or directory)
[     8.907] (EE) AIGLX error: unable to load driver i965
[    10.905] (WW) intel(0): Output eDP1: Strange aspect ratio (30/179), consider adding a quirk
[    34.463] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[  1267.808] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[  1710.292] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[  3134.814] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 11649.438] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 11649.438] (EE) event8  - bcm5974: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
[ 22436.276] (EE) event8  - bcm5974: client bug: event processing lagging behind by 32ms, your system is too slow
[ 27719.291] (EE) event1  - Power Button: client bug: event processing lagging behind by 454ms, your system is too slow
[ 27719.291] (EE) event3  - Power Button: client bug: event processing lagging behind by 454ms, your system is too slow
[ 27719.291] (EE) event4  - Apple Inc. Apple Internal Keyboard / Trackpad: client bug: event processing lagging behind by 382ms, your system is too slow
[ 41075.009] (EE) event1  - Power Button: client bug: event processing lagging behind by 1040ms, your system is too slow
[ 41075.009] (EE) event3  - Power Button: client bug: event processing lagging behind by 1040ms, your system is too slow
[ 60993.939] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 61022.742] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 61456.304] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 62833.756] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 63129.269] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 63129.269] (EE) event8  - bcm5974: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
[ 67081.490] (EE) event8  - bcm5974: client bug: event processing lagging behind by 28ms, your system is too slow
[ 69447.954] (EE) event8  - bcm5974: client bug: event processing lagging behind by 23ms, your system is too slow
[ 69983.294] (EE) event8  - bcm5974: client bug: event processing lagging behind by 23ms, your system is too slow
[ 78710.772] (EE) event8  - bcm5974: kernel bug: Touch jump detected and discarded.
[ 84611.777] (EE) event8  - bcm5974: client bug: event processing lagging behind by 25ms, your system is too slow
There is no /etc/X11/xorg.conf on my system. /etc/X11/xorg.conf.d/ contains a file called 20-displaylink.conf:
Section "Device"
    Identifier  "Intel"
    Driver      "intel"
EndSection
Plus, another file called 90-xpra-virtual.conf which was automatically created:
# Ignore all xpra virtual devices by default,
# these will be enabled explicitly when needed.
Section "InputClass"
        Identifier "xpra-virtual-device"
        MatchProduct "Xpra"
        Option "Ignore" "true"
EndSection
A *systematic troubleshooting guide* would be most helpful/appreciated. Unfortunately, I could not find a suiable one online = one that is specific to this piece of hardware and one that does include a fix, not only diagnosis. P.S.: I have another older computer (an older MacMini) that also has an Intel chipset/GPU, also uses the i915 driver and suffers from the same type of problem (renderer: llvmpipe instead of GPU, even though GPU seems to be "recognzied"). So I am pretty sure that this is related to the upgrade to Trixie/Debian testing. Other than that, I have no idea as where to start troubleshooting this.
Ferdinand Rau (66 rep)
Jul 30, 2025, 08:01 PM • Last activity: Aug 1, 2025, 07:18 PM
0 votes
2 answers
1881 views
No WiFi in Debian after suspending or closing the lid
I know that this question is posted a few times already, but I tried many of the solutions there and they didn't work. If I start my Laptop (restart or fresh boot after being turned off) the WiFi works most of the time and I can connect to it without a problem. *Not always though* If I'm connected a...
I know that this question is posted a few times already, but I tried many of the solutions there and they didn't work. If I start my Laptop (restart or fresh boot after being turned off) the WiFi works most of the time and I can connect to it without a problem. *Not always though* If I'm connected and close the lid or press the power button so that the laptop goes into suspend mode, after I open it up again, I can't connect to the internet. The available networks are shown, but all of them only have a 10% strength and nothing happens when I try to connect to them. If I deactivate and activate WiFi again (either by the switch in network-manager or by the F-Key on the keyboard), it shows WiFi as "not connected". I tried to restart network-manager after the suspension, but that didn't fix the problem. I know that this is not a lot of debugging information, but I'm not knowledgeable enough of Linux to be able to give you a more relevant one. But I'm happy to provide it, if you tell me what exactly. EDIT: After thinking about the problem a little bit more I also remembered the following: If I let the Laptop suspend by going idle and waiting for the 5 minutes it requires, I sometimes have WiFi after booting up again. It also happened recently, that I was playing in offline mode (because I had no WiFi) and after quite some time I could connect to the Internet again (I think about an hour, but I'm not exactly sure). I have seen this phenomenon very rarely and it only happened on a few occasions.
Okaghana (1 rep)
Jul 5, 2020, 01:30 PM • Last activity: Aug 1, 2025, 07:16 PM
0 votes
1 answers
4018 views
Add .ucode driver in Debian installer
When I install Debian, installer request network connection. But Debian can't found my Ethernet card (Intel(R) Dual Band Wireless-AC 8260). I use non-free [installer][1] and try put `.ucode` file in `/firmware/` folder on USB (from [here][2]), but it not work! I also try renamed `iwlwifi-8000` in iw...
When I install Debian, installer request network connection. But Debian can't found my Ethernet card (Intel(R) Dual Band Wireless-AC 8260). I use non-free installer and try put .ucode file in /firmware/ folder on USB (from here ), but it not work! I also try renamed iwlwifi-8000 in iwlwifi-8260, but it also not work. Big thanks for your response!
Nikita Kulikov (3 rep)
Oct 22, 2016, 05:23 AM • Last activity: Aug 1, 2025, 06:02 PM
2 votes
1 answers
274 views
Unable to get NTP (systemd-timesyncd) working over WiFi
I am running pre-built SD card image for the raspberry pi of [nextcloudpi][1], but I figure I might get better help here. I noticed that the time and date was not automatically updated so I started debugging. I noticed that all lines in the file `/etc/systemd/timesyncd.conf` were commented out and t...
I am running pre-built SD card image for the raspberry pi of nextcloudpi , but I figure I might get better help here. I noticed that the time and date was not automatically updated so I started debugging. I noticed that all lines in the file /etc/systemd/timesyncd.conf were commented out and the NTP line was empty. There's no additional timesyncd.conf.d subdirectory. So I uncommented lines and populated the NTP line. Here's how timesyncd.conf file looks now:
[Time]
NTP=0.europe.pool.ntp.org
FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
RootDistanceMaxSec=5
PollIntervalMinSec=32
PollIntervalMaxSec=2048
ConnectionRetrySec=30
SaveIntervalSec=60
It seems that the content is parsed successfully because:
pi@nextcloudpi:~$ timedatectl show-timesync --all
LinkNTPServers=
SystemNTPServers=0.europe.pool.ntp.org
RuntimeNTPServers=
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=
ServerAddress=
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=0
Frequency=0
However:
pi@nextcloudpi:~$ timedatectl
               Local time: Sat 2024-12-28 12:05:31 EET
           Universal time: Sat 2024-12-28 10:05:31 UTC
                 RTC time: n/a
                Time zone: Europe/Helsinki (EET, +0200)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

pi@nextcloudpi:~$ timedatectl timesync-status
       Server: n/a (n/a)
Poll interval: 0 (min: 32s; max 34min 8s)
 Packet count: 0
The System clock synchronized always indicates no and the Server is always n/a. I tried
sudo timedatectl set-ntp false
sudo timedatectl set-ntp true
but it didn't change anything. The systemd-timesyncd service is running:
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/systemd-timesyncd.service.d
             └─override.conf
     Active: active (running) since Fri 2024-12-27 22:38:50 EET; 13h ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 3014 (systemd-timesyn)
     Status: "Daemon is running"
      Tasks: 1 (limit: 761)
     Memory: 576.0K
        CPU: 920ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─3014 /lib/systemd/systemd-timesyncd
I tried enabling debug logging of this service, but nothing useful is printed there. There's never anything like Connecting to time server. It's not even trying. I also tried manually updating with ntpdate
sudo ntpdate -vd pool.ntp.org
and that worked fine. So I assume that this rules out possible DNS and other network related issues. I ran out of ideas. What am I missing here? Here's the version info:
pi@nextcloudpi:~$ sudo lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Armbian-unofficial 24.8.2 bookworm
Release:        12
Codename:       bookworm

pi@nextcloudpi:~$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=rpi4b
BOARD_NAME="Raspberry Pi 4"
BOARDFAMILY=bcm2711
BUILD_REPOSITORY_URL=https://github.com/armbian/build 
BUILD_REPOSITORY_COMMIT=549f321
LINUXFAMILY=bcm2711
ARCH=arm64
BOOT_SOC=
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
VENDOR="Armbian-unofficial"
VENDORDOCS="https://docs.armbian.com/ "
VENDORURL="https://duckduckgo.com/ "
VENDORSUPPORT="https://community.armbian.com/ "
VENDORBUGS="https://armbian.atlassian.net/ "
VERSION=24.8.2
REVISION=24.8.2
Edit:
pi@nextcloudpi:~$ ntpq -np
-bash: ntpq: command not found

pi@nextcloudpi:~$ systemctl status ntp
Unit ntp.service could not be found.
Edit 2: So it seems to be a network related issue somehow. Until now I have been connected through WiFi only. But immediately when I connected also the Ethernet cable, the System clock synchronized turned to yes. But why is it not working over WiFi? Here's resolvectl status when connected to WiFi only:
Global
         Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub
Current DNS Server: 1.0.0.1
        DNS Servers 1.0.0.1

Link 2 (enxb827ebf2575c)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlan0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1
When the Ethernet cable is connected, it is otherwise the same, except for the Link 2 part:
Link 2 (enxb827ebf2575c)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1
Both WiFi and the Ethernet are the same network.
user930473 (141 rep)
Dec 28, 2024, 10:33 AM • Last activity: Aug 1, 2025, 09:05 AM
2 votes
2 answers
6211 views
Problem when using alien to install Oracle SQL Developer
I am trying to use `alien --scripts` to make a `.noarch.rpm` file into a `.deb` file, however, it is not working. I am trying to install Oracle SQL Developer: I have downloaded the `sqldeveloper-4.0.3.16.84-1.noarch.rpm` package from [here][1]. alien --scripts sqldeveloper-4.0.3.16.84-1.noarch.rpm a...
I am trying to use alien --scripts to make a .noarch.rpm file into a .deb file, however, it is not working. I am trying to install Oracle SQL Developer: I have downloaded the sqldeveloper-4.0.3.16.84-1.noarch.rpm package from here . alien --scripts sqldeveloper-4.0.3.16.84-1.noarch.rpm at this point I would expect the file the file sqldeveloper_4.0.3.16.84-2_all.deb to be created so I could call the following command to install it: dpkg -i sqldeveloper_4.0.3.16.84-2_all.deb However this is not the case. When I call alien --scripts sqldeveloper-4.0.3.16.84-1.noarch.rpm I get a folder with the name sqldeveloper-4.0.3.16.84. After looking in the folder, I have found that there is a large proportion of the program missing, the folder which contains all of the executable scripts to set up and run SQL Developer. I am using a `Debian Linux sever, release 6.0.10. Is there a way for me to make it create the .deb file when I call the alien --scripts command?
James (143 rep)
Apr 4, 2015, 03:26 PM • Last activity: Aug 1, 2025, 06:04 AM
9 votes
1 answers
2456 views
How to build and publish binaries for multiple Debian/Ubuntu distributions?
For a proprietary piece of software I'd like to build and publish multiple versions of software for multiple distributions. E.g. 1.0, 1.1 and both versions for squeeze, wheezy and precise. The builds are run on automatically on different machines and produce distribution-specific `.deb` files. Distr...
For a proprietary piece of software I'd like to build and publish multiple versions of software for multiple distributions. E.g. 1.0, 1.1 and both versions for squeeze, wheezy and precise. The builds are run on automatically on different machines and produce distribution-specific .deb files. Distribution-specific in a way that they're linked to distribution-specific versions of libraries. E.g. OpenSSL 0.9.8 for squeeze, 1.0.1 for wheezy. However, these packages are built using the same version number and package name. This is what is probably the cause for the issue following. Currently I'm using reprepro with the includedeb command to add the binaries to the repository. This works out fine, until I add the same package version built for a second distribution. Publishing for Squeeze is fine # reprepro -b ./repo --outdir ./wwwpub/repo includedeb squeeze /path/to/sqeezepackages/packagename-1.0.deb But then publishing the same version of the software built on wheezy, publishing for wheezy fails: # reprepro -b ./repo --outdir ./wwwpub/repo includedeb wheezy /path/to/wheezypackages/packagename-1.0.deb /path/to/wheezypackages/packagename-1.0.deb: component guessed as 'main' ERROR: '/path/to/wheezypackages/packagename-1.0.deb' cannot be included as 'pool/main/p/packagename/packagename_1.0_all.deb'. Already existing files can only be included again, if they are the same, but: md5 expected: e7df7cd2ca07f4f1ab415d457a6e1c13, got: 0fa924209085a5713f79e6a30649455f sha1 expected: 947b41827bbac414baddf0648b9abecaad8de4fe, got: 1be168ff837f043bde17c0314341c84271047b31 sha256 expected: a883dafc480d466ee04e0d6da986bd78eb1fdd2178d04693723da3a8f95d42f4, got: a93dbf1e95ddc4cfa84e9cd3cfa6c9e0e14affd79812abde4bca688224430a65 size expected: 1234, got: 1235 There have been errors! I assume my build needs a unique version number for each distribution. * What's the easiest way to accomplish this? * How do I add this to the current version number? Is it advised to use something like 1.1~wheezy, 1.1+wheezy, 1.1-1 (incrementing), 1.1+deb6, etc.? As jessie is coming up and I'd like the system to recognize this during dist-upgrades, I think just using the distribution name won't work as j comes before the w and will be recognized as older by APT. * Once determined how to build up the version number; how do I add this to my tooling? I guess I need heuristics in the debian/control files to have the version number specific to the distribution it's built on. And for the changelog I'll have to invoke dch to comply with that version number as well.
gertvdijk (14517 rep)
Apr 7, 2014, 12:53 PM • Last activity: Aug 1, 2025, 02:03 AM
Showing page 1 of 20 total questions