Re: Recommended simple PDF viewer to replace Evince
On Tue, 05 Dec 2023 14:30:01 +0100, Eric S Fraga wrote: > I use zathura which is also quite light but I'm not sure if you can > print from it. I tend to print directly using lp although very > infrequently in any case. In zathura :print brings up the Gtk+ print dialog.
Re: fetchmail
On Mon, 12 Sep 2022 19:50:01 +0200, Gerard ROBIN wrote: > Le Mon, Sep 12, 2022 at 09:06:08AM -0000, Bert Riding a écrit : >> Date: Mon, 12 Sep 2022 09:06:08 - (UTC) >> From: Bert Riding >> To: debian-user@lists.debian.org >> Subject: Re: fetchmail >> >> On Sat, 10 Sep 2022 22:50:01 +0200, Gerard ROBIN wrote: >> >> > Hello, >> > in Bullseye (stable) fetchmail works fine, but in Bookworm (testing) I >> > get: >> > >> > fetchmail: can't accept options while a background fetchmail is running. >> > argc = 5, arg list: >> > arg 1 = "-k" >> > arg 2 = "--ssl" >> > arg 3 = "--mda" >> > arg 4 = "/usr/bin/procmail -d %T" >> > >> > No mail arrived since >> > >> > ps ax | grep fetchmail >> > >> > 1943 ?Ss 0:00 fetchmail --nodetach --daemon 300 >> > 4220 pts/1S+ 0:00 grep fetchmail >> > >> > how can i prevent the fetchmail daemon from running on startup in >> > Bookworm ? >> >> >> Fetchmail can now run as a daemon, started by systemd. > Ok good to know. > >> I think maybe the real >> solution for this problem is >> >> systemctl --user stop fetchmail.service >> systemctl --user disable fetchmail.service > it works, just add --user option. > I keep fetchmail. > > Thanks so much I found help in /usr/share/doc/fetchmail after noticing an unexpected error from fetchmail about waking up.
Re: fetchmail
On Sat, 10 Sep 2022 22:50:01 +0200, Gerard ROBIN wrote: > Hello, > in Bullseye (stable) fetchmail works fine, but in Bookworm (testing) I > get: > > fetchmail: can't accept options while a background fetchmail is running. > argc = 5, arg list: > arg 1 = "-k" > arg 2 = "--ssl" > arg 3 = "--mda" > arg 4 = "/usr/bin/procmail -d %T" > > No mail arrived since > > ps ax | grep fetchmail > > 1943 ?Ss 0:00 fetchmail --nodetach --daemon 300 > 4220 pts/1S+ 0:00 grep fetchmail > > how can i prevent the fetchmail daemon from running on startup in > Bookworm ? Fetchmail can now run as a daemon, started by systemd. I think maybe the real solution for this problem is systemctl --user stop fetchmail.service systemctl --user disable fetchmail.service and so on. Bert
Re: Wpa_supplicant Error: No such device
Yes, I'm sorry I didn't mention that my device name was merely an
example. I wonder if "ip link show" or "ls -l /sys/class/net" or the
obsolete "ifconfig a" give the same device name. Udevadm might
help, too. "udevadm info -e | grep .wl" for instance. The name you are
using is the name using the MAC address, which is the last match as udev
lists the names, and won't be used if udev finds another name first. See
https://major.io/2015/08/21/understanding-systemds-predictable-network-device-names/
"nl80211" is the correct name of the driver. I apologize for the error.
On Fri, 12 Jul 2019 04:30:02 +0200, Patrick Bartek wrote:
> On Thu, 11 Jul 2019 21:02:44 - (UTC)
> Bert Riding wrote:
>
>> You could try using the actual device for the -i option (interface)...like
>> wlan0 or, in the new notation wlp3s0, and use nl80122 as the -D
>> option (driver).
>
> iw dev or ip a report the device name to be wlx00e04c2a23c4. This
> designation never changes regardless of reboots or which USB port I
> plug the wireless device into. I examined the output of dmesg and noted
> that udev had reassigned wlan0 to this new name. Don't know why. And it
> does work when scanning or finding device info or bringing device up or
> down. But I initially tried wlan0 anyway. Got "No such
> device . . ." etc.
>
> I tried using -D nl80211 (did you transpose digits?) and not using it.
> wpa_supplicant failed with the same error noted below. Also, tried
> wext. Ditto.
>
> Haven't tried wlp3s0, but haven't found ANY reference to that name
> on the system regardless of which command I use to show network devices.
>
> Thanks for your input.
>
> B
>
>> On Thu, 11 Jul 2019 02:10:02 +0200, Patrick Bartek wrote:
>>
>> > A problem when trying to associate with a wireless router
>> > (WPA2). Get the following error when manually executing:
>> >
>> > wpa_supplicant -i wlx
>> > -c /etc/wpa_supplicant/wpa_supplicant.conf
>> >
>> > Could not read interface wlx flags: No such device
>> > nl80211: Driver does not support authentication/association or connect
>> > commands
>> > nl80122: [can't read my own writing on this one]
>> >
>> > Wpa_supplicant fails whether I use the -B (background) switch or not.
>> >
>> > Here's the wpa_supplicant.conf file:
>> >
>> >
>> > ctrl_interface=DIR=/run/wpa_supplicant
>> > update_config=1
>> >
>> > network={
>> >ssid="ROUTERNAME"
>> > # scan_ssid=1
>> > # key_mgmt=WPA-PSK
>> > # psk="SECRETPASSPHRASE"
>> >psk=longhexnumber
>> > }
>> >
>> > I've tried with and without the commented lines. Same results.
>> >
>> > Here's the wifi portion of my /etc/network/interfaces
>> >
>> > allow-hotplug wlx
>> > iface wlx inet dhcp
>> >wpa-ssid ROUTERNAME
>> > # wpa-key-mgmt WPA-PSK
>> > # wpa-group TKIP CCMP
>> > # wpa-psk SECRETPASSPHRASE
>> >wpa-psk longhexnumber
>> >
>> > The wireless is a Rosewill USB RNX-N180UBEv3. It is UP after boot and
>> > scanning wifi routers works. System tries to associate to router at
>> > boot, but fails. Correct kernel module (rtl8192eu) is loaded.
>> >
>> > Anyone got an idea of why wpa_supplicant is failing? And how to fix
>> > it? All commands issued as root.
>> >
>> > FYI: I have an atypical Stretch install: No desktop environment,
>> > window manager only; sysvinit, but systemd libraries still installed.
>> > Boots to terminal, login there, then startx, if I want a GUI. Wifi UP
>> > at terminal and scanning works. This is not a laptop. Wired ethernet
>> > works and has always (12 years) worked.
>> >
>> > Thanks.
>> >
>> > B
>>
Re: Wpa_supplicant Error: No such device
You could try using the actual device for the -i option (interface)...like
wlan0 or, in the new notation wlp3s0, and use nl80122 as the -D
option (driver).
On Thu, 11 Jul 2019 02:10:02 +0200, Patrick Bartek wrote:
> A problem when trying to associate with a wireless router
> (WPA2). Get the following error when manually executing:
>
> wpa_supplicant -i wlx
> -c /etc/wpa_supplicant/wpa_supplicant.conf
>
> Could not read interface wlx flags: No such device
> nl80211: Driver does not support authentication/association or connect
> commands
> nl80122: [can't read my own writing on this one]
>
> Wpa_supplicant fails whether I use the -B (background) switch or not.
>
> Here's the wpa_supplicant.conf file:
>
>
> ctrl_interface=DIR=/run/wpa_supplicant
> update_config=1
>
> network={
> ssid="ROUTERNAME"
> # scan_ssid=1
> # key_mgmt=WPA-PSK
> # psk="SECRETPASSPHRASE"
> psk=longhexnumber
> }
>
> I've tried with and without the commented lines. Same results.
>
> Here's the wifi portion of my /etc/network/interfaces
>
> allow-hotplug wlx
> iface wlx inet dhcp
> wpa-ssid ROUTERNAME
> # wpa-key-mgmt WPA-PSK
> # wpa-group TKIP CCMP
> # wpa-psk SECRETPASSPHRASE
> wpa-psk longhexnumber
>
> The wireless is a Rosewill USB RNX-N180UBEv3. It is UP after boot and
> scanning wifi routers works. System tries to associate to router at
> boot, but fails. Correct kernel module (rtl8192eu) is loaded.
>
> Anyone got an idea of why wpa_supplicant is failing? And how to fix
> it? All commands issued as root.
>
> FYI: I have an atypical Stretch install: No desktop environment,
> window manager only; sysvinit, but systemd libraries still installed.
> Boots to terminal, login there, then startx, if I want a GUI. Wifi UP
> at terminal and scanning works. This is not a laptop. Wired ethernet
> works and has always (12 years) worked.
>
> Thanks.
>
> B
Re: Locale issue
On Tue, 05 Jun 2018 18:30:02 +0200, John wrote: > Whenever I run emacs on my 64bit Debian (Jessie) machine via ssh I see > > (process:20589): Gtk-WARNING **: Locale not supported by C library. > Using the fallback 'C' locale. > > root@snout:~# printenv (edited) > > LANG=en_GB.UTF-8 > XTERM_LOCALE=C > XTERM_VERSION=XTerm(312) > LANGUAGE=en_GB:en > LC_CTYPE=en_US.UTF-8 > > Is this just another annoyance or can it be stopped? > > ==John ffitch you could compare the results of "locale" and "locale -a" or perhaps install the package localehelper if needed.
Re: Xorg replaces TTY1
On Sun, 22 Nov 2015 00:40:01 +0100, berenger.morel wrote: > Hello. > > There is a behavior change I noticed when I switched to Jessie, which > have always annoyed me but that I never tried to resolve. > > The change is that now, when I use startx on TTY1, Xorg replaces the > TTY. I understand that it is not a problem for 99% of users, but I would > like to know how to configure Debian to stay with the old behavior (aka: > start Xorg on TTY 7+). > Do someone have any clue about how to do that? > > Thanks. > > PS: I am not registed on this list, so please CC me. I too am not a fan of the new behavior. X now runs on the terminal from which it is started, so to run it on tty7 you must run a getty on tty7 and log in there first. Do this by editing /etc/inittab (if using init) or /etc/systemd/logind.conf (if using systemd.)
Re: Ctrl-alt-del to restart window manager with xfce in wheezy?
On Mon, 10 Jun 2013 04:30:02 +0200, Rick Thomas wrote: I've got xfce window manager installed on pretty-much as it comes fresh-out-of-the-box Wheezy. I'd like to have ctrl-alt-del restart the window manager. I've configured it to do so with dpkg-reconfigure keyboard- configuration, but (even after a reboot) that doesn't seem to do the job. Anybody know what I'm missing? Thanks! Sorry to e-mail, I read the list on usenet and they won't let me post. from xfce4, left click in root window, Settings, Session and Startup, Application Autostart, Add Name it what you want, describe how you want, the command should be something like setxkbmap -option terminate:ctrl_alt_bksp. I have this and also the /etc/default/keyboard entry XKBOPTIONS=terminate:ctl_alt_bksp in a kind of belt and suspenders config method. BR -- Bert Riding rerid...@xmission.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130611215806.56473...@blacky.savageroad.com
