Re: 6.5 auto_install fails due to custom /var/tmp?

[Nick Holland]

On 4/29/19 6:09 PM, Lyndon Nerenberg wrote:
> While trying to PXE install a 6.5 machine I was hit with this failure:
> 
>  Installing bsd  100% |**| 15163 KB00:00  
>   
>  Installing bsd.mp   100% |**| 15248 KB00:00  
>   
>  Installing bsd.rd   100% |**|  9984 KB00:00  
>   
>  Installing base65.tgz99% |* |   189 MB00:00 
> ETAtar: Unable to remove directory ./var/tmp: Device busy
>  Installing base65.tgz   100% |**|   190 MB00:14  
>   
>  Installation of base65.tgz failed. Continue anyway? [no] no
> 
> which I suspect is related to this:
> 
>  /   1G
>  swap4G-16G 10%
>  /tmp2G
>  /usr4G
>  /usr/local  2-6G 10%
>  /var10-20G 20%
>  /var/tmp10-20G 15%
>  /var/log20-40G 30%
>  /u  1G-*

yeah.

> I've never run into this until today, when I tried to carve out an explicit
> /var/tmp.  Autopartitioning be able to handle /var/tmp, no?

normally, /var/tmp is a symlink to /tmp.
It can't make the link.  No surprise.
Answer "Yes" to the "Continue anyway?" prompt, and all will be fine, I
believe.

Nick.

6.5 auto_install fails due to custom /var/tmp?

[Lyndon Nerenberg]

While trying to PXE install a 6.5 machine I was hit with this failure:

 Installing bsd  100% |**| 15163 KB00:00
 Installing bsd.mp   100% |**| 15248 KB00:00
 Installing bsd.rd   100% |**|  9984 KB00:00
 Installing base65.tgz99% |* |   189 MB00:00 
ETAtar: Unable to remove directory ./var/tmp: Device busy
 Installing base65.tgz   100% |**|   190 MB00:14
 Installation of base65.tgz failed. Continue anyway? [no] no

which I suspect is related to this:

 /   1G
 swap4G-16G 10%
 /tmp2G
 /usr4G
 /usr/local  2-6G 10%
 /var10-20G 20%
 /var/tmp10-20G 15%
 /var/log20-40G 30%
 /u  1G-*

I've never run into this until today, when I tried to carve out an explicit
/var/tmp.  Autopartitioning be able to handle /var/tmp, no?

--lyndon

Re: sound short stops in mpv when doing firefox stuff

[Jeremy O'Brien]

On Fri, Feb 1, 2019, at 05:45, Mihai Popescu wrote:
> Hello,
> 
> I use mpv with a network stream (radio) and in the same time I use
> firefox for browsing. There is some audible sound short stop each time
> I open a new tab in firefox and sometimes when in change tabs.
> This it doesn't happen if I listen to that stream in the firefox
> browser, no matter how many tabs I open.
> I use the most recent snapshot/amd64. I tried to adjust cache for mpv
> but it does not matter. Vlc is playing fine, as cvlc terminal app.
> 
> I want to stick with mpv for the moment, so if anyone is an expert in
> fine tuning it, please drop here a hint. Even if it cannot be fixed
> for the moment,
> 
> Thank you.
> 

Try changing the mpv audio backend to sndio. Solved it for me. 

Xorg splitting physical output into halves

[Benny]

Hi,

I am planning an openbsd arm AR glasses setup. Is it possible for Xorg to split 
an output into two, which I can use xrandr to mirror them?

I have tried fakeXrandr which creates virtual monitors that can't be mirrored. 
Xephyr is not accelerated and I can't see a way to setup two ouput with it.

Thanks.

Re: Code of Conduct location

[Wolfgang Pfeiffer]

On Sun, Apr 28, 2019 at 03:33:50PM +0200, Rachel Roch wrote:

Apr 28, 2019, 9:16 AM by cho...@jtan.com :


[ .. ]


I believe OpenBSD's code of conduct can be summed up as "if you are the
type of person who needs a code of conduct to teach to you how to human
then you are not welcome here".

At least I hope so.

Matthew



I always thought it could be summed up as "Don't piss off Theo".  ;-)


... :)

He's setting a standard. So I don't have to worry about talking freely
about what I think here. And that's just one reason why I try to
migrate my machines to OpenBSD ...

