* Re: XWin won't run xterm on start
@ 2016-02-21 18:24 Jaakov Jaakov
2016-02-21 18:41 ` Marco Atzeri
0 siblings, 1 reply; 5+ messages in thread
From: Jaakov Jaakov @ 2016-02-21 18:24 UTC (permalink / raw)
To: Cygwin; +Cc: marco.atzeri
Dear Marco:
So, are you saying that not starting xterm is by design?
> http://x.cygwin.com/docs/man1/startxwin.1.html
The manpage above is a bit outdated; creating a .startxwinrc with
xrdb -load $HOME/.Xresources
xbiff -geometry -430+5 &
oclock -geometry 75x75-0-0 &
xload -geometry -80-0 &
xterm -geometry +0+60 -ls &
xterm -geometry +0-100 &
xconsole -geometry -0+0 -fn 5x7 &
exec fbpanel -profile multiwindow
and running startxwin from the text console results in
---
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.18.1.0
OS: CYGWIN_NT-6.3 dell_vostro 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64
OS: Windows 8.1 [Windows NT 6.3 build 9600] (Win64)
Package: version 1.18.1-1 built 2016-02-18
XWin was started with the following command line:
/usr/bin/XWin :0 -multiwindow -auth /home/admin/.serverauth.2104
(II) xorg.conf is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
LoadPreferences: /home/admin/.XWinrc not found
LoadPreferences: Loading /etc/X11/system.XWinrc
LoadPreferences: Done parsing the configuration file...
winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
winDetectSupportedEngines - Returning, supported engines 00000005
winSetEngine - Multi Window or Rootless => ShadowGDI
winScreenInit - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 3520 height: 1080 depth: 32
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
(II) AIGLX: Testing pixelFormatIndex 1
GL_VERSION: 3.1.0 - Build 9.17.10.4229
GL_VENDOR: Intel
GL_RENDERER: Intel(R) HD Graphics 3000
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_SGIX_pbuffer
(II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample
(II) 60 pixel formats reported by wglGetPixelFormatAttribivARB
(II) AIGLX: Set GLX version to 1.4
(II) 15 fbConfigs
(II) ignored pixel formats: 0 not OpenGL, 6 RBGA float, 3 RGBA unsigned float, 0 unknown pixel type, 36 unaccelerated
(II) GLX: Initialized Win32 native WGL GL provider for screen 0
winPointerWarpCursor - Discarding first warp: 1760 540
(--) 3 mouse buttons found
(--) Setting autorepeat to delay=500, rate=31
(--) Windows keyboard layout: "00000407" (00000407) "German", type 4
(--) Found matching XKB configuration "German (Germany)"
(--) Model = "pc105" Layout = "de" Variant = "none" Options = "none"
Rules = "base" Model = "pc105" Layout = "de" Variant = "none" Options = "none"
winInitMultiWindowWM - DISPLAY=:0.0
winMultiWindowXMsgProc - DISPLAY=:0.0
winMultiWindowXMsgProc - xcb_connect() returned and successfully opened the display.
winProcEstablishConnection - winInitClipboard returned.
winClipboardThreadProc - DISPLAY=:0.0
OS maintains clipboard viewer chain: yes
winInitMultiWindowWM - xcb_connect () returned and successfully opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
xrdb: No such file or directory
xrdb: can't open file '/home/admin/.Xresources'
/home/admin/.startxwinrc: Zeile 2: xbiff: Kommando nicht gefunden.
/home/admin/.startxwinrc: Zeile 3: oclock: Kommando nicht gefunden.
/home/admin/.startxwinrc: Zeile 4: xload: Kommando nicht gefunden.
/home/admin/.startxwinrc: Zeile 7: xconsole: Kommando nicht gefunden.
fbpanel: unknown option - -profile
fbpanel 6.1 - lightweight GTK2+ panel for UNIX desktops
Command line options:
--help -- print this help and exit
--version -- print version and exit
--log <number> -- set log level 0-5. 0 - none 5 - chatty
--configure -- launch configuration utility
--profile name -- use specified profile
-h -- same as --help
-p -- same as --profile
-v -- same as --version
-C -- same as --configure
Visit http://fbpanel.sourceforge.net/ for detailed documentation,
xinit: connection to X server lost
waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
winClipboardProc - XDestroyWindow succeeded.
winMultiWindowXMsgProc - Fatal error 1 on xcb connection
winDeinitMultiWindowWM - Noting shutdown in progress
(II) Server terminated successfully (0). Closing log file.
---
Adding one more hyphen in front of -profile leads to two xterm windows. However, there are lots of other errors on the console. Said that, what would be an appropriate .startxwinrc or /etc/X11/xinit/startxwinrc for getting one (not two) xterm? Better, one uxterm?
Best,
Jaakov.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: XWin won't run xterm on start
2016-02-21 18:24 XWin won't run xterm on start Jaakov Jaakov
@ 2016-02-21 18:41 ` Marco Atzeri
2016-02-21 19:16 ` Jaakov Jaakov
0 siblings, 1 reply; 5+ messages in thread
From: Marco Atzeri @ 2016-02-21 18:41 UTC (permalink / raw)
To: Jaakov Jaakov, Cygwin
On 21/02/2016 19:24, Jaakov Jaakov wrote:
>
> Dear Marco:
>
> So, are you saying that not starting xterm is by design?
yes
>> http://x.cygwin.com/docs/man1/startxwin.1.html
>
> The manpage above is a bit outdated; creating a .startxwinrc with
>
> xrdb -load $HOME/.Xresources
> xbiff -geometry -430+5 &
> oclock -geometry 75x75-0-0 &
> xload -geometry -80-0 &
> xterm -geometry +0+60 -ls &
> xterm -geometry +0-100 &
> xconsole -geometry -0+0 -fn 5x7 &
> exec fbpanel -profile multiwindow
>
> and running startxwin from the text console results in
>
> ---
It is an example....
try just
xterm -geometry +0+60 -ls &
xterm -geometry +0-100 &
exec xclock
killing xclock will shutdown the X server.
You can use any other program for that.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Re: XWin won't run xterm on start
2016-02-21 18:41 ` Marco Atzeri
@ 2016-02-21 19:16 ` Jaakov Jaakov
2016-02-21 21:07 ` Eliot Moss
0 siblings, 1 reply; 5+ messages in thread
From: Jaakov Jaakov @ 2016-02-21 19:16 UTC (permalink / raw)
To: Marco Atzeri; +Cc: Cygwin
> > Dear Marco:
> >
> > So, are you saying that not starting xterm is by design?
>
> yes
>
Well, then, apparently, the design changed several months ago.
> >> http://x.cygwin.com/docs/man1/startxwin.1.html
> >
> > The manpage above is a bit outdated; creating a .startxwinrc with
> >
> > xrdb -load $HOME/.Xresources
> > xbiff -geometry -430+5 &
> > oclock -geometry 75x75-0-0 &
> > xload -geometry -80-0 &
> > xterm -geometry +0+60 -ls &
> > xterm -geometry +0-100 &
> > xconsole -geometry -0+0 -fn 5x7 &
> > exec fbpanel -profile multiwindow
> >
> > and running startxwin from the text console results in
> >
> > ---
>
> It is an example....
>
> try just
>
> xterm -geometry +0+60 -ls &
> xterm -geometry +0-100 &
> exec xclock
>
> killing xclock will shutdown the X server.
> You can use any other program for that.
>
>
Thank you, I see. I cannot use xclock - we have one clock in Windows(TM) already, but I'll choose something.
Is there any way to do whatever the current version of
/etc/X11/xinit/startxwinrc
does (xwin-xdg-menu, gnome-keyring-daemon, and lots of other goodies which I sometimes need) and, in addition (as opposed to "instead"), run uxterm?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: XWin won't run xterm on start
2016-02-21 19:16 ` Jaakov Jaakov
@ 2016-02-21 21:07 ` Eliot Moss
0 siblings, 0 replies; 5+ messages in thread
From: Eliot Moss @ 2016-02-21 21:07 UTC (permalink / raw)
To: cygwin
Why not do:
xterm ... &
/etc/X11/xinit/startxwinrc
?
Regards -- Eliot Moss
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Re: XWin won't run xterm on start
@ 2016-02-21 21:28 Jaakov Jaakov
0 siblings, 0 replies; 5+ messages in thread
From: Jaakov Jaakov @ 2016-02-21 21:28 UTC (permalink / raw)
To: Cygwin; +Cc: moss
> Why not do:
> xterm ... &
> /etc/X11/xinit/startxwinrc
> ?
Where do you suggest to do it?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-02-21 21:28 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-21 18:24 XWin won't run xterm on start Jaakov Jaakov
2016-02-21 18:41 ` Marco Atzeri
2016-02-21 19:16 ` Jaakov Jaakov
2016-02-21 21:07 ` Eliot Moss
2016-02-21 21:28 Jaakov Jaakov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).