Re: "Cannot allocate memory" error when memory is enough
Hi Philip, Thanks very much for your time and patience. I run "syspatch" command regularly, so it should be 6.3-stable. My full dmesg output is here: OpenBSD 6.3 (RAMDISK_CD) #98: Sat Mar 24 14:26:39 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 4228214784 (4032MB) avail mem = 4096286720 (3906MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe1840 (41 entries) bios0: vendor FUJITSU // Phoenix Technologies Ltd. version "Version 1.06" date 01/16/2009 bios0: FUJITSU LifeBook T5010 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP HPET MCFG SSDT SSDT APIC BOOT SLIC SSDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz, 2527.30 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,MELTDOWN cpu0: 3MB 64b/line 8-way L2 cache cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus 8 (RP01) acpiprt3 at acpi0: bus 16 (RP02) acpiprt4 at acpi0: bus 24 (RP03) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus 56 (PCIB) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured "FUJ02BF" at acpi0 not configured "FUJ02E5" at acpi0 not configured "FUJ02B1" at acpi0 not configured "SYN1F01" at acpi0 not configured "FUJ02E3" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C0C" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:23:26:5e:36:bc uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int 16 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int 17 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2 int 18 ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2 int 18 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 82801I HD Audio" rev 0x03 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: msi pci1 at ppb0 bus 8 ppb1 at pci0 dev 28 function 1 "Intel 82801I PCIE" rev 0x03: msi pci2 at ppb1 bus 16 ppb2 at pci0 dev 28 function 2 "Intel 82801I PCIE" rev 0x03: msi pci3 at ppb2 bus 24 iwn0 at pci3 dev 0 function 0 "Intel WiFi Link 5300" rev 0x00: msi, MIMO 3T3R, MoW, address 00:21:6a:4f:20:5a uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x03: apic 2 int 23 uhci4 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x03: apic 2 int 19 uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x03: apic 2 int 18 ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x03: apic 2 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x93 pci4 at ppb3 bus 56 cbb0 at pci4 dev 3 function 0 "O2 Micro OZ711SP1 CardBus" rev 0x01: apic 2 int 17 cbb1 at pci4 dev 3 function 1 "O2 Micro OZ711SP1 CardBus" rev 0x01: apic 2 int 17 sdhc0 at pci4 dev 3 function 2 "O2 Micro OZ711MP1 SDHC" rev 0x02: apic 2 int 17 sdhc0: SDHC 3.0, 33 MHz base clock sdmmc0 at sdhc0: 4-bit "O2 Micro OZ711MP1 XDHC" rev 0x01 at pci4 dev 3 function 3 not configured "O2 Micro Firewire" rev 0x02 at pci4 dev 3 function 4 not configured cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 57 device 0 cacheline 0x0, lattimer 0x20 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 57 device 0 cacheline 0x0, lattimer 0x20 pcmcia1 at cardslot1 "Intel 82801IEM LPC" rev 0x03 at pci0 dev 31 function 0 not configured ahci0 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x03: msi, AHCI 1.2 ahci0: port 0: 3.0Gb/s ahci0: port 1: 1.5Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.50e043a28e8c sd0: 305245MB, 512 bytes/sector, 625142448 sectors cd0 at scsibus0 targ 1 lun 0: ATAPI 5/cdrom removable "Intel 82801I SMBus" rev 0x03 at pci0 dev 31 function 3 not configured usb2 at uhci0: USB revision 1.0 uhub2 at usb2 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00 addr 1 usb3 at uhci1: USB revision 1.0 uhub3 at usb3 configuration 1 interface 0
Re: em0: couldn't map interrupt (No support for my Intel NIC?)
On Thu, Jul 05, 2018 at 03:36:17AM +0200, Farid Joubbi wrote: > Hi, > > I have a server running bhyve in FreeBSD. I did PCI passthrough in order > to have exclusive access to one of the network interfaces on the server. > My plan was to use that NIC in OpenBSD. Unfortunately when I boot the 6.3 > release installer I get this in dmesg: > "em0 at pci0 dev 5 function 0 "Intel 82576" rev 0x01: couldn't map > interrupt". > > The installation goes through without errors, but the Intel NIC is not > visible during install or after rebooting the installed system. > > Man pages suggest that the problem is a fatal initialization error. > > The NIC works without problems installing FreeBSD. > In FreeBSD the NIC uses the igb driver. > > https://man.openbsd.org/FreeBSD-11.1/igb.4 > > The OpenBSD man page for em lists 82576EB as supported. > > The NIC is an Intel Gigabi ET2 quad: > https://ark.intel.com/products/series/46841/Intel-Gigabit-ET-Server-Adapter-Series > > Could it be that the quad variant of the NIC is not supported by OpenBSD? > Is there anything I can do to make it work? > Is it possible to use the igb driver in OpenBSD somehow? > > Thanks. Before anyone at all spends any time on this, please verify if this works without bhyve in the way. Eg, boot natively on this hardware and see. Or did you already do that? In which case the commentary about bhyve is extraneous. -ml
em0: couldn't map interrupt (No support for my Intel NIC?)
Hi, I have a server running bhyve in FreeBSD. I did PCI passthrough in order to have exclusive access to one of the network interfaces on the server. My plan was to use that NIC in OpenBSD. Unfortunately when I boot the 6.3 release installer I get this in dmesg: "em0 at pci0 dev 5 function 0 "Intel 82576" rev 0x01: couldn't map interrupt". The installation goes through without errors, but the Intel NIC is not visible during install or after rebooting the installed system. Man pages suggest that the problem is a fatal initialization error. The NIC works without problems installing FreeBSD. In FreeBSD the NIC uses the igb driver. https://man.openbsd.org/FreeBSD-11.1/igb.4 The OpenBSD man page for em lists 82576EB as supported. The NIC is an Intel Gigabi ET2 quad: https://ark.intel.com/products/series/46841/Intel-Gigabit-ET-Server-Adapter-Series Could it be that the quad variant of the NIC is not supported by OpenBSD? Is there anything I can do to make it work? Is it possible to use the igb driver in OpenBSD somehow? Thanks.
Re: Lumina-Terminal on OpenBSD
Don't know what's wrong with you, I copy-paste at xterm(1) frequently. There are three methods which work for me. Method 1: use your mouse to select text using left and right mouse buttons, then press middle mouse button where you want to paste the text (if you don't have middle mouse button, then X.org emulates its click when you press left and right mouse buttons at the same time). Method 2: again use your mouse to select text, but this time we'll place it in different copy buffer using Ctrl + Insert combination. Then to paste the text you just have to press Shift + Insert combination. This one is like Ctrl + C and Ctrl + V in Microsoft Windows. Method 3: learn general tmux(1) commands by reading its manual, you need to enter copy mode: Ctrl + B [ By default it uses Emacs-like key bindings, so mark the start of the text you're interested in: Ctrl + Space Then by using cursor commands select text and press Alt + W to copy it. In the end in the same tmux session (at any pane and any windows) press Ctrl + B ] to paste yanked text.
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
Hi, Eric wrote on Wed, Jul 04, 2018 at 01:55:17PM -0500: > The solution is obvious. If there are any bug fixes of sufficient > importance, report the bug, collect the $500,000 for the foundation, > and then fix it. i can hardly believe this needs to be said, but given the lack of any smiley, and given the presence of several purportedly "humorous" postings in this thread: Given that the very *purpose* of the company trying to buy these exploits is to earn money from COVERTLY BREACHING THE PRIVACY OF SOFTWARE USERS, i'm calling out that company, and any other company with a similar business plan, as a particularly bad instance of ORGANIZED CYBERCRIME according to any reasonable moral standard. For example, i believe that this kind of criminal activity is SUBSTANTIALLY WORSE than ordinary credit card fraud because such companies put hundreds of millions of people at risk who do not even learn that they were harmed, not even after the fact, whereas with ordinary fraud, the victim at least knows about the completed crime. Besides, what this company does is life-threatening, whereas credit card fraud only puts your money in danger. So i'm adamant that anybody even remotely considering to do any kind of business with such a company must be instantly expelled from any kind of free software project. Besides, you can't be so naive as to think that you will see any money from such a criminal enterprise without signing an NDA to NOT DISCLOSE THE VULNERABILITY TO THE SOFTWARE AUTHOR (or anyone else)? Besides, even if you could retain the right to publish the vulnerability you reported, it is an obvious requirement of basic ethics that you report potentially dangerous bugs as soon as possible TO THE SOFTWARE AUTHOR, in particular, before talking to anybody else about them, and that you do not disclose the problem to third parties before the vulnerability is fixed, unless the author fails to fix the problem within reasonable time, typically a few days, sometimes maybe a few weeks. So the order of actions you are proposing is close to criminal as well. Now, can we please stop this thread? Even joking about these matters is hardly funny because it implies an insinuation that there might be anybody involved in OpenBSD who might remotely consider doing business with such criminal organizations, or that there might be any bribable or corrupt people in the vicinity of the project. Such insinuations are not funny. The question how such criminal organizations could be abolished might be considered politically interesting by some, but even that question is totally off-topic on misc@. It is simply and plainly unrelated to OpenBSD. The only on-topic aspect is the fact that state agencies exist that actively and systematically attempt to compromise the security of any kind of software, including free software, including OpenBSD. But that is not news.
Re: Lumina-Terminal on OpenBSD
I recommend you spend some time learning a bit of tmux, then you can use any terminal, copy/paste and much much more will be available. I like urxvt, it's simple, stable and lightweight. On Wed, Jul 4, 2018 at 5:37 PM rehcla wrote: > Hey Martijn, > > Just found a Lumina thread on the OpenBSD Mailinglist and in that one you > said you are the maintainer of the Lumina port. > Is that still the case? > I did like Lumina on TrueOS, but TrueOS was far too unstable for me... > Anyway I identifiy much more with OpenBSD and Theo de Raadt:) > If yes, is there any reason wh lumina-terminal is missing? > xterm has no copy paste feature (what is handy if you need to use mpv as > youtube-player)... > I installed the kde-konsole what dependce on a buch of other kde packages. > It would be great to have lumina-terminal available... How about it? > > Greeting > rehcla > >
Lumina-Terminal on OpenBSD
Hey Martijn, Just found a Lumina thread on the OpenBSD Mailinglist and in that one you said you are the maintainer of the Lumina port. Is that still the case? I did like Lumina on TrueOS, but TrueOS was far too unstable for me... Anyway I identifiy much more with OpenBSD and Theo de Raadt:) If yes, is there any reason wh lumina-terminal is missing? xterm has no copy paste feature (what is handy if you need to use mpv as youtube-player)... I installed the kde-konsole what dependce on a buch of other kde packages. It would be great to have lumina-terminal available... How about it? Greeting rehcla
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
On Wed, 4 Jul 2018 18:06:04 +0200 Reyk Floeter wrote: > I hope somebody steps up and donates $500,000 to the OpenBSD foundation > instead. The solution is obvious. If there are any bug fixes of sufficient importance, report the bug, collect the $500,000 for the foundation, and then fix it. Eric
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
Ok sorry ididnt get it woops ;) On Wed 4 Jul 2018, 19:21 Marko Cupać, wrote: > On Wed, 4 Jul 2018 19:02:56 +0100 > Tom Smyth wrote: > > > Hello Marko /Sekeres > > > > I dont mean to start a flame war as it is counterproductive but Idont > > fully get what you mean / imply by > > > > >.".. while not requiring from OpenBSD to introduce Code of Conduct" > > I'm just trolling around :) > > At the same time I'm relatively long-time *BSD user, thankful to anyone > and everyone who is making them possible. Specially to OpenBSD who still > appears to stick to simple "Don't be an asshole" CoC, as opposed to > some who took the different path, probably partly as a result of > accepting large "generous" "contributions". > > As The Smiths sang, "Some BSDs are bigger than the others". > > Once again, I'm just trolling around, I hope noone takes my posts on > this topic seriously. > -- > Before enlightenment - chop wood, draw water. > After enlightenment - chop wood, draw water. > > Marko Cupać > https://www.mimar.rs/ > >
Re: "Cannot allocate memory" error when memory is enough
On Wed, Jul 4, 2018 at 12:57 AM Nan Xiao wrote: > My OS is 6.3. I already use "pkg_add -u" to upgrade all installed > packages. cmake and egdb are are installed by "pkg_add", not compiled > by me. > You don't mention -release, or -stable, or -current, which is utterly critical: 6.3-release and 6.3-stable are not guaranteed to run -current packages, and ditto for even merely an older -current kernel+base vs fresh -current packages. Your messages continue to lack these critical details, which is why we tell everyone to *include your full dmesg output*. That would have instantly answered what version you were running and how out of date (or not) it is! > "vmstat -m" gives some information: > > $ vmstat -m > ...but you trimmed out most of what would show failures or odd consumption patterns. It seems kernel dynamic memory is run out, and devbuf and temp consume > most of the space. > What I saw in the output doesn't indicate that. Philip Guenther
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
On Wed, 4 Jul 2018 19:02:56 +0100 Tom Smyth wrote: > Hello Marko /Sekeres > > I dont mean to start a flame war as it is counterproductive but Idont > fully get what you mean / imply by > > >.".. while not requiring from OpenBSD to introduce Code of Conduct" I'm just trolling around :) At the same time I'm relatively long-time *BSD user, thankful to anyone and everyone who is making them possible. Specially to OpenBSD who still appears to stick to simple "Don't be an asshole" CoC, as opposed to some who took the different path, probably partly as a result of accepting large "generous" "contributions". As The Smiths sang, "Some BSDs are bigger than the others". Once again, I'm just trolling around, I hope noone takes my posts on this topic seriously. -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
How to configure address selection policy for IPv6 (and IPv4)
Hello, according to RFC3484 and it's successor (RFC6724) a IPv6 implementation should support a configurable address selection via a mechanism at least as powerful as the policy table defines in this RFC's. Found the powerful ip6addrctl command in Freebsd (derived from KAME's addrselect) , but it seem's that there is no such command for OpenBSD. My Questions: 1. Is there some possibility to show and manipulate the address selection policy in OpenBSD ? 2. if not: are there any plans to implement this in the near future ? 3. If not: is the kernel internal address selection policy conform to the default address selection policy in RFC6724 ? Thanks, Hendrik
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
Hello Marko /Sekeres I dont mean to start a flame war as it is counterproductive but Idont fully get what you mean / imply by >.".. while not requiring from OpenBSD to introduce Code of Conduct" I think to anyone who has been on the mailing list for a number of years anyone who has read the project goals it is clear what the projects goals are and one of the most important is increase security users are not in anyway bound to a code of conduct. it is not in the license based on technical discussions and safeguards and talks about risks bugs and their mitigations I don't think any one @openbsd.org would sell the project out suffice to say that the anyone following the Selective Disclosure Controversies would understand that the OpenBSD project is does not endorse them or advocate them. selling zeroday bugs to anyone and deliberately withholding information from the developers of the software is probably the antithesis of what this project stands for. Regards, Tom Smyth On 4 July 2018 at 18:23, Marko Cupać wrote: > On Wed, 4 Jul 2018 18:06:04 +0200 > Reyk Floeter wrote: > >> I hope somebody steps up and donates $500,000 to the OpenBSD >> foundation instead. > > ... while not requiring from OpenBSD to introduce Code od Conduct > > :D > > -- > Before enlightenment - chop wood, draw water. > After enlightenment - chop wood, draw water. > > Marko Cupać > https://www.mimar.rs/ >
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
On Wed, 4 Jul 2018 18:06:04 +0200 Reyk Floeter wrote: > I hope somebody steps up and donates $500,000 to the OpenBSD > foundation instead. ... while not requiring from OpenBSD to introduce Code od Conduct :D -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
Are you advertising this crap on our list? I hope somebody steps up and donates $500,000 to the OpenBSD foundation instead. > Am 30.06.2018 um 23:11 schrieb Szekeres Dani : > > Just read: > > https://www.bleepingcomputer.com/news/security/rewards-of-up-to-500-000-offered-for-freebsd-openbsd-netbsd-linux-zero-days/ > > > > > Rewards of Up to $500,000 Offered for FreeBSD, OpenBSD, NetBSD, Linux > Zero-Days > > Exploit broker Zerodium is offering rewards of up to $500,000 for zero-days > in UNIX-based operating systems like OpenBSD, FreeBSD, NetBSD, but also for > Linux distros such as Ubuntu, CentOS, Debian, and Tails. > > The offer, first advertised via Twitter earlier this week, is available as > part of the company's latest zero-day acquisition drive. Zerodium is known > for buying zero-days and selling them to government agencies and law > enforcement. > > > > https://twitter.com/Zerodium/status/1012007051466162177 >
Re: KDE-apps okular, kmahjongg
Am 07/04/18 um 16:13 schrieb Stuart Henderson:
> On 2018-07-04, Stefan Wollny wrote:
>> Somehow the dbus-daemon is not recognized although started as 'rcctl ls
>> started' shows. And
>
> That is a system dbus-daemon but you didn't have a session dbus-daemon.
>
>> Finally I added 'export $(dbus-launch)' to .xinitrc (plus kdeinit4) and
>> those KDE apps now do get started as they did until last week.
>>
>> Is this expected behaviour? I didn't find anything related to this in
>> the man pages or the FAQ - if it is could s.o. please point my sore eyes
>> to the relevant documentation?
>
> There was a fallback in the dbus port for the case where the session bus
> was missing, it was removed for a bit, but it seems few people bother
> to read the dbus pkg-readme and most software which needs it doesn't
> fail with a very informative error message, so it has gone back in
> for now...
>
> The fallback is not great because it means that each program wanting
> to use dbus has its own separate session bus - there's only supposed to
> be a single one.
>
> You are supposed to run the session bus like this:
>
> $ cat /usr/local/share/doc/pkg-readmes/dbus-*
>
> $OpenBSD: README-main,v 1.3 2017/11/01 06:27:31 ajacoutot Exp $
>
> +---
> | Running dbus-1.12.8p0v0 on OpenBSD
> +---
>
> To start a session bus instance of dbus-daemon (needed by applications
> installing /usr/local/share/dbus-1/services/*.service files), add the
> following lines to your Xsession script before starting the window manager
> (see dbus-launch(1) for more info) -- note that some session/login managers,
> like gnome-session(1) already handle this automatically.
>
> e.g. console login: ~/.xinitrc
> if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then
> eval `dbus-launch --sh-syntax --exit-with-session`
> fi
>
> e.g. graphical display manager: ~/.xsession
> if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then
> eval `dbus-launch --sh-syntax --exit-with-x11`
> fi
>
>
Thank you, Stuart! Excellent explanation and precise help, right to the
point!
Re: KDE-apps okular, kmahjongg
On 2018-07-04, Stefan Wollny wrote:
> Somehow the dbus-daemon is not recognized although started as 'rcctl ls
> started' shows. And
That is a system dbus-daemon but you didn't have a session dbus-daemon.
> Finally I added 'export $(dbus-launch)' to .xinitrc (plus kdeinit4) and
> those KDE apps now do get started as they did until last week.
>
> Is this expected behaviour? I didn't find anything related to this in
> the man pages or the FAQ - if it is could s.o. please point my sore eyes
> to the relevant documentation?
There was a fallback in the dbus port for the case where the session bus
was missing, it was removed for a bit, but it seems few people bother
to read the dbus pkg-readme and most software which needs it doesn't
fail with a very informative error message, so it has gone back in
for now...
The fallback is not great because it means that each program wanting
to use dbus has its own separate session bus - there's only supposed to
be a single one.
You are supposed to run the session bus like this:
$ cat /usr/local/share/doc/pkg-readmes/dbus-*
$OpenBSD: README-main,v 1.3 2017/11/01 06:27:31 ajacoutot Exp $
+---
| Running dbus-1.12.8p0v0 on OpenBSD
+---
To start a session bus instance of dbus-daemon (needed by applications
installing /usr/local/share/dbus-1/services/*.service files), add the
following lines to your Xsession script before starting the window manager
(see dbus-launch(1) for more info) -- note that some session/login managers,
like gnome-session(1) already handle this automatically.
e.g. console login: ~/.xinitrc
if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
e.g. graphical display manager: ~/.xsession
if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then
eval `dbus-launch --sh-syntax --exit-with-x11`
fi
Re: Rewards of Up to $500,000 Offered for OpenBSD Zero-Days (and other dist.)
On Sat, 30 Jun 2018 23:11:15 +0200 "Szekeres Dani" wrote: > Rewards of Up to $500,000 Offered for FreeBSD, OpenBSD, NetBSD, Linux > Zero-Days Seen this comment on /. http://dilbert.com/strip/1995-11-13 :D -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: mgre and bgpd
On 07/04/2018 11:53 AM, Sebastian Benoit wrote: Hi, is this on -current? Please provide a dmesg. Thanks for the reply, it's 6.3 not current. We couldn't see any mgre changes since the 6.3 release. But openbgpd has some changes that look unrelated to our problem as we understand it. Also: are you saying that 'bgpctl sh fib' displays routes that 'netstat -rn' or 'route -n show' do not? Yes that's correct. Here is the dmesg: OpenBSD 6.3 (GENERIC.MP) #4: Sun Jun 17 11:22:20 CEST 2018 r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 137303584768 (130942MB) avail mem = 133135282176 (126967MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xea000 (42 entries) bios0: vendor American Megatrends Inc. version "3.0a" date 02/08/2018 bios0: Supermicro X10SRD-F acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SPMI MCFG UEFI HPET NFIT WDDT SSDT NITR SSDT SSDT PRAD DMAR HEST BERT ERST EINJ acpi0: wakeup devices IP2P(S4) EHC1(S4) EHC2(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) BR1A(S4) BR1B(S4) BR2A(S4) BR2B(S4) BR2C(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) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2200.26 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpitimer0: recalibrated TSC frequency 220199 Hz 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, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2200.00 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2200.00 MHz 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2200.00 MHz 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 8 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2200.00 MHz cpu4: 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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 4, package 0 cpu5 at mainbus0: apid 10 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2200.00 MHz cpu5:
Re: clearing the disk cache
Thanks. :)
But isn't "bufcachepercent < 5" there for a reason? Will my machine
now catch fire?
On Wed, Jul 4, 2018 at 10:23 AM, Boudewijn Dijkstra
wrote:
> Op Tue, 03 Jul 2018 16:06:37 +0200 schreef Maximilian Pichler
> :
>>
>> Now I'm resorting to "sysctl kern.bufcachepercent=5; sysctl
>> kern.bufcachepercent=90" to "almost" clear the cache. If only setting
>> it to 0 were allowed...
>
>
> --- sys/kern/kern_sysctl.c.orig Mon Feb 19 09:59:52 2018
> +++ sys/kern/kern_sysctl.c Wed Jul 4 10:20:53 2018
> @@ -602,7 +602,7 @@
> );
> if (error)
> return(error);
> - if (bufcachepercent > 90 || bufcachepercent < 5) {
> + if (bufcachepercent > 90) {
> bufcachepercent = opct;
> return (EINVAL);
> }
>
>
> --
> Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
>
Re: clearing the disk cache
Op Tue, 03 Jul 2018 16:06:37 +0200 schreef Maximilian Pichler
:
Now I'm resorting to "sysctl kern.bufcachepercent=5; sysctl
kern.bufcachepercent=90" to "almost" clear the cache. If only setting
it to 0 were allowed...
--- sys/kern/kern_sysctl.c.orig Mon Feb 19 09:59:52 2018
+++ sys/kern/kern_sysctl.c Wed Jul 4 10:20:53 2018
@@ -602,7 +602,7 @@
);
if (error)
return(error);
- if (bufcachepercent > 90 || bufcachepercent < 5) {
+ if (bufcachepercent > 90) {
bufcachepercent = opct;
return (EINVAL);
}
--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
Re: "Cannot allocate memory" error when memory is enough
HI Philip, Thanks very much for your detailed explanation! My OS is 6.3. I already use "pkg_add -u" to upgrade all installed packages. cmake and egdb are are installed by "pkg_add", not compiled by me. "vmstat -m" gives some information: $ vmstat -m Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 752 283226592131280 3 32 482 1054 691465 640 99 64 622 41141023682 320 191519 128 4496560 27265523 1603596104 256 164364 107121 80 19059 512 387197 63372 40 18454 1024 1507 5 125086 20 0 2048 36 4 2193 10 0 4096 555 1 80673 5 0 8192 207 1450 5 0 16384 10 0 15 5 0 327689 0 29163 5 0 655369 0 21946371 5 0 2621443 0 3 5 0 5242882 0 2 5 0 .. Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) devbuf 2991 7220K 7220K 78644K 1463470 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536,262144,524288 .. dirhash 678 130K239K 78644K183870 0 16,32,64,128,256,512 .. ttys 408 1724K 1724K 78644K 4080 0 512,1024,4096,8192 .. VM swap 7 299K299K 78644K70 0 16,64,2048,262144 UVM amap 29512K441K 78644K 43028130 0 16,32,64,128,256,512 .. temp54 2082K 2211K 78644K 228087350 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536,524288 .. DRM 275 114K116K 78644K 14100 0 16,32,64,128,256,512,1024,2048,4096,16384 Memory Totals: In UseFreeRequests 12378K619K53994333 Memory resource pool statistics NameSize Requests FailInUse Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle phpool 112849530 4236 125 1 124 124 0 80 extentpl 40 1260 48 1 0 1 1 0 80 pmappl 192662210 34 105 103 2 3 0 80 .. In use 34552K, total allocated 40384K; utilization 85.6% It seems kernel dynamic memory is run out, and devbuf and temp consume most of the space. Could you give some suggestions? Thanks very much in advance! Best Regards Nan Xiao On Wed, Jul 4, 2018 at 10:57 AM, Philip Guenther wrote: > On Tue, 3 Jul 2018, Philip Guenther wrote: > > > Flakey button on my mouse; time to clean it again and throw it out if it > keeps glitching. Sorry about that. > > >> On Tue, Jul 3, 2018 at 4:53 PM Nan Xiao wrote: >> > Thanks for your reply! The "ulimit -a" outputs following: >> > >> > $ ulimit -a >> > time(cpu-seconds)unlimited >> > file(blocks) unlimited >> > coredump(blocks) unlimited >> > data(kbytes) 33554432 >> > stack(kbytes)8192 >> > lockedmem(kbytes)1332328 >> > memory(kbytes) 3978716 >> > nofiles(descriptors) 128 >> > processes1310 >> > >> > It seems should be enough to launch cmake or egdb. > > But it wasn't and the kernel can only indicate that with a single error > code, so now you have to actually dig into what's going on. There are > many possibilities, as a search for ENOMEM in /usr/src/sys/kern/*exec*.c > will show. > 1) the ELF interpreter (normal ld.so) could be too large > 2) the PT_OPENBSD_RANDOMIZE segment could be larger than permitted by the >kernel > 3) program's text segment could exceed the maximum for the arch, MAXTSIZ > 4) the program's vnode couldn't be mmaped for some reason > 5) the argument list and environment were together too big for the stack > 6) the signal trampoline couldn't be mapped into the process VM > 7) other random memory allocation problems > > Of those, (1), (4), and (6) are *really* unlikely. (3) is possible if > you're building a debugging binary that's *huge* as a result. (5) would > result in _all_ programs failing in that shell. I think (7) would show up > in a close examination of the "vmstat -m" output. > > (2) is perhaps the most likely, as recent compiler changes have increased > the expected size of the PT_OPENBSD_RANDOMIZE segment and while the kernel > limit on that was also increased recently, you didn't provide any > information about your setup: are your kernel, userland, and ports all in > sync? > > > Philip Guenther
Re: mgre and bgpd
Hi,
is this on -current? Please provide a dmesg.
Also: are you saying that 'bgpctl sh fib' displays routes that
'netstat -rn' or 'route -n show' do not?
/Benno
Benjamin Girard(benjamin.gir...@kambi.com) on 2018.07.03 14:13:01 +:
> Hi,
>
> So we are currently trying to set up one mgre interface instead of multiple
> gre tunnel between two vpn machines and we are running against a problem with
> bgpd.
>
> we have two machines, vpn1 and vpn2, we have set up an mgre interface on both
> like this:
>
> root@vpn1:~ # ifconfig mgre0
>
> mgre0: flags=8841 mtu 1476
> index 15 priority 0 llprio 3
> encap: vnetid none
> groups: mgre
> tunnel: inet ttl 64 nodf
> inet 172.29.1.2 netmask 0xff00
>
> root@vpn1:~ # route -n show | grep 172.29.1
> 172.29.1/24172.29.1.3 UCn00 - 4 mgre0
> 172.29.1.2 UHS1 21 - L 8 mgre0
> 172.29.1.3 mgre0 UHl0 309 - 1 mgre0
>
> root@vpn2:~ # ifconfig mgre0
>
> mgre0: flags=8841 mtu 1476
> index 15 priority 0 llprio 3
> encap: vnetid none
> groups: mgre
> tunnel: inet 192.168.0.3 ttl 64 nodf
> inet 172.29.1.3 netmask 0xff00
>
> root@vpn2:~ # route -n show | grep 172.29.1
> 172.29.1/24172.29.1.2 UCn00 - 4 mgre0
> 172.29.1.2 mgre0 UHl0 1295 - 1 mgre0
> 172.29.1.3UHS1 39 - L 8 mgre0
>
> The tunnel is up and reachable:
>
> root@vpn1:~ # ping -I 172.29.1.2 172.29.1.3
> PING 172.29.1.3 (172.29.1.3): 56 data bytes
> 64 bytes from 172.29.1.3: icmp_seq=0 ttl=255 time=12.351 m
>
> We then have a bgp session up as follow:
>
> neighbor 172.29.1.3 {
> descr "vpn1"
> local-address 172.29.1.2
> remote-as 64660
> announce IPv4 unicast
> announce IPv6 none
> holdtime 25
> announce all
> }
>
> Bgp tunnel is up:
>
> root@vpn1:~ # bgpctl show
>
> Neighbor ASMsgRcvdMsgSent OutQ Up/Down State/PrfRcvd
> vpn1 64660329201 0 00:17:10410
>
> the bgp fib table shows the prefix received properly:
>
> root@vpn1:~ # bgpctl show fib
> flags: * = valid, B = BGP, C = Connected, S = Static, D = Dynamic
>N = BGP Nexthop reachable via this route R = redistributed
>r = reject route, b = blackhole route
>
> flags prio destination gateway
> *B 48 10.1.0.0/24
> *B 48 10.1.2.0/24
> *B 48 10.1.3.0/24
> *B 48 10.1.4.0/24
> *B 48 10.1.5.0/24
> *B 48 10.1.6.0/24
> *B 48 10.1.16.0/24
> *B 48 10.1.18.0/24
> *B 48 10.1.19.0/24
> *B 48 10.1.20.0/24
> *B 48 10.1.21.0/24
> ... snip
>
> and rib table:
>
> root@vpn1:~ # bgpctl show rib
> flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale
> origin: i = IGP, e = EGP, ? = Incomplete
>
> flags destination gateway lpref med aspath origin
> *>10.1.0.0/24 172.29.1.3 100 1003000 64660 64901 64740 i
> *>10.1.2.0/24 172.29.1.3 100 1361100 64660 64901 i
> *>10.1.3.0/24 172.29.1.3 100 2000100 64660 64901 i
> *>10.1.4.0/24 172.29.1.3 100 1010300 64660 64901 64710 i
> *>10.1.5.0/24 172.29.1.3 100 1365100 64660 64901 64711 i
> *>10.1.6.0/24 172.29.1.3 100 1001200 64660 64901 64712 i
> *>10.1.16.0/24 172.29.1.3 100 1003000 64660 64901 64740 i
> *>10.1.18.0/24 172.29.1.3 100 1361100 64660 64901 i
> *>10.1.19.0/24 172.29.1.3 100 2000100 64660 64901 i
> *>10.1.20.0/24 172.29.1.3 100 1010300 64660 64901 64710 i
> *>10.1.21.0/24 172.29.1.3 100 1365100 64660 64901 64711 i
>
> root@vpn1:~ # bgpctl show fib next
> flags: * = valid, B = BGP, C = Connected, S = Static, D = Dynamic
>N = BGP Nexthop reachable via this route R = redistributed
>r = reject route, b = blackhole route
>
> flags prio destination gateway
> *SNR 8 172.29.1.3/32
> root@vpn1:~ # bgpctl show next
> Flags: * = nexthop valid
>
> Nexthop Route Prio Gateway Iface
> * 172.29.1.3 172.29.1.3/32 8 mgre0 (UP, unknown)
>
>
> But we can't see those prefixes added to the kernel routing table:
>
>
> r...@vpn1.atc.kambi.com(master):~ # route -n show | grep "10\.1\."
> r...@vpn1.atc.kambi.com(master):~ # route -n show | grep mgre
> 172.29.1/24172.29.1.2 UCn00 - 4 mgre0
>
Re: mgre and bgpd
After trying couple of things, we noticed that the bgp routes are missing from the kernel routing table as long as we have a route added toward the other end of the tunnel using the public ip of the tunnel as gateway ie: root@vpn1:~ # netstat -rn | grep UGHS 2 4389837 - 8 vlan10 172.29.1.3 UHS 1 5 - L 8 mgre0 If we remove that route toward 172.29.1.3 (mgre tunnel on the other side) then the routing table gets populated with all the bgp routes, but then we can reach that gateway 172.29.1.3 as soon as we readd that route, all the bgp routes disappear: root@vpn1:~ # route -n show | grep mgre 172.29.1/24 172.29.1.2 UCn 0 0 - 4 mgre0 172.29.1.2 mgre0 UHl 0 18431 - 1 mgre0 172.29.1.3 UHS 1 5 - L 8 mgre0 root@vpn1:~ # route del 172.29.1.3 del host 172.29.1.3 root@vpn1:~ # route -n show | grep mgre 10.1.0/24 172.29.1.3 UG 0 0 - 48 mgre0 10.1.2/24 172.29.1.3 UG 0 0 - 48 mgre0 10.1.3/24 172.29.1.3 UG 0 0 - 48 mgre0 10.1.4/24 172.29.1.3 UG 0 0 - 48 mgre0 10.1.5/24 172.29.1.3 UG 0 0 - 48 mgre0 10.1.6/24 172.29.1.3 UG 0 0 - 48 mgre0 10.1.16/24 172.29.1.3 UG 0 0 - 48 mgre0 ... We also noticed that sometimes the iface is missing in the bgpctl show next command: root@vpn1:~ # bgpctl show next Flags: * = nexthop valid Nexthop Route Prio Gateway Iface * 172.29.1.3 172.29.1.3/32 8 Thanks, Ben
Re: KDE-apps okular, kmahjongg
Am 07/02/18 um 09:43 schrieb Stefan Wollny: > > > Am 06/25/18 um 22:36 schrieb Stefan Wollny: >> Hi there, >> >> I run amd64-current with the latest public snapshots: >> $ dmesg | grep Open >> OpenBSD 6.3-current (GENERIC.MP) #52: Sun Jun 24 09:59:46 MDT 2018 >> < Full dmesg at the end > >> >> Although I try to follow reading src-changes and topics on misc@ as >> close as possible I might have missed something lately. Until a few days >> ago okular and kmahjongg came up without a comment. Now I cannot start >> them (havn't tried other KDE apps) >> >> >> $ okular >> okular(68871)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> KCrash: Application 'okular' crashing... >> KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit >> KCrash: Connect >> sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 >> Warning: connect() failed: : No such file or directory >> KCrash: Attempting to start /usr/local/libexec/drkonqi directly >> drkonqi(78427)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> >> ~ $ kmahjongg >> kmahjongg(43798)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> KCrash: Application 'kmahjongg' crashing... >> KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit >> KCrash: Connect >> sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 >> Warning: connect() failed: : No such file or directory >> KCrash: Attempting to start /usr/local/libexec/drkonqi directly >> drkonqi(34562)/kdeui (kdelibs): Session bus not found >> To circumvent this problem try the following command (with Linux and bash) >> export $(dbus-launch) >> >> What did I miss / what am I doing wrong here? >> >> In /etc/rc.conf.local I have: >> pkg_scripts=freshclam clamd messagebus avahi_daemon cupsd smartd >> cups_browsed >> >> (cups isn't working for a looong time but that should be a different thread) >> >> Anyone got a clue what might be wrong with my system or what knob to >> turn? Or is this just a temporary annnoyance that ought to go away in a >> short time? >> >> TIA. >> >> Best, >> STEFAN >> >> > > Now that I am back in business having updated the system (new dmesg at > the end) and all installed packages I tried again ... yet neither > kmahjongg nor okular are working: > > ~ $ pkg_info | grep kmah > kmahjongg-4.14.3p3 Mah Jongg solitare board game for KDE > libkmahjongg-4.14.3p1 common library for Mah Jongg-based KDE games > > ~ $ pkg_info | grep oku > libmusicbrainz5-5.0.1p4 library for audio metadata lookup (v5) > okular-4.14.3p7 KDE document viewer > > ~ $ kmahjongg > kmahjongg(25428)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > KCrash: Application 'kmahjongg' crashing... > KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit > KCrash: Connect > sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 > Warning: connect() failed: : No such file or directory > KCrash: Attempting to start /usr/local/libexec/drkonqi directly > drkonqi(30570)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > > ~ $ okular > okular(31187)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > KCrash: Application 'okular' crashing... > KCrash: Attempting to start /usr/local/libexec/drkonqi from kdeinit > KCrash: Connect > sock_file=/home/sw/.kde4/socket-asterix.fritz.box/kdeinit4__0 > Warning: connect() failed: : No such file or directory > KCrash: Attempting to start /usr/local/libexec/drkonqi directly > drkonqi(23688)/kdeui (kdelibs): Session bus not found > To circumvent this problem try the following command (with Linux and bash) > export $(dbus-launch) > > > ~ $ doas rcctl ls started > apmd > avahi_daemon > clamd > cron > cups_browsed > cupsd > freshclam > messagebus > ntpd > pflogd > postgresql > sensorsd > slaacd > smartd > smtpd > sndiod > sshd > syslogd > > > Has anyone a clue what might be missing? Wrong permissions? > > Any hint welcome. TIA! > OK - I found a solution (though I still do not understand what has changed): Somehow the dbus-daemon is not recognized although started as 'rcctl ls started' shows. And $ cat /var/log/daemon | grep dbus [ ... ] Jul 3 09:39:34 asterix dbus-daemon[56322]: [system] Activating service name='org.freedesktop.ColorManager' requested by ':1.1' (uid=0 pid=34041 comm="/usr/local/sbin/cupsd -C /etc/cups/cupsd.conf -s /") (using servicehelper) Jul 3 09:39:34 asterix dbus-daemon[56322]: [system] Successfully activated service 'org.freedesktop.ColorManager' Jul 3