And one of the first things I do when looking at software, and whether
it's useful for my needs or not: Are those who write it adults or are
they whinies with problems regarding understandable speech? I'm
trying to keep the latter mostly at safe distances from me, and I
tend to avoid their code getting installed onto my machines ...

So that's another reason I'm glad Theo de Raadt is setting a certain
standard here ...

So yes, for sure: "Don't piss off Theo". And no smiley.

Regards .. :) ..
Wolfgang

Re: Qemu Agent assistance needed

[Strahil Nikolov]

Great.
What about CPU/RAM usage. Do you believe it will be possible to report it to 
the  management layer ?
If not - there will be no use of qemu-ga at all on openBSD.

Best Regards,
Strahil Nikolov


On April 29, 2019 2:49:43 PM GMT+03:00, Stuart Henderson  
wrote:
>On 2019-04-29, Strahil Nikolov  wrote:
>> Yes , but not only.
>> I'm using oVirt - a KVM management tool and I can currently make a
>snapshot only by pausing the VM or by completely stopping it first.
>> For now, it's not a big deal - as I'm still exploring openBSD , but
>who knows.
>> Also the management interface cannot provide details about CPU and
>RAM usage , nor I cannot gracefully shut the VM down from the
>interface.
>> The oVirt manager allows automatic evacuation of the VM, if it
>requires more memory/cpu than the host can currently providing (for a
>lab overcommitting is normal).
>>
>> I'm just looking to enable those fancy things that make our life
>easier.
>
>qemu-ga needs a way to communicate with the kernel to tell it to stop
>filesystem activity etc.  OpenBSD doesn't support this.

Re: Qemu Agent assistance needed

[Stuart Henderson]

On 2019-04-29, Strahil Nikolov  wrote:
> Yes , but not only.
> I'm using oVirt - a KVM management tool and I can currently make a snapshot 
> only by pausing the VM or by completely stopping it first.
> For now, it's not a big deal - as I'm still exploring openBSD , but who knows.
> Also the management interface cannot provide details about CPU and RAM usage 
> , nor I cannot gracefully shut the VM down from the interface.
> The oVirt manager allows automatic evacuation of the VM, if it requires more 
> memory/cpu than the host can currently providing (for a lab overcommitting is 
> normal).
>
> I'm just looking to enable those fancy things that make our life easier.

qemu-ga needs a way to communicate with the kernel to tell it to stop
filesystem activity etc.  OpenBSD doesn't support this.

Re: nat-to random : A couple of questions

[Stuart Henderson]

On 2019-04-28, Rachel Roch  wrote:
> Hi,
>
> I've read the delightful manual but its a little terse in this area, so I 
> hope some knowledgeable soul can enlighten me:
>
> 1) Looking at tcpdumps, I've noticed (on 6.5 have no prior experience with 
> nat-to random to compare against) that 'random' seems to operate more like 
> 'round-robin'  (e.g. if I send traffic, pause, send traffic again it just 
> loops through the IP pool in order). 

Unsure about this.

> 2) I'm unclear when 'sticky-address' should be appended to random ? In my 
> mind I'm thinking about, say, "secure websites" which may track your 
> (apparent) source-IP during the time you are logged in, and if it changes you 
> could be booted out.  Or am I overthinking things and 'sticky-address' is 
> potentially less useful than I think it might be ?

Yes this is definitely still a problem in some cases. In particular some banks
(and some other sites) restrict sessions to a single source IP.

> Finally, is there any reason why there isn't (yet?) a more intelligent 
> mapping ? (e.g. similar to the options in LACP ... e.g. source plus 
> destination, not just source).

I've not seen that suggested before. I imagine tracking source+destination
would be a huge drain on memory though (and might not help in many situations
which want a "sticky" address)..

Re: [6.5] minidlna error: accept(http): Too many open files

[Muhammad Kaisar Arkhan (Yuki)]

I had the same issue with Syncthing. openfiles=infinity in login.conf(5) fixed 
it for me.

syncthing:\
:openfiles=infinity:\
:tc=daemon:

Though some may argue it is better to disable inotify altogether. 

