[Touch-packages] [Bug 1814481] Re: bluetooth keyboard not working

2019-02-22 Thread Alejandro Mery
I can confirm it works out of the box using the latest Ubuntu "disco" live stick. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not workin

[Touch-packages] [Bug 1814481] Re: bluetooth keyboard not working

2019-02-13 Thread Alejandro Mery
I did test with bluez ppa and didn't change anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working Status in bluez package i

[Touch-packages] [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

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

2018-03-24 Thread Alejandro Mery
I had to install ifupdown manually, and got 0.8.17ubuntu1. everything fine now, but shouldn't this package be pulled in automatically somehow? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.la

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

2018-03-19 Thread Alejandro Mery
thanks @albrt, I didn't know that one -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1756846 Title: bridge-utils incompatible with ifupdown on bionic Status in bridg

[Touch-packages] [Bug 1756846] [NEW] bridge-utils incompatible with ifupdown on bionic

2018-03-19 Thread Alejandro Mery
Public bug reported: $ apt-cache policy ifupdown bridge-utils ifupdown: Installed: (none) Candidate: 0.8.16ubuntu2 Version table: 0.8.16ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status bridge-utils: Installed: 1.5-

[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/

[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.ne

[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs

[Touch-packages] [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

[Touch-packages] [Bug 1465183] Re: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-routes

2015-11-05 Thread Alejandro Mery
this bug is horrible. on environments where DHCP is served by a windows server there is no way of passing the default gateway via static routes ("rfc3442-classless-static-routes"). it's MS fault, but the client should be tolerant and notice rfc3442-classless-static-routes doesn't include a default