[Touch-packages] [Bug 1814481] Re: bluetooth keyboard not working
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 working Status in bluez package in Ubuntu: Incomplete Bug description: 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 it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1814481] Re: bluetooth keyboard not working
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 in Ubuntu: Confirmed Bug description: 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 it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1
[Touch-packages] [Bug 1814481] [NEW] bluetooth keyboard not working
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 it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg
[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic
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.launchpad.net/bugs/1756846 Title: bridge-utils incompatible with ifupdown on bionic Status in ifupdown package in Ubuntu: Fix Released Bug description: $ 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-15ubuntu1 Candidate: 1.5-15ubuntu1 Version table: *** 1.5-15ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install ifupdown Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: rdnssd The following packages will be REMOVED bridge-utils The following NEW packages will be installed ifupdown 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 55.2 kB of archives. After this operation, 119 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 0.8.16ubuntu2 [55.2 kB] Fetched 55.2 kB in 0s (1,280 kB/s) (Reading database ... 251311 files and directories currently installed.) Removing bridge-utils (1.5-15ubuntu1) ... Selecting previously unselected package ifupdown. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ... Unpacking ifupdown (0.8.16ubuntu2) ... Setting up ifupdown (0.8.16ubuntu2) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu4) ... Processing triggers for man-db (2.8.2-1) ... $ sudo apt-get install bridge-utils Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ifupdown The following packages will be REMOVED ifupdown The following NEW packages will be installed bridge-utils 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 0 B/30.1 kB of archives. After this operation, 119 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 251318 files and directories currently installed.) Removing ifupdown (0.8.16ubuntu2) ... Selecting previously unselected package bridge-utils. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ... Unpacking bridge-utils (1.5-15ubuntu1) ... Setting up bridge-utils (1.5-15ubuntu1) ... Processing triggers for man-db (2.8.2-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1756846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic
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 bridge-utils package in Ubuntu: Confirmed Bug description: $ 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-15ubuntu1 Candidate: 1.5-15ubuntu1 Version table: *** 1.5-15ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install ifupdown Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: rdnssd The following packages will be REMOVED bridge-utils The following NEW packages will be installed ifupdown 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 55.2 kB of archives. After this operation, 119 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 0.8.16ubuntu2 [55.2 kB] Fetched 55.2 kB in 0s (1,280 kB/s) (Reading database ... 251311 files and directories currently installed.) Removing bridge-utils (1.5-15ubuntu1) ... Selecting previously unselected package ifupdown. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ... Unpacking ifupdown (0.8.16ubuntu2) ... Setting up ifupdown (0.8.16ubuntu2) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu4) ... Processing triggers for man-db (2.8.2-1) ... $ sudo apt-get install bridge-utils Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ifupdown The following packages will be REMOVED ifupdown The following NEW packages will be installed bridge-utils 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 0 B/30.1 kB of archives. After this operation, 119 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 251318 files and directories currently installed.) Removing ifupdown (0.8.16ubuntu2) ... Selecting previously unselected package bridge-utils. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ... Unpacking bridge-utils (1.5-15ubuntu1) ... Setting up bridge-utils (1.5-15ubuntu1) ... Processing triggers for man-db (2.8.2-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1756846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756846] [NEW] bridge-utils incompatible with ifupdown on bionic
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-15ubuntu1 Candidate: 1.5-15ubuntu1 Version table: *** 1.5-15ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install ifupdown Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: rdnssd The following packages will be REMOVED bridge-utils The following NEW packages will be installed ifupdown 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 55.2 kB of archives. After this operation, 119 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 0.8.16ubuntu2 [55.2 kB] Fetched 55.2 kB in 0s (1,280 kB/s) (Reading database ... 251311 files and directories currently installed.) Removing bridge-utils (1.5-15ubuntu1) ... Selecting previously unselected package ifupdown. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ... Unpacking ifupdown (0.8.16ubuntu2) ... Setting up ifupdown (0.8.16ubuntu2) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu4) ... Processing triggers for man-db (2.8.2-1) ... $ sudo apt-get install bridge-utils Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ifupdown The following packages will be REMOVED ifupdown The following NEW packages will be installed bridge-utils 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 0 B/30.1 kB of archives. After this operation, 119 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 251318 files and directories currently installed.) Removing ifupdown (0.8.16ubuntu2) ... Selecting previously unselected package bridge-utils. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ... Unpacking bridge-utils (1.5-15ubuntu1) ... Setting up bridge-utils (1.5-15ubuntu1) ... Processing triggers for man-db (2.8.2-1) ... ** Affects: bridge-utils (Ubuntu) Importance: Undecided Status: New -- 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 bridge-utils package in Ubuntu: New Bug description: $ 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-15ubuntu1 Candidate: 1.5-15ubuntu1 Version table: *** 1.5-15ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install ifupdown Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: rdnssd The following packages will be REMOVED bridge-utils The following NEW packages will be installed ifupdown 0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade. Need to get 55.2 kB of archives. After this operation, 119 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 0.8.16ubuntu2 [55.2 kB] Fetched 55.2 kB in 0s (1,280 kB/s) (Reading database ... 251311 files and directories currently installed.) Removing bridge-utils (1.5-15ubuntu1) ... Selecting previously unselected package ifupdown. (Reading database ... 251286 files and directories currently installed.) Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ... Unpacking ifupdown (0.8.16ubuntu2) ... Setting up ifupdown (0.8.16ubuntu2) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu4) ... Processing triggers for man-db (2.8.2-1) ... $ sudo apt-get install bridge-utils Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ifupdown The following packages will be REMOVED ifupdown The following NEW packages will be installed bridge-utils 0 to upgrade, 1 to
[Touch-packages] [Bug 1692671] Re: intel driver fails to reenable display
** 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/1692671 Title: intel driver fails to reenable display Status in xorg package in Ubuntu: New Bug description: 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 (1920x1080) display, but since I switched to a 3840x2160 display the only reliable solution to get the computer back from blanking is pressing the power button. I can then see the shutdown "splash" and after powering it back again everything is back to normal. until it blanks the screen again obviusly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 22 19:16:43 2017 InstallationDate: Installed on 2015-12-27 (512 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692671] Re: intel driver fails to reenable display
** 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.net/bugs/1692671 Title: intel driver fails to reenable display Status in xorg package in Ubuntu: New Bug description: 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 (1920x1080) display, but since I switched to a 3840x2160 display the only reliable solution to get the computer back from blanking is pressing the power button. I can then see the shutdown "splash" and after powering it back again everything is back to normal. until it blanks the screen again obviusly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 22 19:16:43 2017 InstallationDate: Installed on 2015-12-27 (512 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692671] Re: intel driver fails to reenable display
** 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.launchpad.net/bugs/1692671 Title: intel driver fails to reenable display Status in xorg package in Ubuntu: New Bug description: 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 (1920x1080) display, but since I switched to a 3840x2160 display the only reliable solution to get the computer back from blanking is pressing the power button. I can then see the shutdown "splash" and after powering it back again everything is back to normal. until it blanks the screen again obviusly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 22 19:16:43 2017 InstallationDate: Installed on 2015-12-27 (512 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692671] [NEW] intel driver fails to reenable display
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 (1920x1080) display, but since I switched to a 3840x2160 display the only reliable solution to get the computer back from blanking is pressing the power button. I can then see the shutdown "splash" and after powering it back again everything is back to normal. until it blanks the screen again obviusly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 22 19:16:43 2017 InstallationDate: Installed on 2015-12-27 (512 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1692671 Title: intel driver fails to reenable display Status in xorg package in Ubuntu: New Bug description: 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 (1920x1080) display, but since I switched to a 3840x2160 display the only reliable solution to get the computer back from blanking is pressing the power button. I can then see the shutdown "splash" and after powering it back again everything is back to normal. until it blanks the screen again obviusly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 22 19:16:43 2017 InstallationDate: Installed on 2015-12-27 (512 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1465183] Re: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-routes
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 gateway and use "routes" to fill the gap.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1465183
Title:
ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-
routes
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
Hi.
Sorry for my bad english.
Iam using option rfc3442-classless-static-routes in my dhcp-server.
# cat /var/lib/dhcp/dhclient.eth0.leases
lease {
interface "eth0";
fixed-address 192.168.120.170;
option subnet-mask 255.255.255.0;
option routers 192.168.120.1;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.120.1;
option dhcp-server-identifier 192.168.120.1;
option ntp-servers 192.168.120.1;
option rfc3442-classless-static-routes 24,10,125,0,192,168,120,110;
option broadcast-address 192.168.120.255;
option domain-name "home.xmu";
renew 1 2015/06/15 05:45:48;
rebind 1 2015/06/15 17:04:48;
expire 1 2015/06/15 20:04:48;
}
In other operation system:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.120.1 0.0.0.0 UG0 00 eth0
10.125.0.0 192.168.120.110 255.255.255.0 UG0 00 eth0
192.168.120.0 0.0.0.0 255.255.255.0 U 0 00 eth0
In ubuntu 15.04:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
10.125.0.0 192.168.120.110 255.255.255.0 UG0 00 eth0
192.168.120.0 0.0.0.0 255.255.255.0 U 0 00 eth0
No default gateway!!!
# cat /var/lib/dhcp/dhclient.leases
lease {
interface "eth0";
fixed-address 192.168.120.169;
option subnet-mask 255.255.255.0;
option routers 192.168.120.1;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.120.1;
option dhcp-server-identifier 192.168.120.1;
option ntp-servers 192.168.120.1;
option rfc3442-classless-static-routes 24,10,125,0,192,168,120,110;
option broadcast-address 192.168.120.255;
option domain-name "home.xmu";
renew 1 2015/06/15 07:41:11;
rebind 1 2015/06/15 16:57:38;
expire 1 2015/06/15 19:57:38;
}
If i comment option rfc3442-classless-static-routes in my dhcp-server.
Default gateway works fine:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.120.1 0.0.0.0 UG0 00 eth0
192.168.120.0 0.0.0.0 255.255.255.0 U 0 00 eth0
# cat /etc/issue
Ubuntu 15.04 \n \l
# uname -a
Linux wp01 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
# aptitude show isc-dhcp-client
Package: isc-dhcp-client
State: installed
Automatically installed: no
Version: 4.3.1-5ubuntu2.2
Priority: important
Section: net
Maintainer: Ubuntu Developers
Architecture: amd64
Uncompressed Size: 698 k
Depends: libc6 (>= 2.15), libdns-export100, libirs-export91, libisc-export95,
debianutils (>= 2.8.2), isc-dhcp-common (= 4.3.1-5ubuntu2.2), iproute2
Suggests: resolvconf, avahi-autoipd, apparmor
Provides: dhcp-client
# aptitude show isc-dhcp-common
Package: isc-dhcp-common
State: installed
Automatically installed: no
Version: 4.3.1-5ubuntu2.2
Priority: important
Section: net
Maintainer: Ubuntu Developers
Architecture: amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1465183/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
