Re: dell universal d6000 dock
anybody On 2/5/19 5:17 PM, myml...@gmx.com wrote: Hi, I am running current from Jan 21st on a dell latitude 7490 (dmesg below) and was hoping to get a usb-c dock connected so that I could use 2 display ports, the hdmi, eth and extra usb ports in one easy to disconnect usb-c connection. The hdmi seems to work ok but I get the following errors in /var/log/messages when I plug/unplug a display port. Feb 5 16:48:56 curry /bsd: uhub1 at uhub0 port 1 configuration 1 interface 0 "GenesysLogic USB2.1 Hub" rev 2.10/88.16 addr 5 Feb 5 16:48:56 curry apmd: battery status: high. external power status: connected. estimated battery life 95% Feb 5 16:48:57 curry /bsd: uhub2 at uhub1 port 2 configuration 1 interface 0 "GenesysLogic USB2.1 Hub" rev 2.10/88.17 addr 6 Feb 5 16:48:58 curry /bsd: uhub3 at uhub1 port 3 configuration 1 interface 0 "Genesys Logic USB2.0 Hub" rev 2.00/88.32 addr 7 Feb 5 16:48:59 curry /bsd: uhidev2 at uhub3 port 1 configuration 1 interface 0 "Bizlink D6000 Controller" rev 2.00/0.18 addr 8 Feb 5 16:48:59 curry /bsd: uhidev2: iclass 3/0, 1 report id Feb 5 16:48:59 curry /bsd: uhid4 at uhidev2 reportid 1: input=0, output=0, feature=1 Feb 5 16:48:59 curry /bsd: uhub4 at uhub0 port 13 configuration 1 interface 0 "GenesysLogic USB3.1 Hub" rev 3.10/88.16 addr 9 Feb 5 16:49:00 curry /bsd: uaudio0 at uhub4 port 1 configuration 1 interface 2 "DisplayLink Dell Universal Dock D6000" rev 3.10/31.27 addr 10 Feb 5 16:49:00 curry /bsd: uaudio0: audio descriptors make no sense, error=4 Feb 5 16:49:00 curry /bsd: ugen1 at uhub4 port 1 configuration 1 "DisplayLink Dell Universal Dock D6000" rev 3.10/31.27 addr 10 Feb 5 16:49:01 curry /bsd: uhub5 at uhub4 port 2 configuration 1 interface 0 "GenesysLogic USB3.1 Hub" rev 3.10/88.17 addr 11 Feb 5 16:49:01 curry /bsd: uhub2 detached Feb 5 16:49:01 curry /bsd: uhid4 detached Feb 5 16:49:01 curry /bsd: uhidev2 detached Feb 5 16:49:01 curry /bsd: uhub3 detached Feb 5 16:49:01 curry /bsd: uhub1 detached Feb 5 16:49:02 curry /bsd: uhub1 at uhub0 port 1 configuration 1 interface 0 "GenesysLogic USB2.1 Hub" rev 2.10/88.16 addr 5 Feb 5 16:49:03 curry /bsd: uhub2 at uhub1 port 2 configuration 1 interface 0 "GenesysLogic USB2.1 Hub" rev 2.10/88.17 addr 6 Feb 5 16:49:04 curry /bsd: uhub3 at uhub1 port 3 configuration 1 interface 0 "Genesys Logic USB2.0 Hub" rev 2.00/88.32 addr 7 Feb 5 16:49:05 curry /bsd: uhidev2 at uhub3 port 1 configuration 1 interface 0 "Bizlink D6000 Controller" rev 2.00/0.18 addr 8 Feb 5 16:49:05 curry /bsd: uhidev2: iclass 3/0, 1 report id Feb 5 16:49:05 curry /bsd: uhid4 at uhidev2 reportid 1: input=0, output=0, feature=1 Feb 5 16:49:53 curry /bsd: umass0 at uhub5 port 2 configuration 1 interface 0 "SanDisk Ultra" rev 3.00/1.00 addr 12 Feb 5 16:49:53 curry /bsd: umass0: using SCSI over Bulk-Only Feb 5 16:49:53 curry /bsd: scsibus4 at umass0: 2 targets, initiator 0 Feb 5 16:49:53 curry /bsd: sd2 at scsibus4 targ 1 lun 0: Ultra, 1.00> SCSI4 0/direct removable serial.07815581200212119554 Feb 5 16:49:53 curry /bsd: sd2: 29328MB, 512 bytes/sector, 60063744 sectors Feb 5 16:51:59 curry /bsd: error: [drm:pid69604:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Feb 5 16:54:57 curry /bsd: error: [drm:pid69604:intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe B Feb 5 16:55:56 curry /bsd: WARNING !wm_changed failed at /usr/src/sys/dev/pci/drm/i915/intel_pm.c:3609 Feb 5 16:56:39 curry /bsd: uhub2 detached Feb 5 16:56:39 curry /bsd: uhid4 detached Feb 5 16:56:39 curry /bsd: uhidev2 detached Feb 5 16:56:39 curry /bsd: uhub3 detached Feb 5 16:56:39 curry /bsd: uhub1 detached Feb 5 16:56:39 curry /bsd: uaudio0 detached Feb 5 16:56:39 curry /bsd: ugen1 detached Feb 5 16:56:39 curry /bsd: sd2 detached Feb 5 16:56:39 curry /bsd: scsibus4 detached Feb 5 16:56:39 curry /bsd: umass0 detached Feb 5 16:56:39 curry /bsd: uhub5 detached Feb 5 16:56:39 curry /bsd: uhub4 detached Feb 5 16:56:40 curry apmd: battery status: high. external power status: not connected. estimated battery life 95% Feb 5 17:06:45 curry /bsd: error: [drm:pid69604:intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A Any thoughts? I have to return the dock in a couple of days but if there is any procedures or output that someone would like to see in the meantime, let me know. Thanks, Thomas OpenBSD 6.4-current (GENERIC.MP) #625: Mon Jan 21 22:20:46 MST 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17037066240 (16247MB) avail mem = 16511123456 (15746MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.1 @ 0xe (109 entries) bios0: vendor Dell Inc. version "1.7.2" date 11/26/2018 bios0: Dell Inc. Latitude 7490 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SSDT HPET SSDT UEFI SSDT LPIT SSD
Re: SPA112 VoIP with pf and NAT - States keeps open on address change
> On 07.02.2019, at 14:21, Stuart Henderson wrote: > > On 2019-02-06, Patrick wrote: >> My nat rule use the parenthesis and all other devices behind the >> firewall works fine. I think it’s more a specific issue with the SPA112. >> I have also set the ruleset optimization to conservative but in this >> case the generated state has just a longer time to live. This isn’t the >> problem because the SPA112 sends regular keep alive packets which reset >> the counter for the state. > > Setting to 'conservative' (i.e. hanging on to states for longer) can't > help with this. > > Using parentheses won't help either, that means "do a lookup at state > creation time", but you aren't getting a new state created because the > old one hasn't expired. > >> >> Here the related rules: >> pass out quick on egress inet from (vether0:network) nat-to (egress) >> modulate state >> pass in on egress inet proto udp from to (egress) port 5060 >> >> As I’m just reading again my rules. Is the modulate state the problem? >> Or will pf use keep state for UDP packets as the default? > > PF uses "keep state" by default, and "keep state" is required for NAT. > > I think your main options are: > > - use a *shorter* timeout for this rule (this can be set per-rule > and overrides the default from "set optimization") and have a port > forward rule so that incoming packets still work even when the > state has timed out > > - arrange a way to flush these states when the IP changes > > The first of these is probably easiest if you can do it .. > > Thanks for suggestions. I tried to change the timeouts but every time the state gets deleted the SIP server refused the new connection. I think because of the change of source port. Maybe it would work with static-port option. I choose option two and have created a cron job to reconnect my VDSL connection and flush the state table at 2am in the night. This moved the force termination after 24 hours to the night. I remember that the old firewall had a similar option and probably also deleted the state table at the same time. I didn’t noticed the disconnection of my SPA112 in the middle of the night. To recover quicker from a termination at day I have set the re-register timeout to 30 minutes and also runs a script every five minutes on the firewall to check the current public IPv4 address and the one in the state table for the SPA112 and if it not match delete the state. Best Regards, Patrick
ssh-keygen returns 0 if there is at least one valid key passed via stdin
Hi, what I was trying is to validate ssh public keys passed via stdin to ssh-keygen. It seems one has to split each line before passing to ssh-keygen as ssh-keygen would return 0 if there is at least one valid key in the input. Is this behaviour correct? Jiri $ cat /etc/fstab .ssh/id_rsa.pub | ssh-keygen -l -f - -v debug1: (stdin):1: not a public key debug1: (stdin):2: not a public key debug1: (stdin):3: not a public key debug1: (stdin):4: not a public key debug1: (stdin):5: not a public key debug1: (stdin):6: not a public key debug1: (stdin):7: not a public key debug1: (stdin):8: not a public key debug1: (stdin):9: not a public key debug1: (stdin):12: not a public key debug1: (stdin):13: not a public key debug1: (stdin):14: not a public key 2048 SHA256:3ig2wrDgHa2iNH/89HGFRx+YuP7X6febAZR+kxu3Drg (RSA) +---[RSA 2048]+ | | |. + | | . * . | |. * . o| |. .. . S o = *.| |...+o . o. + o *| | =.o+ +.o..+ . +o| |o + =.o. o o oo=| |. .. .. . E .o==| +[SHA256]-+ $ sysctl kern.version kern.version=OpenBSD 6.4 (GENERIC) #3: Thu Dec 20 18:31:57 CET 2018 r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
Re: Can't set up IPv6 for IKEv2 VPN
On Mon, Feb 11, 2019 at 03:51:00PM +0100, Aram Hăvărneanu wrote: > > By default, iked inserts a flow which blocks IPv6. To prevent > > this, either configure explicit IPv6 flows (from/to with IPv6 > > addresses), or pass the -6 option to iked (see the man page). > > Forgot to mention that I already do this: > > freedom# cat /etc/rc.conf.local > iked_flags=-6 > unbound_flags= Have you tried configuring IPv6 flows instead? Will 'from 0.0.0.0/0 to 0.0.0.0/0' actually match IPv6 traffic?
Re: Can't set up IPv6 for IKEv2 VPN
>> By default, iked inserts a flow which blocks IPv6. To prevent >> this, either configure explicit IPv6 flows (from/to with IPv6 >> addresses), or pass the -6 option to iked (see the man page). > > Forgot to mention that I already do this: > > freedom# cat /etc/rc.conf.local > iked_flags=-6 > unbound_flags= Hmm. I was, indeed, passing -6, but I wasn't passing an explicit ::0/0 in iked.conf. This set-up works: freedom# cat /etc/iked.conf ikev2 "vpn" passive ipcomp esp \ from 0.0.0.0/0 to 0.0.0.0/0 \ from ::0/0 to ::0/0 \ local egress peer any \ psk "X" \ config address 172.24.24.0/24 \ config address 2001:470:8c78:a0::/64 \ config name-server 172.24.24.1 \ config name-server 2001:470:8c78:a0:: \ tag "vpn" tap enc0 Many thanks for the pointer! -- Aram Hăvărneanu
Re: PPPoE vlan issue 6.4
On 11.02.19 04:53, David Gwynne wrote: > Hi Adam, > > It sounds like you're on an ISP with very similar requirements to me. The > exec summary of what my ISP wants is pppoe on vlan2, with the vlan priority > forced to a single value. > > Our (OpenBSD's) understanding of the priority field in VLAN headers is that > it uses 802.1p for the fields value. 802.1p says that priories 0 and 1 are > swapped on the wire, and we use that consistently in the system, ie, the > priority you see in tcpdump on a vlan interface is the same as what you > configure for the priority value there, and visa versa. Everyone else seems > to think 0 is 0 and 1 is 1, which can be confusing. > > My ISP wants priority 0 on the wire, which means 1 in OpenBSD. > > I'm using an APU1, so I have re interfaces instead of em. I have re0 going to > the ISP, and re1 is my internal network. > > hostname.re0: > up > > hostname.vlan2: > vnetid 2 > parent re0 > link0 llprio 1 > up > > hostname.pppoe0: > == pppoe0 == > inet 0.0.0.0 255.255.255.255 0.0.0.1 > pppoedev vlan2 > authproto pap > authname 'dlg@the_isp' authkey 'secret' > group external > !/sbin/route add default -ifp pppoe0 0.0.0.1 > up > > hostname.re1: > inet 192.168.1.1/24 > Absolutely the same for me. Just a small addition, I also have the following in my /etc/pf.conf match on pppoe0 set prio 1 Works like a charm :-) -- Unix _IS_ user friendly - it's just selective about who its friends are!
Re: Can't set up IPv6 for IKEv2 VPN
> By default, iked inserts a flow which blocks IPv6. To prevent > this, either configure explicit IPv6 flows (from/to with IPv6 > addresses), or pass the -6 option to iked (see the man page). Forgot to mention that I already do this: freedom# cat /etc/rc.conf.local iked_flags=-6 unbound_flags= -- Aram Hăvărneanu
Re: Can't set up IPv6 for IKEv2 VPN
On Mon, Feb 11, 2019 at 03:32:17PM +0100, Aram Hăvărneanu wrote: > Hello, > > I am trying to set-up an dual-stack IKEv2/IPsec VPN. The server is > OpenBSD (obviously). The clients are macs (so far). IPv4 works, but > I can't get IPv6 working for the clients. The clients get a v6 IP > and a good route, but it seems routing doesn't work on OpenBSD's > side. > My iked.conf is > > freedom# cat /etc/iked.conf > > ikev2 "vpn" passive ipcomp esp \ > from 0.0.0.0/0 to 0.0.0.0/0 \ > local egress peer any \ > psk "" \ > config address 172.24.24.0/24 \ > config address 2001:470:8c78:a0::/64 \ > config name-server 172.24.24.1 \ > config name-server 2001:470:8c78:a0:: \ > tag "vpn" tap enc0 > freedom# By default, iked inserts a flow which blocks IPv6. To prevent this, either configure explicit IPv6 flows (from/to with IPv6 addresses), or pass the -6 option to iked (see the man page).
Can't set up IPv6 for IKEv2 VPN
Hello, I am trying to set-up an dual-stack IKEv2/IPsec VPN. The server is OpenBSD (obviously). The clients are macs (so far). IPv4 works, but I can't get IPv6 working for the clients. The clients get a v6 IP and a good route, but it seems routing doesn't work on OpenBSD's side. I am using an /48 IPv6 tunnel from HE. Server IPv4:209.51.161.14 Server IPv6:2001:470:1f06:95f::1/64 Client IPv4:207.246.122.61 Client IPv6:2001:470:1f06:95f::2/64 Routed IPv6 Prefixes Routed /48:2001:470:8c78::/48 IPv6 connectivity works from OpenBSD: freedom# uname -a OpenBSD freedom.mgk.ro 6.4 GENERIC.MP#364 amd64 freedom# freedom# ifconfig gif0 # HE tunnel gif0: flags=8051 mtu 1280 index 4 priority 0 llprio 3 groups: gif egress tunnel: inet 207.246.122.61 -> 209.51.161.14 ttl 64 nodf inet6 fe80::42bc:4cfd:6395:7fe%gif0 -> prefixlen 64 scopeid 0x4 inet6 2001:470:1f06:95f::2 -> 2001:470:1f06:95f::1 prefixlen 128 freedom# freedom# route show -inet6 | grep default defaulttunnel521973.tunne UGS03 - 8 gif0 defaultfe80::fc00:1ff:fed UGS00 -56 vio0 freedom# traceroute6 google.com traceroute6 to google.com (2607:f8b0:4006:81a::200e), 64 hops max, 60 byte packets 1 tunnel521973.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:95f::1) 9.048 ms 7.025 ms 6.35 ms 2 ve422.core1.nyc4.he.net (2001:470:0:5d::1) 1.822 ms 1.727 ms 5.251 ms 3 core1-0-0-8.lga.net.google.com (2001:504:f::27) 1.836 ms 1.661 ms 1.659 ms 4 2001:4860:0:1125::1 (2001:4860:0:1125::1) 4.234 ms 3.801 ms 2001:4860:0:1127::1 (2001:4860:0:1127::1) 3.834 ms 5 2001:4860:0:1::17b (2001:4860:0:1::17b) 3.613 ms 2001:4860:0:1::995 (2001:4860:0:1::995) 2.823 ms 2001:4860:0:1::17b (2001:4860:0:1::17b) 2.854 ms 6 lga25s62-in-x0e.1e100.net (2607:f8b0:4006:81a::200e) 2.829 ms 2.764 ms 2.598 ms freedom# I created enc0 for IPsec, and assigned the /48 to it: freedom# cat /etc/hostname.enc0 inet 172.24.24.1 255.255.255.0 172.24.24.255 inet6 2001:470:8c78:a0:: 64 up I enabled IP forwarding: freedom# cat /etc/sysctl.conf hw.smt=1 net.inet.ip.forwarding=1 net.inet6.ip6.forwarding=1 freedom# My iked.conf is freedom# cat /etc/iked.conf ikev2 "vpn" passive ipcomp esp \ from 0.0.0.0/0 to 0.0.0.0/0 \ local egress peer any \ psk "" \ config address 172.24.24.0/24 \ config address 2001:470:8c78:a0::/64 \ config name-server 172.24.24.1 \ config name-server 2001:470:8c78:a0:: \ tag "vpn" tap enc0 freedom# The mac clients "see" the IPv6 address, and create a route: emerald:aram$ ifconfig ipsec0 ipsec0: flags=8051 mtu 1400 inet 172.24.24.193 --> 172.24.24.193 netmask 0xff00 inet6 fe80::3ac9:86ff:fe32:4e3f%ipsec0 prefixlen 64 scopeid 0xf inet6 2001:470:8c78:a0::82f8:21d4 prefixlen 64 nd6 options=201 emerald:aram$ emerald:aram$ netstat -nr | grep default defaultlink#15UCS 1100 ipsec0 default192.168.0.1UGScI 190 en0 default192.168.0.1UGScI 30 en1 default 2001:470:8c78:a0:: UGc ipsec0 default fe80::%utun0 UGcI utun0 default fe80::%utun1 UGcI utun1 default fe80::%utun2 UGcI utun2 I can do IPv4 from the clients, but not IPv6. emerald:aram$ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=106.972 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=107.661 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=108.039 ms ^C --- 1.1.1.1 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 106.972/107.557/108.039/0.442 ms emerald:aram$ ping6 google.com PING6(56=40+8+8 bytes) 2001:470:8c78:a0::82f8:21d4 --> 2607:f8b0:4006:800::200e ^C --- google.com ping6 statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss emerald:aram$ ping6 2001:470:8c78:a0:: PING6(56=40+8+8 bytes) 2001:470:8c78:a0::82f8:21d4 --> 2001:470:8c78:a0:: ^C --- 2001:470:8c78:a0:: ping6 statistics ---
Re: increase user memory limits (staff group)
Hi Solene!
Solene Rapenne wrote:
The names in login.conf are classes, this is not related to groups.
You can find in which class your user by looking at the 5th field of
your username in /etc/master.passwd. You can use the following command:
$ doas awk -F':' '/^YOUR_USER/ { print $5 }' /etc/master.passwd
If it returns "staff" then you should have the correct limits from
/etc/login.conf
thanks for the hint, I got side-tracked by the name of the class being
the same as group.
Your command does not return anything, so the solution was as simple as
sudo usermod -L staff
and now your command returns "staff"... fine!
I won't set any defaults for classes, since it is only me that needs
this for now.
Thanks,
Riccardo
Re: increase user memory limits (staff group)
On Mon, Feb 11, 2019 at 12:09:56PM +0100, Riccardo Mottola wrote:
> Hi all,
>
> I need to compile certain big softare and want to do this as
> user, I am hitting memory limits, e.g:
>
> ./../js/src/libjs_static.a: could not read symbols: Memory exhausted
>
> I read in various post and man pages, but am a little confused.
>
> First thing, I added my user to the "staff" group, which should
> have increased limits, but they are not enough.
>
> $ groups
> staff wheel wsrc
>
> Thanks.
>
> Riccardo
>
The names in login.conf are classes, this is not related to groups.
You can find in which class your user by looking at the 5th field of
your username in /etc/master.passwd. You can use the following command:
$ doas awk -F':' '/^YOUR_USER/ { print $5 }' /etc/master.passwd
If it returns "staff" then you should have the correct limits from
/etc/login.conf
Look at /etc/login.conf.db, if you have that file, you must either
recreate it using cap_mkdb or remove it. If the file is not present
then login.conf is read. If the file is present, login.conf is not
read and login.conf.db is used instead, so you need to recreate it.
This is explained in login.conf(5).
Don't forget to delog yourself and relog-in with the account after
changes into login.conf. Limits are applied at login, not when you
call ulimit.
increase user memory limits (staff group)
Hi all, I need to compile certain big softare and want to do this as user, I am hitting memory limits, e.g: ../../js/src/libjs_static.a: could not read symbols: Memory exhausted I read in various post and man pages, but am a little confused. First thing, I added my user to the "staff" group, which should have increased limits, but they are not enough. $ groups staff wheel wsrc in login.conf, I have: default:\ :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/local/sbin:\ :umask=022:\ :datasize-max=2048M:\ :datasize-cur=1024M:\ :maxproc-max=256:\ :maxproc-cur=128:\ :openfiles-cur=512:\ :stacksize-cur=4M:\ :localcipher=blowfish,a:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults: staff:\ :datasize-cur=2048M:\ :datasize-max=infinity:\ :maxproc-max=512:\ :maxproc-cur=256:\ :stacksize-cur=32M:\ :ignorenologin:\ :requirehome@:\ :tc=default: I see this once logged in: $ ulimit -a time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 1325784 stack(kbytes) 4096 lockedmem(kbytes) 3957020 memory(kbytes) 3957020 nofiles(descriptors) 512 processes 128 I suppose that to solve my "memory exhausted" error I need to increase data and perhaps stack, since memory is already 4GB. However, if I attempt: $ ulimit -d 3957016 ksh: ulimit: -d exceeds allowable limit $ ulimit -d 2097152 ksh: ulimit: -d exceeds allowable limit can you give me a hint of what am I missing? apparently both "datasize-max" and "datasize-cur" aren't working, since as default I get 1GB Thanks. Riccardo
Re: Boot reboot issue after upgrade to 6.4 on amd64
Hi, Joel Sing wrote: The specific "heap full" issue that can be triggered by using a single large partition is not likely to be at fault here - if you cannot boot the ramdisk (bsd.rd/installer) for 6.3 or 6.4 from a USB key, then something else is presumably up (unless you're actually trying to load the installed kernel or ramdisk from the hard disk). some time passed, but I have new information. Essentially, booting from USB key proved sometimes unreliable. I burned a CD-CDROM and am able to do the following - boot from cd and at the bootload prompt - "bood hd0a:bsd" and boot into a fully working 6.4 installation. This is of course a little cumbersome as a workaround. Can I fix it? I attempted to install "biosboot" of 6.3: I extracted 6.3, used 6.4 installboot to install mdec/biosboot from 6.3 It does not help though. What else could I try, given that the bootloader of the CD appears to work fine? Riccardo
Re: Shadow artifacts and color distortions when using compton(1). Perhaps after recent Xenocara update?
On Sun, Feb 10, 2019 at 03:39:29PM -0800, Thomas Frohwein wrote: > On Sun, Feb 10, 2019 at 11:16:03PM +0100, Erling Westenvik wrote: > > Hi, > > After upgrading to todays snapshot (February 10th) I experience some rather > > ugly shadow artifacts and color distortions when using compton(1) under > > cwm(1). > > It may perhaps best be described by linking to an issue report from April > > 2018 > > at github: > > > > https://github.com/chjj/compton/issues/487 > > > > and from that page - a link to a screendump showing exactly what I > > experience: > > > > https://framapic.org/dHfk2217huGs/NIiGKJsfnz52.jpg > > > > The problem can be reproduced by specifying "glx" as backend in compton(1). > > It > > appear to have been major glx-related imports in Xenocara on January 29th > > 2019. > > My previous snapshot was older than that, perhaps as old as from December > > 2018, > > but for certain newer than the previous bulk import which appears to have > > been October 23rd 2018. > > > > My graphics card is a ATI Radeon HD 5770. Dmesg below. > > > > Not sure how to attack this. Help/ideas appreciated. > [...] > > Yep, I noticed the same with compton after the update to Mesa 18 in snaps. I > think the following GitHub issue is actually the more fitting one: > > https://github.com/chjj/compton/issues/477 > > For me, switching to xrender backend for compton is a satisfactory solution > until the freedesktop bug referenced in the above link [1] has been addressed. > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=104597 At least for me that comes with a huge performance penalty, and I cannot have blurred transparent backgrounds. All right, so it's just eye candy, but I find the ability to have a certain sense of visual depth really helpful. Regards, Erling
Re: Missing libraries.
Den mån 11 feb. 2019 kl 06:15 skrev Kihaguru Gathura : > Hi, > Any ideas on how to fix the missing libraries, > www# pkg_add -v mini_sendmail-chroot > Can't install mini_sendmail-chroot-1.3.9 because of libraries > |library c.95.0 not found > | /usr/lib/libc.so.92.6 (system): bad major > It really DOES try to tell you what it wants, and what you have. I looks for libc of version 95.0, och your system seems to be three major versions lower, which implies you have not upgraded the system (from bsd.rd, snapshots, source) in a long while, but the people that build snapshot packages have, because that is what the requirements for running snapshot packages is. Keep the base,x11 and ports/packages in sync. Now there was a week recently where libc.94 was quite short-lived so if you didn't upgrade every week from snapshots you could end up with something similar to this, but here, I think the age of the existing libc says it is close to three months old: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libc/shlib_version.diff?r1=1.201&r2=1.202&f=h If this happened to me, I'd run a ls /usr/lib/libc.so.* and see what the output of that is, compared to what the snapshot port wanted (.95.0) and then either wait until arm snaps show base6x.tgz comes with such a libc, or grab current sources and compile the base system yourself to get uptodate (the FAQ has good guides on how this is done) -- May the most significant bit of your life be positive.