Dim 28 avr 2019, à 22:38, Stephane HUC "PengouinBSD" a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi, all
> 
> After upgrading OpenBSD from 6.4 to 6.5, I've problem to use minidlna.
> It fill the /var/log/minidlna/minidlna.log with severals errors
> messages, as:
> [2019/04/25 15:26:29] monitor_kqueue.c:226: error:
> open(/home/z2/Music/xyz) [Too many open files]
> (...)
> [2019/04/25 20:15:05] minidlna.c:165: error: accept(http): Too many
> open files
> 
> as read on the pkg-readme, I change both files '/etc/sysctl.conf',
> '/etc/login.conf'.
> 
> I added 'kern.maxfiles=16384' for sysctl.
> And on login file, I wrote:
> "minidlna:\
> :openfiles-cur=16384:\
> :openfiles-max=16384:\
> :tc=daemon:
> "
> And after, I rebooted my machine.
> 
> But, thoses errors continue, and grow the log until my dedicated slide
> /var/log is full. and minidlna not run correctly. Why?
> What are the good values of limits systems to run correctly minidlna?
> 
> - 
> 
> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8487260160 (8094MB)
> avail mem = 8220409856 (7839MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec580 (74 entries)
> bios0: vendor Alienware version "A08" date 01/25/2018
> bios0: Alienware Alienware 13
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF!
> SLIC SSDT SSDT SSDT SSDT CSRT SSDT
> acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4)
> PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4)
> PXSX(S4) RP04(S4) RP05(S4) PEGP(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.44 MHz, 06-45-01
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.32 MHz, 06-45-01
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 1 (application processor)
> cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.31 MHz, 06-45-01
> cpu2:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 1, core 0, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.31 MHz, 06-45-01
> cpu3:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
> acpimadt0: bogus nmi for apid 0
> acpimadt0: bogus nmi for apid 2
> acpimadt0: bogus nmi for apid 1
> acpimadt0: bogus nmi for apid 3
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xf800, bus 0-63
> acpihpet0 at acpi0: 

Re: [6.5] Cups + Gutenprint: file rastertogutenprint not found

[Stephane HUC "PengouinBSD"]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, Excuse me if I'm expressing myself badly!

NO.

After the upgrading, by necessity, I attempt to print PDF or OD*
documents, and my printer not reply.

I opened the Webadmin Cups, and I saw this error message on job files.

Into the log /var/log/Cups/error_log, same messages:

E [28/Apr/2019:07:31:57 +0200] BX525WD: File
\"/usr/local/libexec/cups/filter/rastertogutenprint.5.2\" not available:
No such file or directory
E [28/Apr/2019:07:31:57 +0200] [Job 77] Unable to start filter
"rastertogutenprint.5.2" - No such file or directory.
E [28/Apr/2019:07:31:57 +0200] [Job 77] Stopping job because the
scheduler could not execute a filter.
E [28/Apr/2019:07:34:46 +0200] BX525WD: File
\"/usr/local/libexec/cups/filter/rastertogutenprint.5.2\" not available:
No such file or directory
E [28/Apr/2019:07:34:46 +0200] [Job 78] Unable to start filter
"rastertogutenprint.5.2" - No such file or directory.
E [28/Apr/2019:07:34:46 +0200] [Job 78] Stopping job because the
scheduler could not execute a filter.

Then I have verified the number version with the tool pkg_info. And I
saw 5.3.
so I had the idea to change the printer settings by choosing the new driver.

I use root to set parameters. And, I print with my right users.


On 4/28/19 11:18 PM, Predrag Punosevac wrote:
> Stephane HUC wrote: >> > Hi, (just FYI) > > After upgrading OpenBSD from 6.4 
> to 6.5, I had
this problem to print. > The Webadmin of Cups informs me with this
message: > > "/usr/local/libexec/cups/filter/rastertogutenprint.5.2 not
found!" > > On the parameters about my printer, (an MFP Epson BX525WD on
my local > network), I change with the new version of Gutenprint's
driver. (v5.3.x) > > Did you notice that you changed the driver into
v5.3 but Webadmin > > complains about missing
rastertogutenprint.5.2..That doesn't make sense > > at all. I would
expect that Webadmin complain about missing > > rastertogutenprint.5.3.
Did you check if you do have > > rastertogutenprint.5.3 on your system?
Did you check if > > rastertogutenprint.5.3 is in CVS source Gutenprint
5.3 which you just > > installed. > > > Anything in the log files? What
is the username you are using for CUPS? > > I neither use CUPS nor
Gutenprint but searching for similar problems as > > yours turns a dozen
or so leads. > > > IMHO ports list might be a better suitable for
further discussion if > > this turns out to be the case of the missing
file from a package > > (happened before due to the upstream). > > >
Cheers, > > Predrag > > > . > > And, that's run correctly! > > >> >> - --
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD "    +=<<<
- 
Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net
-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXMbDngAKCRATq98t3AMG
7/lOAP0WJS7OccARSWpO8h8JZBkYImXnGERmBLNc0fC7kzKHrgD9G9uIGr+jTpOU
x6kF/+VdJshOQk8+tcYoJHEMaHutqAw=
=qg7I
-END PGP SIGNATURE-

