[Ubuntu-x-swat] [Bug 1692671] Re: intel driver fails to reenable display

2021-08-12 Thread Alejandro Mery
it's been more than 4 years. nothing is the same as when this problem happened -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1692671 Title: intel driver fails to reenable display To man

[Ubuntu-x-swat] [Bug 1814481] [NEW] bluetooth keyboard not working

2019-02-03 Thread Alejandro Mery
Public bug reported: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows

[Ubuntu-x-swat] [Bug 1692671] Re: intel driver fails to reenable display

2017-05-22 Thread Alejandro Mery
** Attachment added: "lspci -v" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881544/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1692671 Titl

[Ubuntu-x-swat] [Bug 1692671] Re: intel driver fails to reenable display

2017-05-22 Thread Alejandro Mery
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881545/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1692671 Title: in

[Ubuntu-x-swat] [Bug 1692671] Re: intel driver fails to reenable display

2017-05-22 Thread Alejandro Mery
** Attachment added: "sudo get-edid | parse-edid" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881543/+files/edid.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/

[Ubuntu-x-swat] [Bug 1692671] [NEW] intel driver fails to reenable display

2017-05-22 Thread Alejandro Mery
Public bug reported: if the display is sent to sleep it won't wake up. If I go to tty1 or tty2 I'm pulled back to tty7 (?) within seconds. sometimes if I ctrl-alt-del I'm sent back to the login screen and from there I can resume the session. everything was working fine with my previous (1920x108

[Ubuntu-x-swat] [Bug 1512307] Re: fglrx and fglrx-updates install crashes system: no screen access possible

2015-11-03 Thread Alejandro Mery
same problem with AMD E2-1800. 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] I can shortly see a kernel panic before it jumps back to graphic mode and freezes permanently but I haven't been able to capture the text yet. -- You received this

[Ubuntu-x-swat] [Bug 1278046] ProcEnviron.txt

2014-02-09 Thread Alejandro Mery
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1278046/+attachment/3974595/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278

[Ubuntu-x-swat] [Bug 1278046] Re: X -configure segfaults

2014-02-09 Thread Alejandro Mery
apport information ** Tags added: apport-collected ** Description changed: I want to use dual head (VGA+LVDS) since lightdm instead of getting Xfce to set it up after login, and using us/altgr-intl instead of us/intl. Also because the mouse pointer is wrongly rendered on the VGA (too high,

[Ubuntu-x-swat] [Bug 1278046] Re: X -configure segfaults

2014-02-09 Thread Alejandro Mery
** Attachment added: "normal /var/log/Xorg.0.log with Xfce configuring the dual head" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278046/+attachment/3974592/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in U

[Ubuntu-x-swat] [Bug 1278046] Re: X -configure segfaults

2014-02-09 Thread Alejandro Mery
** Attachment added: "/var/log/Xorg.0.log with Segmentation fault on X :0 -configure" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278046/+attachment/3974591/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg

[Ubuntu-x-swat] [Bug 1278046] [NEW] X -configure segfaults

2014-02-09 Thread Alejandro Mery
Public bug reported: I want to use dual head (VGA+LVDS) since lightdm instead of getting Xfce to set it up after login, and using us/altgr-intl instead of us/intl. Also because the mouse pointer is wrongly rendered on the VGA (too high, and carrying a black box on it's tail) Ideally I would like

[Ubuntu-x-swat] [Bug 788021] Re: Radeon HD 6310 (amd e-350 zacate) needs nomodeset

2011-05-25 Thread Alejandro Mery
problem remains running oneric's kernel on natty $ cat /proc/version Linux version 2.6.39-3-generic (buildd@allspice) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.0-7ubuntu1) ) #9-Ubuntu SMP Sat May 21 10:16:29 UTC 2011 ** Attachment added: "Xorg.0.log for natty running Oneric's kernel in modeset mod

[Ubuntu-x-swat] [Bug 788021] Re: Radeon HD 6310 (amd e-350 zacate) needs nomodeset

2011-05-25 Thread Alejandro Mery
** Description changed: Binary package hint: xserver-xorg-video-ati - After I removed fglrx to narrow #787980 I had to add nomodeset to the - kernel command line to get something on the display. + After I removed fglrx to narrow bug #787980 I had to add nomodeset to + the kernel command line

[Ubuntu-x-swat] [Bug 788021] Re: Radeon HD 6310 (amd e-350 zacate) needs nomodeset

2011-05-25 Thread Alejandro Mery
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/788021 Title: Radeon HD 6310 (amd e-350 zacate) needs nomodeset ___ Mailing list: htt

[Ubuntu-x-swat] [Bug 788021] [NEW] Radeon HD 6310 (amd e-350 zacate) needs nomodeset

2011-05-25 Thread Alejandro Mery
Public bug reported: Binary package hint: xserver-xorg-video-ati After I removed fglrx to narrow #787980 I had to add nomodeset to the kernel command line to get something on the display. no problem until I uninstalled fglrx, 3 reboots without display (but ssh), 3 reboots with display using nomo