Debian Bug report logs - #681781
dummy: Please include sample xorg.conf

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: dummy: Please include sample xorg.conf

Date: Mon, 16 Jul 2012 15:24:26 +0200

[Message part 1 (text/plain, inline)]

Package: xserver-xorg-video-dummy
Version: 1:0.3.5-2+b1
Severity: wishlist
File: dummy

Hello,

It would be quite helpful to include a sample xorg.conf, preferebly
installed at /etc/X11/xorg.conf.dummy or similar.

Without a configuration file using the dummy driver is quite difficult.

one such configuration file can be found at
https://www.xpra.org/xorg.conf

Thanks

Michal

[xorg.conf.dummy (text/plain, attachment)]

Message #10 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>, 681781@bugs.debian.org

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Sun, 30 Dec 2012 01:53:55 +0100

Mmm, I believe the following would be enough:

Section "Device"
    Identifier "noscreendevice"
    Driver     "dummy"
EndSection

Samuel

Message #15 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Samuel Thibault <sthibault@debian.org>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Wed, 02 Jan 2013 11:27:04 +0100

Excerpts from Samuel Thibault's message of Sun Dec 30 01:53:55 +0100 2012:
> Mmm, I believe the following would be enough:
> 
> Section "Device"
>     Identifier "noscreendevice"
>     Driver     "dummy"
> EndSection
> 
> Samuel

It is exactly because this is NOT sufficient that the sample
configuration is needed.

The X server configures input drivers automagically. The above
configuration sample avoids that.

The default mode list is very insufficient. That is why the additional
modes are added in the configuration.

Thanks

Michal

Message #20 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>, 681781@bugs.debian.org

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Sat, 5 Jan 2013 19:21:25 +0100

[Message part 1 (text/plain, inline)]

Michal Suchanek, le Wed 02 Jan 2013 11:27:04 +0100, a écrit :
> Excerpts from Samuel Thibault's message of Sun Dec 30 01:53:55 +0100 2012:
> > Section "Device"
> >     Identifier "Configured Video Device"
> >     Driver     "dummy"
> > EndSection
> 
> It is exactly because this is NOT sufficient that the sample
> configuration is needed.

I've just tried it, see attached log.

> The X server configures input drivers automagically. The above
> configuration sample avoids that.

The attached log shows it doesn't.

> The default mode list is very insufficient. That is why the additional
> modes are added in the configuration.

Ah, if you want more than 1024x768, yes, of course.  Otherwise my
experience shows 1024x768 does get configured.

Samuel

[Xorg.1.log (text/plain, attachment)]

Message #25 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Samuel Thibault <sthibault@debian.org>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 07 Jan 2013 13:33:11 +0100

Excerpts from Samuel Thibault's message of Sat Jan 05 19:21:25 +0100 2013:
> Michal Suchanek, le Wed 02 Jan 2013 11:27:04 +0100, a écrit :
> > Excerpts from Samuel Thibault's message of Sun Dec 30 01:53:55 +0100 2012:
> > > Section "Device"
> > >     Identifier "Configured Video Device"
> > >     Driver     "dummy"
> > > EndSection
> > 
> > It is exactly because this is NOT sufficient that the sample
> > configuration is needed.
> 
> I've just tried it, see attached log.
> 
> > The X server configures input drivers automagically. The above
> > configuration sample avoids that.
> 
> The attached log shows it doesn't.
> 
> > The default mode list is very insufficient. That is why the additional
> > modes are added in the configuration.
> 
> Ah, if you want more than 1024x768, yes, of course.  Otherwise my
> experience shows 1024x768 does get configured.
> 
> Samuel