Re: Qemu Agent assistance needed

[Jiri B]

QGA depends on specific device name in /dev. Ideally the best would be
kernel-based support like vmt.

Dne po 29. 4. 2019 10:03 uživatel Solene Rapenne  napsal:

> On Sun, Apr 28, 2019 at 11:10:14AM +, Strahil Nikolov wrote:
> > Hi All,
> > I am new to openBSD and I really like the idea. Sadly I do not have
> > suitable hardware to run on , thus I use KVM and I would be happy if
> > anyone hint me of a working solution for Qemu Guest Agent.
> > Anything I dig up (via google searches) show up only suggestions , but
> > nothing more.In openBSD 6.4  I successfully installed qemu (and thus
> > the agent), but I can't understand how to get the device needed for
> > communication with the host up and running.
> > As I mainly know linux - I know that we need a kernel module that to
> > be loaded and with combination of udev rules - the devices is created
> > on the necessary location and with the correct rights.According to
> > many google findings - openBSD doesn't support any more loadable
> > kernel module support.
> > I have tried to figure it out by myself, but I cannot find the
> > necessary module needed, nor how to load it in a proper manner.
> > Any hint is well appreciated.
> > Best Regards,Strahil Nikolov
> >
>
> qemu on openbsd doesn't support any hardware acceleration, and the
> available version is quite old.
>
> I'm not sure it is compatible with libvirt.
>
>

Re: Qemu Agent assistance needed

[Strahil Nikolov]

I have installed qemu, as qemu-ga cannot be installed standalone.

I qm trying to have snapshots without pausing the VM and to provide basic 
functionality from host.

Best Regards,
Strahil Niolov

On April 29, 2019 11:00:42 AM GMT+03:00, Solene Rapenne  wrote:
>On Sun, Apr 28, 2019 at 11:10:14AM +, Strahil Nikolov wrote:
>> Hi All,
>> I am new to openBSD and I really like the idea. Sadly I do not have
>> suitable hardware to run on , thus I use KVM and I would be happy if
>> anyone hint me of a working solution for Qemu Guest Agent.
>> Anything I dig up (via google searches) show up only suggestions ,
>but
>> nothing more.In openBSD 6.4  I successfully installed qemu (and thus
>> the agent), but I can't understand how to get the device needed for
>> communication with the host up and running.
>> As I mainly know linux - I know that we need a kernel module that to
>> be loaded and with combination of udev rules - the devices is created
>> on the necessary location and with the correct rights.According to
>> many google findings - openBSD doesn't support any more loadable
>> kernel module support.
>> I have tried to figure it out by myself, but I cannot find the
>> necessary module needed, nor how to load it in a proper manner.
>> Any hint is well appreciated.
>> Best Regards,Strahil Nikolov  
>> 
>
>qemu on openbsd doesn't support any hardware acceleration, and the
>available version is quite old.
>
>I'm not sure it is compatible with libvirt.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

SOLVED: Re: No more KDE's dolphin after upgrade to 6.5

[Federico Giannici]

On 4/26/19 9:47 PM, Rafael Sadowski wrote:

On Fri Apr 26, 2019 at 05:47:11PM +0200, Federico Giannici wrote:

On 4/26/19 4:10 PM, Rafael Sadowski wrote:

On Thu Apr 25, 2019 at 01:34:24PM +0200, Federico Giannici wrote:

Similarly to konsole, KDE's dolphin no longer works too after upgrade of
amd64 from 6.4 to 6.5.

It seems that dolphin was switched to KF5 too, ma I wasn't able to install
the new package:

