[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#746562: marked as done (xserver-xephyr: large screen size causes immediate exit)

Your message dated Thu, 2 Jul 2015 20:56:06 +0200
with message-id <20150702185606.GC1289@betterave.cristau.org>
and subject line Re: Bug#746562: xserver-xephyr: large screen size causes immediate exit
has caused the Debian Bug report #746562,
regarding xserver-xephyr: large screen size causes immediate exit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
746562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746562
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xserver-xephyr
Version: 2:1.15.1-1
Severity: important

”Xephyr :9 -screen 4096x4096” shortly displays a black screen and exits
silently after that.

Smaller screen sizes are no problem, e.g. “Xephyr :9 -screen 4096x1024”
works as expected.

2:1.15.99.902-1 from experimental has the same problem.

This is a regression: 2:1.14.5-1 works fine, and so did all the
previous versions I used to use over the years.

(In case you’re wondering: Xephyr is useful for taking huge screenshots
from things like Google Street View. ☺)

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Version: 2:1.16.4-1

On Thu, Jul  2, 2015 at 21:47:28 +0300, Heikki Piirainen wrote:

> On Thu, Jul 02, 2015 at 08:26:27PM +0200, Julien Cristau wrote:
> > I'm pretty sure I could reproduce this a while back, but it seems to
> > work when I try it now, with 2:1.16.4-1.  Is this still an issue for
> > you?
> 
> The problem appears to have gone. I believe this bug may be closed now.
> Thank you!
> 
Thanks for the confirmation, closing with this message.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: