Re: Two problems
On Fri, Aug 04, 2023 at 04:12:49PM +0200, Karel Lucas wrote: > > Hi all, > > On a desktop PC on which I have openBSD, I installed KDE. When I start the > X-window system, I still see Fvwm, and no KDE. I also want to start the X > window system when I start this PC, and that is not yet the case. How can I > solve both problems? > > As some others have already commented, there are significant security issues with a big desktop like KDE or Gnome. FVWM in base is setup just enough to let you have an X gui. It is highly customizable to almost whatever you can come up with. FVWM2 is available in ports. It is no longer being developed. It has configuration like the built-in version. Many use it. FVWM3 is under active development and has a very similar configuration, but some notable changes. I use FVWM3 (or 2 from ports if I want to since I already am happy with the configuration I came up with.) If you want to use FVWM and you don't know how to configure it, consider using FVWM3. There is an active forum which provides lots of help. It also has a default configuration that works nicely, but I personally don't like it. It has a menu that will pull up most programs you have installed from KDE, Gnome and others like GIMP, etc. Spectrwm is also nice, small and easy to configure. There are tons of window managers, feel free to try out many until you find what you need and like. I originally came to OpenBSD from Windows, so I used KDE3 a long time ago. Easy switch. But I wouldn't use something like it ever again. xenodm is a good choice. The login screen can be easily customized and you can add functions like shutdown, reboot and a choice of different window managers to start. -- Chris Bennett
Re: Two problems
Just to pass you some hints. The desktop environment choise is very like any very important personal choise: it is about gui, it is about resources and it is about software manufact (ie, I like C lighter ones). KDE and many Gnome applications are often service and resource usage intensive. Starting the desktop environment with the pc has probably some security benefits by doing that via "xenodm" but it is all to demonstrate. Generally speaking by being under a graphic environment you are potentially incrising the chance of a security attack by a Nlots % due to all the services and applications you are bringing up launching it. Then there are also the "bugs" of of X itself. For these reasons I could prefer to keep full control when to start X and eventually to keep something like Fvwm (but I really do not use it) that is light and super tested under OpenBSD. -- Daniele Bonini Aug 4, 2023 16:16:00 Karel Lucas : > > Hi all, > > On a desktop PC on which I have openBSD, I installed KDE. When I start the > X-window system, I still see Fvwm, and no KDE. I also want to start the X > window system when I start this PC, and that is not yet the case. How can I > solve both problems?
Re: Two problems
On Fri, 4 Aug 2023 16:12:49 +0200 Karel Lucas wrote: > Hi all, > > On a desktop PC on which I have openBSD, I installed KDE. When I > start the X-window system, I still see Fvwm, and no KDE. I also want > to start the X window system when I start this PC, and that is not > yet the case. How can I solve both problems? > > Hello, as far as I know, KDE Plasma (the actual desktop environment) is not ported to OpenBSD, just the KDE apps. You've installed the apps, not the desktop environment. If you want X to start automatically, enable the xenodm(1) service. It will display a login interface for you. It seems to have autologin functionality, if you want to be dropped into the desktop immediately. To determine which desktop environment (or window manager) xenodm will start, edit/create the .xsession file in your home directory. exec startxfce4 would make it start XFCE.
Re: Two problems
On 2023-08-04, Karel Lucas wrote: > > On a desktop PC on which I have openBSD, I installed KDE. When I start > the X-window system, I still see Fvwm, and no KDE. I also want to start > the X window system when I start this PC, and that is not yet the case. > How can I solve both problems? there is no "kde desktop" just some of the applications.
Two problems
Hi all, On a desktop PC on which I have openBSD, I installed KDE. When I start the X-window system, I still see Fvwm, and no KDE. I also want to start the X window system when I start this PC, and that is not yet the case. How can I solve both problems?
Re: two problems with the recent X @ i386
On Sun, Sep 11, 2011 at 10:32 AM, patrick keshishian wrote: > On Mon, Aug 22, 2011 at 8:38 AM, Okan Demirmen wrote: >> On Mon 2011.08.22 at 17:19 +0200, Jan Stary wrote: >>> With today's snapshot, I can no longer kill X with crtl+alt+backspace. >>> Has something changed? Is DontZap turned on by default now? I am not >>> using any config file. >> >> I believe that's fixed in -current. > > Did this break again? > > I never saw it broken and fixed (was stuck on an older snapshot). I > just installed a new snapshot (from aug-07) and I can't kill X using ^ Of course I mean sep-07 :-P > ctrl+alt+backspace. > > kern.version=OpenBSD 5.0-current (GENERIC) #55: Wed Sep 7 20:12:59 MDT 2011 >dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > > Also, couple of other weird things which I'm reading man pages for; > probably just changes I need to learn of. > > --patrick
Re: two problems with the recent X @ i386
On Mon, Aug 22, 2011 at 8:38 AM, Okan Demirmen wrote: > On Mon 2011.08.22 at 17:19 +0200, Jan Stary wrote: >> With today's snapshot, I can no longer kill X with crtl+alt+backspace. >> Has something changed? Is DontZap turned on by default now? I am not >> using any config file. > > I believe that's fixed in -current. Did this break again? I never saw it broken and fixed (was stuck on an older snapshot). I just installed a new snapshot (from aug-07) and I can't kill X using ctrl+alt+backspace. kern.version=OpenBSD 5.0-current (GENERIC) #55: Wed Sep 7 20:12:59 MDT 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC Also, couple of other weird things which I'm reading man pages for; probably just changes I need to learn of. --patrick
Re: two problems with the recent X @ i386
On 22 August 2011 17:19, Jan Stary wrote: > With today's snapshot, I can no longer kill X with crtl+alt+backspace. > Has something changed? Is DontZap turned on by default now? I am not > using any config file. I'm completely talking out of my arse here, but I have a strong hunch that this change is Ubuntu's (bad) influence at work: Ubuntu (--> Debian) --> X.org --> Xenocara
Re: two problems with the recent X @ i386
> On 2011-08-22 17.19, Jan Stary wrote: >> With today's snapshot, I can no longer kill X with crtl+alt+backspace. >> Has something changed? Is DontZap turned on by default now? I am not >> using any config file. > > Ah, I've experienced the same thing but in an amd64 environment. > > In my case it started a couple of months ago though, so it may not be > a brand new phenomenon. Can't pinpoint when so I have no idea what > commit to the tree changed the behaviour. I've forgotten to ask about > it since I use Ctrl-Alt-BS so seldom, but every time I do it annoys me. :-) > Same with me. It stopped working a few months ago on amd64. And matthieu@ fixed it a few days ago in current. thanks
Re: two problems with the recent X @ i386
On Mon 2011.08.22 at 17:19 +0200, Jan Stary wrote: > With today's snapshot, I can no longer kill X with crtl+alt+backspace. > Has something changed? Is DontZap turned on by default now? I am not > using any config file. I believe that's fixed in -current. > Also, the starting X says > > cwm: config file /home/hans/.cwmrc has errors, not loading > > but I don't have a ~/.cwmrc This is just a warning, but I've something to fix that. Cheers, Okan
Re: two problems with the recent X @ i386
On 2011-08-22 17.19, Jan Stary wrote:
> With today's snapshot, I can no longer kill X with crtl+alt+backspace.
> Has something changed? Is DontZap turned on by default now? I am not
> using any config file.
Ah, I've experienced the same thing but in an amd64 environment.
In my case it started a couple of months ago though, so it may not be
a brand new phenomenon. Can't pinpoint when so I have no idea what
commit to the tree changed the behaviour. I've forgotten to ask about
it since I use Ctrl-Alt-BS so seldom, but every time I do it annoys me. :-)
Regards,
/Benny
> Also, the starting X says
>
> cwm: config file /home/hans/.cwmrc has errors, not loading
>
> but I don't have a ~/.cwmrc
>
>
> Jan
>
>
>
> OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz ("GenuineIntel" 686-class)
> 2.67 GHz
> cpu0:
> FPU,V86,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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
> real mem = 2145837056 (2046MB)
> avail mem = 2100654080 (2003MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 11/16/07, BIOS32 rev. 0 @ 0xfb3f0,
> SMBIOS rev. 2.4 @ 0xf0100 (40 entries)
> bios0: vendor Award Software International, Inc. version "F10" date 11/16/2007
> bios0: Gigabyte Technology Co., Ltd. P35-DS3
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP HPET MCFG APIC SSDT SSDT
> acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5)
> HUB0(S5) UAR1(S1) USB0(S1) USB1(S1) USB2(S1) USB3(S1) US31(S1) USB4(S1)
> USB5(S1) USBE(S1) USE2(S1) AZAL(S5) PCI0(S5)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimcfg0 at acpi0 addr 0xf000, bus 0-63
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 333MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz ("GenuineIntel" 686-class)
> 2.67 GHz
> cpu1:
> FPU,V86,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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 2
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 2 (PEX0)
> acpiprt2 at acpi0: bus -1 (PEX1)
> acpiprt3 at acpi0: bus -1 (PEX2)
> acpiprt4 at acpi0: bus 3 (PEX3)
> acpiprt5 at acpi0: bus 4 (PEX4)
> acpiprt6 at acpi0: bus -1 (PEX5)
> acpiprt7 at acpi0: bus 5 (HUB0)
> acpicpu0 at acpi0: FVS, 2667, 2000 MHz
> acpicpu1 at acpi0: FVS, 2667, 2000 MHz
> acpibtn0 at acpi0: PWRB
> bios0: ROM list: 0xc/0xce00 0xd/0x1e00! 0xd2000/0x3000!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02
> ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x02: apic 2 int 16
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 8600 GT" rev 0xa1
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 2 int 16
> uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x02: apic 2 int 21
> uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x02: apic 2 int 18
> ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x02: apic 2 int 18
> 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 82801I HD Audio" rev 0x02: msi
> azalia0: codecs: Realtek ALC885
> audio0 at azalia0
> ppb1 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x02: apic 2 int 16
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x02: apic 2 int 19
> pci3 at ppb2 bus 3
> jmb0 at pci3 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev 0x02
> ahci0 at jmb0: apic 2 int 19, AHCI 1.0
> scsibus0 at ahci0: 32 targets
> jmb1 at pci3 dev 0 function 1 "JMicron JMB363 IDE/SATA" rev 0x02
> pciide0 at jmb1: DMA, channel 0 wired to native-PCI, channel 1 wired to
> native-PCI
> pciide0: using apic 2 int 16 for native-PCI interrupt
> atapiscsi0 at pciide0 channel 0 drive 0
> scsibus1 at atapiscsi0: 2 targets
> cd0 at scsibus1 targ 0 lun 0: ATAPI
> 5/cdrom removable
> cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
> pciide0: channel 1 disabled (no drives)
> ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x02: apic 2 int 16
> pci4 at ppb3 bus 4
> re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x01: RTL8168 2 (0x3800),
> apic 2 int 16, address 00:1d:7d:a9:a0:48
> rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2
> uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x02: apic
two problems with the recent X @ i386
With today's snapshot, I can no longer kill X with crtl+alt+backspace.
Has something changed? Is DontZap turned on by default now? I am not
using any config file.
Also, the starting X says
cwm: config file /home/hans/.cwmrc has errors, not loading
but I don't have a ~/.cwmrc
Jan
OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz ("GenuineIntel" 686-class)
2.67 GHz
cpu0:
FPU,V86,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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
real mem = 2145837056 (2046MB)
avail mem = 2100654080 (2003MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/16/07, BIOS32 rev. 0 @ 0xfb3f0, SMBIOS
rev. 2.4 @ 0xf0100 (40 entries)
bios0: vendor Award Software International, Inc. version "F10" date 11/16/2007
bios0: Gigabyte Technology Co., Ltd. P35-DS3
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP HPET MCFG APIC SSDT SSDT
acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5)
HUB0(S5) UAR1(S1) USB0(S1) USB1(S1) USB2(S1) USB3(S1) US31(S1) USB4(S1)
USB5(S1) USBE(S1) USE2(S1) AZAL(S5) PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 333MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz ("GenuineIntel" 686-class)
2.67 GHz
cpu1:
FPU,V86,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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PEX0)
acpiprt2 at acpi0: bus -1 (PEX1)
acpiprt3 at acpi0: bus -1 (PEX2)
acpiprt4 at acpi0: bus 3 (PEX3)
acpiprt5 at acpi0: bus 4 (PEX4)
acpiprt6 at acpi0: bus -1 (PEX5)
acpiprt7 at acpi0: bus 5 (HUB0)
acpicpu0 at acpi0: FVS, 2667, 2000 MHz
acpicpu1 at acpi0: FVS, 2667, 2000 MHz
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0xce00 0xd/0x1e00! 0xd2000/0x3000!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x02: apic 2 int 16
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 8600 GT" rev 0xa1
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 2 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x02: apic 2 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x02: apic 2 int 18
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x02: apic 2 int 18
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 82801I HD Audio" rev 0x02: msi
azalia0: codecs: Realtek ALC885
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x02: apic 2 int 16
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x02: apic 2 int 19
pci3 at ppb2 bus 3
jmb0 at pci3 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev 0x02
ahci0 at jmb0: apic 2 int 19, AHCI 1.0
scsibus0 at ahci0: 32 targets
jmb1 at pci3 dev 0 function 1 "JMicron JMB363 IDE/SATA" rev 0x02
pciide0 at jmb1: DMA, channel 0 wired to native-PCI, channel 1 wired to
native-PCI
pciide0: using apic 2 int 16 for native-PCI interrupt
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom
removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
pciide0: channel 1 disabled (no drives)
ppb3 at pci0 dev 28 function 4 "Intel 82801I PCIE" rev 0x02: apic 2 int 16
pci4 at ppb3 bus 4
re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x01: RTL8168 2 (0x3800), apic
2 int 16, address 00:1d:7d:a9:a0:48
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2
uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x02: apic 2 int 23
uhci4 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x02: apic 2 int 19
uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x02: apic 2 int 18
ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x02: apic 2 int 23
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x92
pci5 at ppb4 bus 5
ichpcib0 at pci0 dev 31 function 0 "Intel 82801IB LPC" rev 0x02: PM disabled
ahci1 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x02: msi, AHCI 1.2
scsibus2 at ahci1: 32 targets
sd0
Re: Two problems upgrading to 4.9
On 07/05/11 20:37, Mark Solocinski wrote: On Mon, 04 Jul 2011 10:26:56 +0200, Federico Giannici wrote: I have just upgraded my amd64 desktop pc from 4.8 to 4.9. I encountered two problems: 1) I have "mouse.resolution=90" in "/etc/wsconsctl.conf". Since the upgrade it doesn't seem to work anymore. It's still there but seems to be ignored. If I set it manually by command line it works. 2) All the "sftp://"; URLs in KDE no longer work. When I try to open such an URL, for example by Konqueror or by Kate, I always get the error "Error encountered while talking to ssh". Are those know problems, or some kind of problem with my installation? Thanks. Did you sysmerge after you updated? http://openbsd.org/faq/upgrade49.html#final I followed "Merging locally changed files via a patch file" and encountered no errors: http://openbsd.org/faq/upgrade49.html#patchfile Thanks.
Re: Two problems upgrading to 4.9
On Mon, 04 Jul 2011 10:26:56 +0200, Federico Giannici wrote: I have just upgraded my amd64 desktop pc from 4.8 to 4.9. I encountered two problems: 1) I have "mouse.resolution=90" in "/etc/wsconsctl.conf". Since the upgrade it doesn't seem to work anymore. It's still there but seems to be ignored. If I set it manually by command line it works. 2) All the "sftp://"; URLs in KDE no longer work. When I try to open such an URL, for example by Konqueror or by Kate, I always get the error "Error encountered while talking to ssh". Are those know problems, or some kind of problem with my installation? Thanks. Did you sysmerge after you updated? http://openbsd.org/faq/upgrade49.html#final
Two problems upgrading to 4.9
I have just upgraded my amd64 desktop pc from 4.8 to 4.9. I encountered two problems: 1) I have "mouse.resolution=90" in "/etc/wsconsctl.conf". Since the upgrade it doesn't seem to work anymore. It's still there but seems to be ignored. If I set it manually by command line it works. 2) All the "sftp://"; URLs in KDE no longer work. When I try to open such an URL, for example by Konqueror or by Kate, I always get the error "Error encountered while talking to ssh". Are those know problems, or some kind of problem with my installation? Thanks.