casa:/home/giannici# pkg_add dolphin-kf5
quirks-3.124 signed on 2019-04-15T12:10:16Z
Can't install dolphin-kf5-18.12.0p2 because of conflicts
(dolphin-plugins-4.14.3p1)
--- dolphin-kf5-18.12.0p2 ---
Can't install dolphin-kf5-18.12.0p2: conflicts
Couldn't install dolphin-kf5-18.12.0p2

I cannot remove dolphin-plugins-4.14.3p1 because kdesdk depends on it, and
kde4 depends on kdesdk:

casa:/home/giannici# pkg_delete dolphin-plugins
can't delete dolphin-plugins-4.14.3p1 without deleting kdesdk-4.14.3p3
Delete them as well ? [y/N/a]

casa:/home/giannici# pkg_delete kdesdk
can't delete kdesdk-4.14.3p3 without deleting kde4-4.14.3p23
Delete them as well ? [y/N/a]


Without dolphin and konsole it's really hard to comfortably use KDE. So,
please can anybody tell me what is the supposed way to use dolphin (and
konsole) with OpenBSD 6.5?

Thanks.



That was a hidden run-time dependency in the KDE4/KDESDK meta package.
I fixed this issue in -current ports tree. For -release I hope I can
help with a non official -- use at own risk -- workaround:

Use my own kde4-4.14.3p25 and kdesdk-4.14.3p4 packages:
env 
TRUSTED_PKG_PATH=https://sizeofvoid.org/pub/OpenBSD/fix-kde4-meta-65/:https://ftp.openbsd.org/pub/OpenBSD/6.5/packages/
 pkg_add -u kdesdk kde4

If kde4-4.14.3p25 and/or kdesdk-4.14.3p4 was successfully installed you
can remove dolphin-plugins-4.14.3p1 without pain and install
dolphin-kf5-18.12.0 and dolphin-plugins-kf5-18.12.0.

Good luck!

RS


Thank you for your interest.

I was able to install your packages and finally dolphin-kf5-18.12.0 and
dolphin-plugins-kf5-18.12.0. I was able to install the konsole-18.12.0p0
package too. Unfortunately they both still don't work!

Below are the errors.

What else I can do?

Thanks.



casa:/home/giannici> pkg_info konsole
Information for inst:konsole-18.12.0p0

Comment:
KDE terminal emulator

Required by:
dolphin-kf5-18.12.0p2

Description:
Konsole is an X terminal emulator for the KDE platform, allowing
users to have a convenient way to use the command line. Aside from
providing a way to use a powerful shell, Konsole also offers features
that make it easier or more pleasurable to work in the command line,
such as profile management, scrollback, and color schemes, including
translucency for effects.

Konsole also provides an embedded KPart terminal which is used by
apps such as Yakuake, Dolphin, and Kate, giving users a consistent
and familiar interface when working in the command line.

Maintainer: Rafael Sadowski 


casa:/home/giannici> konsole
ld.so: konsole: can't load library 'libc++.so.1.0'
Killed






casa:/home/giannici# pkg_info dolphin-kf5
Information for inst:dolphin-kf5-18.12.0p2

Comment:
KDE File Manager

Required by:
dolphin-plugins-kf5-18.12.0p0

Description:
Dolphin is a lightweight file manager. It has been designed with ease of use
and simplicity in mind, while still allowing flexibility and customisation.
This means that you can do your file management exactly the way you want to
do
it.

Maintainer: Rafael Sadowski 


casa:/home/giannici# dolphin
dolphin:/usr/local/lib/libattica.so.1.0: /usr/local/lib/libKF5Attica.so.3.3
: WARNING: symbol(_ZN6Attica15ProviderManager16staticMetaObjectE) size
mismatch, relink your program


[...]


dolphin:/usr/local/lib/libkdeinit5_dolphin.so: undefined symbol
'_ZNK14KItemModelBase9directoryEv'
dolphin(49958) in free(): bogus pointer (double free?) 0x1fedb10f330
Abort



I think something failed on your last update. You can try out out to
update all packages with the following PKG_PATH example:

env PKG_PATH=https://ftp.openbsd.org/pub/OpenBSD/6.5/packages/ pkg_add -u -v 
-Dinstalled

It looks like you mixed packages for 6.4 and 6.5 and/or -current.
Another try: run "pkg_add -X" to remove all your installed packages and
install step by step what you need!


