Re: setxkbmap cannot completely set compose key
To sum up: It helped by recompile and reinstall xterm. But only for a) newly started xterm's b) the xterm where the recompile/reinstall was run I don't remember if I was running stable or current at the time. /NilsOla On Thu, Feb 20, 2020 at 07:46:35AM +0100, NilsOla Nilsson wrote: > We had the same problem in this thread: > https://marc.info/?l=openbsd-misc=156352002210168=2 > > It is working fine for me now, so I can't reproduce it. > > /NilsOla > > > On Thu, Feb 20, 2020 at 06:03:53AM +, Xianwen Chen (陈贤文) wrote: > > Dear Ingo, > > > > Danke! > > > > On 2/19/20, Ingo Schwarze wrote: > > > Just to make sure it worked, could you please show the output of: > > > > > >$ setxkbmap -query > > > > The output is: > > > > rules: base > > model: pc105 > > layout: us > > variant:dvp > > options:compose:ralt > > > > > What exactly do you mean by "not able to use"? > > > If, while xterm is in focus, you press and relese the compose key, > > > then press and release the first key, then press and release the > > > second key, then press and release some latin letter key, what > > > exactly happens after each step? > > > > To type for example ø, I press and release the compose key, then press > > and release the / key, and then press and release the o key. I get > > /o > > on xterm, but ø on firefox. > > > > > Guessing blindly, the problem might be that while firefox finds a font > > > to display the character, xterm does not. Or that you have changed > > > your xterm configuration in some way that disables UTF-8 (it is on > > > by default). Can you please retry in xterm with a different character > > > that can be displayed in xterm out of the box, say U+00E5 LATIN > > > SMALL LETTER A WITH RING ABOVE? What happens if you type and release > > > ralt, then a, then a, then x? > > > > xterm can display å too, when I copies it using shift+insert from > > firefox or other places. > > > > xterm can display ø when I copies it using shift+insert from firefox > > or other places. > > > > > If none of the above lets you solve your problem yet, what does the > > > following command say: > > > > > > $ xterm -report-xres > > > > > > In an xterm started that way, does the compose key work? > > > Both with the character you want and with U+00E5 A RING? > > > > Ugh. xterm says: > > > > xterm: bad command line option "-report-xres" > > > > I forgot to report maybe an important piece of information. I use scim > > to type in Chinese. I use the default xdm. Here is my .xsession: > > > > export LC_CTYPE=en_US.UTF-8 > > > > export XMODIFIERS=@im=SCIM > > export GTK_IM_MODULE="scim" > > export QT_IM_MODULE="scim" > > scim -d > > > > setxkbmap -layout us -variant dvp -option compose:ralt > > > > exec dbus-launch /usr/X11R6/bin/fvwm > > > > I was going to ask my questions one by one so that I will not flood > > the email list with all my questions. But the scim question is the > > following. > > > > Quite the opposite of my compose key problem, I am not able to > > activate scim (by ctrl + space) on normal GUI programs (firefox, > > libreoffice, xpdf, keepassxc, emacs-gtk etc). > > > > But but but, I am able to activate scim on xterm and type Chinese there. > > > > So I have actually been typing æ, ø, å in firefox and copy back to > > xterm and typing Chinese using scim on xterm and copy back to firefox > > / libreoffice for like more than half a year I had this problem on > > OpenBSD 6.5 too (I was using OpenBSD like 10 years ago for some time > > and also in between in the past ten years. I went back, last year, to > > OpenBSD... Was using NetBSD even longer time ago and started using > > unix-like system around 2001 or 2002). But I did not have this > > type of scim / compose key problems on Debian, NixOS, Arch Linux, or > > Void Linux, which are the Linux distributions that I used in the > > recent years. > > > > Good morning, by the way! > > > > Yours sincerely, > > Xianwen > > -- > Nils Ola Nilsson, email nils...@abc.se, tel +46-70-374 69 89 -- Nils Ola Nilsson, email nils...@abc.se, tel +46-70-374 69 89 signature.asc Description: PGP signature
Re: suggestions for USB printer (maybe even with scanner)?
On 2020-02-18 21:28, Stuart Longland wrote: On 6/2/20 7:26 am, Adam Thompson wrote: I don't know what you need in a printer, and I don't know what you mean by cheap, so... YMMV. However, I've found Brother **LASER** printers to be very good, and most of them support PCL6 and/or PS3. For example, the HL-L2370DW can only connect via USB, and supports PCL6, and currently sells for ~C$150-160. Somewhat related, does this hold true for their Ethernet-connected printers as well? We have an Epson WF-7510 which is due for replacement and while I can set up OpenBSD on a small box to act as a print server, having something I can point OpenBSD's lpd or cups at over a network is helpful too. Yes, I have a Brother laser printer that I print to using lpd. I can send it PDF or postscript documents (or raw text) via lpr and it prints just fine, without any drivers or cups or other such nonsense.
Re: setxkbmap cannot completely set compose key
We had the same problem in this thread: https://marc.info/?l=openbsd-misc=156352002210168=2 It is working fine for me now, so I can't reproduce it. /NilsOla On Thu, Feb 20, 2020 at 06:03:53AM +, Xianwen Chen (陈贤文) wrote: > Dear Ingo, > > Danke! > > On 2/19/20, Ingo Schwarze wrote: > > Just to make sure it worked, could you please show the output of: > > > >$ setxkbmap -query > > The output is: > > rules: base > model: pc105 > layout: us > variant:dvp > options:compose:ralt > > > What exactly do you mean by "not able to use"? > > If, while xterm is in focus, you press and relese the compose key, > > then press and release the first key, then press and release the > > second key, then press and release some latin letter key, what > > exactly happens after each step? > > To type for example ø, I press and release the compose key, then press > and release the / key, and then press and release the o key. I get > /o > on xterm, but ø on firefox. > > > Guessing blindly, the problem might be that while firefox finds a font > > to display the character, xterm does not. Or that you have changed > > your xterm configuration in some way that disables UTF-8 (it is on > > by default). Can you please retry in xterm with a different character > > that can be displayed in xterm out of the box, say U+00E5 LATIN > > SMALL LETTER A WITH RING ABOVE? What happens if you type and release > > ralt, then a, then a, then x? > > xterm can display å too, when I copies it using shift+insert from > firefox or other places. > > xterm can display ø when I copies it using shift+insert from firefox > or other places. > > > If none of the above lets you solve your problem yet, what does the > > following command say: > > > > $ xterm -report-xres > > > > In an xterm started that way, does the compose key work? > > Both with the character you want and with U+00E5 A RING? > > Ugh. xterm says: > > xterm: bad command line option "-report-xres" > > I forgot to report maybe an important piece of information. I use scim > to type in Chinese. I use the default xdm. Here is my .xsession: > > export LC_CTYPE=en_US.UTF-8 > > export XMODIFIERS=@im=SCIM > export GTK_IM_MODULE="scim" > export QT_IM_MODULE="scim" > scim -d > > setxkbmap -layout us -variant dvp -option compose:ralt > > exec dbus-launch /usr/X11R6/bin/fvwm > > I was going to ask my questions one by one so that I will not flood > the email list with all my questions. But the scim question is the > following. > > Quite the opposite of my compose key problem, I am not able to > activate scim (by ctrl + space) on normal GUI programs (firefox, > libreoffice, xpdf, keepassxc, emacs-gtk etc). > > But but but, I am able to activate scim on xterm and type Chinese there. > > So I have actually been typing æ, ø, å in firefox and copy back to > xterm and typing Chinese using scim on xterm and copy back to firefox > / libreoffice for like more than half a year I had this problem on > OpenBSD 6.5 too (I was using OpenBSD like 10 years ago for some time > and also in between in the past ten years. I went back, last year, to > OpenBSD... Was using NetBSD even longer time ago and started using > unix-like system around 2001 or 2002). But I did not have this > type of scim / compose key problems on Debian, NixOS, Arch Linux, or > Void Linux, which are the Linux distributions that I used in the > recent years. > > Good morning, by the way! > > Yours sincerely, > Xianwen -- Nils Ola Nilsson, email nils...@abc.se, tel +46-70-374 69 89 signature.asc Description: PGP signature
Re: Cannot start conversation using talk
On 19.02.2020. 22:08, b...@0x1bi.net wrote: I've set my hostname to point to 127.0.0.1 and I still receive the same error. I tried with and without the domain information. Is there a log for talkd or inetd? I've attempted to use the -d flag for inetd however I receive no error messages or warnings. Ben Raskin. I haven't used talk in decades (literally), but here is an interesting comment from /etc/hosts on the system I am currently logged in (a Slackware Linux): # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. Just add the names, addresses # and any aliases to this file... # # By the way, Arnt Gulbrandsen says that 127.0.0.1 # should NEVER be named with the name of the machine. It causes problems # for some (stupid) programs, irc and reputedly talk. :^) # # For loopbacking. 127.0.0.1localhost 172.30.1.10 myhost.mydomain.lan myhost So it seems that talk had always been picky about host name resolution. Appart from setting your address and host and domain names in /etc/hosts, do you have a "lookup file bind" line in /etc/resolv.conf ? If you don't, it defaults to "lookup bind file", so it will query DNS first, and then look into /etc/hosts. There is a possibility this too can confuse talk. Best regards, Zeljko Jovanovic
Re: setxkbmap cannot completely set compose key
Dear Ingo, Danke! On 2/19/20, Ingo Schwarze wrote: > Just to make sure it worked, could you please show the output of: > >$ setxkbmap -query The output is: rules: base model: pc105 layout: us variant:dvp options:compose:ralt > What exactly do you mean by "not able to use"? > If, while xterm is in focus, you press and relese the compose key, > then press and release the first key, then press and release the > second key, then press and release some latin letter key, what > exactly happens after each step? To type for example ø, I press and release the compose key, then press and release the / key, and then press and release the o key. I get /o on xterm, but ø on firefox. > Guessing blindly, the problem might be that while firefox finds a font > to display the character, xterm does not. Or that you have changed > your xterm configuration in some way that disables UTF-8 (it is on > by default). Can you please retry in xterm with a different character > that can be displayed in xterm out of the box, say U+00E5 LATIN > SMALL LETTER A WITH RING ABOVE? What happens if you type and release > ralt, then a, then a, then x? xterm can display å too, when I copies it using shift+insert from firefox or other places. xterm can display ø when I copies it using shift+insert from firefox or other places. > If none of the above lets you solve your problem yet, what does the > following command say: > > $ xterm -report-xres > > In an xterm started that way, does the compose key work? > Both with the character you want and with U+00E5 A RING? Ugh. xterm says: xterm: bad command line option "-report-xres" I forgot to report maybe an important piece of information. I use scim to type in Chinese. I use the default xdm. Here is my .xsession: export LC_CTYPE=en_US.UTF-8 export XMODIFIERS=@im=SCIM export GTK_IM_MODULE="scim" export QT_IM_MODULE="scim" scim -d setxkbmap -layout us -variant dvp -option compose:ralt exec dbus-launch /usr/X11R6/bin/fvwm I was going to ask my questions one by one so that I will not flood the email list with all my questions. But the scim question is the following. Quite the opposite of my compose key problem, I am not able to activate scim (by ctrl + space) on normal GUI programs (firefox, libreoffice, xpdf, keepassxc, emacs-gtk etc). But but but, I am able to activate scim on xterm and type Chinese there. So I have actually been typing æ, ø, å in firefox and copy back to xterm and typing Chinese using scim on xterm and copy back to firefox / libreoffice for like more than half a year I had this problem on OpenBSD 6.5 too (I was using OpenBSD like 10 years ago for some time and also in between in the past ten years. I went back, last year, to OpenBSD... Was using NetBSD even longer time ago and started using unix-like system around 2001 or 2002). But I did not have this type of scim / compose key problems on Debian, NixOS, Arch Linux, or Void Linux, which are the Linux distributions that I used in the recent years. Good morning, by the way! Yours sincerely, Xianwen
Re: Cannot start conversation using talk
I've set my hostname to point to 127.0.0.1 and I still receive the same error. I tried with and without the domain information. Is there a log for talkd or inetd? I've attempted to use the -d flag for inetd however I receive no error messages or warnings. Ben Raskin.
Re: Cannot start conversation using talk
On Wed, Feb 19, 2020 at 07:13:48PM +, b...@0x1bi.net wrote: > > Do you have a correct entry with the machine hostname (full hostname(1) > > output) in /etc/hosts? > > I don't. What should the entry look like? Should the hostname point to > 0.0.0.0? It should point to 127.0.0.1
Re: Cannot start conversation using talk
> Do you have a correct entry with the machine hostname (full hostname(1) > output) in /etc/hosts? I don't. What should the entry look like? Should the hostname point to 0.0.0.0? Ben Raskin.
Re: Cannot start conversation using talk
On Wed, Feb 19, 2020 at 06:25:56PM +, b...@0x1bi.net wrote: > >Did you restart inetd after editing inetd.conf? It has to decide what > >ports to listen on when it starts up, which means it isn't going to > >notice edits. > > Yes, I restarted inetd. I still receive the 'Couldn't bind to socket: > Can't assign requested address' > > I'm not attempting to talk to another user on a different host, I'm > attempting to contact a local user, which I'm assuming will not pose > any issues. I use talk and ytalk [1] regularly on OpenBSD machines, between local users. Do you have a correct entry with the machine hostname (full hostname(1) output) in /etc/hosts? [1] https://www.cambus.net/talk-and-ytalk-nostalgia/
Re: Cannot start conversation using talk
>Did you restart inetd after editing inetd.conf? It has to decide what >ports to listen on when it starts up, which means it isn't going to >notice edits. Yes, I restarted inetd. I still receive the 'Couldn't bind to socket: Can't assign requested address' I'm not attempting to talk to another user on a different host, I'm attempting to contact a local user, which I'm assuming will not pose any issues. Ben Raskin.
Re: Cannot start conversation using talk
On 2020-02-19 9:48, b...@0x1bi.net wrote: I verified the output of rcctl and inetd is running. Did you restart inetd after editing inetd.conf? It has to decide what ports to listen on when it starts up, which means it isn't going to notice edits. -- Matthew Weigel
Re: Cannot start conversation using talk
I verified the output of rcctl and inetd is running. Ben Raskin.
Re: Cannot start conversation using talk
On Wed, Feb 19, 2020 at 03:38:24PM +, b...@0x1bi.net wrote: > > Hello, everyone; > > I'm attempting to initiate a conversation via talk(1) however upon > executing the command I receive the following error: > > talk: Couldn't bind to control socket: Can't assign requested address > > I've uncommented the line in /etc/inetd.conf which corresponds to the > talkd daemon, however talk still refuses to work: > > ntalk dgram udp waitroot/usr/libexec/ntalkd ntalkd > > Am I missing something? Does anyone else have this issue? Thank you in > advance. > > Ben Raskin. > inetd is not enabled by default. -Otto
Cannot start conversation using talk
Hello, everyone; I'm attempting to initiate a conversation via talk(1) however upon executing the command I receive the following error: talk: Couldn't bind to control socket: Can't assign requested address I've uncommented the line in /etc/inetd.conf which corresponds to the talkd daemon, however talk still refuses to work: ntalk dgram udp waitroot/usr/libexec/ntalkd ntalkd Am I missing something? Does anyone else have this issue? Thank you in advance. Ben Raskin.
Re: setxkbmap cannot completely set compose key
Hi, Xianwen Chen wrote on Wed, Feb 19, 2020 at 10:37:58AM +: > I run OpenBSD 6.6 amd64. I'm trying to reproduce on OpenBSD-current. > The window manager is fvwm I'm using that, too. > with stock configuration. Well, my configuration is much less bloated than the default (125 rather than 491 lines). But that shouldn't make a difference. > I am not able to completely set compose key by > > $ setxkbmap -layout us -variant dvp -option compose:ralt Just to make sure it worked, could you please show the output of: $ setxkbmap -query > What I meant by *not completely* is that I am able to use _right alt_ > as the compose key on for example Firefox. However, on xterm, I am not > able to use the compose key. It certainly works for me. What exactly do you mean by "not able to use"? If, while xterm is in focus, you press and relese the compose key, then press and release the first key, then press and release the second key, then press and release some latin letter key, what exactly happens after each step? Guessing blindly, the problem might be that while firefox finds a font to display the character, xterm does not. Or that you have changed your xterm configuration in some way that disables UTF-8 (it is on by default). Can you please retry in xterm with a different character that can be displayed in xterm out of the box, say U+00E5 LATIN SMALL LETTER A WITH RING ABOVE? What happens if you type and release ralt, then a, then a, then x? If none of the above lets you solve your problem yet, what does the following command say: $ xterm -report-xres In an xterm started that way, does the compose key work? Both with the character you want and with U+00E5 A RING? Yours, Ingo
setxkbmap cannot completely set compose key
Dear OpenBSD users, I run OpenBSD 6.6 amd64. The window manager is fvwm with stock configuration. I am not able to completely set compose key by $ setxkbmap -layout us -variant dvp -option compose:ralt What I meant by *not completely* is that I am able to use _right alt_ as the compose key on for example Firefox. However, on xterm, I am not able to use the compose key. Any hint? Yours sincerely, Xianwen
Re: Old thread, but wondering if any updates?
On 2020-02-19, myml...@gmx.com wrote: > I posted this way back in 2017 but i'm wondering if anything has changed... > > https://marc.info/?l=openbsd-misc=149613307021262=2 > > Is the 16Tb restriction been removed for full disk encryption? The only thing that changed is that the failure is now more obvious from the error message - the limit remains.
Re: Packages for 6.6 mips64el missing from cdn.openbsd.org
Stuart Henderson writes: > On 2020-02-12, Xiyue Deng wrote: >> --=-=-= >> Content-Type: text/plain >> >> Xiyue Deng writes: >> >>> Hi, >>> >>> It looks like cdn.openbsd.org[1] doesn't sync the 6.6 packages for mips64el >>> from ftp.openbsd.org[2]. >>> >>> [1] http://cdn.openbsd.org/pub/OpenBSD/6.6/packages/ >>> [2] http://ftp.openbsd.org/pub/OpenBSD/6.6/packages/ >> >> Ping. >> >> --=-=-= >> Content-Type: application/pgp-signature; name="signature.asc" >> >> --=-=-=-- >> >> > > cdn.openbsd.org is basically just a web cache, pointing at various different > origin servers in different places round the world, and it varies for > different > directories. > > See what you get in "Backend Name" from this, that will give a clue at which > origin server has the problem: > > curl -I http://cdn.openbsd.org/pub/OpenBSD/6.6/packages/ > > If it is one of the leaseweb ones (which is used as an origin server in some > places) then you also need to look at which of them it is, because the > leaseweb > sites are 3rd-level mirrors and all sync from different 2nd-levels. Thanks Stuart. The output of the curl command is below for reference: , | HTTP/1.1 200 OK | Server: nginx/1.16.1 | Content-Type: text/html | Backend-Name: 5GnZ0LBU5CzDw9NCjFbkjI--F_mirror_leaseweb_com__primary_ | Content-Length: 4119 | Accept-Ranges: bytes | Date: Wed, 19 Feb 2020 08:31:05 GMT | Via: 1.1 varnish | Age: 89 | Connection: keep-alive | X-Served-By: cache-bur17572-BUR | X-Cache: HIT | X-Cache-Hits: 1 | X-Timer: S1582101065.252099,VS0,VE0 ` The good news is that the issue seems to have been fixed since my last ping, so everything is good now. signature.asc Description: PGP signature