> [ 67138.290] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event19)
> [ 67138.290] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
> [ 67138.290] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
> [ 67138.290] (**) Logitech USB Keyboard: always reports core events
> [ 67138.290] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event19"
> [ 67138.290] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d
> [ 67138.290] (--) evdev: Logitech USB Keyboard: Found keys
> [ 67138.290] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
> [ 67138.290] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3:1.0/input/input19/event19"
> [ 67138.290] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 11)
> [ 67138.290] (**) Option "xkb_rules" "evdev"
> [ 67138.290] (**) Option "xkb_model" "geniuskb19e"
> [ 67138.290] (**) Option "xkb_layout" "fr,brai"
> [ 67138.290] (**) Option "xkb_variant" "oss,"
> [ 67138.290] (**) Option "xkb_options" "compose:lwin,compose:rwin,nbsp:level3n,grp:shift_caps_toggle,grp_led:scroll,terminate:ctrl_alt_bksp,kpdl:kposs"
> [ 67138.291] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event20)
> [ 67138.291] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
> [ 67138.291] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
> [ 67138.291] (**) Logitech USB Keyboard: always reports core events
> [ 67138.292] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event20"
> [ 67138.292] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d
> [ 67138.292] (--) evdev: Logitech USB Keyboard: Found absolute axes
> [ 67138.292] (II) evdev: Logitech USB Keyboard: Forcing absolute x/y axes to exist.
> [ 67138.292] (--) evdev: Logitech USB Keyboard: Found keys
> [ 67138.292] (II) evdev: Logitech USB Keyboard: Configuring as mouse
> [ 67138.292] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
> [ 67138.292] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3:1.1/input/input20/event20"
> [ 67138.292] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 12)
> [ 67138.292] (**) Option "xkb_rules" "evdev"
> [ 67138.292] (**) Option "xkb_model" "geniuskb19e"
> [ 67138.292] (**) Option "xkb_layout" "fr,brai"
> [ 67138.292] (**) Option "xkb_variant" "oss,"
> [ 67138.292] (**) Option "xkb_options" "compose:lwin,compose:rwin,nbsp:level3n,grp:shift_caps_toggle,grp_led:scroll,terminate:ctrl_alt_bksp,kpdl:kposs"
> [ 67138.292] (II) evdev: Logitech USB Keyboard: initialized for absolute axes.
> [ 67138.292] (**) Logitech USB Keyboard: (accel) keeping acceleration scheme 1
> [ 67138.292] (**) Logitech USB Keyboard: (accel) acceleration profile 0
> [ 67138.292] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000
> [ 67138.292] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4
> [ 67138.292] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event21)
> [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
> [ 67138.292] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
> [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
> [ 67138.292] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event21"
> [ 67138.292] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc050
> [ 67138.292] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
> [ 67138.292] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
> [ 67138.292] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
> [ 67138.292] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
> [ 67138.292] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
> [ 67138.292] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
> [ 67138.292] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
> [ 67138.292] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> [ 67138.292] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.4/2-1.1.4:1.0/input/input21/event21"
> [ 67138.292] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 13)
> [ 67138.292] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
> [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
> [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
> [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
> [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
> [ 67138.293] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse2)
> [ 67138.293] (II) No input driver specified, ignoring this device.
> [ 67138.293] (II) This device may have been added with another device file.
> [ 67138.293] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
> [ 67138.293] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
> [ 67138.293] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
> [ 67138.293] (**) AT Translated Set 2 keyboard: always reports core events
> [ 67138.293] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
> [ 67138.293] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
> [ 67138.293] (--) evdev: AT Translated Set 2 keyboard: Found keys
> [ 67138.293] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
> [ 67138.293] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
> [ 67138.293] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
> [ 67138.293] (**) Option "xkb_rules" "evdev"
> [ 67138.293] (**) Option "xkb_model" "geniuskb19e"
> [ 67138.293] (**) Option "xkb_layout" "fr,brai"
> [ 67138.293] (**) Option "xkb_variant" "oss,"
> [ 67138.293] (**) Option "xkb_options" "compose:lwin,compose:rwin,nbsp:level3n,grp:shift_caps_toggle,grp_led:scroll,terminate:ctrl_alt_bksp,kpdl:kposs"

How are these devices not configured?

It may not lock out the terminal from receiving keyboard input but it
still configures input drivers and receives input from them.

Thanks

Michal

Message #30 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 7 Jan 2013 13:40:50 +0100

Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> How are these devices not configured?

Err, aren't you taking this thread for another one?  See the subject,
this is about providing a sample xorg.conf.  I'm here saying there
is no need for input sections, since they are already automatically
configured.

> It may not lock out the terminal from receiving keyboard input but it
> still configures input drivers and receives input from them.

Sure, that's what I'm saying.  This is independant from the other issue,
which is the VT not being allocated for input to actually happen.

Samuel

Message #35 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Samuel Thibault <sthibault@debian.org>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 07 Jan 2013 14:01:35 +0100

Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > How are these devices not configured?
> 
> Err, aren't you taking this thread for another one?  See the subject,
> this is about providing a sample xorg.conf.  I'm here saying there
> is no need for input sections, since they are already automatically
> configured.

And I am saying that there *is* need for input sections to prevent them
from being automatically configured.

Thanks

Michal

Message #40 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 7 Jan 2013 14:24:24 +0100

Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit :
> Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > > How are these devices not configured?
> > 
> > Err, aren't you taking this thread for another one?  See the subject,
> > this is about providing a sample xorg.conf.  I'm here saying there
> > is no need for input sections, since they are already automatically
> > configured.
> 
> And I am saying that there *is* need for input sections to prevent them
> from being automatically configured.

Ooops, sorry, I hadn't understood that input devices were not desired in
this bug report.

I'm however wondering how this use case differs from simply using Xvfb.

Samuel

Message #45 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Samuel Thibault <sthibault@debian.org>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 07 Jan 2013 14:38:13 +0100

Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013:
> Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit :
> > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > > > How are these devices not configured?
> > > 
> > > Err, aren't you taking this thread for another one?  See the subject,
> > > this is about providing a sample xorg.conf.  I'm here saying there
> > > is no need for input sections, since they are already automatically
> > > configured.
> > 
> > And I am saying that there *is* need for input sections to prevent them
> > from being automatically configured.
> 
> Ooops, sorry, I hadn't understood that input devices were not desired in
> this bug report.
> 
> I'm however wondering how this use case differs from simply using Xvfb.

Xvfb is deprecated, bitrotten, does not support xrandr and other
extensions, ..

Thanks

Michal

Message #50 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 7 Jan 2013 15:01:28 +0100

Michal Suchanek, le Mon 07 Jan 2013 14:38:13 +0100, a écrit :
> Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013:
> > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit :
> > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > > > > How are these devices not configured?
> > > > 
> > > > Err, aren't you taking this thread for another one?  See the subject,
> > > > this is about providing a sample xorg.conf.  I'm here saying there
> > > > is no need for input sections, since they are already automatically
> > > > configured.
> > > 
> > > And I am saying that there *is* need for input sections to prevent them
> > > from being automatically configured.
> > 
> > Ooops, sorry, I hadn't understood that input devices were not desired in
> > this bug report.
> > 
> > I'm however wondering how this use case differs from simply using Xvfb.
> 
> Xvfb is deprecated, bitrotten, does not support xrandr and other
> extensions, ..

Could it perhaps be replaced by a mere shell script which invokes Xorg,
giving it the sample xorg.conf you provided?  That'd be a way easier
upgrade path for users than knowing about the dummy driver etc.

Samuel

Message #55 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Samuel Thibault <sthibault@debian.org>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 07 Jan 2013 15:13:27 +0100

Excerpts from Samuel Thibault's message of Mon Jan 07 15:01:28 +0100 2013:
> Michal Suchanek, le Mon 07 Jan 2013 14:38:13 +0100, a écrit :
> > Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013:
> > > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit :
> > > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> > > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > > > > > How are these devices not configured?
> > > > > 
> > > > > Err, aren't you taking this thread for another one?  See the subject,
> > > > > this is about providing a sample xorg.conf.  I'm here saying there
> > > > > is no need for input sections, since they are already automatically
> > > > > configured.
> > > > 
> > > > And I am saying that there *is* need for input sections to prevent them
> > > > from being automatically configured.
> > > 
> > > Ooops, sorry, I hadn't understood that input devices were not desired in
> > > this bug report.
> > > 
> > > I'm however wondering how this use case differs from simply using Xvfb.
> > 
> > Xvfb is deprecated, bitrotten, does not support xrandr and other
> > extensions, ..
> 
> Could it perhaps be replaced by a mere shell script which invokes Xorg,
> giving it the sample xorg.conf you provided?  That'd be a way easier
> upgrade path for users than knowing about the dummy driver etc.

For that the sample config has to live somewhere. It won't live in Xvfb
package because while it's deprecated upstream it's not a reason for
Debian to remove it. Or is it?

Thanks

Michal

Message #60 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 7 Jan 2013 15:21:44 +0100

Michal Suchanek, le Mon 07 Jan 2013 15:13:27 +0100, a écrit :
> Excerpts from Samuel Thibault's message of Mon Jan 07 15:01:28 +0100 2013:
> > Michal Suchanek, le Mon 07 Jan 2013 14:38:13 +0100, a écrit :
> > > Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013:
> > > > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit :
> > > > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> > > > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > > > > > > How are these devices not configured?
> > > > > > 
> > > > > > Err, aren't you taking this thread for another one?  See the subject,
> > > > > > this is about providing a sample xorg.conf.  I'm here saying there
> > > > > > is no need for input sections, since they are already automatically
> > > > > > configured.
> > > > > 
> > > > > And I am saying that there *is* need for input sections to prevent them
> > > > > from being automatically configured.
> > > > 
> > > > Ooops, sorry, I hadn't understood that input devices were not desired in
> > > > this bug report.
> > > > 
> > > > I'm however wondering how this use case differs from simply using Xvfb.
> > > 
> > > Xvfb is deprecated, bitrotten, does not support xrandr and other
> > > extensions, ..
> > 
> > Could it perhaps be replaced by a mere shell script which invokes Xorg,
> > giving it the sample xorg.conf you provided?  That'd be a way easier
> > upgrade path for users than knowing about the dummy driver etc.
> 
> For that the sample config has to live somewhere. It won't live in Xvfb
> package because while it's deprecated upstream it's not a reason for
> Debian to remove it. Or is it?

It can be a reason for removing it. Or better, replacing it with the
proposed script. That said, the xorg.conf would better be maintained
under the xorg umbrella, officially replacing Xvfb.

Samuel

Message #65 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Samuel Thibault <sthibault@debian.org>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 07 Jan 2013 15:35:38 +0100

Excerpts from Samuel Thibault's message of Mon Jan 07 15:21:44 +0100 2013:
> Michal Suchanek, le Mon 07 Jan 2013 15:13:27 +0100, a écrit :
> > Excerpts from Samuel Thibault's message of Mon Jan 07 15:01:28 +0100 2013:
> > > Michal Suchanek, le Mon 07 Jan 2013 14:38:13 +0100, a écrit :
> > > > Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013:
> > > > > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit :
> > > > > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013:
> > > > > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit :
> > > > > > > > How are these devices not configured?
> > > > > > > 
> > > > > > > Err, aren't you taking this thread for another one?  See the subject,
> > > > > > > this is about providing a sample xorg.conf.  I'm here saying there
> > > > > > > is no need for input sections, since they are already automatically
> > > > > > > configured.
> > > > > > 
> > > > > > And I am saying that there *is* need for input sections to prevent them
> > > > > > from being automatically configured.
> > > > > 
> > > > > Ooops, sorry, I hadn't understood that input devices were not desired in
> > > > > this bug report.
> > > > > 
> > > > > I'm however wondering how this use case differs from simply using Xvfb.
> > > > 
> > > > Xvfb is deprecated, bitrotten, does not support xrandr and other
> > > > extensions, ..
> > > 
> > > Could it perhaps be replaced by a mere shell script which invokes Xorg,
> > > giving it the sample xorg.conf you provided?  That'd be a way easier
> > > upgrade path for users than knowing about the dummy driver etc.
> > 
> > For that the sample config has to live somewhere. It won't live in Xvfb
> > package because while it's deprecated upstream it's not a reason for
> > Debian to remove it. Or is it?
> 
> It can be a reason for removing it. Or better, replacing it with the
> proposed script. That said, the xorg.conf would better be maintained
> under the xorg umbrella, officially replacing Xvfb.

For that the dummy driver would have to support all the features of
Xvfb. Some Xvfb options could be emulated with generating xorg.conf on
the fly perhaps but the shared memory option is not implemented in dummy
AFAIK and may be used by some automated tests.

Thanks

Michal

Message #70 received at 681781@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "681781@bugs.debian.org" <681781@bugs.debian.org>

Subject: Re: Bug#681781: dummy: Please include sample xorg.conf

Date: Mon, 7 Jan 2013 15:39:37 +0100

Michal Suchanek, le Mon 07 Jan 2013 15:35:38 +0100, a écrit :
> Some Xvfb options could be emulated with generating xorg.conf on
> the fly perhaps

That would surely be more user-friendly than having to deal with
modelines in xorg.conf :)

> but the shared memory option is not implemented in dummy
> AFAIK and may be used by some automated tests.

That however is a problem indeed. It could be made a /etc/alternative
for Xvfb.

Samuel

Send a report that this bug log contains spam.