Re: [Xcb] planning to remove xprint, x11proto-print-dev too?

2011-04-21 Thread Drew Parsons
The same question of removing the libxprint* (or libxp) packages applies
also to x11proto-print-dev.

Is there any reason to keep shipping x11proto-print-dev if we no longer
supply an Xprint server?

Drew




-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1303448126.26732.26.camel@pug



Bug#618900: xserver-xorg-video-mga: does not work with MGA G100 chip

2011-04-21 Thread Tormod Volden
I have gone through the logs. The detected max dotclock of the monitor
(from EDID) has changed from 90 to 95 MHz. The default mode has
changed from 1280x768@80.1Hz to 1360x768@84.8Hz.

Does it help to change resolution, for instance by blind-typing
"xrandr -s 800x600" ?

Can you please also provide the output from "xrandr --verbose" in both cases?
Either by blind-typing, or starting X like this:
 xinit -e 'sh -c "xrandr --verbose > xrandr.log" '

Also, with only 6MB of video RAM, you may want to reduce the color
depth. Try starting X with:
 xinit -- -depth 16
and you might get more available resolutions.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktikd287csqnnoj9b4gn6ka1rfe1...@mail.gmail.com



Processed: Fixing affects for 604680

2011-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 604680 gnome-terminal libvte9 evilvte libvte-2.90-9
Bug #604680 [xserver-xorg-video-intel] gnome-terminal: Corruption from text
Bug #616392 [xserver-xorg-video-intel] gnome-terminal: display corruption when 
rendering text
Added indication that 604680 affects libvte-2.90-9, libvte9, gnome-terminal, 
and evilvte
Added indication that 616392 affects libvte-2.90-9, libvte9, gnome-terminal, 
and evilvte
> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
604680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.130342368810529.transcr...@bugs.debian.org



Processed: Reassigning 604680 & friends

2011-04-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 604680 xserver-xorg-video-intel
Bug #604680 [libvte9] gnome-terminal: Corruption from text
Bug #616392 [libvte9] gnome-terminal: display corruption when rendering text
Bug reassigned from package 'libvte9' to 'xserver-xorg-video-intel'.
Bug reassigned from package 'libvte9' to 'xserver-xorg-video-intel'.
Bug No longer marked as found in versions vte/1:0.27.5-1 and vte/1:0.24.3-2.
Bug No longer marked as found in versions vte/1:0.27.5-1 and vte/1:0.24.3-2.
> affects 604680 gnome-terminal
Bug #604680 [xserver-xorg-video-intel] gnome-terminal: Corruption from text
Bug #616392 [xserver-xorg-video-intel] gnome-terminal: display corruption when 
rendering text
Removed indication that 604680 affects evilvte
Added indication that 604680 affects gnome-terminal
Removed indication that 616392 affects evilvte
Added indication that 616392 affects gnome-terminal
> affects 604680 libvte9
Bug #604680 [xserver-xorg-video-intel] gnome-terminal: Corruption from text
Bug #616392 [xserver-xorg-video-intel] gnome-terminal: display corruption when 
rendering text
Removed indication that 604680 affects gnome-terminal
Added indication that 604680 affects libvte9
Removed indication that 616392 affects gnome-terminal
Added indication that 616392 affects libvte9
> affects 604680 libvte-2.90-9
Bug #604680 [xserver-xorg-video-intel] gnome-terminal: Corruption from text
Bug #616392 [xserver-xorg-video-intel] gnome-terminal: display corruption when 
rendering text
Removed indication that 604680 affects libvte9
Added indication that 604680 affects libvte-2.90-9
Removed indication that 616392 affects libvte9
Added indication that 616392 affects libvte-2.90-9
> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
604680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13034232399453.transcr...@bugs.debian.org



[bts-link] source package xorg-server

2011-04-21 Thread bts-link-upstream
#
# bts-link upstream status pull for source package xorg-server
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #622864 (http://bugs.debian.org/622864)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=31501
#  * remote status changed: (?) -> NEW
usertags 622864 + status-NEW

# remote status report for #622864 (http://bugs.debian.org/622864)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=31501
#  * remote status changed: (?) -> NEW
usertags 622864 + status-NEW

thanks


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110421211828.2252.48289.btsl...@busoni.debian.org



Bug#618900: xserver-xorg-video-mga: does not work with MGA G100 chip

2011-04-21 Thread Martin
Did the supplied info helped to naroww down where the problem may be?
Any additional info needed?
I really need X to work!

Bye
Martin



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110421194538.GA1575@alfa



Re: [Xcb] planning to remove xprint, libxprintutil and related packages

2011-04-21 Thread Julien Danjou
On Thu, Apr 21 2011, Jamey Sharp wrote:

> - In libxcb master, I'd be happy to change configure.ac to default to
>   not building xprint. I'd personally continue building it because I
>   build all known extensions, just to check for build regressions, but
>   there's no reason everybody else needs to.
>
> - For Debian, while I can't argue with your point, Julien, that "I don't
>   see any good reason not to build it," I also don't see any good reason
>   *to* build it, and I have a lot of sympathy with wanting to "hide that
>   Xprint ever existed." :-)

