hi thanks for the prompt reply. you were quite right with the brightness suggestion - it was down to zero on the laptop screen when gdm loads. i didn't think to try that...
after increasing the brightness and logging in, it went back to zero as my gnome session started and i needed to bump the brightness up again. so something is definitely wrong here - not sure its xorg anymore - maybe gdm ?? that seg fault in the xorg log not significant? i will try and fiddle with the gdm init as a work-around and see if i can get it to flick the brightness up on the gdm login screen and post-login as the gnome session starts. again, this has been recent since the xorg update - previously all was well. the complete apt update performed just before all this began is below for reference. thanks. Takis Upgraded the following packages: bash (4.3-9.1) to 4.3-9.2 consolekit (0.4.6-4) to 0.4.6-5 dconf-cli (0.20.0-2) to 0.22.0-1 dconf-editor (0.20.0-2) to 0.22.0-1 dconf-gsettings-backend (0.20.0-2) to 0.22.0-1 dconf-service (0.20.0-2) to 0.22.0-1 dconf-tools (0.20.0-2) to 0.22.0-1 gir1.2-gdata-0.0 (0.15.2-1) to 0.16.0-1 gir1.2-gdesktopenums-3.0 (3.12.2-1) to 3.14.0-1 gir1.2-gnomebluetooth-1.0 (3.12.0-5) to 3.14.0-1 gir1.2-gnomedesktop-3.0 (3.12.2-2) to 3.14.0-1 gir1.2-gtkclutter-1.0 (1.5.4-2) to 1.6.0-1 gir1.2-gucharmap-2.90 (1:3.12.1-1) to 1:3.14.0-1 gir1.2-peas-1.0 (1.10.1-4) to 1.12.1-1 gir1.2-totem-plparser-1.0 (3.10.2-3) to 3.10.3-1 gnome-bluetooth (3.12.0-5) to 3.14.0-1 gnome-calculator (3.12.3-1) to 3.14.0-1 gnome-contacts (3.12.0-1+b2) to 3.14.0-1 gnome-desktop3-data (3.12.2-2) to 3.14.0-1 gnome-power-manager (3.12.2-1+b1) to 3.14.0-1 gnome-robots (1:3.8.1-2) to 1:3.14.0-1 gnome-user-share (3.10.2-1) to 3.14.0-1 gsettings-desktop-schemas (3.12.2-1) to 3.14.0-1 gucharmap (1:3.12.1-1) to 1:3.14.0-1 krb5-locales (1.12.1+dfsg-9) to 1.12.1+dfsg-10 libchamplain-0.12-0 (0.12.8-1) to 0.12.9-1 libchamplain-gtk-0.12-0 (0.12.8-1) to 0.12.9-1 libck-connector0 (0.4.6-4) to 0.4.6-5 libclutter-gtk-1.0-0 (1.5.4-2) to 1.6.0-1 libdconf1 (0.20.0-2) to 0.22.0-1 libgdata-common (0.15.2-1) to 0.16.0-1 libgdata19 (0.15.2-1) to 0.16.0-1 libgnome-bluetooth13 (3.12.0-5) to 3.14.0-1 libgnome-desktop-3-10 (3.12.2-2) to 3.14.0-1 libgssapi-krb5-2 (1.12.1+dfsg-9) to 1.12.1+dfsg-10 libgucharmap-2-90-7 (1:3.12.1-1) to 1:3.14.0-1 libjasper1 (1.900.1-debian1-2) to 1.900.1-debian1-2+b1 libk5crypto3 (1.12.1+dfsg-9) to 1.12.1+dfsg-10 libkrb5-3 (1.12.1+dfsg-9) to 1.12.1+dfsg-10 libkrb5support0 (1.12.1+dfsg-9) to 1.12.1+dfsg-10 libncurses5 (5.9+20140712-2) to 5.9+20140913-1 libncursesw5 (5.9+20140712-2) to 5.9+20140913-1 libpam-ck-connector (0.4.6-4) to 0.4.6-5 libpeas-1.0-0 (1.10.1-4) to 1.12.1-1 libpeas-common (1.10.1-4) to 1.12.1-1 libpipeline1 (1.3.0-1) to 1.3.1-1 libprotobuf9 (2.6.0-3) to 2.6.0-4 libslang2 (2.2.4-17) to 2.3.0-1 libtinfo5 (5.9+20140712-2) to 5.9+20140913-1 libtotem-plparser18 (3.10.2-3) to 3.10.3-1 linux-compiler-gcc-4.8-x86 (3.14.15-2) to 3.16.3-2 linux-headers-amd64 (3.14+59) to 3.16+61 linux-image-amd64 (3.14+59) to 3.16+61 linux-libc-dev (3.14.15-2) to 3.16.3-2 ncurses-base (5.9+20140712-2) to 5.9+20140913-1 ncurses-bin (5.9+20140712-2) to 5.9+20140913-1 ncurses-term (5.9+20140712-2) to 5.9+20140913-1 sound-juicer (3.12.0-2) to 3.14.0-1 task-desktop (3.24) to 3.27 task-english (3.24) to 3.27 task-gnome-desktop (3.24) to 3.27 task-laptop (3.24) to 3.27 task-print-server (3.24) to 3.27 task-ssh-server (3.24) to 3.27 tasksel (3.24) to 3.27 tasksel-data (3.24) to 3.27 xserver-common (2:1.16.0.901-1) to 2:1.16.1-1 xserver-xephyr (2:1.16.0.901-1) to 2:1.16.1-1 xserver-xorg-core (2:1.16.0.901-1) to 2:1.16.1-1 On 21 October 2014 02:29, Julien Cristau <jcris...@debian.org> wrote: > Control: severity -1 normal > Control: tag -1 moreinfo > > On Mon, Oct 20, 2014 at 23:18:14 +1100, Takis Diakoumis wrote: > >> Package: xserver-xorg-core >> Version: 2:1.16.1-1 >> Severity: grave >> >> Dear Maintainer, >> >> [ issues with reportbug #758619 prevented me from using it completely >> to send this report so I generated using reportbug --template ] >> >> Since upgrading from 2.:1.16.0.901-1 to the above version I have been >> unable to use a second screen attached to my laptop. During this >> update, I also went from linux-image-amd64 (3.14+59) to 3.16+61 – not >> sure if its relevant. >> > Actually this seems more likely to be a kernel issue than an X one. > >> I have Debian Jessie on a Thinkpad T440s. >> >> I normally boot with the second monitor attached and it boots fine >> into gdm. Since the update, booting with the monitor attached blanks >> the laptop screen (primary screen) as X starts. The second screen >> works fine as a second screen – as in the primary display is off but >> it behaves as if it is there. The only way out here is to ctrl-alt-f1 >> to a terminal and reboot. >> > Is the screen actually dead, or does it "just" reset the brightness to > minimum? I.e. do the brightness keys or poking > /sys/class/backlight/*/brightness work? > > Cheers, > Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
