[Touch-packages] [Bug 1803681] Re: osmesa doesn't suport core contexts but could
** Attachment added: "simple osmesa test program" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+attachment/5213361/+files/osdemo.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1803681 Title: osmesa doesn't suport core contexts but could Status in mesa package in Ubuntu: New Bug description: If the --enable-osmesa in the mesa configuration were replaced with --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be able to return OpenGL core contexts. To show this I'm attaching a modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz). The modified code is all within the #ifdef USE_CORE_CONTEXT. To compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm". With the libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext failed!". But with a libOSmesa.so from a mesa that is configured with --enable-galliums-osmesa instead of --enable-osmesa, it works! Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1. While --enable-gallium-osmesa gets it up to OpenGL 3.3. My testing was with mesa 17.3.9 and mesa 18.2.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+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 1803681] [NEW] osmesa doesn't suport core contexts but could
Public bug reported: If the --enable-osmesa in the mesa configuration were replaced with --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be able to return OpenGL core contexts. To show this I'm attaching a modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz). The modified code is all within the #ifdef USE_CORE_CONTEXT. To compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm". With the libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext failed!". But with a libOSmesa.so from a mesa that is configured with --enable-galliums- osmesa instead of --enable-osmesa, it works! Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1. While --enable-gallium-osmesa gets it up to OpenGL 3.3. My testing was with mesa 17.3.9 and mesa 18.2.5. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1803681 Title: osmesa doesn't suport core contexts but could Status in mesa package in Ubuntu: New Bug description: If the --enable-osmesa in the mesa configuration were replaced with --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be able to return OpenGL core contexts. To show this I'm attaching a modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz). The modified code is all within the #ifdef USE_CORE_CONTEXT. To compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm". With the libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext failed!". But with a libOSmesa.so from a mesa that is configured with --enable-galliums-osmesa instead of --enable-osmesa, it works! Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1. While --enable-gallium-osmesa gets it up to OpenGL 3.3. My testing was with mesa 17.3.9 and mesa 18.2.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+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 1801128] Re: OpenSSH 7.7 -w tunnel bug
tagged and uploaded to C-unapproved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1801128 Title: OpenSSH 7.7 -w tunnel bug Status in openssh package in Ubuntu: In Progress Status in openssh source package in Cosmic: In Progress Bug description: [Impact] A regression in OpenSSH 7.7 breaks tunnelling via the -w switch in the ssh command. [Test Case] # lxc launch ubuntu:cosmic tester && lxc exec tester bash # apt update && \ apt dist-upgrade -y && \ sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config && \ service sshd restart && \ echo ubuntu:ubuntu | chpasswd # ssh -w any ubuntu@localhost ubuntu@localhost's password: Tunnel device open failed. Could not request tunnel forwarding. [Regression Potential] This is already fixed and tested upstream, and thus has little regression potential. [Original Description] Just upgraded to cosmic, which picks up OpenSSH 7.7. OpenSSH 7.7 has known bug https://bugzilla.mindrot.org/show_bug.cgi?id=2855 which is fixed in OpenSSH 7.8. It's a regression that completely breaks -w tunneling. The OpenSSH bug contains a trivial two-line patch to fix the bug. I downloaded the Ubuntu openssh package source, applied the patch and rebuilt, and can confirm that is does fix the problem. Any chance we could get this patch backported to Cosmic? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Thu Nov 1 09:36:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-ssh N/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: Upgraded to cosmic on 2018-11-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1801128/+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 1762127] Re: Ubuntu stuck in loop at boot after upgrade from 17.10 to 18.04
Please try removing all PPAs from the system (using ppa-purge) and see if that solves the problem. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: xdiagnose (Ubuntu) Status: New => Incomplete -- 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/1762127 Title: Ubuntu stuck in loop at boot after upgrade from 17.10 to 18.04 Status in xdiagnose package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: * I did a do-release-upgrade -d * After the upgrade was done, I rebooted Result: My computer was stuck in a boot loop, showing alternatively a black screen, a text log and a set of random pixels. Here is a GIF of the loop: https://imgur.com/zGGTzma As I had to make my computer work again I had to reinstal Ubuntu from a 18.04 live USB stick, so I'm not sure if I could get information from the previous installation. Reinstalling made my computer work fine with 18.04. I just need to reinstall all my applications. I had an external Mesa installation on 17.10 from Padoka Stable PPA. May it be related? At the moment, Mesa version from Padoka Stable is 18.0.0~*~padoka0, whereas after a 18.04 reinstall it is 18.0.0-rc5 Note: I tried to boot in safe mode with graphics, but it does not start, I get this error in the console: /usr/share/xdiagnose/failsafeXinit: line 194 : [: == : unary operator expected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.13 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 8 08:56:54 2018 InstallationDate: Installed on 2018-04-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1762127/+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 1761971] Re: ps2 keyboard not working after upgrade 16.04 -> 18.04
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1761971 Title: ps2 keyboard not working after upgrade 16.04 -> 18.04 Status in xorg-server package in Ubuntu: New Bug description: the problem seems to be related to xorg Symptomes: no key works in xorg but the device /dev/input/event2 is there and works according to evtest The keyboard works during startup and in the text consoles. "solution": I am now using a second usb keyboard (/dev/input/event4 on my machine) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 7 12:48:36 2018 DistUpgraded: 2018-04-07 09:51:42,601 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.8, 4.10.0-42-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1494] InstallationDate: Installed on 2017-12-27 (100 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=aabc1b46-62b2-4910-870e-ff827d8783dd ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-04-07 (0 days ago) dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.asset.tag: CZC2250RZC dmi.board.name: 1494 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC2250RZC dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite CMT PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Sat Apr 7 12:35:27 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1761971/+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 1761834] Re: Right-click doesn't work
** Package changed: xorg (Ubuntu) => libinput (Ubuntu) -- 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/1761834 Title: Right-click doesn't work Status in libinput package in Ubuntu: Confirmed Bug description: I decided to try out the beta for 18.04 from 17.10. Upon upgrading, I discovered that right-clicking no longer works on my trackpad, and right-clicks are handled as left-clicks would be. Two-finger right click does not work either. If I plug in a mouse with a physical right button, right clicking does work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 6 11:26:00 2018 DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2017-05-04 (337 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago) dmi.bios.date: 08/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1761834/+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 1761773] Re: Touch Screen stop working on 18.04 beta1
Is this bug still a problem in the latest updates to 18.04? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) ** No longer affects: mutter (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg-server package in Ubuntu: Incomplete Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1761773/+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 1761743] Re: Xorg crash, session logout after screen turned off
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- 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/1761743 Title: Xorg crash, session logout after screen turned off Status in xorg-server package in Ubuntu: Incomplete Bug description: Session logout after screen turned off and also logout during work May be related to Bug 1721428 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 15:52:02 2018 DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 [1462:7996] InstallationDate: Installed on 2017-03-02 (400 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7996 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=fa8af88c-68e6-4582-872e-a2c53edcbf97 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-04-02 (4 days ago) dmi.bios.date: 07/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7996 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1761743/+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 1761338] Re: Login screen upside down(reversed)
*** This bug is a duplicate of bug 1726160 *** https://bugs.launchpad.net/bugs/1726160 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1726160, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1726160 On login, display rotates to wrong orientation [HP Pavilion] -- 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/1761338 Title: Login screen upside down(reversed) Status in Ubuntu: New Bug description: Ubuntu 17.10, Nvidia drivers installed (official package nvidia-384). Computer: HP laptop: HP 14-008nf (with graphics: integrated + NVidia Geforce 940mx) Sometimes when i reboot the Ubuntu login screen is reversed, all the screen is upside down, then just rebooting without changing anything and it's back to normal...but not all the time (sometimes after booting to Windows also, cause i have dual boot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2) ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 01:55:57 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed bbswitch, 0.8, 4.13.0-37-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-37-generic, x86_64: installed virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:820a] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820a] InstallationDate: Installed on 2018-03-16 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=ce30d1fb-9d99-4019-8b24-6cd1462d771d ro quiet splash pci=noaer vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820A dmi.board.vendor: HP dmi.board.version: 82.26 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd07/04/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820A:rvr82.26:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1761338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.
[Touch-packages] [Bug 1761044] Re: xorg error
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1761044 Title: xorg error Status in xorg-server package in Ubuntu: Incomplete Bug description: when ever the system is recovered from the sleep mod due to inactivity i get an xorg error msg ... ProblemType: Bug DistroRelease: elementary 0.4.1 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 4 09:06:22 2018 DistUpgraded: Fresh install DistroCodename: loki DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:832b] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] [103c:832b] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=cb67384c-374d-4721-a7b6-d21e48bc769a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd07/04/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.37:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Laptop 15-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 4 08:55:42 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1761044/+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 1760721] Re: Resolution is stuck at 640x480
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- 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/1760721 Title: Resolution is stuck at 640x480 Status in xorg-server package in Ubuntu: Won't Fix Bug description: This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 resolution, this happened since the first boot. I researched and found in forums that xdiagnose provides a workaround by deactivating some graphics at boot, so I installed it and it worked, however, just as a workaround. I can change the resolution now, but the size of apps sometimes takes way more screen space than it should, and the screen flickers randomly. By selecting "inform errors" in xdiagnose I got a pop up message saying the computer is providing 3D by software instead of hardware, I don't know how to fix this, any guidance? Let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic i686 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Apr 2 16:30:13 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1025:0083] InstallationDate: Installed on 2018-04-02 (0 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release i386 (20180105) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Aspire 3000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a37feeb6-1e6a-47c6-b003-a161b5612912 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/06 dmi.bios.vendor: Acer dmi.bios.version: 3A32 dmi.board.name: Lugano M dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: , Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A32:bd02/20/06:svnAcer,inc.:pnAspire3000:pvrNotApplicable:rvnAcer,Inc.:rnLuganoM:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 3000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Apr 2 16:18:06 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@l
[Touch-packages] [Bug 1604467] Re: Alt-Left changes display screen
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 520546, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 520546 Alt+KEY incorrectly behaves like Ctrl+Alt+KEY -- 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/1604467 Title: Alt-Left changes display screen Status in xorg package in Ubuntu: Confirmed Bug description: When I press Alt and Left, it changes to tty1. I expect it to move my browser back a page. It does that also, but I can't see that until I change back to tty2 which is where my session is. This began today, I don't know if there was an update that caused it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 19 11:40:34 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.26, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80a1] InstallationDate: Installed on 2015-12-20 (212 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 006: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP) Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=c16d5370-604d-47f6-8b73-e4766ccdfb7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.80 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A1 dmi.board.vendor: HP dmi.board.version: 91.1D dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.80:bd06/14/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1D:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 22 17:30:27 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1604467/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
** Summary changed: - Alt-f2 switches to virtual terminal 2 + Alt+KEY incorrectly behaves like Ctrl+Alt+KEY ** Tags removed: lucid precise quantal zesty ** Tags added: cosmic ** Changed in: console-setup (Ubuntu) Importance: Undecided => High ** No longer affects: console-cyrillic (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1760312] Re: AMD or Intel VGA driver
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1760312 Title: AMD or Intel VGA driver Status in Ubuntu: Won't Fix Bug description: Can't install AMD or Intel VGA driver ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 31 21:49:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-03-31 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=0e6bda63-55f9-42e5-8061-7f3db5d18136 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.65 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.65:bd04/06/2017:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760312/+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 1759682] Re: buckup problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1759682 Title: buckup problem Status in Ubuntu: Incomplete Bug description: xorg (Ubuntu) bug reporting guidelines: Please report bugs against xorg with this command: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: SYSROOT: clean, 164759/1160992 files, 1338235/4638464 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 28 16:39:28 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. 82945G/GZ Integrated Graphics Controller [105b:0d47] InstallationDate: Installed on 2018-03-23 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: OEM OEM ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic root=UUID=fb43f0b9-8312-4291-ac88-efd27ea02c84 ro debian dont tach my grub-pc quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 45CMX/45GMX/45CMX-K dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svnOEM:pnOEM:pvr:rvnFoxconn:rn45CMX/45GMX/45CMX-K:rvr:cvnOEM:ct3:cvr: dmi.product.name: OEM dmi.sys.vendor: OEM version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Mar 28 09:12:37 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputUVC Camera (046d:0825) KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22984 vendor GSM xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1759682/+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 1803691] [NEW] package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 23
Public bug reported: Frequent error messages concerning systemd-services not able to install and asking for permission to report it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-services (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Nov 15 17:46:42 2018 DuplicateSignature: package:systemd-services:(not installed) Unpacking systemd-services (204-5ubuntu20) ... dpkg: error processing archive /tmp/apt-dpkg-install-dmkWIE/03-systemd-services_204-5ubuntu20_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 InstallationDate: Installed on 2018-11-04 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6 SourcePackage: systemd Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803691 Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 Status in systemd package in Ubuntu: New Bug description: Frequent error messages concerning systemd-services not able to install and asking for permission to report it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-services (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Nov 15 17:46:42 2018 DuplicateSignature: package:systemd-services:(not installed) Unpacking systemd-services (204-5ubuntu20) ... dpkg: error processing archive /tmp/apt-dpkg-install-dmkWIE/03-systemd-services_204-5ubuntu20_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 InstallationDate: Installed on 2018-11-04 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6 SourcePackage: systemd Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803691/+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 1803691] Re: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803691 Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 Status in systemd package in Ubuntu: New Bug description: Frequent error messages concerning systemd-services not able to install and asking for permission to report it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-services (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Nov 15 17:46:42 2018 DuplicateSignature: package:systemd-services:(not installed) Unpacking systemd-services (204-5ubuntu20) ... dpkg: error processing archive /tmp/apt-dpkg-install-dmkWIE/03-systemd-services_204-5ubuntu20_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 InstallationDate: Installed on 2018-11-04 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6 SourcePackage: systemd Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 237-3ubuntu10.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803691/+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 1759916] Re: black screen after logon
It looks like this bug was reported before the official release of 18.04. Can you please update the system and tell us if the bug still occurs? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1759916 Title: black screen after logon Status in Ubuntu: Incomplete Bug description: black screen after logon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 29 19:41:21 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:3824] InstallationDate: Installed on 2015-12-14 (836 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80K6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C2CN17WW(V1.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Z51-70 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z51-70 dmi.modalias: dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70: dmi.product.family: IDEAPAD dmi.product.name: 80K6 dmi.product.version: Lenovo Z51-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 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 xserver.bootTime: Thu Mar 29 19:26:30 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1759916/+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 1760020] Re: Ubuntu crash after wake from suspend
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1760020 Title: Ubuntu crash after wake from suspend Status in Ubuntu: Won't Fix Bug description: I usually have my notebook connected with a monitor by HDMI. If I suspend it, after wake just appear the desktop in the notebook but no in monitor, and no respond to any input device (mouse, keyboard), except to combine keys to restart: ctrl+alt+prt sc -> ctrl+alt+F12 -> ctrl+alt+B ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.15.0-041500-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Fri Mar 30 02:02:13 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:836b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:836b] InstallationDate: Installed on 2018-01-21 (67 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP Pavilion Power Laptop 15-cb0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500-generic root=UUID=8cd5eb50-c2e6-47c7-a30f-a562941c0465 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.11:bd09/06/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760020/+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 1761267] Re: issue is regarding boot hanging between work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1761267 Title: issue is regarding boot hanging between work Status in Ubuntu: Incomplete Bug description: while getting started it is hanged and sometime it doesnot open the required folder any software downloaded from internet is not installed in "exe." file especially sometime keyboard stops working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 4 23:11:32 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0767] InstallationDate: Installed on 2018-02-22 (41 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override locale=en_US SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0C6XG5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 4 20:29:12 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1317 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1761267/+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 1758700] Re: Internal display not working
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- 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/1758700 Title: Internal display not working Status in xorg-server package in Ubuntu: Won't Fix Bug description: My internal display is not working. The internal display works at boot and goes black during ubuntu boot. I am able to use the hdmi monitor but i need my internal screen to work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 09:35:30 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] InstallationDate: Installed on 2018-02-18 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=cd069400-aa78-43dd-9434-6d260f2c78f1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0K99NX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0K99NX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1803221830.bb45ce~oibaf~a version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803241930.d60eaf~oibaf~a version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803241930.d60eaf~oibaf~a version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1+git1803151933.fdba53~oibaf~a version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1803021934.aa3639~oibaf~a version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1803090733.ac8f7b~oibaf~a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1758700/+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 1759042] Re: apport-bug amd64 artful ubuntu
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1759042 Title: apport-bug amd64 artful ubuntu Status in Ubuntu: Won't Fix Bug description: apport-bug amd64 artful ubuntu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13 Uname: Linux 4.13.0-37-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 26 23:41:42 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:0358] InstallationDate: Installed on 2018-03-09 (17 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-lowlatency root=UUID=a9b9e879-acb5-44e8-ba69-5377b28a36b1 ro recovery nomodeset priority=low Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3027 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3027:bd10/31/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Mar 26 23:31:47 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1759042/+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 1758713] Re: system
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1758713 Title: system Status in Ubuntu: Incomplete Bug description: Ubuntu 16.04 LTS system bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 25 19:33:39 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: microdia, 2009.01: added v4l2loopback, 0.9.1, 4.13.0-36-generic, i686: installed v4l2loopback, 0.9.1, 4.13.0-37-generic, i686: installed virtualbox, 5.0.40, 4.13.0-36-generic, i686: installed virtualbox, 5.0.40, 4.13.0-37-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 1100/1150] [1458:d000] InstallationDate: Installed on 2018-02-28 (24 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) JournalErrors: -- Logs begin at v 2018-03-25 19:03:19 CEST, end at v 2018-03-25 19:34:01 CEST. -- márc 25 19:28:46 hostname com.canonical.Unity.Scope.Applications[1847]: Error loading package indexes: Couldn't stat '/var/cache/software-center/xapian' márc 25 19:28:46 hostname com.canonical.Unity.Scope.Applications[1847]: (unity-scope-loader:5431): unity-applications-daemon-CRITICAL **: daemon.vala:144: Failed to load Software Center index. 'Apps Available for Download' will not be listed MachineType: FUJITSU SIEMENS GA-K8RS482M ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: GA-K8RS482M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr: dmi.product.name: GA-K8RS482M dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 25 17:47:59 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSIGMACHIP Usb Mouse MOUSE, id 8 inputHID 1267:0103KEYBOARD, id 9 inputHID 1267:0103KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1758713/+subscriptions
[Touch-packages] [Bug 1111882] Re: GnuTLS recv error (-9): A TLS packet with unexpected length was received
Also seeing this with libgnutls30 and git 2.17.1-ubuntu0 on 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/882 Title: GnuTLS recv error (-9): A TLS packet with unexpected length was received Status in apt package in Ubuntu: Invalid Status in curl package in Ubuntu: Invalid Status in git package in Ubuntu: Confirmed Status in gnutls26 package in Ubuntu: Confirmed Bug description: On Precise 12.04 whilst attempting: GIT_CURL_VERBOSE=1 git clone -v https://git01.codeplex.com/typescript the operation fails after the final git pack-file has been received and the already-created repository is deleted from the file system. ... > POST /typescript/git-upload-pack HTTP/1.1 User-Agent: git/1.8.1.2.433.g9808ce0.dirty Host: git01.codeplex.com Accept-Encoding: gzip Content-Type: application/x-git-upload-pack-request Accept: application/x-git-upload-pack-result Content-Length: 611 * upload completely sent off: 611out of 611 bytes < HTTP/1.1 200 OK < Cache-Control: no-cache, max-age=0, must-revalidate < Pragma: no-cache < Content-Type: application/x-git-upload-pack-result < Expires: Fri, 01 Jan 1980 00:00:00 GMT < Server: Microsoft-IIS/7.5 < X-Powered-By: ASP.NET < Date: Thu, 31 Jan 2013 21:43:55 GMT < Connection: close < remote: Counting objects: 149766, done. remote: Compressing objects: 100% (10580/10580), done. * GnuTLS recv error (-9): A TLS packet with unexpected length was received. * Closing connection #0 remote: Total 149766 (delta 138201), reused 149559 (delta 138077) Receiving objects: 100% (149766/149766), 198.98 MiB | 361 KiB/s, done. error: RPC failed; result=56, HTTP code = 200 Resolving deltas: 100% (138201/138201), done. git exits at this point but it deletes the entire cloned ./typescript directory. I tried building the latest git binary and included an additional debug option in "http.c" that allowed me to set the protocol version using an environment option: CURLOPT_SSLVERSION=1 git clone ... where 1 = TLSv1, 2 = SSLv2, 3 = SSLv3. I tried each protocol but the result was the same. The knock-on bug here is that git ought not to delete what it has fetched - in this case more than 250MB of data. I did try to build the latest gnutls but it needs a very recent version of libnettle which has the "rsa_decrypt_tr" function. I stopped at that point since I don't want to get into dependency and library version issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/882/+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 1803704] [NEW] package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
Public bug reported: erro ao processar o pacote libflite1:amd64 (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: libflite1:amd64 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libflite1:amd64 2.0.0-release-1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 15 17:08:50 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2 1.1.0-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2018-11-05 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: flite Title: package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flite in Ubuntu. https://bugs.launchpad.net/bugs/1803704 Title: package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in flite package in Ubuntu: New Bug description: erro ao processar o pacote libflite1:amd64 (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: libflite1:amd64 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libflite1:amd64 2.0.0-release-1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 15 17:08:50 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2 1.1.0-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2018-11-05 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: flite Title: package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1803704/+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 1803707] [NEW] merge nss 2:3.39-1 from Debian unstable
Public bug reported: please merge newer nss for disco ** Affects: nss (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1803707 Title: merge nss 2:3.39-1 from Debian unstable Status in nss package in Ubuntu: New Bug description: please merge newer nss for disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1803707/+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 1803313] Re: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1803313 Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I don't know anything about initralfs and *-tools. But Ubuntu rise a bug... Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy initramfs-tools initramfs-tools: Installé : 0.130ubuntu3.5 Candidat : 0.130ubuntu3.5 Table de version : *** 0.130ubuntu3.5 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.130ubuntu3 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Nov 14 09:11:28 2018 Df: Dmesg: ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-11-11 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1803313/+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 1803743] [NEW] Иногда пропадает звук. Помогает только перезагрузка.
Public bug reported: Здравствуйте! С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук. Определить по какой причине так и не получилось. Если звук пропадает то помогает только перезагрузка. Обращался на форум, но безрезультатно https://forum.ubuntu.ru/index.php?topic=278602.0 Пару раз переустанавливал Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. Первых два шага не помогают. Проблема остается и звук появляется только при перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю. В третьем шаге предлагается специальный скрипт, который собирает всю необходимую информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей системе в момент когда звук отсутствует http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 Помогите, пожалуйста. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1803743 Title: Иногда пропадает звук. Помогает только перезагрузка. Status in alsa-driver package in Ubuntu: New Bug description: Здравствуйте! С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук. Определить по какой причине так и не получилось. Если звук пропадает то помогает только перезагрузка. Обращался на форум, но безрезультатно https://forum.ubuntu.ru/index.php?topic=278602.0 Пару раз переустанавливал Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. Первых два шага не помогают. Проблема остается и звук появляется только при перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю. В третьем шаге предлагается специальный скрипт, который собирает всю необходимую информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей системе в момент когда звук отсутствует http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 Помогите, пожалуйста. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803743/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
Cosmic verification slapd package on the consumer: Installed: 2.4.46+dfsg-5ubuntu1 Candidate: 2.4.46+dfsg-5ubuntu1 Version table: *** 2.4.46+dfsg-5ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages Confirming failed replication attempt: provider: Nov 16 16:16:53 cosmic-provider slapd[2339]: conn=1004 fd=12 ACCEPT from IP=10.0.100.71:37472 (IP=0.0.0.0:389) Nov 16 16:16:53 cosmic-provider slapd[2339]: conn=1004 op=0 UNBIND Nov 16 16:16:53 cosmic-provider slapd[2339]: conn=1004 fd=12 closed consumer: Nov 16 16:16:53 cosmic-consumer slapd[2344]: slap_client_connect: URI=ldap://cosmic-provider.lxd ldap_sasl_interactive_bind_s failed (-2) Nov 16 16:16:53 cosmic-consumer slapd[2344]: do_syncrepl: rid=001 rc -1 retrying Host: [sex nov 16 14:17:52 2018] audit: type=1400 audit(1542385073.436:831): apparmor="DENIED" operation="open" namespace="root//lxd-cosmic-consumer_" profile="/usr/sbin/slapd" name="/etc/krb5/user/110/client.keytab" pid=20151 comm="slapd" requested_mask="r" denied_mask="r" fsuid=165646 ouid=165536 Right after the consumer's openldap packages were updated, the provider logged this, showing that replication is working: Nov 16 16:34:46 cosmic-provider slapd[2339]: conn=1022 fd=12 ACCEPT from IP=10.0.100.71:37582 (IP=0.0.0.0:389) Nov 16 16:34:46 cosmic-provider slapd[2339]: conn=1022 op=0 BIND dn="" method=163 Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=0 RESULT tag=97 err=14 text=SASL(0): successful result: Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=1 BIND dn="" method=163 Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=1 RESULT tag=97 err=14 text=SASL(0): successful result: Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=2 BIND dn="" method=163 Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=2 BIND authcid="consumer" authzid="consumer" Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=2 BIND dn="uid=consumer,cn=gssapi,cn=auth" mech=GSSAPI sasl_ssf=56 ssf=56 Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=2 RESULT tag=97 err=0 text= Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=3 SRCH base="dc=lxd" scope=2 deref=0 filter="(objectClass=*)" Nov 16 16:34:51 cosmic-provider slapd[2339]: conn=1022 op=3 SRCH attr=* + The consumer also has a tgt now in /tmp: -rw--- 1 openldap openldap 1903 Nov 16 16:34 krb5cc_110 Consumer's packages: root@cosmic-consumer:~# apt-cache policy slapd slapd: Installed: 2.4.46+dfsg-5ubuntu1.1 Candidate: 2.4.46+dfsg-5ubuntu1.1 Version table: *** 2.4.46+dfsg-5ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages Cosmic verification succeeded. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Trusty: Fix Committed Status in openldap source package in Xenial: Fix Committed Status in openldap source package in Bionic: Fix Committed Status in openldap source package in Cosmic: Fix Committed Bug description: [Impact] When using syncrepl replication with openldap, the consumer needs to authenticate to the provider in order to perform the searches and fetch the data. When this authentication is a simple bind, a simple username/password pair is used and that can be easily supplied in a configuration file. When one wants to use a stronger authentication mechanism, like gssapi (kerberos), the authentication is based on keytab files and tickets. The consumer needs to obtain a ticket from the KDC, and use that ticket to authenticate itself with the provider. For users, it's a simple matter of running kinit(1) and providing a password. For services, the solution is to extract the key from the KDC and store it in a local keytab file, which is then used by the service to obtain the TGT. Problem is this TGT expires, and needs to be renewed periodically. Solutions have popped up for that issue, the most famous one being kstart (https://www.eyrie.org/~eagle/software/kstart/), but since the MIT kerberos 1.11 release, there is a simpler way. Via the default_client_keytab_name krb5.conf(5) option, one can specify the default location of a keytab file per local user. The kerberos library will then automatically use that file to obtain the TGT, and proceed as usual from there. The default value of that setting is /etc/krb5/user//client.keytab. Turns out the openldap slapd apparmor profile doesn't account for that, and blocks attempts to read that file. It also blocks reading the TGT that is obtained and stored in /tmp/krb5cc_, resulting
[Touch-packages] [Bug 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
Bionic verification Reproducing the bug with: root@bionic-consumer:~# apt-cache policy slapd slapd: Installed: 2.4.45+dfsg-1ubuntu1 Candidate: 2.4.45+dfsg-1ubuntu1 Version table: *** 2.4.45+dfsg-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Provider logs as soon as the consumer finished setup, showing replication attempt that didn't complete: Nov 16 16:40:30 bionic-provider slapd[1710]: conn=1004 fd=12 ACCEPT from IP=10.0.100.14:34322 (IP=0.0.0.0:389) Nov 16 16:40:30 bionic-provider slapd[1710]: conn=1004 op=0 UNBIND Nov 16 16:40:30 bionic-provider slapd[1710]: conn=1004 fd=12 closed Host logs showing apparmor denied messages: [sex nov 16 14:40:29 2018] audit: type=1400 audit(1542386430.603:919): apparmor="DENIED" operation="open" namespace="root//lxd-bionic-consumer_" profile="/usr/sbin/slapd" name="/etc/krb5/user/111/client.keytab" pid=17456 comm="slapd" requested_mask="r" denied_mask="r" fsuid=165647 ouid=165536 Updating the consumer's packages: root@bionic-consumer:~# apt-cache policy slapd slapd: Installed: 2.4.45+dfsg-1ubuntu1.1 Candidate: 2.4.45+dfsg-1ubuntu1.1 Version table: *** 2.4.45+dfsg-1ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages Replication attempt succeeded (provider's logs): Nov 16 16:42:42 bionic-provider slapd[1710]: conn=1007 op=2 BIND dn="" method=163 Nov 16 16:42:42 bionic-provider slapd[1710]: conn=1007 op=2 BIND authcid="consumer" authzid="consumer" Nov 16 16:42:42 bionic-provider slapd[1710]: conn=1007 op=2 BIND dn="uid=consumer,cn=gssapi,cn=auth" mech=GSSAPI sasl_ssf=56 ssf=56 Nov 16 16:42:42 bionic-provider slapd[1710]: conn=1007 op=2 RESULT tag=97 err=0 text= Nov 16 16:42:42 bionic-provider slapd[1710]: conn=1007 op=3 SRCH base="dc=lxd" scope=2 deref=0 filter="(objectClass=*)" Nov 16 16:42:42 bionic-provider slapd[1710]: conn=1007 op=3 SRCH attr=* + Consumer has kerberos ticket in /tmp: -rw--- 1 openldap openldap 1903 Nov 16 16:42 krb5cc_111 Bionic verification succeeded. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Trusty: Fix Committed Status in openldap source package in Xenial: Fix Committed Status in openldap source package in Bionic: Fix Committed Status in openldap source package in Cosmic: Fix Committed Bug description: [Impact] When using syncrepl replication with openldap, the consumer needs to authenticate to the provider in order to perform the searches and fetch the data. When this authentication is a simple bind, a simple username/password pair is used and that can be easily supplied in a configuration file. When one wants to use a stronger authentication mechanism, like gssapi (kerberos), the authentication is based on keytab files and tickets. The consumer needs to obtain a ticket from the KDC, and use that ticket to authenticate itself with the provider. For users, it's a simple matter of running kinit(1) and providing a password. For services, the solution is to extract the key from the KDC and store it in a local keytab file, which is then used by the service to obtain the TGT. Problem is this TGT expires, and needs to be renewed periodically. Solutions have popped up for that issue, the most famous one being kstart (https://www.eyrie.org/~eagle/software/kstart/), but since the MIT kerberos 1.11 release, there is a simpler way. Via the default_client_keytab_name krb5.conf(5) option, one can specify the default location of a keytab file per local user. The kerberos library will then automatically use that file to obtain the TGT, and proceed as usual from there. The default value of that setting is /etc/krb5/user//client.keytab. Turns out the openldap slapd apparmor profile doesn't account for that, and blocks attempts to read that file. It also blocks reading the TGT that is obtained and stored in /tmp/krb5cc_, resulting in such DENIED errors in the logs: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 Since the slapd apparmor is enabled by default, this blocks the usage of this very helpful feature. Also considering that kerberos/gssapi errors are usually hard to debug, it might take a while for an admin to figure out what is going on. The fix is to u
[Touch-packages] [Bug 1803749] [NEW] apt.Cache.clear() may set apt.Package.is_auto_removable to False
Public bug reported: While triaging LP: #1803587 I found that originally autoremovable packages were handled as newly autoremovable ones by unattended-upgrades due to not finding all of them at the beginning of u-u's run. The root cause seems to be cache.clear() resetting pkg.is_auto_removable to False under some circumstances I haven't fully narrowed down. The reproduction is as follows: Set up a Bionic (or later) system with autoremovable packages, packages upgradable from -security and blacklist at least one upgradable package and apply the following patch to u-u: root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig /usr/bin/unattended-upgrade --- /usr/bin/unattended-upgrade.orig2018-11-16 16:17:58.522583254 + +++ /usr/bin/unattended-upgrade 2018-11-16 16:36:12.226675870 + @@ -948,7 +948,9 @@ def rewind_cache(cache, pkgs_to_upgrade): # type: (apt.Cache, List[apt.Package]) -> None """ set the cache back to the state with packages_to_upgrade """ +print([pkg.name for pkg in cache if pkg.is_auto_removable]) cache.clear() +print([pkg.name for pkg in cache if pkg.is_auto_removable]) for pkg2 in pkgs_to_upgrade: pkg2.mark_install(from_user=not pkg2.is_auto_installed) if cache.broken_count > 0: Run u-u to observe cache.clear() resetting the list of autoremovable packages: ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: systemd Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Using (^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools) regexp to find kernel packages Using (^linux-image.*4.15.0-38-generic|^linux-headers.*4.15.0-38-generic|^linux-image-extra.*4.15.0-38-generic|^linux-modules.*4.15.0-38-generic|^linux-modules-extra.*4.15.0-38-generic|^linux-signed-image.*4.15.0-38-generic|^kfreebsd-image.*4.15.0-38-generic|^kfreebsd-headers.*4.15.0-38-generic|^gnumach-image.*4.15.0-38-generic|4.15.0-38-generic.*-modules|4.15.0-38-generic.*-kernel|^linux-backports-modules-.*.*4.15.0-38-generic|^linux-modules-.*.*4.15.0-38-generic|^linux-tools.*4.15.0-38-generic|^linux-cloud-tools.*4.15.0-38-generic) regexp to find running kernel packages Checking: apport ([]) adjusting candidate version: apport=2.20.9-0ubuntu7.1 ... Checking: libnss-systemd ([, ]) skipping blacklisted package systemd pkg systemd package has been blacklisted sanity check failed ['libfreetype6'] [] ... ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1803749 Title: apt.Cache.clear() may set apt.Package.is_auto_removable to False Status in python-apt package in Ubuntu: New Bug description: While triaging LP: #1803587 I found that originally autoremovable packages were handled as newly autoremovable ones by unattended- upgrades due to not finding all of them at the beginning of u-u's run. The root cause seems to be cache.clear() resetting pkg.is_auto_removable to False under some circumstances I haven't fully narrowed down. The reproduction is as follows: Set up a Bionic (or later) system with autoremovable packages, packages upgradable from -security and blacklist at least one upgradable package and apply the following patch to u-u: root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig /usr/bin/unattended-upgrade --- /usr/bin/unattended-upgrade.orig 2018-11-16 16:17:58.522583254 + +++ /usr/bin/unattended-upgrade 2018-11-16 16:36:12.226675870 + @@ -948,7 +948,9 @@ def rewind_cache(cache, pkgs_to_upgrade): # type: (apt.Cache, List[apt.Package]) -> None """ set the cache back to the state with packages_to_upgrade """ +print([pkg.name for pkg in cache if pkg.is_auto_removable]) cache.clear() +print([pkg.name for pkg in cache if pkg.is_auto_removable]) for pkg2 in pkgs_to_upgrade: pkg2.mark_install(from_user=not pkg2.is_auto_installed) if cache.broken_count > 0: Run u-u to observe cache.clear() resetting the list of autoremovable packages: ~# /usr/bin/unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: systemd Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Using (^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-mo
[Touch-packages] [Bug 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
xenial verification First confirming the bug Package on the consumer: root@xenial-consumer:~# apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.3 Version table: *** 2.4.42+dfsg-2ubuntu3.3 500 500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages As soon as consumer setup is done, provider logs the attempted replication: Nov 16 16:53:21 xenial-provider slapd[2189]: conn=1004 fd=13 ACCEPT from IP=10.0.100.180:40382 (IP=0.0.0.0:389) Nov 16 16:53:21 xenial-provider slapd[2189]: conn=1004 op=0 UNBIND Nov 16 16:53:21 xenial-provider slapd[2189]: conn=1004 fd=13 closed Host has apparmor denied error: [sex nov 16 14:53:21 2018] audit: type=1400 audit(1542387201.938:973): apparmor="DENIED" operation="open" namespace="root//lxd-xenial-consumer_" profile="/usr/sbin/slapd" name="/etc/krb5/user/112/client.keytab" pid=7896 comm="slapd" requested_mask="r" denied_mask="r" fsuid=165648 ouid=165536 Consumer also logs replication error: Nov 16 16:53:21 xenial-consumer slapd[2024]: slap_client_connect: URI=ldap://xenial-provider.lxd ldap_sasl_interactive_bind_s failed (-2) Nov 16 16:53:21 xenial-consumer slapd[2024]: do_syncrepl: rid=001 rc -1 retrying Updating the packages on the consumer: root@xenial-consumer:~# apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.4 Candidate: 2.4.42+dfsg-2ubuntu3.4 Version table: *** 2.4.42+dfsg-2ubuntu3.4 500 500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages Provier logs show replication worked this time: Nov 16 16:55:32 xenial-provider slapd[2189]: conn=1007 op=2 BIND authcid="consumer" authzid="consumer" Nov 16 16:55:32 xenial-provider slapd[2189]: conn=1007 op=2 BIND dn="uid=consumer,cn=gssapi,cn=auth" mech=GSSAPI sasl_ssf=56 ssf=56 Nov 16 16:55:32 xenial-provider slapd[2189]: conn=1007 op=2 RESULT tag=97 err=0 text= Nov 16 16:55:32 xenial-provider slapd[2189]: conn=1007 op=3 SRCH base="dc=lxd" scope=2 deref=0 filter="(objectClass=*)" Nov 16 16:55:32 xenial-provider slapd[2189]: conn=1007 op=3 SRCH attr=* + Consumer has a kerberos ticket in /tmp: -rw--- 1 openldap openldap 1903 Nov 16 16:55 krb5cc_112 Xenial verification succeeded. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Trusty: Fix Committed Status in openldap source package in Xenial: Fix Committed Status in openldap source package in Bionic: Fix Committed Status in openldap source package in Cosmic: Fix Committed Bug description: [Impact] When using syncrepl replication with openldap, the consumer needs to authenticate to the provider in order to perform the searches and fetch the data. When this authentication is a simple bind, a simple username/password pair is used and that can be easily supplied in a configuration file. When one wants to use a stronger authentication mechanism, like gssapi (kerberos), the authentication is based on keytab files and tickets. The consumer needs to obtain a ticket from the KDC, and use that ticket to authenticate itself with the provider. For users, it's a simple matter of running kinit(1) and providing a password. For services, the solution is to extract the key from the KDC and store it in a local keytab file, which is then used by the service to obtain the TGT. Problem is this TGT expires, and needs to be renewed periodically. Solutions have popped up for that issue, the most famous one being kstart (https://www.eyrie.org/~eagle/software/kstart/), but since the MIT kerberos 1.11 release, there is a simpler way. Via the default_client_keytab_name krb5.conf(5) option, one can specify the default location of a keytab file per local user. The kerberos library will then automatically use that file to obtain the TGT, and proceed as usual from there. The default value of that setting is /etc/krb5/user//client.keytab. Turns out the openldap slapd apparmor profile doesn't account for that, and blocks attempts to read that file. It also blocks reading the TGT that is obtained and stored in /tmp/krb5cc_, resulting in such DENIED errors in the logs: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 Since the slapd apparmor is enabled by default, this blocks the usage of this ver
[Touch-packages] [Bug 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager
@vorlon: OK, let's use this bug to track the improvement for u-m. While triaging I found LP: #1803749 , which you may have hit if you have Unattended-Upgrade::Remove-New-Unused-Dependencie set to False. Is that the case on your system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1803587 Title: kernel from bionic did not get autoremoved by either unattended- upgrades or update-manager Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: I happened to run apt manually on my system this morning to remove a package, and I was informed: The following packages were automatically installed and are no longer required: linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic linux-modules-extra-4.15.0-36-generic This was surprising, since I have run update-manager yesterday (with no intervening reboot), and unattended-upgrades is enabled, and both of those packages should have already removed this stale kernel before now. After apt autoremove, my current installed packages are: $ dpkg -l linux-image'*' | grep ^ii ii linux-image-4.18.0-10-generic 4.18.0-10.11 amd64Signed kernel image generic ii linux-image-4.18.0-11-generic 4.18.0-11.12 amd64Signed kernel image generic ii linux-image-generic4.18.0.11.12 amd64Generic Linux kernel image $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803587/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
To add to the above: shutting down the laptop and then starting from there in Ubuntu, as suggested in one of the workarounds above, actually made the sound work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor
** Attachment added: "dmseg file" https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+attachment/5213529/+files/dmesg ** Tags added: 18.10 cosmic ** Tags added: hid ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-common (Ubuntu) Importance: Undecided Status: New -- 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/1803752 Title: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor Status in ubuntu-mate: New Status in mate-common package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Ever since upgrading to 18.10 plugging in external monitors has been buggy. Device Lenovo T460s. Ubuntu-Mate 18.10. Plugging in External monitor using mini-display port causes keyboard to be unresponsive. Mouse buttons as well. though can still move mouse on screen. Plugging in and out using arndr sometimes resolves this. Notwithstanding, no smooth transition to multimonitor mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+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 1300382] Re: input events not being flushed in browser until pressing hardware keys
I have recently got to know about the input event not flushing in the browser which is really a very big problem which you may face and really encounter the problem. I have got to know about the description of the bug and visited https://babasupport.org/mac/resolve-mac-error-code-43/ for the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1300382 Title: input events not being flushed in browser until pressing hardware keys Status in Oxide: Fix Released Status in ubuntu-keyboard: Fix Released Status in The Webapps-core project: Invalid Status in oxide-qt package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Released Bug description: using webbrowser-app from Silo 9 and oxide in universe Log in to Facebook on the phone Click "comment" in someone's post Start typing Expected results: The comment button should become enabled so you can submit comment Actual results: The comment button always stays disabled. Tested this on webbrowser-app on desktop with oxide (explicilty loading m.facebook.com) and becomes enabled as it should after typing. Seems specific to device. Guessing it's a UA String issue. Is there a way to see the JS console to see if a JS error is occuring? To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1300382/+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 1454450] Re: Bluetooth mouse laggy and erratic
^I agree with John that this must be related to both Bluetooth and Wifi on at the same time. I don't have an RJ45-USBC dongle to confirm however Im able to see an increase in how often the shuddering occurs when using a 5GHz band wifi vs a 2.4GHz. I was suggested to update the BIOS by another thread post and that did improve my performance, now the shuddering only begins after some network usage while before the mouse was not usable even when sitting at the desktop. Reloading the btusb module using modprobe like suggested above also removes the shuddering only to come back after a few moments. Inserting the supplied BT dongle instead of using the internal radios also eliminates the shuddering but then removes one of the highly valuable USB ports and inevitably will have this port fail on my as this dongle catches on everything when I move the notebook in and out of my backpack. True story =( Im experience this on both Ubuntu 16.04 and Kubuntu 18.04 on a XPS 13 9350 with latest BIOS Mouse Im using is the Logitech 2S Anywhere or the 2S Master -- 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/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mi
[Touch-packages] [Bug 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager
$ grep -r Remove-New /etc/apt /etc/apt/apt.conf.d/50unattended-upgrades://Unattended-Upgrade::Remove-New-Unused-Dependencies "false"; $ So it appears this is commented out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1803587 Title: kernel from bionic did not get autoremoved by either unattended- upgrades or update-manager Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: I happened to run apt manually on my system this morning to remove a package, and I was informed: The following packages were automatically installed and are no longer required: linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic linux-modules-extra-4.15.0-36-generic This was surprising, since I have run update-manager yesterday (with no intervening reboot), and unattended-upgrades is enabled, and both of those packages should have already removed this stale kernel before now. After apt autoremove, my current installed packages are: $ dpkg -l linux-image'*' | grep ^ii ii linux-image-4.18.0-10-generic 4.18.0-10.11 amd64Signed kernel image generic ii linux-image-4.18.0-11-generic 4.18.0-11.12 amd64Signed kernel image generic ii linux-image-generic4.18.0.11.12 amd64Generic Linux kernel image $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803587/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
trusty verification reproducing the bug: slapd: Installed: 2.4.31-1+nmu2ubuntu8.4 Candidate: 2.4.31-1+nmu2ubuntu8.4 Version table: *** 2.4.31-1+nmu2ubuntu8.4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages As soon as the consumer is setup, the provider logs the attempted replication: Nov 16 18:24:12 trusty-provider slapd[3414]: conn=1004 fd=19 ACCEPT from IP=10.0.100.46:58678 (IP=0.0.0.0:389) Nov 16 18:24:12 trusty-provider slapd[3414]: conn=1004 op=0 UNBIND Nov 16 18:24:12 trusty-provider slapd[3414]: conn=1004 fd=19 closed Consumer logs that it was a failure: Nov 16 18:24:12 trusty-consumer slapd[3408]: slap_client_connect: URI=ldap://trusty-provider.lxd ldap_sasl_interactive_bind_s failed (-2) Nov 16 18:24:12 trusty-consumer slapd[3408]: do_syncrepl: rid=001 rc -1 retrying Host logs apparmor denied message: [sex nov 16 16:24:11 2018] audit: type=1400 audit(1542392652.079:1015): apparmor="DENIED" operation="open" namespace="root//lxd-trusty-consumer_" profile="/usr/sbin/slapd" name="/etc/krb5/user/106/client.keytab" pid=22261 comm="slapd" requested_mask="r" denied_mask="r" fsuid=165642 ouid=165536 Updating the openldap packages on the consumer: root@trusty-consumer:~# apt-cache policy slapd slapd: Installed: 2.4.31-1+nmu2ubuntu8.5 Candidate: 2.4.31-1+nmu2ubuntu8.5 Version table: *** 2.4.31-1+nmu2ubuntu8.5 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages Provider logs the replication: Nov 16 18:26:15 trusty-provider slapd[3414]: conn=1007 op=2 BIND authcid="consumer" authzid="consumer" Nov 16 18:26:15 trusty-provider slapd[3414]: conn=1007 op=2 BIND dn="uid=consumer,cn=gssapi,cn=auth" mech=GSSAPI sasl_ssf=56 ssf=56 Nov 16 18:26:15 trusty-provider slapd[3414]: conn=1007 op=2 RESULT tag=97 err=0 text= Nov 16 18:26:15 trusty-provider slapd[3414]: conn=1007 op=3 SRCH base="dc=lxd" scope=2 deref=0 filter="(objectClass=*)" Nov 16 18:26:15 trusty-provider slapd[3414]: conn=1007 op=3 SRCH attr=* + Consumer has kerberos ticket: -rw--- 1 openldap openldap 1903 Nov 16 18:26 krb5cc_106 Trusty verification succeeded. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Trusty: Fix Committed Status in openldap source package in Xenial: Fix Committed Status in openldap source package in Bionic: Fix Committed Status in openldap source package in Cosmic: Fix Committed Bug description: [Impact] When using syncrepl replication with openldap, the consumer needs to authenticate to the provider in order to perform the searches and fetch the data. When this authentication is a simple bind, a simple username/password pair is used and that can be easily supplied in a configuration file. When one wants to use a stronger authentication mechanism, like gssapi (kerberos), the authentication is based on keytab files and tickets. The consumer needs to obtain a ticket from the KDC, and use that ticket to authenticate itself with the provider. For users, it's a simple matter of running kinit(1) and providing a password. For services, the solution is to extract the key from the KDC and store it in a local keytab file, which is then used by the service to obtain the TGT. Problem is this TGT expires, and needs to be renewed periodically. Solutions have popped up for that issue, the most famous one being kstart (https://www.eyrie.org/~eagle/software/kstart/), but since the MIT kerberos 1.11 release, there is a simpler way. Via the default_client_keytab_name krb5.conf(5) option, one can specify the default location of a keytab file per local user. The kerberos library will then automatically use that file to obtain the TGT, and proceed as usual from there. The default value of that setting is /etc/krb5/user//client.keytab. Turns out the openldap slapd apparmor profile doesn't account for that, and blocks attempts to read that file. It also blocks reading the TGT that is obtained and stored in /tmp/krb5cc_, resulting in such DENIED errors in the logs: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 Since the slapd apparmor is enabled by default, this blocks the usage of this very helpful feature. Also considering that kerberos/gssapi errors are usually hard to debug, it mig
[Touch-packages] [Bug 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager
@vorlon: OK, being commented out (and not set elsewhere) makes it default to True. The misleading comment is fixed in later releases. ** Changed in: update-manager (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager + Update-manager does not remove autoremovable kernel packages _before_installing new (kernel) packages ** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1803587 Title: Update-manager does not remove autoremovable kernel packages _before_installing new (kernel) packages Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Triaged Bug description: I happened to run apt manually on my system this morning to remove a package, and I was informed: The following packages were automatically installed and are no longer required: linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic linux-modules-extra-4.15.0-36-generic This was surprising, since I have run update-manager yesterday (with no intervening reboot), and unattended-upgrades is enabled, and both of those packages should have already removed this stale kernel before now. After apt autoremove, my current installed packages are: $ dpkg -l linux-image'*' | grep ^ii ii linux-image-4.18.0-10-generic 4.18.0-10.11 amd64Signed kernel image generic ii linux-image-4.18.0-11-generic 4.18.0-11.12 amd64Signed kernel image generic ii linux-image-generic4.18.0.11.12 amd64Generic Linux kernel image $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803587/+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 1803587] Re: kernel from bionic did not get autoremoved by either unattended-upgrades or update-manager
In my tests u-u successfully removed the kernels as new unused packages even when hitting LP: #1803749 for the record. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1803587 Title: Update-manager does not remove autoremovable kernel packages _before_installing new (kernel) packages Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Triaged Bug description: I happened to run apt manually on my system this morning to remove a package, and I was informed: The following packages were automatically installed and are no longer required: linux-image-4.15.0-36-generic linux-modules-4.15.0-36-generic linux-modules-extra-4.15.0-36-generic This was surprising, since I have run update-manager yesterday (with no intervening reboot), and unattended-upgrades is enabled, and both of those packages should have already removed this stale kernel before now. After apt autoremove, my current installed packages are: $ dpkg -l linux-image'*' | grep ^ii ii linux-image-4.18.0-10-generic 4.18.0-10.11 amd64Signed kernel image generic ii linux-image-4.18.0-11-generic 4.18.0-11.12 amd64Signed kernel image generic ii linux-image-generic4.18.0.11.12 amd64Generic Linux kernel image $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1803587/+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 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor
What GPU and video driver are you using? -- 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/1803752 Title: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor Status in ubuntu-mate: New Status in mate-common package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Ever since upgrading to 18.10 plugging in external monitors has been buggy. Device Lenovo T460s. Ubuntu-Mate 18.10. Plugging in External monitor using mini-display port causes keyboard to be unresponsive. Mouse buttons as well. though can still move mouse on screen. Plugging in and out using arndr sometimes resolves this. Notwithstanding, no smooth transition to multimonitor mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+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 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor
I believe that is a kernel problem. -- 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/1803752 Title: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor Status in ubuntu-mate: New Status in mate-common package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Ever since upgrading to 18.10 plugging in external monitors has been buggy. Device Lenovo T460s. Ubuntu-Mate 18.10. Plugging in External monitor using mini-display port causes keyboard to be unresponsive. Mouse buttons as well. though can still move mouse on screen. Plugging in and out using arndr sometimes resolves this. Notwithstanding, no smooth transition to multimonitor mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+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 1799693] Re: Stable libopus-1.3 released
Ubuntu's opus comes directly from Debian. Therefore, it would be helpful if someone would report this issue to Debian. There are some instructions available for that at https://wiki.ubuntu.com/Debian/Bugs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opus in Ubuntu. https://bugs.launchpad.net/bugs/1799693 Title: Stable libopus-1.3 released Status in opus package in Ubuntu: New Bug description: Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now outdated and technically marked as a beta. http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1799693/+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
Re: [Touch-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor
VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Kernel driver in use: i915 Kernel modules: i915 AND attached Xorg.0.log On Fri, Nov 16, 2018 at 11:00 AM APolihron wrote: > What GPU and video driver are you using? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1803752 > > Title: > HID inputs (mouse buttons and keyboard) stop responding when plug in > DP monitor > > Status in ubuntu-mate: > New > Status in mate-common package in Ubuntu: > New > Status in xorg package in Ubuntu: > New > > Bug description: > Ever since upgrading to 18.10 plugging in external monitors has been > buggy. > > Device Lenovo T460s. Ubuntu-Mate 18.10. > > Plugging in External monitor using mini-display port causes keyboard > to be unresponsive. Mouse buttons as well. though can still move mouse > on screen. Plugging in and out using arndr sometimes resolves this. > Notwithstanding, no smooth transition to multimonitor mode. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+subscriptions > ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/bugs/1803752/+attachment/5213531/+files/Xorg.0.log -- 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/1803752 Title: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor Status in ubuntu-mate: New Status in mate-common package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Ever since upgrading to 18.10 plugging in external monitors has been buggy. Device Lenovo T460s. Ubuntu-Mate 18.10. Plugging in External monitor using mini-display port causes keyboard to be unresponsive. Mouse buttons as well. though can still move mouse on screen. Plugging in and out using arndr sometimes resolves this. Notwithstanding, no smooth transition to multimonitor mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1803752/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@Karen Chaltikian Good news! Although I've tried this on my UX391UA, but without success. Can you describe your procedure step-by-step? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1803655] Re: screen flickering and appearing green colour at screen edges
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1803655 Title: screen flickering and appearing green colour at screen edges Status in xorg package in Ubuntu: New Bug description: recently ihave installed ubuntu 18.10 version from 16.04 lts but it has started screen flickering and screen appearing green at edges of the screen before logging the system the screen flickering is appearing and with green color after login the screen flickering dissapears .I hope you will find the solution and this problem is appearing from 5 days is this a software or hardware problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 16 09:45:49 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:365e] InstallationDate: Installed on 2018-11-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 10104 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=UUID=72505e1c-0f9f-4860-b3d1-59f626acc7e8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: ELKT29AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Win8 STD EM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrELKT29AUS:bd12/03/2012:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvrWin8STDEMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: IdeaCentre dmi.product.name: 10104 dmi.product.sku: LENOVO_MT_1010 dmi.product.version: Lenovo C440 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1803655/+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 1803470] Re: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1803470 Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: There seems to be a programming error in aptdaemon, the software that allows you to install/remove software and to perform other package management related tasks. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-39-generic 4.15.0-39.42 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1187 F pulseaudio juan 1898 F pulseaudio /dev/snd/controlC0: gdm1187 F pulseaudio juan 1898 F pulseaudio Date: Wed Nov 14 19:17:20 2018 Df: Dmesg: ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=45ec2b0c-3e08-4c6c-abb9-645caf9f287b InstallationDate: Installed on 2018-02-15 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: TOSHIBA Satellite P55t-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=efe479bd-ea94-4b87-91c8-74190bf43a1b ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to bionic on 2018-10-14 (31 days ago) dmi.bios.date: 12/09/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG20SQ dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.50:bd12/09/2014:svnTOSHIBA:pnSatelliteP55t-B:pvrPSPNVU-03XNC1:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite P55t-B dmi.product.version: PSPNVU-03XNC1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1803470/+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 1803524] Re: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803524 Title: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.6 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:i386: Install NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules 70-snap.core.rules Date: Fri Nov 9 16:32:19 2018 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-15 (518 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer INC. KGP(M)E-D16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=9b274dac-457e-417c-8141-15ff0892fa08 ro quiet splash vt.handoff=1 Python3Details: /usr/local/bin/python3.6, Python 3.6.4, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-09-06 (69 days ago) dmi.bios.date: 02/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: KGP(M)E-D16 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xxG dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3201:bd02/19/2013:svnASUSTeKComputerINC.:pnKGP(M)E-D16:pvrSystemVersion:rvnASUSTeKComputerINC.:rnKGP(M)E-D16:rvrRev1.xxG:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: KGP(M)E-D16 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803524/+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 1803524] Re: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803524 Title: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.6 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:i386: Install NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules 70-snap.core.rules Date: Fri Nov 9 16:32:19 2018 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-15 (518 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer INC. KGP(M)E-D16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=9b274dac-457e-417c-8141-15ff0892fa08 ro quiet splash vt.handoff=1 Python3Details: /usr/local/bin/python3.6, Python 3.6.4, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package udev 237-3ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-09-06 (69 days ago) dmi.bios.date: 02/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: KGP(M)E-D16 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xxG dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3201:bd02/19/2013:svnASUSTeKComputerINC.:pnKGP(M)E-D16:pvrSystemVersion:rvnASUSTeKComputerINC.:rnKGP(M)E-D16:rvrRev1.xxG:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: KGP(M)E-D16 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803524/+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 1552792] Re: gnome software leaves dependencies installed
I've verified this fixes the issue with the following versions: packagekit=1.1.9-1ubuntu2.18.04.4 gnome-software=3.28.1-0ubuntu4.18.04.7 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1788220] Re: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap
** Changed in: ubuntu-meta (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1788220 Title: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap Status in gnome-calculator package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Ubuntu 18.04 includes the calculator as a snap. The standard installation of snap, with no custom snap apps installed other than what Ubuntu installs by default, takes a whooping 1.6GB of hard disk. Calc takes forever to start in a modern machine compared to the normal calc installed with APT, creates snap files in the user's home dir (with name $HOME/snap). This is ridiculous. Snap is immature, there's no sysadmin tool support, and it's not ready to make it the default for standard Ubuntu LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1788220/+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 1800836] Re: systemd-networkd doesn't process IPv6 RA properly
systemd from Cosmic is not affected by this bug: # apt-cache policy systemd systemd: Installed: 239-7ubuntu10.3 Candidate: 239-7ubuntu10.3 Version table: *** 239-7ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 239-7ubuntu10 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages ** Summary changed: - systemd-networkd doesn't IPv6 RA properly + systemd-networkd doesn't process IPv6 RA properly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1800836 Title: systemd-networkd doesn't process IPv6 RA properly Status in systemd package in Ubuntu: New Bug description: The gateways/firewalls in our DC are highly available and when there is a failover their IPv6 VIP (fe80::1) moves from the master to the backup one. We found that only our Bionic VMs behind those gateways had issues after a failover. Those Bionic VMs were all running systemd-networkd (from netplan) and before the failover they had: $ ip -6 route ... default via fe80::1 dev eth0 proto ra metric 1024 pref medium But after a failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 And after another failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1 This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as their default gateway even when this gateway is unavailable: $ ip -6 route get :: :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src fe80::a800:ff:fe51:8c37 metric 1024 pref medium We concluded it was a systemd-networkd bug after checking that the following combinations were NOT affected: 1) Xenial+4.4 kernel 2) Xenial+4.15 kernel 3) Bionic+ifupdown Additional information: $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 08:47:28 2018 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836/+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 1797649] Re: receive authentication canceled in terminal when changing options in "Other Software"
*WORKAROUND* in Ubuntu 18.10: $ sudo -i # software-properties-gtk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1797649 Title: receive authentication canceled in terminal when changing options in "Other Software" Status in software-properties package in Ubuntu: Confirmed Bug description: I've tried to disable some PPAs in the "Other Software" tab of software-properties and whenever I check a box for the first time I get a message in the terminal about "ERROR:root:Authentication canceled, changes have not been saved" (although an authentication dialog has not appeared) and the dialog box greys out. However, frequently upon clicking the box for a second time (when it is greyed out) I am then presented with an authentication dialog. This seems quite odd. I've tested this the following versions of software-properties-gtk. 0.96.24.32.5 from bionic 0.26.27 from cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+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 1792874] Re: Bluetooth will get off after turn it on few seconds.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1792874 Title: Bluetooth will get off after turn it on few seconds. Status in bluez package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Test machine: M820z-1 Image: sutton-wilkes-xenial-amd64-20180717-84 (OEM image) CPU: Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92] BIOS: M1NKT25A Steps: 1. Installed system and log in. 2. Connect BT device (computer). 3. Transfer a file to the device 4. Open system settings -> Bluetooth window 5. Navigate to Bluetooth logo in top of right corner 6. Unfold and hover on the connecting device 7. Verify the result Actual result: Bluetooth will turn off few seconds later. Please refer to the video in attachment. Expected result: Bluetooth should not turn off automatically. Note: The issue can reproduce on Ubuntu 16.04 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792874/+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 1792954] Re: Search for bluetooth devices stuck
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1792954 Title: Search for bluetooth devices stuck Status in bluez package in Ubuntu: Expired Bug description: This seems to be an old bug with no visible resolution. As of today September 17 2018 (!) I am running this os64@os64-desktop:~$ uname -a Linux os64-desktop 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792954/+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 1792874] Re: Bluetooth will get off after turn it on few seconds.
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1792874 Title: Bluetooth will get off after turn it on few seconds. Status in bluez package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Test machine: M820z-1 Image: sutton-wilkes-xenial-amd64-20180717-84 (OEM image) CPU: Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92] BIOS: M1NKT25A Steps: 1. Installed system and log in. 2. Connect BT device (computer). 3. Transfer a file to the device 4. Open system settings -> Bluetooth window 5. Navigate to Bluetooth logo in top of right corner 6. Unfold and hover on the connecting device 7. Verify the result Actual result: Bluetooth will turn off few seconds later. Please refer to the video in attachment. Expected result: Bluetooth should not turn off automatically. Note: The issue can reproduce on Ubuntu 16.04 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1792874/+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 1803804] Re: Recommends: ssh-import-id missing in openssh 1:7.9p1-1
The build log also shows that the Ubuntu default path is not being set: --with-default-path=/usr/local/bin:/usr/bin:/bin:/usr/games -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1803804 Title: Recommends: ssh-import-id missing in openssh 1:7.9p1-1 Status in openssh package in Ubuntu: New Bug description: ssh-import-id shows on http://people.canonical.com/~ubuntu-archive /component-mismatches as wanting demotion to universe. This is because openssh-server in disco has dropped its Recommends on this package, which appears to be a misbuild. From the build log, I see: dh_gencontrol -- -V'openssh-server:Recommends=' (https://launchpad.net/ubuntu/+source/openssh/1:7.9p1-1/+build/15632765) But debian/rules has: ifeq ($(UBUNTU),yes) server_recommends := ssh-import-id else server_recommends := endif [...] override_dh_gencontrol: dh_gencontrol -- -V'openssh-server:Recommends=$(server_recommends)' So this is supposed to be set but isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1803804/+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 1803804] [NEW] Recommends: ssh-import-id missing in openssh 1:7.9p1-1
Public bug reported: ssh-import-id shows on http://people.canonical.com/~ubuntu-archive /component-mismatches as wanting demotion to universe. This is because openssh-server in disco has dropped its Recommends on this package, which appears to be a misbuild. >From the build log, I see: dh_gencontrol -- -V'openssh-server:Recommends=' (https://launchpad.net/ubuntu/+source/openssh/1:7.9p1-1/+build/15632765) But debian/rules has: ifeq ($(UBUNTU),yes) server_recommends := ssh-import-id else server_recommends := endif [...] override_dh_gencontrol: dh_gencontrol -- -V'openssh-server:Recommends=$(server_recommends)' So this is supposed to be set but isn't. ** Affects: openssh (Ubuntu) Importance: High Status: New ** Changed in: openssh (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1803804 Title: Recommends: ssh-import-id missing in openssh 1:7.9p1-1 Status in openssh package in Ubuntu: New Bug description: ssh-import-id shows on http://people.canonical.com/~ubuntu-archive /component-mismatches as wanting demotion to universe. This is because openssh-server in disco has dropped its Recommends on this package, which appears to be a misbuild. From the build log, I see: dh_gencontrol -- -V'openssh-server:Recommends=' (https://launchpad.net/ubuntu/+source/openssh/1:7.9p1-1/+build/15632765) But debian/rules has: ifeq ($(UBUNTU),yes) server_recommends := ssh-import-id else server_recommends := endif [...] override_dh_gencontrol: dh_gencontrol -- -V'openssh-server:Recommends=$(server_recommends)' So this is supposed to be set but isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1803804/+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 1803804] Re: Recommends: ssh-import-id missing in openssh 1:7.9p1-1
printf debugging of debian/rules shows that $(UBUNTU) is set to the literal string: dpkg-vendor --derives-from && echo yes || echo no That seems unexpected. It seems /usr/share/dpkg/vendor.mk is incorrect about the usage of dpkg_vendor_derives_from and that this has never worked as advertised, but that openssh in disco has switched to using this function for the first time, introducing the regression. ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Canonical Server Team (canonical-server) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1803804 Title: Recommends: ssh-import-id missing in openssh 1:7.9p1-1 Status in openssh package in Ubuntu: New Bug description: ssh-import-id shows on http://people.canonical.com/~ubuntu-archive /component-mismatches as wanting demotion to universe. This is because openssh-server in disco has dropped its Recommends on this package, which appears to be a misbuild. From the build log, I see: dh_gencontrol -- -V'openssh-server:Recommends=' (https://launchpad.net/ubuntu/+source/openssh/1:7.9p1-1/+build/15632765) But debian/rules has: ifeq ($(UBUNTU),yes) server_recommends := ssh-import-id else server_recommends := endif [...] override_dh_gencontrol: dh_gencontrol -- -V'openssh-server:Recommends=$(server_recommends)' So this is supposed to be set but isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1803804/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I have the issue as well. I have a dual boot system with following. Zenbook UX490UAR Ubuntu 18.04.1 Windows 10 I think this is due to windows not properly shutting down and holding on to a hardware device, although not sure how. Managed to resolve by a full shutdown. i.e. go to shutdown on the windows start menu and hold shift while pressing restart. A screen will appear where you can select to shutdown. After the restart and logging into ubuntu, sound works . For the volume control related bug, there was a guide here : https://askubuntu.com/questions/906303/volume-control-on-asus-zenbook-3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1728988] Re: poppler crashes on this file
This file no longer crashes evince/poppler on Ubuntu 18.04 "Bionic Beaver" 64 bit with libcairo2 1.15.10-2 ** Changed in: cairo (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1728988 Title: poppler crashes on this file Status in cairo package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Invalid Bug description: When opening the PDF file available at: https://mega.nz/#!QUlxRabb!CkbkbKanfjFCO6OaKCoFq2_yHoIWChV-ruc3PHB87E8 evince/pdftocairo are core dumping. As far as I can tell it's because the underlying lib (cairo/poppler) has a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1728988/+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