Wifi - unable to connect.
Hi there,
I'm trying to connect to wifi at work, unfortunately I get the following:
wlan0: SME: Trying to authenticate with 24:81:3b:2a:0f:e1 (SSID='ssid'
freq=2412 MHz)
wlan0: Trying to associate with 24:81:3b:2a:0f:e1 (SSID='ssid' freq=2412
MHz)
wlan0: Associated with 24:81:3b:2a:0f:e1
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=PL
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=26
wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 26 (MSCHAPV2) selected
EAP-MSCHAPV2: Authentication succeeded
wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
wlan0: PMKSA-CACHE-ADDED 24:81:3b:2a:0f:e1 1
wlan0: RSN: PMKID mismatch - authentication server may have derived
different MSK?!
wlan0: CTRL-EVENT-DISCONNECTED bssid=24:81:3b:2a:0f:e1 reason=1
locally_generated=1
BSSID 24:81:3b:2a:0f:e1 ignore list count incremented to 2, ignoring for
10 seconds
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
According to the instruction the settings should be:
WPA2 Enterprise,
PEAP,
MSCHAPv2,
no certificate.
And my wpa config is:
network={
ssid="ssid"
proto=RSN
key_mgmt=WPA-EAP
pairwise=CCMP
auth_alg=OPEN
eap=MSCHAPV2
identity="uid"
password="pas"
mesh_fwding=1
}
Any suggestions?
--
Regards
Greg
Bookworm: lighttpd as tvheadend proxy
Hi there,
I'm using Lighttpd as https to http proxy for encrypting tvheadend
connections. After upgrading from Bullseye to Bookworm
(lighttpd-1.4.69-1) I see only some table borders after opening
tvheadend. Downgrading to lighttpd-1.4.59-1+deb11u2 solves the problem.
My guess is that it is related to websockets. This is my Lighttpd proxy
config:
$HTTP["url"] =~ "^/tv/comet/ws" {
setenv.add-request-header = (
"Connection" => "Upgrade")
setenv.add-response-header = (
"Connection" => "Upgrade")
proxy.server = ( "" => (
( "host" => "127.0.0.1",
"port" => "9981" ) )
)
proxy.header = ( "upgrade" => "enable")
}
$HTTP["url"] =~ "^/tv/" {
proxy.server = ( "" => (
"internal" => (
"host" => "127.0.0.1",
"port" => "9981",
"fix-redirects" => 1,
)
) )
--
Pozdriówka
Grzesiek
Najlepszym przyjacielem człowieka wcale nie jest pies a ..
... kolonia drożdży.
Duża kolonia => mnóstwo (% ;) ) radości.
LXDM & on screen keyboard
Hi there, How to setup setup on screen keyboard on LXDM? I added /usr/bin/florence to /etc/lxdm/LoginReady unfortunately, in the /var/log/lxdm.log I get: (florence:2825): Gtk-WARNING **: 14:21:06.181: cannot open display: :0 Florence version 0.6.3 Any suggestions?
Buster -> Bullseye: cups printing
Hi there, I have cups configured to print to smb shared printer. Required user id and password is included in printer configuration. Before upgrading to Bullseye printing worked as expected (any app, no password required). After the upgrade apps like LibreOffice, Firefox, Evince ask for smb share password (which is included in cups printer configuration). Even more interesting is that xpdf prints without asking for passwd. Is there any way to restore previous behaviour (from Buster) and make apps other than xpdf print without asking for password?? -- Pozdriówka Grzesiek Najlepszym przyjacielem człowieka wcale nie jest pies a .. ... kolonia drożdży. Duża kolonia => mnóstwo (% ;) ) radości.
[Sid] csync2 startup scripts
I think there is something wrong with scync2 startup scripts: # systemctl status csync2.service ○ csync2.service - LSB: Cluster file synchronization daemon Loaded: loaded (/etc/init.d/csync2; generated) Active: inactive (dead) since Tue 2021-10-19 15:44:16 CEST; 7min ago Docs: man:systemd-sysv-generator(8) Process: 1220 ExecStart=/etc/init.d/csync2 start (code=exited, status=0/SUCCESS) Process: 1859 ExecStop=/etc/init.d/csync2 stop (code=exited, status=0/SUCCESS) CPU: 28ms Oct 19 15:08:42 Artemis systemd[1]: Starting LSB: Cluster file synchronization daemon... Oct 19 15:08:42 Artemis csync2[1220]: Starting Cluster file synchronization daemon: csync2 Oct 19 15:08:42 Artemis systemd[1]: Started LSB: Cluster file synchronization daemon. Oct 19 15:44:16 Artemis systemd[1]: Stopping LSB: Cluster file synchronization daemon... Oct 19 15:44:16 Artemis csync2[1864]: start-stop-daemon: --remove-pidfile requires --pidfile Oct 19 15:44:16 Artemis csync2[1864]: Try 'start-stop-daemon --help' for more information. Oct 19 15:44:16 Artemis systemd[1]: csync2.service: Deactivated successfully. Oct 19 15:44:16 Artemis systemd[1]: Stopped LSB: Cluster file synchronization daemon.
Re: Qualcomm Snapdragon X12 LTE Modem
Hi there, I managed to connect _but_ I do no know how to obtain address. I tried: udhcpc -q -f -n -i wwan0 no luck, unfortunately. Any suggestions? To connect I use the following: # mmcli -m 0 --simple-connect="apn=darmowy" successfully connected the modem # mmcli -m 0 General |dbus path: /org/freedesktop/ModemManager1/Modem/0 |device id: 09cd50ccb01495e91195c6792755a95ef0ad604c Hardware | manufacturer: Qualcomm |model: Snapdragon(TM) X12 LTE-A |firmware revision: T77W676.F0.0.0.4.7.GC.017 | 041 | h/w revision: Snapdragon(TM) X12 LTE-A |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 359195080308286 System | device: /sys/devices/pci:00/:00:14.0/usb2/2-3 | drivers: cdc_mbim | plugin: generic | primary port: cdc-wdm2 |ports: cdc-wdm2 (mbim), wwan0 (net) Status | unlock retries: sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 9% (recent) Modes|supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | current: allowed: 3g, 4g; preferred: 4g Bands|supported: utran-1, utran-4, utran-6, | utran-5, utran-8, utran-2, | eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, | eutran-8, | eutran-12, eutran-13, eutran-17, | eutran-18, eutran-19, eutran-20, | eutran-21, eutran-25, eutran-26, | eutran-28, eutran-29, eutran-30, | eutran-38, eutran-39, eutran-40, | eutran-41, eutran-66, utran-19 | current: utran-1, utran-4, utran-6, | utran-5, utran-8, utran-2, | eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, | eutran-8, | eutran-12, eutran-13, eutran-17, | eutran-18, eutran-19, eutran-20, | eutran-21, eutran-25, eutran-26, | eutran-28, eutran-29, eutran-30, | eutran-38, eutran-39, eutran-40, | eutran-41, eutran-66, utran-19 IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 3591950803 |enabled locks: fixed-dialing | operator id: 26001 |operator name: Aero2 | registration: home 3GPP EPS | initial bearer dbus path: /org/freedesktop/ModemManager1/Bearer/0 SIM |dbus path: /org/freedesktop/ModemManager1/SIM/0 Bearer |dbus path: /org/freedesktop/ModemManager1/Bearer/1 Regards Greg
[sid] efibootmgr not working
Hi there, I noticed recently that efibootmgr stoped working. On all my Sid machines I get the following: # efibootmgr EFI variables are not supported on this system. But if I run Buster (the same hardware) then everything is ok. So this is definitely software problem. I also noticed that the /sys/firmware/efi/efivars directory is empty. Kernel problem? Missing modules? Regards Greg
OT: it8728F PWM configuration
Hi there, I'm trying to configure automatic fan speed control. Unfortunately, in the it87 kernel module documentation explains only settings of IT8705F and IT8712F (these chips do not have slope setting). Could some explain how it works: # grep "" pwm1* pwm1:70 pwm1_auto_channels_temp:1 pwm1_auto_point1_temp:0 pwm1_auto_point1_temp_hyst:-3000 pwm1_auto_point2_temp:2 pwm1_auto_point3_temp:5 pwm1_auto_slope:16 pwm1_auto_start:70 pwm1_enable:2 pwm1_freq:23437 I know what pwm1_auto_channels_temp, pwm1_enable, pwm1_freq mean. What about the others? In particular, how the PWN value would be calculated for 40deg. Thanks in advance for any help Greg
Re: OT: GTX780 broken? - mystery solved ;)
On 2/26/21 6:48 AM, Alexander V. Makartsev wrote: On 26.02.2021 03:31, Grzesiek Sójka wrote: Hi there, It looks that my GPU may be broken. Frame buffer works ok but after starting xorg I get black screen. GPU is Asus GeForce GTX 780 (GTX780-DC2OC-3GD5). - Any suggestions?? Try it with proprietary nvidia supported driver: # apt install nvidia-driver nvidia-driver-libs nvidia-driver-bin nvidia-kernel-support It's a hardware problem, bad quality soldering. I king of solved the issue by worming up the GPU. Tutorials suggest to put GPU (stripped from cooler etc.) to an oven for 8-12min, ~200 deg. Celsius. I used heat gun. I don't think all the soldering was melted, it's rather temporary solution. Regards, Greg
OT: GTX780 broken?
Hi there, It looks that my GPU may be broken. Frame buffer works ok but after starting xorg I get black screen. GPU is Asus GeForce GTX 780 (GTX780-DC2OC-3GD5). -- # dmesg | grep nouveau [4.121840] fb0: switching to nouveaufb from EFI VGA [4.124068] nouveau :03:00.0: vgaarb: deactivate vga console [4.124167] nouveau :03:00.0: NVIDIA GK110 (0f0040a1) [4.245975] nouveau :03:00.0: bios: version 80.10.3a.00.13 [4.246847] nouveau :03:00.0: fb: 3072 MiB GDDR5 [4.317285] nouveau :03:00.0: DRM: VRAM: 3072 MiB [4.317287] nouveau :03:00.0: DRM: GART: 1048576 MiB [4.317291] nouveau :03:00.0: DRM: TMDS table version 2.0 [4.317293] nouveau :03:00.0: DRM: DCB version 4.0 [4.317295] nouveau :03:00.0: DRM: DCB outp 00: 01000f02 00020030 [4.317298] nouveau :03:00.0: DRM: DCB outp 01: 02000f00 [4.317300] nouveau :03:00.0: DRM: DCB outp 02: 08011f82 00020030 [4.317302] nouveau :03:00.0: DRM: DCB outp 04: 02022f62 00020010 [4.317304] nouveau :03:00.0: DRM: DCB outp 05: 04833fb6 0f420010 [4.317305] nouveau :03:00.0: DRM: DCB outp 06: 04033f72 00020010 [4.317308] nouveau :03:00.0: DRM: DCB conn 00: 1030 [4.317309] nouveau :03:00.0: DRM: DCB conn 01: 00020131 [4.317311] nouveau :03:00.0: DRM: DCB conn 02: 2261 [4.317313] nouveau :03:00.0: DRM: DCB conn 03: 00010346 [4.317688] nouveau :03:00.0: fifo: fault 00 [READ] at 0020 engine 04 [BAR1] client 07 [HUB/HOST_CPU] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.317825] nouveau :03:00.0: fifo: fault 00 [READ] at 0020 engine 04 [BAR1] client 07 [HUB/HOST_CPU] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.317837] nouveau :03:00.0: DRM: MM: using COPY for buffer copies [4.318247] nouveau :03:00.0: fifo: fault 01 [WRITE] at 0021 engine 04 [BAR1] client 08 [HUB/HOST_CPU_NB] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.318280] nouveau :03:00.0: fifo: fault 00 [READ] at 0021 engine 04 [BAR1] client 07 [HUB/HOST_CPU] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.319020] nouveau :03:00.0: fifo: fault 00 [READ] at 0021 engine 04 [BAR1] client 07 [HUB/HOST_CPU] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.320585] nouveau :03:00.0: fifo: fault 00 [READ] at 0021 engine 04 [BAR1] client 07 [HUB/HOST_CPU] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.320698] snd_hda_intel :03:00.1: bound :03:00.0 (ops nv50_audio_component_bind_ops [nouveau]) [4.320699] nouveau :03:00.0: fifo: fault 00 [READ] at 0021 engine 04 [BAR1] client 07 [HUB/HOST_CPU] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.705312] nouveau :03:00.0: DRM: allocated 2560x1600 fb: 0xa, bo (ptrval) [4.705370] nouveau :03:00.0: fifo: fault 01 [WRITE] at engine 04 [BAR1] client 08 [HUB/HOST_CPU_NB] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.705418] fbcon: nouveaudrmfb (fb0) is primary device [4.855740] nouveau :03:00.0: fifo: fault 01 [WRITE] at 0021 engine 04 [BAR1] client 08 [HUB/HOST_CPU_NB] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.857159] nouveau :03:00.0: fifo: fault 01 [WRITE] at 0021 engine 04 [BAR1] client 08 [HUB/HOST_CPU_NB] reason 00 [PDE] on channel -1 [00bfc25000 unknown] [4.857176] nouveau :03:00.0: fifo: DROPPED_MMU_FAULT [6.856688] nouveau :03:00.0: DRM: base-0: timeout [8.856736] nouveau :03:00.0: DRM: base-1: timeout [9.014830] nouveau :03:00.0: [drm] fb0: nouveaudrmfb frame buffer device [9.027975] [drm] Initialized nouveau 1.3.1 20120801 for :03:00.0 on minor 0 - Any suggestions??
Re: NULL pointer dereference
On 12/20/20 10:22 PM, Marko Randjelovic wrote: > How often does this happen? Not too often, once per few days. Does it happen only on high load? Difficult to say, rather not. > I'm asking > because you might boot live system with newest kernel possible to see > if this will happen. Also you can simply try with backported kernel > 5.9.6. Thanks for the tip btw I think it started after installing HPE Ethernet 1Gb 4-port 331T Adapter. This is server adapter end requires PCIe pin B5 and B6 covering to disconnect SMBus
Re: NULL pointer dereference
On 12/19/20 9:57 PM, Alexander V. Makartsev wrote: If this is recurring error, was it identical in terms of codes, trace and register data? Errors look similar but I'm not an expert. Some numbers are different. I think it started after installing HPE Ethernet 1Gb 4-port 331T Adapter. This is server adapter end requires PCIe pin B5 and B6 covering to disconnect SMBus
Re: NULL pointer dereference
On 12/19/20 8:43 PM, David Christensen wrote: > > Which Debian? Buster, up to date > Which kernel? cat /proc/version Linux version 4.19.0-13-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28) > Did you follow the instructions and reboot? Yes, reboot does not help Greg
NULL pointer dereference
Hi there, I found the following in my "server" log: == BUG: unable to handle kernel NULL pointer dereference at 0008 PGD 0 P4D 0 Oops: [#2] SMP PTI CPU: 5 PID: 12441 Comm: awk Tainted: G D 4.19.0-13-amd64 #1 Debian 4.19.160-2 Hardware name: FUJITSU D3162-B1/D3162-B1, BIOS V4.6.5.3 R1.23.0 for D3162-B1x 12/01/2014 RIP: 0010:unmap_page_range+0x561/0xa60 Code: 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 49 8b 46 28 <8b> 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f 84 d2 00 00 RSP: 0018:9c3a49167cd0 EFLAGS: 00010206 RAX: RBX: 8e2f47a83a10 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7faa2ed43000 R08: R09: 8e2ef8ae1c70 R10: 8e2f9e5df000 R11: R12: 7faa2ed42000 R13: 00014fd44025 R14: 9c3a49167dd0 R15: d073853f5100 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0008 CR3: 00015020a003 CR4: 000606e0 Call Trace: unmap_vmas+0x7f/0xb0 exit_mmap+0xaa/0x180 mmput+0x54/0x130 do_exit+0x33f/0xbb0 ? handle_mm_fault+0xd6/0x200 do_group_exit+0x3a/0xa0 __x64_sys_exit_group+0x14/0x20 do_syscall_64+0x53/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7faa2eaa99d6 Code: Bad RIP value. RSP: 002b:7ffd860931d8 EFLAGS: 0246 ORIG_RAX: 00e7 RAX: ffda RBX: 7faa2eb9a760 RCX: 7faa2eaa99d6 RDX: RSI: 003c RDI: RBP: R08: 00e7 R09: ff80 R10: 7ffd86093096 R11: 0246 R12: 7faa2eb9a760 R13: 0001 R14: 7faa2eba3428 R15: Modules linked in: ppp_deflate cfg80211 rfkill 8021q garp stp mrp llc ppp_async crc_ccitt ppp_generic slhc nfsd auth_rpcgss nfs_acl lockd grace sunrpc xt_nat nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipt_REJECT nf_reject_ipv4 nft_limit xt_limit xt_tcpudp nft_compat x_tables nft_counter nf_tables nfnetlink binfmt_misc bonding sch5636 sch56xx_common rc_it913x_v1 it913x af9033 dvb_usb_af9035 dvb_usb_v2 dvb_core rc_core snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl i915 x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_hda_codec coretemp snd_hda_core snd_hwdep snd_pcm xhci_pci ehci_pci ahci snd_timer xhci_hcd drm_kms_helper ehci_hcd libahci kvm snd mei_wdt tg3 iTCO_wdt irqbypass mei_me e1000e drm libata usbcore iTCO_vendor_support soundcore lpc_ich libphy mei i2c_algo_bit usb_common mfd_core crct10dif_pclmul crc32_pclmul ppdev ghash_clmulni_intel sg i2c_i801 intel_cstate evdev intel_uncore pcc_cpufreq video parport_pc button intel_rapl_perf pcspkr parport ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod crc32c_intel aacraid aesni_intel aes_x86_64 crypto_simd scsi_mod cryptd glue_helper thermal fan CR2: 0008 ---[ end trace 1f0672175c6e1ff0 ]--- RIP: 0010:unmap_page_range+0x55d/0xa60 Code: ff 83 ac 84 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 <49> 8b 46 28 8b 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f RSP: 0018:9c3a43a67cd0 EFLAGS: 00010202 RAX: 0004 RBX: 8e2f47a0deb0 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7f9f121d7000 R08: R09: 8e2f6a6e09c0 R10: 8e2f9e5df000 R11: R12: 7f9f121d6000 R13: 00081e49f025 R14: 9c3a43a67dd0 R15: d073a07927c0 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7faa2eaa99ac CR3: 00015020a003 CR4: 000606e0 Fixing recursive fault but reboot is needed! This is not the first time, so I suspect a persistent problem. I have no idea how to look for the solution. Any suggestions?? Just in case: # lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller:
Re: Qualcomm Snapdragon X12 LTE Modem
Hi there, To be more specific: I already installed Debian Sid and the tablet is HP Elite X2 1013 G3. I'm trying to learn how to use the modem mentioned to connect to the internet.
Qualcomm Snapdragon X12 LTE Modem
Hi there, I have a tablet equipped with the modem mentioned above. I do not have any experience with such devices. I would be grateful for some links with some information how to use it on Debian. regards
[Sid] gvfs & nfs shares icons on desktop
Hi there, I'm using laptop with Xfce and the following in the /etc/fstab: server:/mnt/ex /mnt/ex nfs vers=3,defaults,noauto,users 0 0 Recently I installed gvfs. Before gvfs installtion: I had nfs icon on the desktop, so I could easily mount/unmount nfs (by right click). Since this is mobile device nfs needs to be mounted on demand. After gvfs installation: The nfs share icon disappeared from the desktop. So I need to mount by a terminal command. Is there a way to have gvfs and have icons of nfs shares (defined in /etc.fstab) on the desktop?
.xsession-errors
Hi there, I found the following in the ~/.xsession-errors : dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 I was trying to search the net but no luck. Any suggestions? Missing packages? Thanks in advance for any help Greg
Re: [Sid] ahci: disk order
On 2020-07-24 21:08, Reco wrote: Hi. On Fri, Jul 24, 2020 at 10:03:01PM +0300, Andrei POPESCU wrote: On Vi, 24 iul 20, 21:58:26, Andrei POPESCU wrote: On Vi, 24 iul 20, 19:39:21, Grzesiek Sójka wrote: Hi there, I noticed that SATA disks appear in random order. More precisely, I have two disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and sometimes HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order? Not that I know of. I would like the disk connected to port 1 to be sda, disk connected to port 2 to be sdb and so on (like it was in the past) It might be possible with some special udev rules, Correction: probably not, since those names are assigned by the kernel. A correction over the correction ;) : - it's possible, it's called RENAME= in udev rules. - it's unneeded in about every case, given that wonderful /dev/disk directory. - and if it is needed for some reason, one's always better to use SYMLINK over the RENAME. Thanks for the info
[Sid] ahci: disk order
Hi there, I noticed that SATA disks appear in random order. More precisely, I have two disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and sometimes HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order? I would like the disk connected to port 1 to be sda, disk connected to port 2 to be sdb and so on (like it was in the past) Thanks in advance for any help.
[Sid] Tablet PC
Hi there, I have a tablet PC (withot keyboard). The problem is that "Unlock Keyring" window locks the focus on itself. This makes impossible to use on-screen keyboard. Is it possible to prevent "unlock Keyring" window from stilling focus? Thanks in advance for any help Greg
[Sid] hp active stylus support
Hi there, I'm considering buying Hp Elite X2 1013 tablet PC. I'm wondering if the Hp active stylus attached to the device is supported by Debian Sid. Any experiences? Thanks in advance for any help Greg
Re: Sid: /sbin/ifenslave missing??
On 5/17/20 12:34 PM, Sven Hartge wrote: Mind doing a "ifup -v bond0" to really see what is called how and where it fails in what way? after "ifup -v bond0" I get a larg number of following messages (probably 1000?): + [ -n ] + return 0 + setup_master + add_master + [ -f /sys/class/net/bond0/bonding/slaves ] + return + early_setup_master + sysfs fail_over_mac + [ -n ] + return 0 + setup_master + add_master + [ -f /sys/class/net/bond0/bonding/slaves ] + return + early_setup_master + sysfs fail_over_mac /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth (1000) reached run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2 ifup: failed to bring up bond0 BTW: # apt-list | grep ifup ifupdown/unstable,now 0.8.35+b1 amd64 [installed]
Re: Sid: /sbin/ifenslave missing??
On 5/17/20 12:13 PM, Sven Hartge wrote: How does your /etc/network/interfaces look like? Usally all the work is done via if-pre-up.d and if-up.d scripts provided by the ifenslave package. # cat /etc/network/interfaces source-directory /etc/network/interfaces.d auto bond0 iface bond0 inet static address 192.168.0.130 netmask 255.255.255.252 gateway 192.168.0.129 slaves eth0 eth1 mtu 9000 So I need to "adjust" network configuration to bond using iproute2 instead?
Sid: /sbin/ifenslave missing??
Hi there, After upgrading ifenslave from 2.9 to 2.10 i found that there if no /sbin/ifenslave binary. To restore network connectivity I had to manually downgrade to 2.9. Is it on purpose? If so, then how to properly configure link aggregation? Thank for any help in advance Greg
[solved] [sid] xorg keymap modifying
On 2/1/20 6:11 PM, Siard wrote: Grzesiek Sójka wrote: I do have sid running on tablet pc. I decided to use one of the physical keys as F11. Its keycode is 125 (the one with windows icon). To do it on console i put the following in /etc/rc.local: echo "keycode 125 = F11" | loadkeys And it works as expected. Unfortunately, I did not find a way to do it on xorg. xmodmap is used for that. $ xmodmap -e "keycode 125 = F11" Actually, I did try using xmodmap. What I didn't know was that the keycodes for console and x-environment may be different. The proper keycode is 133 (when running xorg). Thanks! -- Greg
[sid] xorg keymap modifying
Hi there, I do have sid running on tablet pc. I decided to use one of the physical keys as F11. Its keycode is 125 (the one with windows icon). To do it on console i put the following in /etc/rc.local: echo "keycode 125 = F11" | loadkeys And it works as expected. Unfortunately, I did not find a way to do it on xorg. Thanks in advance for any help. Greg
crc16
Hi there, Is there any utility to calculate crc16 (not the crc32) in Debian? Thanks in advance for any help
Temperatures rrd
Hi there, Since sensord was removed I would like to ask what do you use to log sensors readings to rrd database. Regards Greg
Re: Permanent Use of IPv4
On 2/15/19 4:12 PM, Stephen P. Molnar wrote:
Thanks for help from this gropup I can force the use of IPv4 by
running: sysctl -w net.ipv6.conf.all.disable_ipv6=1.
If you would like to prevent the kernel from loading IPv6 simply add the
following: ipv6.disable=1 to the kernel boot parameters. If you use lilo
then in the /etc/lilo.conf should be line beginning with append:
image=/boot/vmlinuz
root=/dev/md0
label=DebianSid
initrd=/boot/initrd.img
append="net.ifnames=0 biosdevname=0 ipv6.disable=1"
In case of grub.conf search for the line beginning with "linux":
# For booting GNU/Linux
menuentry "Stretch - remote" --id deb {
set root=(hd0,msdos2)
linux /boot/vmlinuz root=/dev/sda2 net.ifnames=0 biosdevname=0
ipv6.disable=1
initrd /boot/initrd.img
}
After reboot you should see ipv6.disable=1 in /proc/cmdline
Greg
Re: Permanent Use of IPv4
On 2/15/19 4:12 PM, Stephen P. Molnar wrote: Thanks for help from this gropup I can force the use of IPv4 by running: sysctl -w net.ipv6.conf.all.disable_ipv6=1. If you would like to prevent the kernel from loading IPv6 simply add the followink
Re: Stretch: APC Smart-UPS 1500 & nut
I corrected the subject. It was Sid but it should be stretch. Sorry, to many computers. On 2/12/19 10:54 AM, Grzesiek Sójka wrote: On 2/11/19 1:56 PM, Alexander V. Makartsev wrote: On 11.02.2019 16:20, Grzesiek Sójka wrote: Hi there, Ups is connected via usb: Bus 003 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Recently I noticed that nut stopped to recognize it (probably after some update): # /lib/nut/usbhid-ups -a APC Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found # cat /etc/nut/ups.conf [APC] driver = usbhid-ups port = auto I did try to fix the problem by adding vendor or product options or changing the driver but no luck. Any suggestions? Is the driver correct? I don't know about nut, but I had similar problems with APC SU1500 models in the past. They had some kind of firmware bug, or hardware problem with USB interface and sporadically loose connectivity to host. Also there was no [...] I have PLD-linux in chroot ad I did run the following: # /lib/nut/usbhid-ups -u root -a APC Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Using subdriver: APC HID 0.96 As you can see, result is positive. No reboot, the same kernel. So, this is 100% software problem related to Debian. A bug maybe?? Any suggestions? Workaround?? Different driver??
Re: Sid: APC Smart-UPS 1500 & nut
On 2/11/19 1:56 PM, Alexander V. Makartsev wrote: On 11.02.2019 16:20, Grzesiek Sójka wrote: Hi there, Ups is connected via usb: Bus 003 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Recently I noticed that nut stopped to recognize it (probably after some update): # /lib/nut/usbhid-ups -a APC Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found # cat /etc/nut/ups.conf [APC] driver = usbhid-ups port = auto I did try to fix the problem by adding vendor or product options or changing the driver but no luck. Any suggestions? Is the driver correct? I don't know about nut, but I had similar problems with APC SU1500 models in the past. They had some kind of firmware bug, or hardware problem with USB interface and sporadically loose connectivity to host. Also there was no [...] I have PLD-linux in chroot ad I did run the following: # /lib/nut/usbhid-ups -u root -a APC Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Using subdriver: APC HID 0.96 As you can see, result is positive. No reboot, the same kernel. So, this is 100% software problem related to Debian. A bug maybe?? Any suggestions? Workaround?? Different driver??
Sid: APC Smart-UPS 1500 & nut
Hi there, Ups is connected via usb: Bus 003 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Recently I noticed that nut stopped to recognize it (probably after some update): # /lib/nut/usbhid-ups -a APC Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 No matching HID UPS found # cat /etc/nut/ups.conf [APC] driver = usbhid-ups port = auto I did try to fix the problem by adding vendor or product options or changing the driver but no luck. Any suggestions? Is the driver correct? Ps. # apt --installed list | egrep 'linux-image|nut-' | cut -d' ' -f1 linux-image-4.18.0-0.bpo.3-amd64/now linux-image-4.19.0-0.bpo.1-amd64-unsigned/stretch-backports,now linux-image-amd64/stretch-backports,now nut-client/stable,now nut-server/stable,now
Re: e2fsck detail check
On 12/29/18 7:20 PM, Jude DaShiell wrote: I have a question about the -c fd command line switch. Would the valid options for fd be stdin stdout and stderr? I may need to provide remote support for someone and it will be helpful if e2fsck can show completion percentage as any repair happens. I use -C 0 (the capital "C") -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
12" ARM Debian Tablet
Hi there, I'm looking for a tablet with a native linux support (not chroot!). What I found is this: https://forum.xda-developers.com/showthread.php?s=5dd2e0cb26bc93f3f37e1eb58bf5023c=2195778=9 Unfortunately, N80XX are only 10". So, my question is if there is any at least 12" ARM tablet with native (not a chroot!) linux (preferebly Debian) support?? -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind
On 10/28/18 2:10 PM, Sven Joachim wrote: Wouldn't it be better to fix the init system that sets such a bad default PATH? Whatever init system that may be - sysv-rc's /etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this should not happen with sysvinit + sysv-rc. Please, keep in mind that /etc/init.d/rpcbind may also be invoked by /etc/network/if-up.d/mountnfs (after bringing up interfaces): # grep PATH /etc/network/if-up.d/mountnfs PATH=/sbin:/bin What init system do you use? # apt --installed list | grep sys | cut -f 1 -d ' ' busybox-syslogd/unstable,now init-system-helpers/unstable,now libboost-filesystem1.62.0/unstable,now libboost-system1.62.0/unstable,now libsystemd0/unstable,now sysv-rc/unstable,now sysvinit-core/unstable,now sysvinit-utils/unstable,now -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind
On 10/28/18 11:27 AM, Grzesiek Sójka wrote: Hi there, I just upgraded Sid and now I get the following during boot: [] Configuring network interfaces.../etc/init.d/rpcbind: 42: /etc/init.d/rpcbind: stat: not found /run/rpcbind not owned by root failed! Starting NFS common utilities: statd Not starting: portmapper is not running ... (warning). mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. done. [ ok ] Starting RPC port mapper daemon: rpcbind. [ ok ] Starting NFS common utilities: statd. The problem is caused by wrong setting of the PATH variable during the execution of the /etc/init.d/rpcbind script. The new version uses stat binary which is located in /usr/bin but the PATH is set to PATH='/sbin:/bin'. As a workaround I added PATH="$PATH:/usr/bin" to /etc/init.d/rpcbind. It works fine now. Please fix init scripts. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Sid: NFS after upgrade
Hi there, I just upgraded Sid and now I get the following during boot: [] Configuring network interfaces.../etc/init.d/rpcbind: 42: /etc/init.d/rpcbind: stat: not found /run/rpcbind not owned by root failed! Starting NFS common utilities: statd Not starting: portmapper is not running ... (warning). mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. done. [ ok ] Starting RPC port mapper daemon: rpcbind. [ ok ] Starting NFS common utilities: statd. Thus NFS directories are not mounted automatically during boot. But, after booting the command: mount -at nfs works perfectly. Moreover: # rpcinfo localhost program version netid addressserviceowner 104tcp 0.0.0.0.0.111 portmapper superuser 103tcp 0.0.0.0.0.111 portmapper superuser 102tcp 0.0.0.0.0.111 portmapper superuser 104udp 0.0.0.0.0.111 portmapper superuser 103udp 0.0.0.0.0.111 portmapper superuser 102udp 0.0.0.0.0.111 portmapper superuser 104local /run/rpcbind.sock portmapper superuser 103local /run/rpcbind.sock portmapper superuser 1000241udp 0.0.0.0.171.0 status 103 1000241tcp 0.0.0.0.162.173status 103 1000211udp 0.0.0.0.168.197nlockmgr superuser 1000213udp 0.0.0.0.168.197nlockmgr superuser 1000214udp 0.0.0.0.168.197nlockmgr superuser 1000211tcp 0.0.0.0.141.197nlockmgr superuser 1000213tcp 0.0.0.0.141.197nlockmgr superuser 1000214tcp 0.0.0.0.141.197nlockmgr superuser # egrep -v '^$|^#' /etc/default/nfs-common NEED_STATD=yes STATDOPTS= NEED_IDMAPD=no NEED_GSSD= # ll /run/rpc* -d -rw-r--r-- 1 root root 0 Oct 28 11:06 /run/rpc.statd.lock -rw-r--r-- 1 statd nogroup 5 Oct 28 11:06 /run/rpc.statd.pid drwxr-xr-x 2 _rpc root40 Oct 28 11:06 /run/rpcbind -r--r--r-- 1 root root 0 Oct 28 11:06 /run/rpcbind.lock -rw-r--r-- 1 root root 4 Oct 28 11:06 /run/rpcbind.pid srw-rw-rw- 1 root root 0 Oct 28 11:06 /run/rpcbind.sock Any ideas?? -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: ncurses problem
On 9/29/18 9:14 AM, Sven Joachim wrote: On 2018-09-29 11:02 +, Grzesiek Sójka wrote: On 9/28/18 9:44 AM, Sven Joachim wrote: Actually it is exactly the other way around. If LINES and COLUMNS are set in the environment, then the ncurses library will _not_ update the screen size upon receiving SIGWINCH, and that causes the behavior Grzesiek observed. This is documented in ncurses(3). It seems that the problem is not related to the environment: # set | egrep 'LINE|COL|BASHOPTS' BASHOPTS=checkwinsize:cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath BASH_LINENO=() COLORTERM=truecolor COLUMNS=119 LINES=84 # ssh localhost # set | egrep 'LINE|COL|BASHOPTS' BASHOPTS=checkwinsize:cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath BASH_LINENO=() COLUMNS=119 LINES=84 You need to look at the output of env(1) instead. By default bash does not export LINES and COLUMNS, so they are not visible in child programs: , | % bash | $ echo $LINES | 52 | $ dash | $ echo $LINES | ` Ok, you right. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: ncurses problem
On 9/28/18 9:44 AM, Sven Joachim wrote: On 2018-09-27 08:51 -0400, Greg Wooledge wrote: On Wed, Sep 26, 2018 at 10:38:53PM +, Grzesiek Sójka wrote: Hi there, I compiled following test program: == #include #include [snip] It's supposed to show current window dimension when resizing terminal window. Unfortunately, dimensions are not updated and it shows initial geometry. Interesting thing is that it works perfectly after "ssh localhost" or "su -". I tested on both, sid and stretch. exactly the same result. Any ideas?? My first thought is that your shell login profile, PS. I use xfce4 and lxdm. ... which is NOT how you normally log in, is turning on bash's checkwinsize option, which causes bash to set the LINES and COLUMNS variables upon receipt of a SIGWINCH (a signal that is sent when the window changes size). In the absence of that option, those variables might not be set at all, or might be set to the wrong size, and won't be updated when the window changes size while sitting in an idle shell. (What an ncurses program does with this signal, I honestly do not know.) So, just wild-ass guessing here, you might have put the necessaray "shopt -s checkwinsize" and "export LINES COLUMNS" into ~/.profile which is only read when you perform a shell login, and NOT when you perform an lxdm login. Actually it is exactly the other way around. If LINES and COLUMNS are set in the environment, then the ncurses library will _not_ update the screen size upon receiving SIGWINCH, and that causes the behavior Grzesiek observed. This is documented in ncurses(3). It seems that the problem is not related to the environment: # set | egrep 'LINE|COL|BASHOPTS' BASHOPTS=checkwinsize:cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath BASH_LINENO=() COLORTERM=truecolor COLUMNS=119 LINES=84 # ssh localhost # set | egrep 'LINE|COL|BASHOPTS' BASHOPTS=checkwinsize:cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath BASH_LINENO=() COLUMNS=119 LINES=84 -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
ncurses problem
Hi there,
I compiled following test program:
==
#include
#include
int main()
{
initscr();
int key;
while ((key = getch()) != 27) {
if (key == KEY_RESIZE) {
clear();
mvprintw(0, 0, "COLS = %d, LINES = %d", COLS, LINES);
for (int i = 0; i < COLS; i++)
mvaddch(1, i, '*');
refresh();
}
}
endwin();
return 0;
}
==
It's supposed to show current window dimension when resizing terminal
window. Unfortunately, dimensions are not updated and it shows initial
geometry. Interesting thing is that it works perfectly after "ssh
localhost" or "su -". I tested on both, sid and stretch. exactly the
same result.
Any ideas??
PS. I use xfce4 and lxdm.
--
Pozdrawiam
Grzesiek
Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: cannot open display: localhost:0.0 [solved]
On 9/23/18 2:36 PM, Rob van der Putten wrote: Hi there On 23/09/2018 13:48, Grzegorz Sójka wrote: I need to allow remote applications to connect to xorg. Since I log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Did you check port 6000? root@pc6:~# netstat -anp | grep 6000 tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 2684/Xorg tcp6 0 0 :::6000 :::* LISTEN 2684/Xorg Bingo! The command gave me empty output. Now -nolisten tcp is the default Xorg behaviour. Thus, you need to add -listen tcp flag explicitly. I added: arg=/usr/bin/X -background vt07 -listen tcp to /etc/lxdm/lxdm.conf and now it works perfectly. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: cannot open display: localhost:0.0
On 9/23/18 1:06 PM, Étienne Mollier wrote: On 9/23/18 2:59 PM, The Wanderer wrote: On 2018-09-23 at 10:24, Grzesiek Sójka wrote: On 9/23/18 10:30 AM, Étienne Mollier wrote: Maybe try: xhost +LOCAL: DISPLAY=localhost:0.0 xterm It does not work: # xhost +LOCAL; DISPLAY=localhost:0.0 xterm xhost: bad hostname "LOCAL" Did you try with '+LOCAL:' instead of '+LOCAL'? The colon is important. Indeed, furthermore if you need to do remote X, using X forwarding through SSH should be preferred and won't require you using “xhost” or removing “-nolisten” to Xorg parameters: ssh -YC user@remotehost I do not need encryption since all machines are in the same network segment. So I prefer not to use ssh. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: cannot open display: localhost:0.0
On 9/23/18 12:59 PM, The Wanderer wrote: On 2018-09-23 at 10:24, Grzesiek Sójka wrote: On 9/23/18 10:30 AM, Étienne Mollier wrote: On 9/23/18 1:48 PM, Grzegorz Sójka wrote: Hi there, I need to allow remote applications to connect to xorg. Since I log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Maybe try: xhost +LOCAL: DISPLAY=localhost:0.0 xterm It does not work: # xhost +LOCAL; DISPLAY=localhost:0.0 xterm xhost: bad hostname "LOCAL" Did you try with '+LOCAL:' instead of '+LOCAL'? The colon is important. $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm non-network local connections being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Please note that I need to enable remote connections. I use localhost just for testing. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: cannot open display: localhost:0.0
On 9/23/18 12:27 PM, Anders Andersson wrote: On Sun, Sep 23, 2018 at 4:24 PM, Grzesiek Sójka wrote: On 9/23/18 10:30 AM, Étienne Mollier wrote: On 9/23/18 1:48 PM, Grzegorz Sójka wrote: Hi there, I need to allow remote applications to connect to xorg. Since I log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Maybe try: xhost +LOCAL: DISPLAY=localhost:0.0 xterm It does not work: # xhost +LOCAL; DISPLAY=localhost:0.0 xterm xhost: bad hostname "LOCAL" xterm: Xt error: Can't open display: localhost:0.0 Are you using Wayland? If you're using debian testing you probably use wayland. Forgot to mention, I use Sid and xfce4. If i'm not wrong xfce does not support Wayland. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: cannot open display: localhost:0.0
On 9/23/18 10:30 AM, Étienne Mollier wrote: On 9/23/18 1:48 PM, Grzegorz Sójka wrote: Hi there, I need to allow remote applications to connect to xorg. Since I log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without -nolisten tcp flag. Unfortunately: $ xhost +localhost; DISPLAY=localhost:0.0 xterm localhost being added to access control list xterm: Xt error: Can't open display: localhost:0.0 Any suggestions?? Maybe try: xhost +LOCAL: DISPLAY=localhost:0.0 xterm It does not work: # xhost +LOCAL; DISPLAY=localhost:0.0 xterm xhost: bad hostname "LOCAL" xterm: Xt error: Can't open display: localhost:0.0 Please note that I need to connect also from remote hosts. I used localhost just for testing. Regards
