Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #2427 > unrolled thread

neat way to crash X

Back to article view | Back to comp.lang.postscript

Contents

  neat way to crash X Peter Billam <peter@www.pjb.com.au> - 2016-01-24 08:31 +0000
    Re: neat way to crash X Chris Liddell <news@shadesoft.net> - 2016-01-26 12:16 +0000
      Re: neat way to crash X Peter Billam <peter@www.pjb.com.au> - 2016-01-28 08:02 +0000
        Re: neat way to crash X Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-06 19:17 -0700

#2427 — neat way to crash X

Greetings.  Wanting to go full-screen on my debian stable
 ~> xwininfo -root | grep geometry
    -geometry 1920x1080+0+0
running Xorg 1:7.7+7 and gs 9.06, I typed, instead of the intended -g,
 ~> gs -r1920x1080

Pow! Instant blackness, and the monitor switched instantly into
power-saving mode...  With enough Ctrl-Alt-Fkey and Alt-Fkey attempts
I was able to get back to a console-login and log in again and startx,
no harm done.

/var/log/messages was full of lines like:
Jan 24 15:31:19 box8 kernel: [17862.077403] [1398] 500 1398 1816    1  7  539 0 bash
Jan 24 15:31:19 box8 kernel: [17862.077406] [1400] 500 1400 1816   64  7  476 0 bash
Jan 24 15:31:19 box8 kernel: [17862.077411] [2649]   0 2649 2008    9  7   85 0 lpd
Jan 24 15:31:19 box8 kernel: [17862.077414] [2694] 500 2694 3842  347 10 1288 0 slrn
Jan 24 15:31:19 box8 kernel: [17862.077418] [2695] 500 2695 2677   59  8  778 0 vim
Jan 24 15:31:19 box8 kernel: [17862.077422] [2739] 500 2739 565    13  4    0 0 sh
Jan 24 15:31:19 box8 kernel: [17862.077426] [2740] 500 2740 2244  448  8    0 0 vim
Jan 24 15:31:19 box8 kernel: [17862.077429] [2767] 500 2767 6371 1313 16    0 0 gs

and so on.  Apart from avoiding -r on X, what should be done next ?

Regards,  Peter

-- 

Peter Billam    www.pjb.com.au    www.pjb.com.au/comp/contact.html

[toc] | [next] | [standalone]

#2428

On Sun, 24 Jan 2016 08:31:05 +0000, Peter Billam wrote:

<SNIP>
> and so on.  Apart from avoiding -r on X, what should be done next ?

Upgrade? The current release is 9.18, and there have been some changes to 
the x11 device(s) which I suspect may have an effect here. The problem 
certainly doesn't occur for me (using 9.16 on this machine).

If it still happens with up to date code, report it:
http://bugs.ghostscript.com/

Giving *full* details (platform, distro, etc) of how to reproduce.

Chris

[toc] | [prev] | [next] | [standalone]

#2429

On 2016-01-26, Chris Liddell <news@shadesoft.net> wrote:
> On Sun, 24 Jan 2016 08:31:05 +0000, Peter Billam wrote:
>> Greetings.  Wanting to go full-screen on my debian stable
>>  ~> gs -r1920x1080
>> Pow! ... Apart from avoiding -r on X, what should be done next ?
>
> Upgrade? The current release is 9.18, and there have been some changes
> to the x11 device(s) which I suspect may have an effect here. The
> problem certainly doesn't occur for me (using 9.16 on this machine).

Yup, 9.18 fixes it :-)

I wasn't sure whether gs or Xorg or should assume responsibility;
probably this was discussed at the time...

Thanks,  Regards,  Peter

-- 

Peter Billam    www.pjb.com.au    www.pjb.com.au/comp/contact.html

[toc] | [prev] | [next] | [standalone]

#2634

On Thursday, January 28, 2016 at 9:02:44 PM UTC+13, Peter Billam wrote:

> I wasn't sure whether gs or Xorg or should assume responsibility;

I would assume it shouldn’t be possible for an ordinary app to crash X.

For the record, the command “gs -r1920x1080” works fine for me, too.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.postscript

csiph-web