[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
** Attachment added: "1871148-vm-no-varlib-mount_diddledan.svg" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5350256/+files/1871148-vm-no-varlib-mount_diddledan.svg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in apparmor package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1869747] [NEW] Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
Public bug reported: I am unsure where the problem stems, but changes since the 25th have caused my system to fail to initialise the Xorg display. The console remains operational for debugging. I am currently using ZFS snapshots to use the system as it was on the 25th of March 2020 because that is the last snapshot before this issue. This bug was captured using ubuntu-bug when booted into the broken (i.e. not working) latest snapshot of my filesystem. The versions of packages from the not broken (i.e. correctly working) earlier snapshot of my filesystem are: libnvidia-cfg1-440:amd64 440.64-0ubuntu2 libnvidia-common-440 440.64-0ubuntu2 libnvidia-compute-440:amd64 440.64-0ubuntu2 libnvidia-compute-440:i386 440.64-0ubuntu2 libnvidia-decode-440:amd64 440.64-0ubuntu2 libnvidia-decode-440:i386440.64-0ubuntu2 libnvidia-encode-440:amd64 440.64-0ubuntu2 libnvidia-encode-440:i386440.64-0ubuntu2 libnvidia-fbc1-440:amd64 440.64-0ubuntu2 libnvidia-fbc1-440:i386 440.64-0ubuntu2 libnvidia-gl-440:amd64 440.64-0ubuntu2 libnvidia-gl-440:i386440.64-0ubuntu2 libnvidia-ifr1-440:amd64 440.64-0ubuntu2 libnvidia-ifr1-440:i386 440.64-0ubuntu2 nvidia-compute-utils-440 440.64-0ubuntu2 nvidia-dkms-440 440.64-0ubuntu2 nvidia-driver-440440.64-0ubuntu2 nvidia-kernel-common-440 440.64-0ubuntu2 nvidia-kernel-source-440 440.64-0ubuntu2 nvidia-prime 0.8.14 nvidia-settings 440.64-0ubuntu1 nvidia-utils-440 440.64-0ubuntu2 xserver-xorg-video-nvidia-440440.64-0ubuntu2 $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Mon Mar 30 15:49:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-UD5 TH dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal nvidia regression reproducible ubuntu ** Tags added: champagne ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
** Also affects: command-not-found (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1633319] Re: memory leak in indicator-datetime
This affects Eoan if you install Ubuntu proper, add accounts to "Online Accounts", then switch into an Ubuntu Mate session (installed via Apt on top of the same system - apt install ubuntu-mate-desktop^) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also affects Disco ** Tags added: disco -- 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/1820074 Title: Running glxgears with Indirect GLX crashes Xorg Status in mesa package in Ubuntu: New Bug description: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Touch-packages] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
The crash is in XorgLogOld.txt, and the backtrace reproduced here: [ 9027.274] (EE) Backtrace: [ 9027.274] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b9210ba229] [ 9027.275] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fdf6dcc4e1f] [ 9027.275] (EE) 2: /usr/lib/xorg/Xorg (ResetCurrentRequest+0xb) [0x55b9210b92ab] [ 9027.275] (EE) 3: /usr/lib/xorg/Xorg (DRI2WaitSwap+0x56) [0x55b921086716] [ 9027.275] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.275] (EE) 4: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7faa20] [ 9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.276] (EE) 5: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7f3010] [ 9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.276] (EE) 6: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7eefd0] [ 9027.276] (EE) 7: /usr/lib/xorg/Xorg (dri3_send_open_reply+0xe2a) [0x55b92108b12a] [ 9027.277] (EE) 8: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x55b920f60be4] [ 9027.277] (EE) 9: /usr/lib/xorg/Xorg (CloseDownClient+0x5f) [0x55b920f5acbf] [ 9027.277] (EE) 10: /usr/lib/xorg/Xorg (OsCleanup+0x591) [0x55b9210bb021] [ 9027.277] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1c3) [0x55b9210b3b93] [ 9027.277] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x10c) [0x55b920f5b72c] [ 9027.277] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55b920f5f906] [ 9027.278] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fdf6daea09b] [ 9027.278] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x55b920f4967a] [ 9027.278] (EE) [ 9027.278] (EE) Segmentation fault at address 0x8 [ 9027.278] (EE) Fatal server error: [ 9027.278] (EE) Caught signal 11 (Segmentation fault). Server aborting -- 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/1820074 Title: Running glxgears with Indirect GLX crashes Xorg Status in mesa package in Ubuntu: New Bug description: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Touch-packages] [Bug 1820074] [NEW] Running glxgears with Indirect GLX crashes Xorg
Public bug reported: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Touch-packages] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also crashes with nVidia using nouveau drivers (see attached log) ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+attachment/5246195/+files/Xorg.0.log.old -- 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/1820074 Title: Running glxgears with Indirect GLX crashes Xorg Status in mesa package in Ubuntu: New Bug description: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Touch-packages] [Bug 1747281] Re: 18.04 nvidia driver installation failure
Likely duplicate of #1752053 -- 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/1747281 Title: 18.04 nvidia driver installation failure Status in software-properties package in Ubuntu: Confirmed Bug description: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Despite the recent switch to Xorg from Wayland, the NVIDIA driver installed via the Additional Drivers tab in software-properties-gtk still does not properly install the driver. Although the initial install appears to successfully complete, the system does not load properly on the next reboot and yields an unusable system; GDM login is never displayed. Looking at the log from the reboot following the NVIDIA driver install, the Nouveau driver appears to still be in use for video, while the NVIDIA driver is associated with HDMI audio: Feb 3 12:23:38 panther2 kernel: [2.097370] nouveau :01:00.0: NVIDIA GF1 16 (0cf200a1) Feb 3 12:23:38 panther2 kernel: [2.212100] usb 4-1: new full-speed USB devi ce number 2 using ohci-pci Feb 3 12:23:38 panther2 kernel: [2.226839] nouveau :01:00.0: bios: vers ion 70.26.3a.00.01 Feb 3 12:23:38 panther2 kernel: [2.376254] nouveau :01:00.0: fb: 1024 M iB GDDR5 Feb 3 12:23:38 panther2 kernel: [3.676249] [TTM] Zone kernel: Available gr aphics memory: 2019142 kiB Feb 3 12:23:38 panther2 kernel: [3.676250] [TTM] Initializing pool allocato r Feb 3 12:23:38 panther2 kernel: [3.676255] [TTM] Initializing DMA pool allo cator Feb 3 12:23:38 panther2 kernel: [3.676270] nouveau :01:00.0: DRM: VRAM: 1024 MiB Feb 3 12:23:38 panther2 kernel: [3.676272] nouveau :01:00.0: DRM: GART: 1048576 MiB Feb 3 12:23:38 panther2 kernel: [3.676276] nouveau :01:00.0: DRM: TMDS table version 2.0 Feb 3 12:23:38 panther2 kernel: [3.676277] nouveau :01:00.0: DRM: DCB v ersion 4.0 Feb 3 12:23:38 panther2 kernel: [3.676280] nouveau :01:00.0: DRM: DCB o utp 00: 02000300 Feb 3 12:23:38 panther2 kernel: [3.676282] nouveau :01:00.0: DRM: DCB o utp 01: 01000302 00020030 Feb 3 12:23:38 panther2 kernel: [3.676284] nouveau :01:00.0: DRM: DCB o utp 02: 04011380 Feb 3 12:23:38 panther2 kernel: [3.676285] nouveau :01:00.0: DRM: DCB o utp 03: 08011382 00020030 Feb 3 12:23:38 panther2 kernel: [3.676287] nouveau :01:00.0: DRM: DCB o utp 04: 02022362 00020010 Feb 3 12:23:38 panther2 kernel: [3.676288] nouveau :01:00.0: DRM: DCB c onn 00: 1030 Feb 3 12:23:38 panther2 kernel: [3.676290] nouveau :01:00.0: DRM: DCB c onn 01: 00010130 Feb 3 12:23:38 panther2 kernel: [3.676291] nouveau :01:00.0: DRM: DCB c onn 02: 2261 Feb 3 12:23:38 panther2 kernel: [3.677453] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Feb 3 12:23:38 panther2 kernel: [3.677454] [drm] Driver supports precise vb lank timestamp query. Feb 3 12:23:38 panther2 kernel: [3.728374] nouveau :01:00.0: DRM: MM: u sing COPY0 for buffer copies Feb 3 12:23:38 panther2 kernel: [3.847607] nouveau :01:00.0: DRM: alloc ated 1920x1080 fb: 0x6, bo 8e45e7246000 Feb 3 12:23:38 panther2 kernel: [3.859190] fbcon: nouveaufb (fb0) is primar y device Feb 3 12:23:38 panther2 kernel: [3.859275] Console: switching to colour fra me buffer device 240x67 Feb 3 12:23:38 panther2 kernel: [3.859314] nouveau :01:00.0: fb0: nouve aufb frame buffer device Feb 3 12:23:38 panther2 kernel: [3.936124] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) LoadModule: "gl x" Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) Loading /usr/li b/xorg/modules/extensions/libglx.so Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) Module glx: ven dor="X.Org Foundation" Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: #011compiled for 1.1 9.6, module version = 1.0.0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: #011ABI class: X.Org Server Extension, version 10.0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nvidia as autoconfigured driver 0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nouveau as autoconfigured driver 1 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nvidia as autoconfigured driver 2 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nouveau as autoconfigured driver 3 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched modeset ting as autoconfigured driver 4
[Touch-packages] [Bug 1752111] Re: Xorg on Bionic doesn't start anymore
*** This bug is a duplicate of bug 1752053 *** https://bugs.launchpad.net/bugs/1752053 ** This bug is no longer a duplicate of bug 1752307 incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf ** This bug has been marked a duplicate of bug 1752053 nvidia-390 fails to boot graphical display -- 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/1752111 Title: Xorg on Bionic doesn't start anymore Status in xorg package in Ubuntu: New Bug description: Xorg on Bionic went from "totally working" with nVidia drivers, to "OutputClass is Broken and doesn't support 'Option' and 'ModulePath'" for some reason. See the Xorg logs attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: 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 390.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: /dev/nvme0n1p3: clean, 588184/15138816 files, 9668625/60549376 blocks /dev/nvme0n1p3: clean, 594889/15138816 files, 9852207/60549376 blocks /dev/nvme0n1p3: clean, 601030/15138816 files, 9914821/60549376 blocks Date: Tue Feb 27 06:27:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Device [1043:8694] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8513] InstallationDate: Installed on 2018-02-27 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9b6920f1-6ce1-4284-a76f-e0474605c41f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-G GAMING (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd09/14/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-GGAMING(WI-FIAC):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 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+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/+bug/1752111/+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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
*** This bug is a duplicate of bug 1752053 *** https://bugs.launchpad.net/bugs/1752053 ** This bug has been marked a duplicate of bug 1752053 nvidia-390 fails to boot graphical display -- 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/1752307 Title: incompatible configuration in default nvidia-drm-outputclass- ubuntu.conf Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. -- Added by diddledan: -- From the log file: Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf "Option" is not a valid keyword in this section. Commenting out this line proceeds to alert about the next line which is also an "Option" line, and commenting that out moves the alert onto the final line, "ModulePath", before EndSection. Commenting all three offending lines fixes this particular issue. On diddledan's system, which may be an anomaly, Xorg then complains that libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so. -- End added by diddledan -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: 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 390.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Wed Feb 28 04:47:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] MachineType: Hewlett-Packard h8-1559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: AMI dmi.bios.version: v8.10 dmi.board.name: 2AC8 dmi.board.vendor: Gigabyte dmi.board.version: 1.2 dmi.chassis.asset.tag: MXX30503QF dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: h8-1559 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 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+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/+bug/1752307/+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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** Tags removed: single-occurrence -- 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/1752307 Title: incompatible configuration in default nvidia-drm-outputclass- ubuntu.conf Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. -- Added by diddledan: -- From the log file: Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf "Option" is not a valid keyword in this section. Commenting out this line proceeds to alert about the next line which is also an "Option" line, and commenting that out moves the alert onto the final line, "ModulePath", before EndSection. Commenting all three offending lines fixes this particular issue. On diddledan's system, which may be an anomaly, Xorg then complains that libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so. -- End added by diddledan -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: 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 390.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Wed Feb 28 04:47:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] MachineType: Hewlett-Packard h8-1559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: AMI dmi.bios.version: v8.10 dmi.board.name: 2AC8 dmi.board.vendor: Gigabyte dmi.board.version: 1.2 dmi.chassis.asset.tag: MXX30503QF dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: h8-1559 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 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+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/+bug/1752307/+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 1752111] Re: Xorg on Bionic doesn't start anymore
*** This bug is a duplicate of bug 1752307 *** https://bugs.launchpad.net/bugs/1752307 ** This bug has been marked a duplicate of bug 1752307 incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf -- 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/1752111 Title: Xorg on Bionic doesn't start anymore Status in xorg package in Ubuntu: New Bug description: Xorg on Bionic went from "totally working" with nVidia drivers, to "OutputClass is Broken and doesn't support 'Option' and 'ModulePath'" for some reason. See the Xorg logs attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: 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 390.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: /dev/nvme0n1p3: clean, 588184/15138816 files, 9668625/60549376 blocks /dev/nvme0n1p3: clean, 594889/15138816 files, 9852207/60549376 blocks /dev/nvme0n1p3: clean, 601030/15138816 files, 9914821/60549376 blocks Date: Tue Feb 27 06:27:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Device [1043:8694] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8513] InstallationDate: Installed on 2018-02-27 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9b6920f1-6ce1-4284-a76f-e0474605c41f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-G GAMING (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd09/14/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-GGAMING(WI-FIAC):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 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+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/+bug/1752111/+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 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** Description changed: - Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. + Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. + + -- + Added by diddledan: + -- + From the log file: + Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf + "Option" is not a valid keyword in this section. + + Commenting out this line proceeds to alert about the next line which is + also an "Option" line, and commenting that out moves the alert onto the + final line before EndSection. Commenting all three offending lines fixes + this particular issue. + + On diddledan's system, which may be an anomaly, Xorg then complains that libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so. + -- + End added by diddledan + -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: 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 390.25 Wed Jan 24 20:02:43 PST 2018 - GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.25 Wed Jan 24 20:02:43 PST 2018 + GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Wed Feb 28 04:47:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] + NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] MachineType: Hewlett-Packard h8-1559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: AMI dmi.bios.version: v8.10 dmi.board.name: 2AC8 dmi.board.vendor: Gigabyte dmi.board.version: 1.2 dmi.chassis.asset.tag: MXX30503QF dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: h8-1559 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 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+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Description changed: Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. -- Added by diddledan: -- From the log file: Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf - "Option" is not a valid keyword in this section. + "Option" is not a valid keyword in this section. Commenting out this line proceeds to alert about the next line which is also an "Option" line, and commenting that out moves the alert onto the - final line before EndSection. Commenting all three offending lines fixes - this particular issue. + final line, "ModulePath", before EndSection. Commenting all three + offending lines fixes this particular issue. On diddledan's system, which may be an anomaly, Xorg then complains that libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so. -- End added by diddledan -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules:
[Touch-packages] [Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** Summary changed: - xorg + incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf -- 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/1752307 Title: incompatible configuration in default nvidia-drm-outputclass- ubuntu.conf Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: 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 390.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Wed Feb 28 04:47:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] MachineType: Hewlett-Packard h8-1559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: AMI dmi.bios.version: v8.10 dmi.board.name: 2AC8 dmi.board.vendor: Gigabyte dmi.board.version: 1.2 dmi.chassis.asset.tag: MXX30503QF dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: h8-1559 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 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+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/+bug/1752307/+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 654493] Re: infinit loop with openssl s_client -connect xmpp-gmx.gmx.net:5222 -starttls xmpp
attempt to fix upstream but link ** Bug watch added: OpenSSL RT #2812 http://rt.openssl.org/Ticket/Display.html?id=2812 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/654493 Title: infinit loop with openssl s_client -connect xmpp-gmx.gmx.net:5222 -starttls xmpp Status in OpenSSL cryptography and SSL/TLS toolkit: New Status in openssl package in Ubuntu: Confirmed Bug description: Binary package hint: openssl i try to check sertifikat of jabber server i use, with fallowing result: openssl s_client -connect xmpp-gmx.gmx.net:5222 -starttls xmpp -debug CONNECTED(0003) write to 0x258bf60 [0x7fff56396990] (121 bytes = 121 (0x79)) - 3c 73 74 72 65 61 6d 3a-73 74 72 65 61 6d 20 78 stream:stream x 0010 - 6d 6c 6e 73 3a 73 74 72-65 61 6d 3d 27 68 74 74 mlns:stream='htt 0020 - 70 3a 2f 2f 65 74 68 65-72 78 2e 6a 61 62 62 65 p://etherx.jabbe 0030 - 72 2e 6f 72 67 2f 73 74-72 65 61 6d 73 27 20 78 r.org/streams' x 0040 - 6d 6c 6e 73 3d 27 6a 61-62 62 65 72 3a 63 6c 69 mlns='jabber:cli 0050 - 65 6e 74 27 20 74 6f 3d-27 78 6d 70 70 2d 67 6d ent' to='xmpp-gm 0060 - 78 2e 67 6d 78 2e 6e 65-74 27 20 76 65 72 73 69 x.gmx.net' versi 0070 - 6f 6e 3d 27 31 2e 30 27-3eon='1.0' read from 0x258bf60 [0x2582e70] (8192 bytes = 238 (0xEE)) - 3c 3f 78 6d 6c 20 76 65-72 73 69 6f 6e 3d 27 31 ?xml version='1 0010 - 2e 30 27 3f 3e 3c 73 74-72 65 61 6d 3a 73 74 72 .0'?stream:str 0020 - 65 61 6d 20 78 6d 6c 6e-73 3d 27 6a 61 62 62 65 eam xmlns='jabbe 0030 - 72 3a 63 6c 69 65 6e 74-27 20 78 6d 6c 6e 73 3a r:client' xmlns: 0040 - 73 74 72 65 61 6d 3d 27-68 74 74 70 3a 2f 2f 65 stream='http://e 0050 - 74 68 65 72 78 2e 6a 61-62 62 65 72 2e 6f 72 67 therx.jabber.org 0060 - 2f 73 74 72 65 61 6d 73-27 20 69 64 3d 27 32 34 /streams' id='24 0070 - 34 32 33 35 33 33 38 37-27 20 66 72 6f 6d 3d 27 42353387' from=' 0080 - 67 6d 78 2e 64 65 27 20-78 6d 6c 3a 6c 61 6e 67 gmx.de' xml:lang 0090 - 3d 27 65 6e 27 3e 3c 73-74 72 65 61 6d 3a 65 72 ='en'stream:er 00a0 - 72 6f 72 3e 3c 68 6f 73-74 2d 75 6e 6b 6e 6f 77 rorhost-unknow 00b0 - 6e 20 78 6d 6c 6e 73 3d-27 75 72 6e 3a 69 65 74 n xmlns='urn:iet 00c0 - 66 3a 70 61 72 61 6d 73-3a 78 6d 6c 3a 6e 73 3a f:params:xml:ns: 00d0 - 78 6d 70 70 2d 73 74 72-65 61 6d 73 27 2f 3e 3c xmpp-streams'/ 00e0 - 2f 73 74 72 65 61 6d 3a-65 72 72 6f 72 3e /stream:error read from 0x258bf60 [0x2582e70] (8192 bytes = 16 (0x10)) - 3c 2f 73 74 72 65 61 6d-3a 73 74 72 65 61 6d 3e /stream:stream read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes = 0 (0x0)) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openssl 0.9.8o-1ubuntu4 Uname: Linux 2.6.36-rc4-00134-g03a7ab0 x86_64 Architecture: amd64 Date: Mon Oct 4 12:39:43 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100803.1) ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: openssl To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/654493/+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 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT
ok, I spoke too soon about it being fixed. The problem is back again. I've created a fully-symbolised backtrace using apport. Find it attached. ** Attachment added: properly traced backtrace https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235567/+attachment/4245825/+files/_usr_lib_ibus_ibus-ui-gtk3.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235567 Title: ibus-ui-gtk3 crashed with SIGABRT Status in IBus: Unknown Status in “ibus” package in Ubuntu: Triaged Bug description: Restarted system after installing updates was greeting me with that message ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 08:17:10 2013 Disassembly: = 0x7f62f38f4f77: Cannot access memory at address 0x7f62f38f4f77 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2013-06-12 (114 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1235567/+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 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT
seems fixed after installing ibus-dbg along with the utopic updates accumulated for a week or so installed just now at 09:40 GMT on the 20th october. Unsure whether it was the ibus-dbg and it's dependencies or the latest utopic updates that fixed things. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235567 Title: ibus-ui-gtk3 crashed with SIGABRT Status in IBus: Unknown Status in “ibus” package in Ubuntu: Triaged Bug description: Restarted system after installing updates was greeting me with that message ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 08:17:10 2013 Disassembly: = 0x7f62f38f4f77: Cannot access memory at address 0x7f62f38f4f77 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2013-06-12 (114 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1235567/+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 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT
adding upstream bugreport ** Bug watch added: IBus bugs #1744 http://code.google.com/p/ibus/issues/detail?id=1744 ** Changed in: ibus Importance: Undecided = Unknown ** Changed in: ibus Status: New = Unknown ** Changed in: ibus Remote watch: None = IBus bugs #1744 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235567 Title: ibus-ui-gtk3 crashed with SIGABRT Status in IBus: Unknown Status in “ibus” package in Ubuntu: Confirmed Bug description: Restarted system after installing updates was greeting me with that message ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 08:17:10 2013 Disassembly: = 0x7f62f38f4f77: Cannot access memory at address 0x7f62f38f4f77 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2013-06-12 (114 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1235567/+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 1369658] Re: Ubuntu 14.04.1 x86 uses wrong library search path order
I may be wrong on this assignment, but /etc/ld.so.conf.d/i386-linux- gnu.conf is handled by libc6 according to apt-file and Mark suggests that the order of this file is the source of the issue? ** Package changed: ubuntu = eglibc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1369658 Title: Ubuntu 14.04.1 x86 uses wrong library search path order Status in “eglibc” package in Ubuntu: New Bug description: Ubuntu 14.04.1 x86 uses wrong library search path order I was trying to link an app against /usr/lib/i386-linux-gnu/libEGL.so.1, but at runtime it kept finding /usr/lib/i386-linux-gnu/mesa-egl/libEGL.so.1. This is fixable several ways (including using -rpath or LD_LIBRARY_PATH), but I thought there might be something odd with the default library search order. I noticed the the search order defined by /etc/ld.so.conf causes /usr/lib/i386-linux-gnu/mesa-egl to be searched before /usr/lib/i386-linux-gnu, because /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf is found before /etc/ld.so.conf.d/i686-linux-gnu.conf. Suggested solutions (caveat: I don't fully understand why something things are named i386-* vs i686-*. ): 1. rename /etc/ld.so.conf.d/i686-linux-gnu.conf to /etc/ld.so.conf.d/i386-linux-gnu.conf, it would work as I expect and the linker would search /usr/lib/i386-linux-gnu before /usr/lib/i386-linux-gnu/mesa-egl 2. move the search path for /usr/lib/i386-linux-gnu from /etc/ld.so.conf.d/i686-linux-gnu.conf into a new /etc/ld.so.conf.d/i386-linux-gnu.conf 3. rename /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf to /etc/ld.so.conf.d/i686-linux-gnu_EGL.conf more /etc/ld.so.conf include /etc/ld.so.conf.d/*.conf more /etc/ld.so.conf.d/*.conf :: /etc/ld.so.conf.d/fakeroot-i386-linux-gnu.conf :: /usr/lib/i386-linux-gnu/libfakeroot :: /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf :: /usr/lib/i386-linux-gnu/mesa-egl :: /etc/ld.so.conf.d/i386-linux-gnu_GL.conf :: /usr/lib/i386-linux-gnu/mesa :: /etc/ld.so.conf.d/i686-linux-gnu.conf :: # Multiarch support /lib/i386-linux-gnu /usr/lib/i386-linux-gnu /lib/i686-linux-gnu /usr/lib/i686-linux-gnu :: 14.04 x86_64 doesn't have this issue because the conf file names all start with x86_64* and are read in the expected order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1369658/+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 1369658] Re: Ubuntu 14.04.1 x86 uses wrong library search path order
alternatively it might more likely be libegl1-mesa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1369658 Title: Ubuntu 14.04.1 x86 uses wrong library search path order Status in “eglibc” package in Ubuntu: New Bug description: Ubuntu 14.04.1 x86 uses wrong library search path order I was trying to link an app against /usr/lib/i386-linux-gnu/libEGL.so.1, but at runtime it kept finding /usr/lib/i386-linux-gnu/mesa-egl/libEGL.so.1. This is fixable several ways (including using -rpath or LD_LIBRARY_PATH), but I thought there might be something odd with the default library search order. I noticed the the search order defined by /etc/ld.so.conf causes /usr/lib/i386-linux-gnu/mesa-egl to be searched before /usr/lib/i386-linux-gnu, because /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf is found before /etc/ld.so.conf.d/i686-linux-gnu.conf. Suggested solutions (caveat: I don't fully understand why something things are named i386-* vs i686-*. ): 1. rename /etc/ld.so.conf.d/i686-linux-gnu.conf to /etc/ld.so.conf.d/i386-linux-gnu.conf, it would work as I expect and the linker would search /usr/lib/i386-linux-gnu before /usr/lib/i386-linux-gnu/mesa-egl 2. move the search path for /usr/lib/i386-linux-gnu from /etc/ld.so.conf.d/i686-linux-gnu.conf into a new /etc/ld.so.conf.d/i386-linux-gnu.conf 3. rename /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf to /etc/ld.so.conf.d/i686-linux-gnu_EGL.conf more /etc/ld.so.conf include /etc/ld.so.conf.d/*.conf more /etc/ld.so.conf.d/*.conf :: /etc/ld.so.conf.d/fakeroot-i386-linux-gnu.conf :: /usr/lib/i386-linux-gnu/libfakeroot :: /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf :: /usr/lib/i386-linux-gnu/mesa-egl :: /etc/ld.so.conf.d/i386-linux-gnu_GL.conf :: /usr/lib/i386-linux-gnu/mesa :: /etc/ld.so.conf.d/i686-linux-gnu.conf :: # Multiarch support /lib/i386-linux-gnu /usr/lib/i386-linux-gnu /lib/i686-linux-gnu /usr/lib/i686-linux-gnu :: 14.04 x86_64 doesn't have this issue because the conf file names all start with x86_64* and are read in the expected order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1369658/+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 1368687] Re: Post upgradation to Ubunto 14.04, Laptop is detecting wifi connection
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1368687 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs. ** Package changed: ubuntu = network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1368687 Title: Post upgradation to Ubunto 14.04, Laptop is detecting wifi connection Status in “network-manager” package in Ubuntu: New Bug description: Hi, Yesterday my Laptop automatically got upgraded to Ubunto 14.04. Post upgradation laptop is not detecting any Wifi connection. Normally at my residence 6-10 wifi connection are active. It is not detecting any one. Before upgrade internet was working perfectly fine. Laptop Dell Inspiron. Regards, Rohit Hirani To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368687/+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 1366854] Re: bluetooth will not enable stays blocked
Thank you for taking the time to report this bug and helping to make Ubuntu better. I believe you were right to file this under bluez, so I've reassigned it back there. While waiting for someone to take a look, please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1366854 ** Package changed: ubuntu = bluez (Ubuntu) -- 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/1366854 Title: bluetooth will not enable stays blocked Status in “bluez” package in Ubuntu: New Bug description: Since installation of 14.04.1 I've been trying to get bluetooth working. Under preferences bluetooth says it's disabled. So I did $rfkill list all, and that showed me that asus bluetooth is soft blocked. I did an $rfkill unblock all, and nothing. I have tried everything listed here: http://askubuntu.com/questions/521190 /bluetooth-disabled-asus-g750jm and the person answering my questions suggested I report it as a bug because I'm out of options. I'm running a ROG ASUS G750JM it's a fairly new gaming laptop, the modem installation went fine through the install process of ubuntu. But bluetooth hasn't worked yet. I'm not sure what package it is it's probably bluez and it's up to date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1366854/+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 1368167] Re: Keyboard: Different input for each window sources does not work after upgrading from 12.04 to 14.04
This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in ibus. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs. ** Package changed: ubuntu = ibus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1368167 Title: Keyboard: Different input for each window sources does not work after upgrading from 12.04 to 14.04 Status in “ibus” package in Ubuntu: New Bug description: After upgrading from 12.04 to 14.04 keyboard indicator ignores Different input for each window setting in System settings - layout remains the same on switching b/w windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1368167/+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 1368489] Re: trusty tahr upgrade system error, cups based.
** Package changed: ubuntu = cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1368489 Title: trusty tahr upgrade system error, cups based. Status in “cups” package in Ubuntu: New Bug description: DIST-UPGRADED to trusty tahr, what a mess. Previously fine-working auto-loaded canon printer, now toast. Annoying sys error, like others complain but diff. details as follow, hand typed best I can. Is it possible, linux is having viruses now? Keep asking me to sign into keyring; fix online did not solve. Afraid to sign in, as its similar to a windows virus popup, etc. Signs of browser virus, transposer of type, only in browser window typing/addy bar, all spelling jumbled in pairs. Even after purging/reinstalling chrome. Notice the below, says no log of upgrade, i did dist-upgrade, so should be there. 13.04 worked fine with printer. thinking apps, as keep failing weird errors, purged openshot, gimp, chromium-browser; reinstalled, all 3 bizarre problems. No effect. still have the typo backwards spelling-affecting thing similar to virus, tho browser now fully replaced. sys: dell latitude d620 amd64, running upgraded to trusty tahr; no google info, others similar, but not identical cups origin: Sorry, Ubuntu 14.04 has experienced an error: executable (hand typing) path: /usr/lib/x86)64-linux-gnu/cups-pk-helper-mechanism package cups-pk-helper 0.2.5-Oubuntu1 problem type - crash title cups-pk-helper-mechanism crashed wtih signal 5 in g_variant_new_va() apportversion: 2.14.1-Oubuntu3.4 Architecture: amd64 Core Dump (binary data) Date Sept. 9 ... Dependencies: adduser3.113+nmu3ubuntu3 apt-utils 1.0.1ubuntu2.1 base-passwd 3.5.33 busybox-initramfs 1:1.21.0-1ubuntu1 coreutils 8.21-1ubuntu5 cpio 2.11+dfsg-1ubuntu1 dbus 1.6.18-0ubuntu4.1 debconf 1.5.51ubuntu2 debianutils 4.4 dpkg 1.17.5ubuntu5.3 e2fslibs 1.42.9-3ubuntu1 e2fsprogs 1.42.9-3ubuntu1 findutils4.4.2-7 gcc-4.8-base 4.8.2-19ubuntu1 gcc-4.9-base 4.9-20140406-0ubuntu1 ifupdown 0.7.47.2ubuntu4.1 initramfs-tools 0.103ubuntu4.2 initramfs-tools-bin 0.103ubuntu4.2 initscripts 2.88dsf-41ubuntu6 insserv 1.14.0-5ubuntu2 iproute2 3.12.0-2 isc-dhcp-client 4.2.4-7ubuntu12 isc-dhcp-common 4.2.4-7ubuntu12 klibc-utils .20.3-0ubuntu1 kmod 14-0ubuntu6 krb5-locales 1.12+dfsg-2ubuntu4.2 libacl1 2.2.52-1 libapparmor1 2.8.95~2430-0ubuntu5 libapt-inst1.5 1.0.1ubuntu2.1 libapt-pkg4.12 1.0.1ubuntu2.1 libattr1 1:2.4.47-1ubuntu1 AN DA WHOLE SHOOTLOAD MORE THAT I CANNOT POSSIBLY TYPE. ITS MAKING SYS SO SLOW, CURSOR ON BROWSRE TAKES FOREVER TO UNFREEZE, FRUCKING UP MY SPELLING CONSTANTLY. LIST continues: disassembly: ubnhc of niternla addsy DsitorRleesae Uubnut 41.04 SEE THAT? I TYPED IT ACCURATELY, TOOK FOREVER TO SHOW, ALL JUMBLED: disassembly (bunch of IRQ looking addys) Distro Release: Ubuntu 14.04 Installation Date: 2014 7 30 Install media: trusty tahr amd64 arch: amd64 procCmdline: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism ProcEnviron (blank) ProcMaps: (ton of stuff) ProcStatus: name: cups-pk-helper- (ver batim) state S (sleeping) tgid: 13288 Ngid 0 Pid 13288 PPid 1 tracer Pid 0 Uid 0 0 0 0 Gid 0 0 0 0 FDSize 64 Groups 0 VMPeak: 307264 kb VMSize 241864 kb VmLck: 0 kb vmPin 0 kb VmHWM: 5016 kB vmRSS 5016 kB vmData: 148244 kB VmStk 136 kB vmExe 112 KB VmLib 10980 kB VmPTE: 208 kb vmSwap: 0 kb threads 3 sigQ 0/23835 sigPnd 00 shdPnd: SigBlk ditto SigIgn ditto SigCgt 00018000 CapInh all zeros CapPrm 001f Cap Eff 001 f CapBnd 001 f Seccomp 0 Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed ,1 Mems_allowed_list: 0 voluntary_ctxt_switches: 21 nonvoluntary_ctxt_switches: 2 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Registers: ton of stuff: Signal: 5 Source Package: cups-pk-helper Stacktrace: too much to type Tags: trusty Threadstacktrace (not typing) Uname: Linux 3.13.0-35-generic x86x64 UpgradeStatus: no upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1368489/+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 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs
assigning to cups package. Hans, please review the steps at the following link and attach the output from the commands to this bug. This will help to diagnose the issue: https://wiki.ubuntu.com/DebuggingPrintingProblems ** Package changed: ubuntu = cups (Ubuntu) ** Changed in: cups (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1366743 Title: Ubuntu 14.04 only prints LibreOffice Docs Status in “cups” package in Ubuntu: Incomplete Bug description: I use Ubuntu 14.04, a Logilink Fast Ethernet Printserver and a HP Color Laserjet 2550L. Under Ubuntu 12.10 everything worked fine and I could print any file. The printer is connected via a USB to the Printserver and adressed via HP Jet Direct. As already said, everything worked fine under 12.10 and I didn't change any settings on the printserver. I use the ubuntu tool for installing the printer, as a normal user not su. Searching the network, for network printers offers me three possibilities for adressing the printer. HP Jet Direct, IPP and LPD/LPR. I tried all of them with the same result. I use the drivers from the Database, not surprisingly HP/Color Laserjet 2550/HP Color Laserjet 2550 Series Postscript [en] (recommended). After installing the printer the first thing that fails is the Testpage. The ubunut printer spooler tells me that the job is in progress and the printer starts to blink to tell me that he is receiving input. Unfortunatly the job never starts or gets finished. After blinking quite a while the printer stops an nothing happes. Interestingly, after canceling the job on my computer and a restart of the printer, the printserver and my computer, I can open libre office writing Hello World go to print and the printer starts immediately and prints the correct result. But this only works for libreoffice and only with text, as soon as there is an image in the document it doesn't work. I can't print any pdf or even from gedit. Nothing works. Always the same as with the Testpage. Printer starts to blink but nothing happens. lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Thanks for Help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+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 1352255] Re: Impossible to configure network interface with only IPv6 address
drive-by: setting package to ifupdown ** Package changed: ubuntu = ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1352255 Title: Impossible to configure network interface with only IPv6 address Status in “ifupdown” package in Ubuntu: New Bug description: As it says on the tin. I'm unable to configure my Ubuntu 14.04 VM to have only an IPv6 address on boot-up. Dual stack works fine. My /etc/networking/interfaces looks like this: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet6 static address 2001:610:188:444::55 netmask 64 gateway 2001:610:188:444::1 autoconf 0 privext 0 accept_ra 0 dns-search terena.org dns-domain terena.org dns-nameservers 2001:610:1:800a:192:87:106:106 After boot-up there is only a link-local address: root@trusty-test:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:50:56:95:42:ab inet6 addr: fe80::250:56ff:fe95:42ab/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:101 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6644 (6.6 KB) TX bytes:2132 (2.1 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:240 errors:0 dropped:0 overruns:0 frame:0 TX packets:240 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:18192 (18.1 KB) TX bytes:18192 (18.1 KB) However, if I manually ifdown/ifup the interface, then things start working: root@trusty-test:~# ifdown eth0 root@trusty-test:~# ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:240 errors:0 dropped:0 overruns:0 frame:0 TX packets:240 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:18192 (18.1 KB) TX bytes:18192 (18.1 KB) root@trusty-test:~# ifup eth0 Waiting for DAD... Done root@trusty-test:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:50:56:95:42:ab inet6 addr: fe80::250:56ff:fe95:42ab/64 Scope:Link inet6 addr: 2001:610:188:444::55/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500
[Touch-packages] [Bug 1313292] Re: Keyboard layout changes not persistant
** Package changed: ubuntu = console-setup (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/1313292 Title: Keyboard layout changes not persistant Status in “console-setup” package in Ubuntu: New Bug description: In 14.04 I can set the correct keyboard layout (gb) via dpkg- reconfigure keyboard-configuration, and /etc/default/keyboard has the correct keyboard layout. However when I reboot the layout is set to us. This is possibly because the locale is en-nz and the us layout is the default for that locale. This worked in 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1313292/+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 1309812] Re: Unity launcher on one screen will only launch application once
** Package changed: ubuntu = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1309812 Title: Unity launcher on one screen will only launch application once Status in “unity” package in Ubuntu: New Bug description: When you have the unity launcher on one monitor only if you click on an icon to start an application then close the application the launcher icon will not start the application again. This behavior did not exist in 12.04 and is now appearing in 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1309812/+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 1295348] Re: interfaces(5) man page should mention 70-persistent-net.rules for consistent eth* naming
** Package changed: ubuntu = ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1295348 Title: interfaces(5) man page should mention 70-persistent-net.rules for consistent eth* naming Status in Manual Pages: New Status in “ifupdown” package in Ubuntu: New Bug description: Currently interfaces(5) says in KNOWN BUGS/LIMITATIONS: Unfortunately it can happen that the kernel assigns different physical interface names to the same hardware at different times; for example, what was called eth0 last time you booted is now called eth1 and vice versa. This creates a problem if you want to configure the interfaces appropriately. A way to deal with this problem is to use mapping scripts that choose logical interface names according to the properties of the interface hardware. See the get-mac-address.sh script in the examples directory for an example of such a mapping script. See also Debian bug #101728. The modern solution, described in Debian docs [1], is to use edit /etc/udev/rules.d/70-persistent-net.rules. I suggest we stop talking about confusing get-mac-address.sh script and instead replace the last two See… sentences with: See /etc/udev/rules.d/70-persistent-net.rules for a way to set interface names persistently. I realize that Debian docs is linked at the end of this man page. But it's not clear it will help with consistent names problem, because KNOWN BUGS says get-mac-address.sh is needed for this. Let's help people new to all these things! We've all been there :-) [1]: http://www.debian.org/doc/manuals/debian-reference/ch05.en.html To manage notifications about this bug go to: https://bugs.launchpad.net/manpages/+bug/1295348/+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 1175345] Re: After upgrading to Ubuntu 13.04 I can only start X by terminal startx and some windows are modal
** Package changed: ubuntu = lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1175345 Title: After upgrading to Ubuntu 13.04 I can only start X by terminal startx and some windows are modal Status in “lightdm” package in Ubuntu: New Bug description: After I have upgraded to Ubuntu 13.04 I first had a problem with my screen, it showed black with a cross cursor and nothing else. I got that fixed by installing latest NVIDIA drivers. Now, when I run gedit form a terminal I get the following message: (gedit:26002): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported This is my graphics RESULT OF: sudo lshw -c video *-display description: VGA compatible controller product: GF116 [GeForce GTS 450 Rev. 2] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:16 memory:fc00-fdff memory:d800-dfff memory:d400-d7ff ioport:bc00(size=128) memory:fe00-fe07 Further, windows are modal and cannot be resized! Any advice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1175345/+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