If the decision to disable its building by default in XCB is taken, I
think we should follow XCB decision in the Debian packaging and disable
(or "not enable") its building.

But for the XCB-side decision, I really don't have enough hindsight to
have a decent opinion, so I'll leave that up to you. :)

-- 
Julien Danjou
❱ http://julien.danjou.info


pgphbXCqqG6gD.pgp
Description: PGP signature


Re: [Xcb] planning to remove xprint, libxprintutil and related packages

2011-04-21 Thread Jamey Sharp
On Thu, Apr 21, 2011 at 04:22:17PM +0200, Julien Danjou wrote:
> On Thu, Apr 21 2011, Drew Parsons wrote:
> > cc: xcb maintainers: should you keep libxcb-xprint0 ? Do we need to talk
> > about this? libxcb-xprint0 has no relation (in a packaging sense) to
> > xprint.
> 
> I see no harm providing it. It exists, so we can just let it be. Nothing
> depends on it I guess, and nothing should ever depends on it, but I
> don't see any good reason not to build it either.
> 
> If you really want to hide that Xprint ever existed, maybe that'd be a
> reason to stop building that package, otherwise, I don't see really any.
> :)

Speaking as both a Debian user and an XCB developer:

- I think we'll leave xprint.xml in xcb-proto forever, because it's
  protocol documentation that may be useful to somebody.

- In libxcb master, I'd be happy to change configure.ac to default to
  not building xprint. I'd personally continue building it because I
  build all known extensions, just to check for build regressions, but
  there's no reason everybody else needs to.

- For Debian, while I can't argue with your point, Julien, that "I don't
  see any good reason not to build it," I also don't see any good reason
  *to* build it, and I have a lot of sympathy with wanting to "hide that
  Xprint ever existed." :-)

Jamey


signature.asc
Description: Digital signature


Bug#623235: x11-utils: font utilities crash X

2011-04-21 Thread Heikki Kantola
According to Cyril Brulebois :
> Heikki Kantola  (18/04/2011):
> > I just noticed that both xfontsel and xlsfonts kill my X session
> > when invoked. I do happen to have fairly large amount of fonts
> > installed and X gets its fonts from xfs if that matters.
> 
> Hi,
> 
> I guess removing the line(s) mentioning 'unix' in your xorg.conf makes
> that issue go away?

Yes, now I have tried without font paths pointing to xfs and with this
kind of configuration these programs work fine. 

-- 
Heikki "Hezu" Kantola, 
Lähettämällä mainoksia tai muuta asiatonta sähköpostia yllä olevaan
osoitteeseen sitoudut maksamaan oikolukupalvelusta EUR100 alkavalta
tunnilta.



--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110421143346.ga27...@ruuvi.it.helsinki.fi



Re: [Xcb] planning to remove xprint, libxprintutil and related packages

2011-04-21 Thread Julien Danjou
On Thu, Apr 21 2011, Drew Parsons wrote:

> cc: xcb maintainers: should you keep libxcb-xprint0 ? Do we need to talk
> about this? libxcb-xprint0 has no relation (in a packaging sense) to
> xprint.

I see no harm providing it. It exists, so we can just let it be. Nothing
depends on it I guess, and nothing should ever depends on it, but I
don't see any good reason not to build it either.

If you really want to hide that Xprint ever existed, maybe that'd be a
reason to stop building that package, otherwise, I don't see really any.
:)

-- 
Julien Danjou
❱ http://julien.danjou.info


pgpeKdoxeXb6y.pgp
Description: PGP signature


Bug#425662: Reopened #425662

2011-04-21 Thread Alberto Gallardo
>
> The way I'm using Xephyr is as follows (this has been the only way to get my
> german keyboard configured properly):
>
>    1. Open Xephyr:
>    Xephyr -keybd ephyr,,,xkbmodel=evdev,xkblayout=de -ac -reset -screen
> 1672x1022 -retro :10 &
>
>     2. Store xmodmap and launch a new terminal in Xephyr:
>    xmodmap -pke > /tmp/my_modmap ; DISPLAY=:10 nohup terminator -e "xmodmap
> /tmp/my_modmap; bash" &
>    (* for details about terminator, see footer of this message)
>
>    3. Start a gnome-session in the terminal opened in 2.:
>    gnome-session

I found an easier way to open Xephyr with the keyboard properly
configured that I'm using now:

Xephyr -keybd
ephyr,,,xkbmodel=pc105,xkblayout=de,xkbrules=evdev,xkboption=grp:alts_toogle
-ac -reset -screen 1672x1022 -retro :10 &



--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktimdvlbf5mak3k1rhwhdzs-kwuw...@mail.gmail.com



planning to remove xprint, libxprintutil and related packages