I tried that but didn't worked.

Anyway I found the problem with both dolphin and konsole: I think it was 
caused by the change in version numbering of the "private" libraries.


In my system there were still around the 6.3 libraries (version 51):

-rw-r--r-- 1 root bin 1821661 Oct 12 2018 libdolphinprivate.so.51.0
-rw-r--r-- 1 root bin 1806868 Mar 28 2018 libkonsoleprivate.so.51.0

alongside the new ones, but with "0" version:

-rw-r--r--  1 root  bin  1720320 Apr 15 01:17 libdolphinprivate.so.0.1
-rw-r--r--  1 root  bin  1872672 Apr 14 20:12 libkonsoleprivate.so.0.0

As soon I removed the old ones, both dolphin and konsole worked!

Maybe it could be useful for other users to add a note in the upgrade 
guide to 6.5?



Now, I still have some 

Re: Qemu Agent assistance needed

[Solene Rapenne]

On Sun, Apr 28, 2019 at 11:10:14AM +, Strahil Nikolov wrote:
> Hi All,
> I am new to openBSD and I really like the idea. Sadly I do not have
> suitable hardware to run on , thus I use KVM and I would be happy if
> anyone hint me of a working solution for Qemu Guest Agent.
> Anything I dig up (via google searches) show up only suggestions , but
> nothing more.In openBSD 6.4  I successfully installed qemu (and thus
> the agent), but I can't understand how to get the device needed for
> communication with the host up and running.
> As I mainly know linux - I know that we need a kernel module that to
> be loaded and with combination of udev rules - the devices is created
> on the necessary location and with the correct rights.According to
> many google findings - openBSD doesn't support any more loadable
> kernel module support.
> I have tried to figure it out by myself, but I cannot find the
> necessary module needed, nor how to load it in a proper manner.
> Any hint is well appreciated.
> Best Regards,Strahil Nikolov  
> 

qemu on openbsd doesn't support any hardware acceleration, and the
available version is quite old.

I'm not sure it is compatible with libvirt.

reboot when 'shutdown -p -h now' called after upgrade

[Damien Thiriet]

Hello @misc,


The encoding issue at the beginning of the dmesg I send previously is
connected to st. I don't have this issue on xterm. Sorry for this noise.
This doesn't change the unwanted rebooting issue though.

Regards,


Damien Thiriet

Re: Xorg blanks until I switch to a TTY and back on 6.5

[Jonathan Gray]

On Sun, Apr 28, 2019 at 07:26:54PM -0400, Charles wrote:
> Hello list,
> 
> Ever since the new inteldrm driver got merged into -current, shortly
> before the 6.5 release, I'm seeing an odd new behavior on my Thinkpad
> T430 -- when an external display is connected, Xorg blanks all screens
> (but the mouse can still be seen) until I switch to a TTY and back with
> (i.e. C-A-F4 then C-A-F5) after which point it goes back to normal.
> 
> I'm glad the new inteldrm driver got merged, since it fixes several
> other video issues I was having. This problem is very minor since the
> workaround is just a few extra keystrokes when I dock or undock, but it
> is nevertheless annoying.
> 
> Is anyone else experiencing this issue on third gen core-I series Intel
> chips with integrated graphics? Or on any other chips for that matter?
> 
> I checked Xorg.0.log and didn't see anything suspicious. I also tried
> disabling monitor hotplugging via Xorg.conf, but I either did it wrong
> or it had no effect.
> 
> I would attach xorg logs and dmesg, but AFAIK misc@ does not allow
> attachments, and I don't want to annoy people with that much inline
> info.

Does this help?

Index: sys/dev/pci/drm/drm_fb_helper.c
===
RCS file: /cvs/src/sys/dev/pci/drm/drm_fb_helper.c,v
retrieving revision 1.13
diff -u -p -r1.13 drm_fb_helper.c
--- sys/dev/pci/drm/drm_fb_helper.c 14 Apr 2019 10:14:51 -  1.13
+++ sys/dev/pci/drm/drm_fb_helper.c 29 Apr 2019 06:58:25 -
@@ -575,6 +575,9 @@ static bool drm_fb_helper_is_bound(struc
 #ifdef notyet
if (READ_ONCE(dev->master))
return false;
+#else
+   if (!SPLAY_EMPTY(>files))
+   return false;
 #endif
 
drm_for_each_crtc(crtc, dev) {

Re: nat-to random : A couple of questions

[Bohdan Tashchuk]

> 1) Looking at tcpdumps, I've noticed (on 6.5 have no prior experience
> with nat-to random to compare against) that 'random' seems to operate
> more like 'round-robin'

