Re: WARNING: symbol(icudt58_dat) size mismatch, relink your program
On 2017-04-21 19:09, bian wrote: I did not try slappasswd but the message is triggered from other places as well. From my ~/.xsession-errors (using 6.1 , xfce4): firefox-esr:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program soffice.bin:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program vlc:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program Best regards /Birger On 2017-04-20 21:40, Predrag Punosevac wrote: Sorry for the noise. Did anybody try to use slappasswd after upgrading from 6.0 to 6.1 (amd64). I get slappasswd:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program I tried reinstalling openldap-server-2.4.44p3 which I only keep around. I actually use ldapd from the base. Best, Predrag
chromium 48 (64-bit) crashes on 5.9-beta and xfce-4.12
Hi, running stock OpenBSD 5.9-beta, xfce-4.12p3, and chromium 48.0.2564.97 (64-bit) from snapshots as of Feb. 2 I get get frequent chromium crashes with resulting core dumps (about every 7-8 starts). This happens when starting the browser. Once started it is stable. dmesg and output from gdb on a chromium core dump can be found below. I have similar problems when using firefox-esr 38.6.0, also from snapshots of the same date. Here the start typically goes well, but when switching to another desktop, opening thunar (the file manager), and opening a text file for editing, then chances are high that firefox crashes. This is, however highly irregular and I haven't really found a reliable way to reproduce the error. Both browsers have one extension installed, uBlock Origin, otherwise they are stock. This crashing behaviour occurred also on obsd-5.8 and it was one of my reasons for switching from 5.8 to 5.9-beta. Does anyone know what is going on here? Best regards /birger OpenBSD 5.9-beta (GENERIC.MP) #1863: Sun Jan 24 21:35:42 MST 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4139388928 (3947MB) avail mem = 4009746432 (3823MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe9f80 (88 entries) bios0: vendor Hewlett-Packard version "786G1 v01.16" date 03/05/2009 bios0: Hewlett-Packard HP Compaq dc7900 Convertible Minitower acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC ASF! MCFG TCPA SLIC HPET DMAR acpi0: wakeup devices COM1(S4) COM2(S4) PCI0(S4) PEG1(S4) PEG2(S4) IGBE(S4) PCX1(S4) PCX2(S4) PCX5(S4) PCX6(S4) HUB_(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) [...] 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)2 Duo CPU E8500 @ 3.16GHz, 3159.12 MHz 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 332MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, 3158.75 MHz 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu1: 6MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf400, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEG1) acpiprt2 at acpi0: bus -1 (PEG2) acpiprt3 at acpi0: bus 32 (PCX1) acpiprt4 at acpi0: bus -1 (PCX2) acpiprt5 at acpi0: bus 48 (PCX5) acpiprt6 at acpi0: bus -1 (PCX6) acpiprt7 at acpi0: bus 7 (HUB_) acpicpu0 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1), PSS acpibtn0 at acpi0: PBTN cpu0: Enhanced SpeedStep 3159 MHz: speeds: 3166, 1998 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Q45 Host" rev 0x03 ppb0 at pci0 dev 1 function 0 "Intel Q45 PCIE" rev 0x03: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 2600 XT" rev 0x00 drm0 at radeondrm0 radeondrm0: msi "Intel Q45 HECI" rev 0x03 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 "Intel Q45 PT IDER" rev 0x03: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) puc0 at pci0 dev 3 function 3 "Intel Q45 KT" rev 0x03: ports: 1 com com4 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com4: probed fifo depth: 15 bytes em0 at pci0 dev 25 function 0 "Intel ICH10 D BM LM" rev 0x02: msi, address 00:24:81:1f:f4:91 uhci0 at pci0 dev 26 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801JD USB" rev 0x02: apic 1 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801JD HD Audio" rev 0x02: msi azalia0: codecs: Analog Devices AD1884A audio0 at azalia0 ppb1 at pci0 dev 28 function 0
Re: smplayer 14.9 gets muted when moving or resizing windows in xfce 4.12
Mouse, both in xfce and awesome. With the checkboxes 'Hide content of windows [when moving] or [when resizing]' ticked in xfce muting occurs when (a) pressing keycomb alt+F7 (for moving) and any arrowkey, or (b) alt+F8 (for resizing). As before, this applies regardless of using smplayer or starting mplayer in a terminal. Changing any window (not just the application one) will cause the effect. Complete dmesg and usbdevs are in the first message in this thread. /birger On 2016-01-19 06:28, Jan Lambertz wrote: what Input devices are you useing to resize/move the window ? usb/ps2, Keyboard/mouse ?
smplayer 14.9 gets muted when moving or resizing windows in xfce 4.12
When using smplayer version: 14.9.0 (svn r6994) under xfce 4.12 as supplied in stock obsd 5.8 moving or resizing a window mutes the sound. This happens under the condition that the checkboxes 'Hide content of windows [when moving] or [when resizing]' are ticked. Those boxes are found under the Settings -> Window Manager -> Advanced tab in the main xfce menu. Muting occurs when resizing or moving the smplayer window or any other unrelated window. The problem is repeatable. When using vlc for playing a file and the boxes are ticked as above then there is no muting. dmesg: OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4139388928 (3947MB) avail mem = 4010045440 (3824MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe9f80 (88 entries) bios0: vendor Hewlett-Packard version "786G1 v01.16" date 03/05/2009 bios0: Hewlett-Packard HP Compaq dc7900 Convertible Minitower acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC ASF! MCFG TCPA SLIC HPET DMAR acpi0: wakeup devices COM1(S4) COM2(S4) PCI0(S4) PEG1(S4) PEG2(S4) IGBE(S4) PCX1(S4) PCX2(S4) PCX5(S4) PCX6(S4) HUB_(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) [...] 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)2 Duo CPU E8500 @ 3.16GHz, 3159.13 MHz 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 332MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, 3158.76 MHz 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu1: 6MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf400, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEG1) acpiprt2 at acpi0: bus -1 (PEG2) acpiprt3 at acpi0: bus 32 (PCX1) acpiprt4 at acpi0: bus -1 (PCX2) acpiprt5 at acpi0: bus 48 (PCX5) acpiprt6 at acpi0: bus -1 (PCX6) acpiprt7 at acpi0: bus 7 (HUB_) acpicpu0 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1), PSS acpibtn0 at acpi0: PBTN cpu0: Enhanced SpeedStep 3159 MHz: speeds: 3166, 1998 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Q45 Host" rev 0x03 ppb0 at pci0 dev 1 function 0 "Intel Q45 PCIE" rev 0x03: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 "ATI Radeon X1600" rev 0x00 drm0 at radeondrm0 radeondrm0: apic 1 int 16 "ATI Radeon X1600 Sec" rev 0x00 at pci1 dev 0 function 1 not configured "Intel Q45 HECI" rev 0x03 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 "Intel Q45 PT IDER" rev 0x03: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) puc0 at pci0 dev 3 function 3 "Intel Q45 KT" rev 0x03: ports: 1 com com4 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com4: probed fifo depth: 15 bytes em0 at pci0 dev 25 function 0 "Intel ICH10 D BM LM" rev 0x02: msi, address XXX uhci0 at pci0 dev 26 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801JD USB" rev 0x02: apic 1 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801JD HD Audio" rev 0x02: msi azalia0: codecs: Analog Devices AD1884A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 "Intel 82801JD PCIE" rev 0x02: msi pci2 at ppb1 bus 32 ppb2 at pci0 dev 28 function 4 "Intel 82801JD PCIE" rev 0x02: msi pci3 at ppb2 bus 48 uhci3 at pci0 dev 29 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 20 uhci4 at pci0 dev 29 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 21 uhci5 at pci0 dev 29 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 22 ehci1 at pci0 dev 29 function 7
Re: faq 11 can be clarified
On 2015-11-14 17:22, Mike Burns wrote: On 2015-11-14 16.27.30 +0100, bian wrote: * mention that the "segmentation fault"-message when running the X -configure is harmless and that the xorg.conf.new file was created as it should. That's a bug, and while I likely can't fix it (will gladly look), we'll need your dmesg and the backtrace from the coredump, in the least. I believe Xorg -configure has been useless for a long time. With a hardware that just works, X just works. If a xorg.conf is needed (as when e.g. using vesa instead of a misbehaving driver), it is easier to write a simple one from xorg.conf(5) by hand. Jan This is one way of looking at it, yes. However, the quality of the produced xorg.conf.new is fine. /Birger
Re: faq 11 can be clarified
On 2015-11-14 19:58, bian wrote: On 2015-11-14 17:22, Mike Burns wrote: On 2015-11-14 16.27.30 +0100, bian wrote: * clear up the links http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.amd64 and http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.i386 . The linked text refers to the page where the links are. This is not very helpful as the user never would have clicked the link if the info already was available. Furthermore, the linked text ends with the phrase "problem_blurb" suggesting that it is unfinished. Perhaps you have a patch that clarifies this? No patch, but a short term improvement is to replace the text which the above links point at with the text in /usr/X11R6/README included in the 5.8 release. Which is the following: --- README.amd64Sun Nov 15 14:44:32 2015 +++ README.5.8 Sun Nov 15 14:45:10 2015 @@ -27,9 +27,9 @@ Conventions used in this document: See also Xorg(1), xorg.conf(5). -3. With X.Org XOrgVersion, you can use anti-aliased fonts in many applications. +3. With X.Org 7.7, you can use anti-aliased fonts in many applications. visit http://www.openbsd.org/faq/truetype.html for more information. -problem_blurb + $OpenBSD: README.amd64,v 1.8 2014/07/30 20:06:30 matthieu Exp $
faq 11 can be clarified
Being a recent user of OpenBSD I had the need to read faq 11 in some detail. May I propose to the responsible(s) that the following additions/clarifications be added to the faq: * mention that the "segmentation fault"-message when running the X -configure is harmless and that the xorg.conf.new file was created as it should. * be sure that this info is obvious: "Your xorg.conf file is /root/xorg.conf.new ". A new user typically logs in to his account, su to root, run X -configure, and start looking for the file in the current directory. Well, it's not there. * clear up the links http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.amd64 and http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.i386 . The linked text refers to the page where the links are. This is not very helpful as the user never would have clicked the link if the info already was available. Furthermore, the linked text ends with the phrase "problem_blurb" suggesting that it is unfinished. /Birger
Re: faq 11 can be clarified
On 2015-11-14 17:22, Mike Burns wrote: On 2015-11-14 16.27.30 +0100, bian wrote: * mention that the "segmentation fault"-message when running the X -configure is harmless and that the xorg.conf.new file was created as it should. That's a bug, and while I likely can't fix it (will gladly look), we'll need your dmesg and the backtrace from the coredump, in the least. I will post this shortly in the bugs list on your suggestion. * be sure that this info is obvious: "Your xorg.conf file is /root/xorg.conf.new ". A new user typically logs in to his account, su to root, run X -configure, and start looking for the file in the current directory. Well, it's not there. Seems like something that should be updated in Xorg(1). Though, I must say: typically a new user will not configure X at all, true, but how can faq 11 help if he must (or want). and won't use su(1) if they do. Does this confusion appear when using doas(1)/sudo(1)? Yes. Running sudo X -configure will create the file in /root as expected. This way of working does not improve on the situation. * clear up the links http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.amd64 and http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/xenocara/distrib/notes/README.i386 . The linked text refers to the page where the links are. This is not very helpful as the user never would have clicked the link if the info already was available. Furthermore, the linked text ends with the phrase "problem_blurb" suggesting that it is unfinished. Perhaps you have a patch that clarifies this? No patch, but a short term improvement is to replace the text which the above links point at with the text in /usr/X11R6/README included in the 5.8 release. Generally about faq 11, there was a promising discussion on quality issues in http://marc.info/?l=openbsd-www=139222057820465=2 but it seems to have fizzled out unfortunately.
