Hi all, did someone saw similar problem in scrotwm(1)? Eg. when I start xeyes(1) on empty workspace from menu M-p it simply "shut down" X. If I start eg. xcalc(1) then everything is ok. Another problem is with xlock(1). When I want to lock my screen and start xlock(1) eg. this way 'xlock -mode atlantis' then my computer completely hangs and I must to turn it off with button on case. Last problem which I discovered is with warzone game. When I start it on empty workspace then it says that timing of monitor is not ok for this app and X is not working anymore and I must kill X from console. So someone here with similar behaviour? OpenBSD 4.8 (GENERIC.MP) #356: Mon Aug 9 00:28:02 MDT 2010 email@example.com:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 11<memory_size> cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz ("GenuineIntel" 686-class) 2.93 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3 ,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem = 3487125504 (3325MB) avail mem = 3420106752 (3261MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 02/13/10, BIOS32 rev. 0 @ 0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (82 entries) bios0: vendor Dell Inc. version "A03" date 02/13/2010 bios0: Dell Inc. OptiPlex 780 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET DMAR SLIC SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz ("GenuineIntel" 686-class) 2.93 ...
Wish I hadn't tried it :) Yes, it happens here too. Yep! Daniel -- LIVAI Daniel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
I'm sorry, here's my dmesg (and I'm using scrotwm-0.9.25 from packages): OpenBSD 4.8 (GENERIC.MP) #358: Wed Aug 11 10:18:19 MDT 2010 firstname.lastname@example.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Genuine Intel(R) CPU T2400 @ 1.83GHz ("GenuineIntel" 686-class) 1.83 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM real mem = 2145808384 (2046MB) avail mem = 2100715520 (2003MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/27/09, BIOS32 rev. 0 @ 0xfd6b0, SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version "79ETE5WW (2.25 )" date 08/27/2009 bios0: LENOVO 2007FRG acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Genuine Intel(R) CPU T2400 @ 1.83GHz ("GenuineIntel" 686-class) 1.83 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical ...
not sure if it is the same bug but i have seen ephemeral windows e.g. the little "Sending mail..." windows from seamonkey's mail client cause scrotwm to crash. there is a patch to stop the crashing behavior in the current cvs version. checkout cvs and see if your problem persists: cvs -d email@example.com:/scrotwm co scrotwm cd scrotwm make obj && make depend && make && sudo make -DDEBUG install - issue M-q to soft restart scrotwm using the freshly installed binary - issue M-S-v to verify you are running the cvs version, should be 1.300 when i had scrotwm crashing, it would drop .core files and you can do a decent backtrace with gdb when you have the symbols in there. run 'gdb /usr/local/bin/scrotwm scrotwm.core' and issue 'bt full'. this output is helpful for finding the bug(s) you're hitting.
scrotwm works OK for me with latest snapshot on Lenovo T400 (i386). But it is incredebily slow comparable with same setup on Ubuntu :( jirib
On Tue, 17 Aug 2010 06:40:21 -0500 I have to first eliminate potential involvement of i/o slowdown because Anyway, this always makes my scrotwm to be f*cked up: `mplayer -fs -vo sdl video' jirib
Why are you using sdl for video playing in the first place? Almost always the default XVideo one is the one you want. -0- -- To the systems programmer, users and applications serve only to provide a test load.
dmesg is in my first post, but here is error output from startx from start to crash after startup of xeyes (there is not core file) : xauth: creating new authority file /home/user/.serverauth.5483 X.Org X Server 1.8.2 Release Date: 2010-07-01 X Protocol Version 11, Revision 0 Build Operating System: OpenBSD 4.8 i386 Current Operating System: OpenBSD hostname 4.8 GENERIC.MP#359 i386 Build Date: 08 August 2010 11:09:28PM Current version of pixman: 0.16.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 18 07:12:17 2010 (==) Using default built-in configuration (21 lines) XRANDR name: DisplayPort-1 Connector: DisplayPort DFP1: INTERNAL_UNIPHY DDC reg: 0x7e60 XRANDR name: DisplayPort-0 Connector: DisplayPort DFP2: INTERNAL_UNIPHY DDC reg: 0x7e20 finished output detect: 0 finished output detect: 1 finished all detect before xf86InitialConfiguration after xf86InitialConfiguration Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success mc fb loc is 00df00d0 Output DIG0 transmitter setup success Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success Output DIG0 transmitter setup success Mode 1680x1050 - 1840 1080 9 freq: 119000000 best_freq: 119000000 best_feedback_div: 119 best_ref_div: 3 best_post_div: 9 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable ...
I bet that is the controlled shut down where applications create windows and then destroy them before scrotwm can focus on them. I fixed this in cvs and would appreciate a test report. CVS instructions are on the www scrotwm page and it conveniently installs over the pkg.
I checked out sources from cvs and then make ; sudo make install, but it's still same version as in packages/ports (0.9.25). Same version
no it isn't. the external version isn't the same as the cvs version. obviously we don't change the external version after every commit. use m-s-v for the real version.
Welcome to scrotwm V0.9.25 cvs tag: $scrotwm: scrotwm.c,v 1.300 2010/08/11 03:15:40 marco Exp $
For the record, it would be nice to test with a different window manager. Bugs in scrotwm do not count as bugs in OpenBSD.
M-?xeyes<enter> in cwm (on current, amd64) runs fine. So i bet a scrotwm bug. Then again the mail contains at least 3 bugs being mentioned, this only treats the first. As for the third (warzone) the monitor timing is probably a warzone or X bug, the rest of the failure could be the WM or the application just not quitting and keeping the keyboard grabbed (that would be an application bug). That can be tested using ssh and kill -9. As a note, scotwm really needs it own mailing list, scrotwm bugs are not really topical for misc. -0- -- She missed an invaluable opportunity to give him a look that you could have poured on a waffle.
On 08/18/10 14:02, Owain Ainsworth wrote: and a graphic! don't forget a graphi...er..hmmm.... Maybe that wouldn't be such a good idea. Nick.
aaaand I now have coffee all over my laptop. many thanks for that.
Why? What's wrong with a graphic for scot-wm? I imagine something with a kilt, and a bagpipe, and some sheep. And a tartan background for the screen, perhaps...