2011-04-21 Thread Drew Parsons
Xprint has been obsolete for some time now, and it's time to let it go
to rest.  It was originally useful as a solution for printing non-latin
webpages from iceweasel 2, but that firefox problem has been fixed since
iceweasel 3 was released using cairo.

Xprint provided a kind a "wysiwig" API by which you could print from an
app using the normal X11 API. Maybe that should be "wypiwys" "what you
program is what you see". Displaying "on paper" instead of "on screen",
as it were.  Today that kind of functionality is better programmed
through cairo.

I'm planning to schedule xprint for removal shortly but wanted to give
this notification in case any odd individuals are still finding use for
it.  Though they should have already noticed the message in the version
in squeeze that it was obsolete :)  Actually I'm expecting more a
response of indifferent cheers than cries of dismay...

The xprint family of packages lined up for removal is:
xprint xprint-common
xprint-utils
libxprintutil1 libxprintutil-dev
libxprintapputil1  libxprintapputil-dev
libxfontp1 libxfontp-dev  libxfontp1-dbg

While animosity has been directed towards the xprint package, leaving
the other packages sitting quietly minding their own business, I don't
think it really makes sense to keep shipping the libxprint libraries if
there is no xprint. Please speak up if you think libxprint* or
xprint-utils should stay anyway.

libxp6 and libxp-dev are in a different position. I don't think it
particularly makes sense to keep them either, same as libxprint*, but
they have a bundle of reverse depends:
libxp-dev: lesstif2-dev libcoin60-dev  libecore-dev  gromacs-dev
libxp6: arb ddd dx fop grace gridengine-qmon lesstif-bin lesstif2 libdx4
libdx4 libecore-x1 libmotif-dev libmotif4 libxbae4 libxp-dev libxp6-dbg
motif-clients mtink twpsk whitedune xastir xtel 
So I'll put libxp into the too-hard basket now and won't touch it.

cc: iceweasel maintainers: please drop the iceweasel suggests on xprint
now!

cc: xcb maintainers: should you keep libxcb-xprint0 ? Do we need to talk
about this? libxcb-xprint0 has no relation (in a packaging sense) to
xprint.

Cheers,
Drew




signature.asc
Description: This is a digitally signed message part


Bug#598803: X crashes / hung gpu, now and then

2011-04-21 Thread Harri Haataja
Package: xserver-xorg-video-intel
Followup-For: Bug #598803


This is an FSC Amilo M1450G laptop.

Installing 2:2.15.0-1 from sid made the random hang go away for me.
It's been over a day now, running and suspended, with no incident.
Previously it would happen within a few minutes, at random, in normal
use with 2.6.38 but never with 2.6.32 (kept as a backup kernel).

Logs:

Apr 11 20:34:15 iofiel kernel: [ 3331.024067] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Apr 11 20:34:15 iofiel kernel: [ 3331.027314] [drm:i915_do_wait_request] 
*ERROR* i915_do_wait_request returns -11 (awaiting 81560 at 81558, next 81561)

Also:

Apr 17 22:39:32 iofiel kernel: [15200.988545] 
[drm:i915_gem_object_pin_and_relocate] *ERROR* Failure to install fence: -28

No errors so far in this version.


Rest added by reportbug...

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun  6  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1783236 Mar 26 09:55 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1140 Apr 17 18:27 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "fi"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
EndSection

Section "Device"
Identifier  "Configured Video Device"
Driver  "intel"
#Option "DRI" "off"
EndSection

Section "Monitor"
Identifier  "Configured Monitor"
EndSection

Section "Screen"
Identifier  "Default Screen"
Monitor "Configured Monitor"
#Option "Accel" "off"
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
  blacklist drm_kms_helper

Kernel version (/proc/version):
---
Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 24574 Apr 21 10:34 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   134.631] 
X.Org X Server 1.9.5
Release Date: 2011-03-17
[   134.645] X Protocol Version 11, Revision 0
[   134.647] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian
[   134.649] Current Operating System: Linux iofiel 2.6.38-2-686 #1 SMP Thu Apr 
7 05:24:21 UTC 2011 i686
[   134.651] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-686 
root=/dev/mapper/iofiel-root ro nomodeset
[   134.653] Build Date: 26 March 2011  07:50:38AM
[   134.655] xorg-server 2:1.9.5-1 (Cyril Brulebois ) 
[   134.658] Current version of pixman: 0.21.4
[   134.660]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   134.664] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   134.670] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 20 12:47:02 
2011
[   134.701] (==) Using config file: "/etc/X11/xorg.conf"
[   134.706] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   134.728] (==) No Layout section.  Using the first Screen section.
[   134.728] (**) |-->Screen "Default Screen" (0)
[   134.728] (**) |   |-->Monitor "Configured Monitor"
[   134.729] (==) No device specified for screen "Default Screen".
Using the first device section listed.
[   134.729] (**) |   |-->Device "Configured Video Device"
[   134.729] (==) Automatically adding devices
[   134.729] (==) Automatically enabling d