I can't speak to the rest of your questions. But I can share something
about a very similar issue. A few releases ago I ran into a this same
bug, not with nat-to, but with rdr-to. I haven't confirmed this
behavior in the most recent release.

I am keeping locally generated ntp traffic from going out to Apple's
internet ntp servers, instead serving them locally from my OpenBSD
firewall. I use a pf configuration something like this:

   pass in quick on $iif proto udp from any
to "17.0.0.0/8" port ntp rdr-to "127.17.42.0/28" random

My local ntpd listens on those 16 ports. Here are some comments
from my pf.conf which summarize why, at least for me, round robin
behavior is better than random:

# Note that rdr-to with CIDR target address only works with random
# keyword, and behaves like round-robin. With all other keywords the
# target address is borked, behaving like 0.0.0.0, 0.0.0.1, 0.0.0.2,
# etc.
# However, rdr-to with a 16-entry table target, 16 distinct addresses,
# works correctly in all modes, random is truly random. N.B. we
# definitely don't want truly random, because it sometimes results
# in duplicate target addresses, which causes lost reply packets.


A restatement of the above pf file comment:

1) for rdr-to, for CIDR target addresses, only "random" works.
All other modes are borked. "random" behaves like "round-robin".

2) for rdr-to, when the target address is a table, all modes work.
"random" is truly random.

3) for some setups, truly random target addresses will cause
creation of duplicate target addresses. That's bad, because some
replies will be lost.


In conclusion:

Are you sure you really need random behavior for your application?
Depending on what you are doing, round-robin may actually be better!
You didn't post your pf configuration so I don't know what you're
trying to do.

I hope you can gleam something from my rdr-to issue to help you
with your nat-to issue.

Re: [6.5] minidlna error: accept(http): Too many open files

[Martijn van Duren]

I haven't spend any time on the why, but I also had some problems with  
openfiles-{cur,max}, but changing it to openfiles=x worked for me.

ymmv.

martijn@

On 4/28/19 10:35 PM, Stephane HUC "PengouinBSD" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi, all
> 
> After upgrading OpenBSD from 6.4 to 6.5, I've problem to use minidlna.
> It fill the /var/log/minidlna/minidlna.log with severals errors
> messages, as:
> [2019/04/25 15:26:29] monitor_kqueue.c:226: error:
> open(/home/z2/Music/xyz) [Too many open files]
> (...)
> [2019/04/25 20:15:05] minidlna.c:165: error: accept(http): Too many
> open files
> 
> as read on the pkg-readme, I change both files '/etc/sysctl.conf',
> '/etc/login.conf'.
> 
> I added 'kern.maxfiles=16384' for sysctl.
> And on login file, I wrote:
> "minidlna:\
> :openfiles-cur=16384:\
> :openfiles-max=16384:\
> :tc=daemon:
> "
> And after, I rebooted my machine.
> 
> But, thoses errors continue, and grow the log until my dedicated slide
> /var/log is full. and minidlna not run correctly. Why?
> What are the good values of limits systems to run correctly minidlna?
> 
> - 
> 
> OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8487260160 (8094MB)
> avail mem = 8220409856 (7839MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec580 (74 entries)
> bios0: vendor Alienware version "A08" date 01/25/2018
> bios0: Alienware Alienware 13
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF!
> SLIC SSDT SSDT SSDT SSDT CSRT SSDT
> acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4)
> PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4)
> PXSX(S4) RP04(S4) RP05(S4) PEGP(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.44 MHz, 06-45-01
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.32 MHz, 06-45-01
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 1 (application processor)
> cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.31 MHz, 06-45-01
> cpu2:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 1, core 0, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.31 MHz, 06-45-01
> cpu3:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,
> CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,
> DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
> BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
> F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
> P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
> acpimadt0: bogus nmi for apid 0
> acpimadt0: bogus nmi for apid 2
> acpimadt0: bogus nmi for apid 1
> acpimadt0: bogus nmi for apid 3
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xf800, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus