[Touch-packages] [Bug 1751225] Re: apt update hangs when repository url is redirect url
I was sort of waiting for 16.04.4 to be released and then lost track of it. Uploading fixed version today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+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 1753532] Re: apt-get update doesn't get new packages
** Package changed: linux (Ubuntu) => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1753532 Title: apt-get update doesn't get new packages Status in apt package in Ubuntu: New Bug description: apt-get update and upgrade do not upgrade the system --Steps to Reproduce--- apt-get update and apt-get upgrade. It shows nothing to upgrade. But the kernel level is in an old version. New kernel packages are not shown in apt-cache. Somehow, the new packages are not being got from repo server when do apt-get update. Executed on 16.04.3 Btw, not all the Ubuntu servers have that issues. I crossed check the sources.list among the servers, there is no difference. So don't know what caused some of them cannot get any update from ubuntu repo. However, I can install individual packages via apt-get install command. There is not any error during the apt-get update && apt-get upgrade. It showed nothing to upgrade. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The servers were able to manually upgrade for a long time. But all the sudden, they are not upgradable. It looks it can not retrieve new kernel level packages during the apt-get update. The highest kernel level can be installed is 4.4.0-97.. not more higher.. HWS: I mirrored this problem description, to be able to get support for getting this fixed. Even it seems to be an environment problem. But direct Q&A will probably help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753532/+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 1753532] Re: apt-get update doesn't get new packages
I can only think of that you deleted the meta package on some servers, hence there are only new kernel packages available, but no meta package to pull them in. ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1753532 Title: apt-get update doesn't get new packages Status in apt package in Ubuntu: Incomplete Bug description: apt-get update and upgrade do not upgrade the system --Steps to Reproduce--- apt-get update and apt-get upgrade. It shows nothing to upgrade. But the kernel level is in an old version. New kernel packages are not shown in apt-cache. Somehow, the new packages are not being got from repo server when do apt-get update. Executed on 16.04.3 Btw, not all the Ubuntu servers have that issues. I crossed check the sources.list among the servers, there is no difference. So don't know what caused some of them cannot get any update from ubuntu repo. However, I can install individual packages via apt-get install command. There is not any error during the apt-get update && apt-get upgrade. It showed nothing to upgrade. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The servers were able to manually upgrade for a long time. But all the sudden, they are not upgradable. It looks it can not retrieve new kernel level packages during the apt-get update. The highest kernel level can be installed is 4.4.0-97.. not more higher.. HWS: I mirrored this problem description, to be able to get support for getting this fixed. Even it seems to be an environment problem. But direct Q&A will probably help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753532/+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 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"
** Also affects: gdm3 (Ubuntu Bionic) Importance: High Status: Confirmed ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Tags removed: rls-bb-incoming -- 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/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)" Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+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 1725921] Re: [regression] Combobox menus have gray text on gray background
** Also affects: ubuntu-themes (Ubuntu Bionic) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1725921 Title: [regression] Combobox menus have gray text on gray background Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Status in ubuntu-themes source package in Bionic: In Progress Bug description: See pictures. Application: pcbnew Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build Libraries: wxWidgets 3.0.3 libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 (+libidn2/2.0.2) librtmp/2.3 Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK Build Info: wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24 Boost: 1.62.0 Curl: 7.52.1 Compiler: GCC 6.3.0 with C++ ABI 1010 Build settings: USE_WX_GRAPHICS_CONTEXT=OFF USE_WX_OVERLAY=OFF KICAD_SCRIPTING=ON KICAD_SCRIPTING_MODULES=ON KICAD_SCRIPTING_WXPYTHON=ON KICAD_SCRIPTING_ACTION_MENU=ON BUILD_GITHUB_PLUGIN=ON KICAD_USE_OCE=ON KICAD_SPICE=ON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+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 1750122] [NEW] gnome-terminal right mouse click drop-down menu is small, unreadable and unusable
You have been subscribed to a public bug: Steps to reproduce: 1. Install Ubuntu 17.10 2. Launch `gnome-terminal` 3. Run some command - for example `uname -a` 4. Try to copy command output by right mouse click and selecting *Copy* from it. Expected results: Right mouse click drop-down menu has normal size, readable and usable Actual results: Right mouse click drop-down menu is small, unreadable and unusable (see screenshot). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 14:17:48 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful wayland-session -- gnome-terminal right mouse click drop-down menu is small, unreadable and unusable https://bugs.launchpad.net/bugs/1750122 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- 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 1726124] Re: DNS domain search paths not updated when VPN started
We won't be able to add the option to select between the two options this cycle. -- 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/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version
[Touch-packages] [Bug 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest
** Also affects: cups (Ubuntu Bionic) Importance: High Assignee: Till Kamppeter (till-kamppeter) Status: Confirmed ** Tags removed: rls-bb-incoming -- 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/1750514 Title: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest Status in CUPS: Unknown Status in cups package in Ubuntu: Confirmed Status in cups source package in Bionic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups. This problem was most recently seen with package version 2.2.6-5, the problem page at https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1750514/+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 1750122] Re: gnome-terminal right mouse click drop-down menu is small, unreadable and unusable
Reassigning, there's no way gnome-terminal could ask gtk to do this. Must be a gtk bug. ** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1750122 Title: gnome-terminal right mouse click drop-down menu is small, unreadable and unusable Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Launch `gnome-terminal` 3. Run some command - for example `uname -a` 4. Try to copy command output by right mouse click and selecting *Copy* from it. Expected results: Right mouse click drop-down menu has normal size, readable and usable Actual results: Right mouse click drop-down menu is small, unreadable and unusable (see screenshot). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 14:17:48 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1750122/+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 972537] Re: lightdm doesn't allow expired passwords
** Changed in: lightdm (Ubuntu Precise) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/972537 Title: lightdm doesn't allow expired passwords Status in lightdm package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in unity-greeter source package in Precise: Triaged Bug description: [Impact] Kerberos accounts on Ubuntu 12.04.1 can't force password changes via unity-greeter. [Test Case] 1. Set up a Kerberos server and client machine (see http://bobthegnome.blogspot.co.nz/2012/11/testing-kerberos-in-ubuntu.html) 2. Log into unity-greeter on client machine Expected result: Unity Greeter shows appropriate prompts to change password and can log in once password changed/ Observed result: Some prompts skipped, password not changed and unable to log in. [Regression Potential] Potential of breaking other authentication. This has been tested with the lightdm regression tests. In Ubuntu 12.04, when logging in using the unity greeter in lightdm (1.1.9-0ubuntu1) with a user using Kerberos with an expired password, the login screen doesn't give the user the appropriate feedback to set their new password. The text console works correctly. The previous LTS used GDM, which behaved correctly. The normal prompting for this is: Username: cmo-test Password: Password expired. You must change it now. Enter new password: Enter it again: Instead, in lightdm, it is: Username: cmo-test Password: Enter it again: The "Password expired" message is never shown, and "Enter it again" is shown in the box instead of "Enter new password". If you use lighdm- gtk-greeter, you get the "password expired" message printed under the box, but still have the same prompting, never asking for the new password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/972537/+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 856269] Re: lightdm does not ask for a new password with pam_winbind or pam_krb5 authentications when the password is expired
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/856269 Title: lightdm does not ask for a new password with pam_winbind or pam_krb5 authentications when the password is expired Status in lightdm package in Ubuntu: Confirmed Bug description: I'm using an up-to-date oneiric workstation joined through samba and winbind to an AD domain controlled by a Windows server. When the password of a domain user is expired and when pam_winbind is used as first authentication, lightdm does not ask for a new password and does not allow to login, displaying the message "Invalid password, please try again". Instead, when pam_krb5 is used as first authentication, lightdm asks two times for a password ("Enter it again:") and then allows to login even if the password is expired. When using a text console to login, the password changing dialog is immediately presented (as it happens in natty with gdm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/856269/+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 1350393] Re: Recent accountsservice update causes login window to hang
** Changed in: accountsservice (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1374379] Re: lightdm's session-cleanup-script get's called on unlock
** Changed in: lightdm/1.10 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.12 Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1374379 Title: lightdm's session-cleanup-script get's called on unlock Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in Light Display Manager 1.12 series: Won't Fix Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Won't Fix Bug description: When I unlock the screen after it has been locked by light locker the session-cleanup-script of lightdm get's called. I used to use the session-cleanup-script to umount some volumes on logout. I don't want to umount the volumes on lock or unlock. Maybe this is related to lightdm's #1249515 and might actually be a bug in lightdm!? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker 1.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 26 12:02:17 2014 InstallationDate: Installed on 2014-08-09 (47 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1374379/+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 1100469] Re: session processes left running after session logout
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1100469 Title: session processes left running after session logout Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Bug description: The fix for the zombie processes seems to have create the opposite issue, if you log in and out there is a session process left running, that happens for every session opened and closed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1100469/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen
** Changed in: lightdm/1.18 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.10 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.20 Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1656399 Title: Returning to existing session is unreliable and can leave on blank screen Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in Light Display Manager 1.20 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: [Impact] Due to a logic bug LightDM returning to an existing session from a greeter can be unreliable. This case is common in systems which use the greeter as a lock screen. The bug was introduced in revision 1954 to fix bug 1296276. The race condition seems to have been made more likely to the change in revision 2437 to fix bug 1637758. [Test Case] 1. Log into a session 2. Switch to the greeter (e.g. dm-tool switch-to-greeter) 3. Log in again Expected result Returned to existing session Observed result Not always returned, can end up on blank screen. Since this is a race condition this may not occur on some systems. [Regression Potential] Low, the fix is to correct a logic bug that made LightDM think it hadn't stopped a session correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1517685] Re: XDMCP server starts without authentication if configured key does not exist
** Changed in: lightdm (Ubuntu Precise) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1517685 Title: XDMCP server starts without authentication if configured key does not exist Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Confirmed Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Vivid: Fix Released Status in lightdm source package in Wily: Fix Released Bug description: [Impact] An incorrectly configured XDMCP server will start without authentication instead of disabling XDMCP / stopping LightDM. [Test Case] 1. Set up LightDM to run an XDMCP server using an XDM authentication key, i.e. in lightdm.conf: [XDMCPServer] enabled=true key=key-name 2. Do not create /etc/lightdm/keys.conf or do not define 'key-name' in keys.conf. 3. Start LightDM 4. Connect XDMCP client. Expected result: Either LightDM doesn't start or the XDMCP server doesn't start. Observed result: XDMCP server starts without authentication, any XDMCP client is able to connect. Debug message printed to log warning about missing key, but not easy to spot. [Regression Potential] Low - change is to not start LightDM if this case occurs. This could affect someone who currently has a misconfigured LightDM. In this case a warning message is printed to the log. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1517685/+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 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider
** Changed in: gnome-online-accounts (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1752472 Title: [ffe] Implement an Ubuntu Single Sign-on Provider Status in gnome-online-accounts: Confirmed Status in gnome-online-accounts package in Ubuntu: Fix Committed Bug description: Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to use this inside: 1) gnome-software 2) software-properties To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+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 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest
Reported upstream as https://github.com/apple/cups/issues/5258 Mike Sweet (author of CUPS) is looking into it. ** Bug watch added: github.com/apple/cups/issues #5258 https://github.com/apple/cups/issues/5258 ** Also affects: cups via https://github.com/apple/cups/issues/5258 Importance: Unknown Status: Unknown -- 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/1750514 Title: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest Status in CUPS: Unknown Status in cups package in Ubuntu: Confirmed Status in cups source package in Bionic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups. This problem was most recently seen with package version 2.2.6-5, the problem page at https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1750514/+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 915382] Re: ACPI events to shutdown/reboot don't generate a popup like after logging in
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/915382 Title: ACPI events to shutdown/reboot don't generate a popup like after logging in Status in lightdm package in Ubuntu: Triaged Bug description: There was a bug against virt-manager* where sending a "reboot" or "shutdown" event to a client seemingly doesn't do anything. Turns out that this only happens on the login screen, inside a session you get a popup asking what to do after the power button has been pushed. So something is wrong on the lightdm session, that prevents the popup from happening. This happens on real hw as well; if you hit the power button while looking at the login screen, nothing happens. * bug 228690 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/915382/+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 1753441] Re: [MIR] lame
This package has a long security history, and a currently left-open CVE because the upload of 3.100 did not include closing the active CVE. If there's a go-ahead from the Security Team (I'm not looking for a code review, just an acknowledgement that they are aware of the requirement for this package, and are fine with its current general state); then I see no issues with this MIR. ** Changed in: lame (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1751225] Re: apt update hangs when repository url is redirect url
Uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+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 1663157] Re: Guest session processes are not confined in 16.10 and newer releases
** Changed in: lightdm Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1663157 Title: Guest session processes are not confined in 16.10 and newer releases Status in Light Display Manager: New Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Status in lightdm source package in Artful: Fix Released Bug description: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1663157/+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 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Changed in: lightdm/1.10 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.2 Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Vivid: Fix Released Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+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 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()
** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1539995 Title: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates() Status in apport package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Partial Upgrade failed (crash) Ubuntu Mate 16 Alpha install testing on different machines. This machine Dell Optiplex 960 linuxpusher@linuxpusher-OptiPlex-960:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 linuxpusher@linuxpusher-OptiPlex-960:~$ sudo lshw [sudo] password for linuxpusher: linuxpusher-optiplex-960 description: Computer width: 64 bits capabilities: smbios-2.5 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 7819MiB *-cpu product: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority *-pci description: Host bridge product: 4 Series Chipset DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 03 width: 32 bits clock: 33MHz configuration: driver=agpgart-intel resources: irq:0 *-display:0 description: VGA compatible controller product: 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 03 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:fe80-febf memory:d000-dfff ioport:ecb0(size=8) *-display:1 UNCLAIMED description: Display controller product: 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 03 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:fe70-fe7f *-communication:0 description: Communication controller product: 4 Series Chipset HECI Controller vendor: Intel Corporation physical id: 3 bus info: pci@:00:03.0 version: 03 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=mei_me latency=0 resources: irq:34 memory:feda6000-feda600f *-ide description: IDE interface product: 4 Series Chipset PT IDER Controller vendor: Intel Corporation physical id: 3.2 bus info: pci@:00:03.2 version: 03 width: 32 bits clock: 66MHz capabilities: ide pm msi bus_master cap_list configuration: driver=ata_generic latency=0 resources: irq:18 ioport:fe80(size=8) ioport:fe90(size=4) ioport:fea0(size=8) ioport:feb0(size=4) ioport:fef0(size=16) *-communication:1 description: Serial controller product: 4 Series Chipset Serial KT Controller vendor: Intel Corporation physical id: 3.3 bus info: pci@:00:03.3 version: 03 width: 32 bits clock: 66MHz capabilities: pm msi 16550 bus_master cap_list configuration: driver=serial latency=0 resources: irq:17 ioport:ecb8(size=8) memory:fe6d8000-fe6d8fff *-network description: Ethernet interface product: 82567LM-3 Gigabit Network Connection vendor: Intel Corporation physical id: 19 bus info: pci@:00:19.0 logical name: enp0s25 version: 02
[Touch-packages] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1264543 Title: Trusty sometimes boots with inactive keyboard . Status in lightdm package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing ++F2 and withing the terminal. Logout and login from the terminal followed by ++F7 to reaccess X does not bring back the keyboard. My current workaround is to use suspend and then reactivate. This always finds the keyboard after which all is normal. The problem began after an update to something (I'm not sure what as the problem is spasmodic). It was first noticed some two or three weeks ago. WORKAROUND: Works in Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-all 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu3 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 CurrentDesktop: Unity CurrentDmesg: [ 26.884218] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 550.563790] audit_printk_skb: 138 callbacks suppressed [ 550.563794] type=1400 audit(1388145574.597:67): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2772 comm="apparmor_parser" [ 550.563802] type=1400 audit(1388145574.597:68): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" [ 550.564387] type=1400 audit(1388145574.597:69): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" Date: Fri Dec 27 16:23:05 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:9901] InstallationDate: Installed on 2013-10-21 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=b0a5ccea-5d55-4be4-838d-195afa498cc5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: FM2A55M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Fri Dec 27 11:50:49 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1264543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lis
[Touch-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Changed in: lightdm (Ubuntu Wily) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: New Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Vivid: Fix Released Status in lightdm source package in Wily: Fix Committed Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+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 1753663] Re: [Mesa 18.0] No 3D acceleration, using llvmpipe
a aptitude search nvidia | grep "i " gives only " i A libnvidia-common-390 - Shared files used by the NVIDIA libraries i A libnvidia-gl-390 - NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD " $ aptitude show libnvidia-common-390 Paket: libnvidia-common-390 Version: 390.25-0ubuntu4 Neu: ja Zustand: Installiert Automatisch installiert: ja Multi-Arch: foreign Priorität: optional Bereich: restricted/libs Verwalter: Ubuntu Core Developers Architektur: all Unkomprimierte Größe: 31,7 k Beschädigt: libnvidia-gl-390 (< 390.25-0ubuntu2~), libnvidia-gl-390:i386 (< 390.25-0ubuntu2~) Ersetzt: libnvidia-common, libnvidia-gl-390 (< 390.25-0ubuntu2~), libnvidia-gl-390:i386 (< 390.25-0ubuntu2~) Liefert: libnvidia-common, libnvidia-common-390:i386 (= 390.25-0ubuntu4) Beschreibung: Shared files used by the NVIDIA libraries This package provides a set of files that are required by the NVIDIA libraries. Homepage: http://www.nvidia.com $ aptitude show libnvidia-gl-390 Paket: libnvidia-gl-390 Version: 390.25-0ubuntu4 Neu: ja Zustand: Installiert Automatisch installiert: ja Multi-Arch: same Priorität: optional Bereich: restricted/libs Verwalter: Ubuntu Core Developers Architektur: amd64 Unkomprimierte Größe: 73,2 M Hängt ab von: libnvidia-common-390, libc6 (>= 2.2.5), libwayland-client0 (>= 1.3.92), libwayland-server0 (>= 1.2.0), libx11-6, libxext6 Empfiehlt: libnvidia-gl-390:i386 Kollidiert mit: libnvidia-gl, libnvidia-gl:i386 Beschädigt: libnvidia-gl-390:i386 (!= 390.25-0ubuntu4) Ersetzt: libnvidia-gl, nvidia-384 (< 390.25), nvidia-384:i386 (< 390.25), nvidia-390 (< 390.25-0ubuntu1), libnvidia-gl:i386, libnvidia-gl-390:i386 (< 390.25-0ubuntu4) Liefert: libegl-vendor, libglx-vendor, libnvidia-gl Beschreibung: NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD This package provides the NVIDIA OpenGL/GLX/EGL/GLES libraries and the Vulkan ICD. Homepage: http://www.nvidia.com -- 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/1753663 Title: [Mesa 18.0] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation
[Touch-packages] [Bug 1753663] Re: [Mesa 18.0] No 3D acceleration, using llvmpipe
It seems the package layout has changed a lot in 390: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390 So I'm not sure if your driver is fully installed, or if it is expected to work at all. Maybe see also bug 1752053. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [Mesa 18.0] No 3D acceleration, using llvmpipe + [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe ** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: libglvnd (Ubuntu) Status: Incomplete => 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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/libglvnd/+bug/1753663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1751225] Re: apt update hangs when repository url is redirect url
Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+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 1753450] Re: [MIR] mpg123
MIR ack for libmpg123-0 if the Security Team acknowledges they are aware of this requirement. ** Changed in: mpg123 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
** Tags added: nvidia -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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/libglvnd/+bug/1753663/+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 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
This bug was fixed in the package apt - 1.6~beta1 --- apt (1.6~beta1) unstable; urgency=medium [ David Kalnischkies ] * allow the apt/lists/auxfiles/ directory to be missing (Closes: 887624) * add apt-helper drop-privs command… * restore gcc visibility=hidden for apt-private * ensure correct file permissions for auxfiles * allow the apt/lists/auxfiles/ directory to be missing (Closes: 887624) * add apt-helper drop-privs command… * restore gcc visibility=hidden for apt-private * ensure correct file permissions for auxfiles [ Julian Andres Klode ] * indexcopy: Copy uncompressed indices from cdrom again (LP: #1746807) * Work around test-method-mirror failure by setting umask at start * Check that Date of Release file is not in the future * apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159) * indexcopy: Copy uncompressed indices from cdrom again (LP: #1746807) * Work around test-method-mirror failure by setting umask at start * Check that Date of Release file is not in the future * apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159) [ Chris Leick ] * German manpage translation update * German manpage translation update -- Julian Andres Klode Mon, 26 Feb 2018 13:14:13 +0100 ** Changed in: apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: When running kernel version 4.4.0-78 (for example) and the unattended- upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+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 1753059] Re: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Thanks for filing this bug in Ubuntu. The logs show: Setting up ntp (1:4.2.8p10+dfsg-5ubuntu3.2) ... Installing new version of config file /etc/apparmor.d/usr.sbin.ntpd ... Segmentation fault (core dumped) dpkg: error processing package ntp (--configure): subprocess installed post-installation script returned error exit status 139 And in dmesg: [721832.927616] addgroup[1326]: segfault at 339 ip 5569dd6ce6f6 sp 7ffd260fb1f0 error 4 in perl[5569dd5bb000+1f7000] The ntp postinst always calls addgroup and adduser: if [ "$1" = "configure" ]; then addgroup --system --quiet ntp adduser --system --quiet --ingroup ntp --no-create-home --home /nonexistent ntp ... Can you check if you already have an ntp user and group please: id ntp getent group ntp getent passwd ntp And try one more time: sudo apt update sudo apt -f install Please post back the results. Thanks! ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1753059 Title: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in ntp package in Ubuntu: Incomplete Bug description: Issue with package install was reported by system after using Software Updater to install new updates on Lubuntu 17.10. Equipment is a Dell Optiplex GX620. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3.2 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sat Mar 3 02:32:57 2018 DuplicateSignature: package:ntp:1:4.2.8p10+dfsg-5ubuntu3.2 Installing new version of config file /etc/apparmor.d/usr.sbin.ntpd ... Segmentation fault (core dumped) dpkg: error processing package ntp (--configure): subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2017-12-30 (62 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=f42c87eb-f326-4389-a256-d2a9d596508e ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: ntp Title: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1753059/+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 1753704] [NEW] package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: package initramfs-tools 0.122ubuntu8.10 failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.10 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 00:22:13 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1753704 Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: package initramfs-tools 0.122ubuntu8.10 failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.10 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 00:22:13 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 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/1753704/+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 1751129] [NEW] I think there is some security issue in my ubuntu .
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: If I log into any other user i am able to access my main user through terminal with my current user password. I am using ubuntu 16.04 and I think it might be in all ubuntu 16.04 operating systems. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.5+16.04.20171201.3 Uname: Linux 4.15.1-041501-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 23 01:06:34 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed bbswitch, 0.8, 4.15.1-041501-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.15.1-041501-generic, x86_64: installed virtualbox, 5.0.40, 4.13.0-32-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2018-01-22 (31 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_IN LANGUAGE=en_IN:en XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.1-041501-generic root=UUID=95af4278-a5ad-4183-9691-2a68fd0e627e ro resume=UUID=a7e7e167-65b7-4b78-ad75-4400e9b38bad resume= resume= quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.33 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.57 dmi.chassis.asset.tag: CNU4219GQQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.33:bd09/01/2015:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009FD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009FD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20171116-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 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: Thu Feb 22 21:34:13 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 ** Affects: sudo (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- I think there is some security issue in my ubuntu . https://bugs.launchpad.net/bugs/1751129 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. -- 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 1753532] Re: apt-get update doesn't get new packages
How do your apt config folders look like? $ ls -la /etc/apt/apt.conf.d/ 00aptitude 01autoremove-kernels 15update-stamp 70debconf 00trustcdrom 01-vendor-ubuntu 20archive 99update-notifier 01autoremove 10periodic 50unattended-upgrades $ ls -la /etc/apt/preferences.d/ total 8 drwxr-xr-x 2 root root 4096 Apr 14 2016 . drwxr-xr-x 6 root root 4096 Mar 6 03:45 .. Do you have special (maybe unwanted) files (for example for pinning) in place? Do you notice a difference if using apt instead of apt-get? sudo apt update apt list --upgradable and then maybe: sudo apt upgrade or: sudo apt full-upgrade Btw. In your sources.list you have lot's of deb-src lines active - in case you don't do development based on the package sources you should consider to disable them (comment out). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1753532 Title: apt-get update doesn't get new packages Status in apt package in Ubuntu: Incomplete Bug description: apt-get update and upgrade do not upgrade the system --Steps to Reproduce--- apt-get update and apt-get upgrade. It shows nothing to upgrade. But the kernel level is in an old version. New kernel packages are not shown in apt-cache. Somehow, the new packages are not being got from repo server when do apt-get update. Executed on 16.04.3 Btw, not all the Ubuntu servers have that issues. I crossed check the sources.list among the servers, there is no difference. So don't know what caused some of them cannot get any update from ubuntu repo. However, I can install individual packages via apt-get install command. There is not any error during the apt-get update && apt-get upgrade. It showed nothing to upgrade. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The servers were able to manually upgrade for a long time. But all the sudden, they are not upgradable. It looks it can not retrieve new kernel level packages during the apt-get update. The highest kernel level can be installed is 4.4.0-97.. not more higher.. HWS: I mirrored this problem description, to be able to get support for getting this fixed. Even it seems to be an environment problem. But direct Q&A will probably help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753532/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
The thing is: I don't need this driver at all (having only Intel...) Theoretically, I could simply remove this driver, but... $ sudo apt remove libnvidia-gl-390 libnvidia-common-390 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: gir1.2-grilo-0.3 gnome-orca gnome-software-common libboost-filesystem1.65.1:i386 libboost-system1.65.1:i386 libges-1.0-0 libmircore1:i386 libsnapd-glib1 plasma-discover plasma-discover-common qml-module-org-kde-kio vlc-bin vlc-plugin-qt xwayland Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden zusätzlichen Pakete werden installiert: libcapnp-0.6.1 libegl-mesa0 libmirclient9 libmircommon7 libmircore1 Die folgenden Pakete werden ENTFERNT: apturl bluedevil browser-plugin-vlc gdm3 gir1.2-ges-1.0 gnome-music gnome-packagekit-session gnome-session-bin gnome-session-flashback gnome-software gnome-software-plugin-snap kaffeine kate kscreen libcapnp-0.6.1:i386 libegl-mesa0:i386 libegl1:i386 libegl1-mesa:i386 libgtk-3-0:i386 libmikmod3:i386 libmirclient9:i386 libmircommon7:i386 libnvidia-common-390 libnvidia-gl-390 libsdl-mixer1.2:i386 libsdl2-2.0-0:i386 libwayland-egl1-mesa:i386 libwebkit2gtk-4.0-37-gtk2 nautilus-share plasma-desktop plasma-pa python-gst-1.0 python3-gst-1.0 session-shortcuts software-properties-gtk ubuntu-desktop ubuntu-session ubuntu-software unity-session vlc Die folgenden NEUEN Pakete werden installiert: libcapnp-0.6.1 libegl-mesa0 libmirclient9 libmircommon7 libmircore1 0 aktualisiert, 5 neu installiert, 40 zu entfernen und 0 nicht aktualisiert. Es müssen 1.045 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 171 MB Plattenplatz freigegeben. So, I think there are 2 bugs: 1. The nvidia package kills the Intel accelaration 2. There are errors in the dependencies which prevent me to simply remove the driver. -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.v
[Touch-packages] [Bug 1753704] Re: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1753704 Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: package initramfs-tools 0.122ubuntu8.10 failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.10 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 00:22:13 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 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/1753704/+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 1746579] Re: A boxes instead of a Cyrillic chars in VTs
Evgeniy, when you'll try, please, choose Ukrainian for localization and Ukrainian for keyboard layout during installation as I did it. -- 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/1746579 Title: A boxes instead of a Cyrillic chars in VTs Status in console-setup package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Встановлено: 1.166ubuntu7 Кандидат:1.166ubuntu7 Таблиця версій: *** 1.166ubuntu7 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ua.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status I expected to have cyrillic fonts in any of six VTs, /dev/tty[1-6], but it shows boxes instead of them. Please, see screen shot in attachment. It's very likely that this is an old bug that was fixed earlier but it appeared it 18.04 dev again. Here it is: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1565542 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.166ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jan 31 20:46:57 2018 InstallationDate: Installed on 2018-01-12 (19 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180103) PackageArchitecture: all ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1746579/+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 1753441] Re: [MIR] lame
+1 from security team for this to go forward. We will not be doing a code review at this time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1751129] Re: I think there is some security issue in my ubuntu .
Hello Umer, I believe this is working as intended. By default Ubuntu users in the admin or sudo group have full privileges on the system via sudo. If you can reproduce this without being in either of these groups, please re-open, attach your sudoers(5) file, and a terminal transcript showing id(1) output and the problem. Thanks ** Package changed: unity (Ubuntu) => sudo (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1751129 Title: I think there is some security issue in my ubuntu . Status in sudo package in Ubuntu: Incomplete Bug description: If I log into any other user i am able to access my main user through terminal with my current user password. I am using ubuntu 16.04 and I think it might be in all ubuntu 16.04 operating systems. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.5+16.04.20171201.3 Uname: Linux 4.15.1-041501-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 23 01:06:34 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed bbswitch, 0.8, 4.15.1-041501-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.15.1-041501-generic, x86_64: installed virtualbox, 5.0.40, 4.13.0-32-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2018-01-22 (31 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_IN LANGUAGE=en_IN:en XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.1-041501-generic root=UUID=95af4278-a5ad-4183-9691-2a68fd0e627e ro resume=UUID=a7e7e167-65b7-4b78-ad75-4400e9b38bad resume= resume= quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.33 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.57 dmi.chassis.asset.tag: CNU4219GQQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.33:bd09/01/2015:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009FD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009FD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20171116-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 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: Thu Feb 22 21:34:13 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/sudo/+bug/1751129/+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 1753441] Re: [MIR] lame
** Changed in: lame (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1753450] Re: [MIR] mpg123
** Changed in: mpg123 (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1752123] Re: Force 8bit RGB config
You still can, by setting "allow_rgb10_configs" true in drirc for gnome- shell. Only the driver defaults were flipped. Note that the modesetting driver does not support it, only after we get xserver 1.20 in 18.10. So for Intel hw you'd need to use the -intel driver until then. ** Also affects: clutter (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/1752123 Title: Force 8bit RGB config Status in clutter package in Ubuntu: New Status in cogl package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: New mesa supports 10bit RGB configs, and this causes issues with cogl/mutter which get a random EGLConfig that breaks some autopkgtests. To fix this this merge request is needed for mutter https://gitlab.gnome.org/GNOME/mutter/merge_requests/36 and a similar one for cogl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter/+bug/1752123/+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 1753441] Re: [MIR] lame
I just researched current open CVEs in bionic. The only one open is CVE-2017-15019, which is a minor issue. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15019 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1753450] Re: [MIR] mpg123
All CVEs are currently fixed in bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1753450] Re: [MIR] mpg123
+1 to go ahead. The Security Team will not do a code review at this time. ** Changed in: mpg123 (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Incomplete Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1753361] Re: Please set a maximum size for the sytemd journal
/var/log/systemd is not a path used by systemd Could you please paste the output of: $ journalctl -b -u systemd-journald.service | grep max ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: Invalid => Incomplete -- 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/1753361 Title: Please set a maximum size for the sytemd journal Status in systemd package in Ubuntu: Incomplete Bug description: I noticed today that /var/log/systemd/journal/ was taking up 4.5 GB of space. Please set a default maximum size for the journal, especially for desktop users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753361/+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 1753724] [NEW] nano fails to redo a file insertion
Public bug reported: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html ** Affects: nano (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-undo-when-redoing-don-t-try-to-find-a-line-number-th.patch" https://bugs.launchpad.net/bugs/1753724/+attachment/5070577/+files/0001-undo-when-redoing-don-t-try-to-find-a-line-number-th.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1753724 Title: nano fails to redo a file insertion Status in nano package in Ubuntu: New Bug description: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1753724/+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 1753450] Re: [MIR] mpg123
libmpg123-0 's MIR is approved then. ** Changed in: mpg123 (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Fix Committed Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1753731] [NEW] Playing media file over gvfs ceased working
Public bug reported: I am trying to play a media file over gvfs with totem which stopped working. Also showing the media information of such a remote file in nautilus doesn't work anymore. My guess was this is a regression of 1.13.1, but using gst-play-1.0 directly surprisingly works. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: I am trying to play a media file over gvfs with totem which stopped working. Also showing the media information of such a remote file in nautilus doesn't work anymore. - Using gst-play-1.0 directly surprisingly works. + My guess was this is a regression of 1.13.1, but using gst-play-1.0 + directly surprisingly works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1753731 Title: Playing media file over gvfs ceased working Status in gstreamer1.0 package in Ubuntu: New Bug description: I am trying to play a media file over gvfs with totem which stopped working. Also showing the media information of such a remote file in nautilus doesn't work anymore. My guess was this is a regression of 1.13.1, but using gst-play-1.0 directly surprisingly works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1753731/+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 1753724] Re: nano fails to redo a file insertion
The attachment "0001-undo-when-redoing-don-t-try-to-find-a-line-number- th.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1753724 Title: nano fails to redo a file insertion Status in nano package in Ubuntu: New Bug description: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1753724/+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 1753739] [NEW] Xorg freeze
Public bug reported: mouse still working but click doesn't after 2 or 3 minutes everything becoming functional again ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 6 13:32:43 2018 DistUpgraded: 2017-10-23 14:36:10,677 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio «./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8)) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.13.0-32-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] InstallationDate: Installed on 2015-09-14 (903 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_pstate=disable SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-23 (133 days ago) dmi.bios.date: 04/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0PPXP5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd04/28/2016:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0PPXP5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. 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 1:2.10.5-1ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful false-gpu-hang freeze 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/1753739 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: mouse still working but click doesn't after 2 or 3 minutes everything becoming functional again ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 6 13:32:43 2018 DistUpgraded: 2017-10-23 14:36:10,677 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio «./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8)) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.13.0-32-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] InstallationDate: Installed on 2015-09-14 (903 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_pstate=disable SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-23 (133 days ago) dmi.bios.date: 04/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0PPXP5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Del
[Touch-packages] [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
For open-vm-tools this issue will only exist with the planned backport of the newer version. Since we will not ship the broken backport as we found it in pre-checks the correct state for open-vm-tools in xenial is invalid. ** Changed in: open-vm-tools (Ubuntu Xenial) Status: Triaged => Invalid -- 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/1750780 Title: Race with local file systems can make open-vm-tools fail to start Status in cloud-init: Invalid Status in open-vm-tools package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in open-vm-tools source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in open-vm-tools package in Debian: Incomplete Bug description: Since the change in [1] open-vm-tools-service starts very (very) early. Not so much due to the Before=cloud-init-local.service But much more by DefaultDependencies=no That can trigger an issue that looks like root@ubuntuguest:~# systemctl status -l open-vm-tools.service ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor preset: enabled) Active: failed (Result: resources) As it is right now open-vm-tools can race with the other early start and then fail. In detail one can find a message like: open-vm-tools.service: Failed to run 'start' task: Read-only file system" This is due to privtaeTmp=yes which is also set needing a writable /var/tmp [2] To ensure this works PrivateTmp would have to be removed (not good) or some after dependencies added that make this work reliably. I added After=local-fs.target which made it work for me in 3/3 tests. I' like to have an ack by the cloud-init Team that this does not totally kill the originally intended Before=cloud-init-local.service I think it does not as local-fs can complete before cloud-init-local, then open-vm-tools can initialize and finally cloud-init-local can pick up the data. To summarize: # cloud-init-local # DefaultDependencies=no Wants=network-pre.target After=systemd-remount-fs.service Before=NetworkManager.service Before=network-pre.target Before=shutdown.target Before=sysinit.target Conflicts=shutdown.target RequiresMountsFor=/var/lib/cloud # open-vm-tools # DefaultDependencies=no Before=cloud-init-local.service Proposed is to add to the latter: After=local-fs.target [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677 [2]: https://github.com/systemd/systemd/issues/5610 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1753724] Re: nano fails to redo a file insertion
** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1753724 Title: nano fails to redo a file insertion Status in nano package in Ubuntu: New Bug description: In Bionic Beaver (and in any nano between 2.8.0 and 2.9.3), trying to redo a file insertion can fail with the message: "[ Gone undo line -- please report a bug ]". To reproduce, run 'nano --ignore' and type: Ctrl+R /etc/issue Alt+U Alt+E Attached upstream patch fixes the issue. References: https://savannah.gnu.org/bugs/?53272 http://git.savannah.gnu.org/cgit/nano.git/commit/?id=e9eabdcd http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00015.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1753724/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
A few weeks ago one of my five rsync backup processes that runs from a daily cron 03:00 am has started failing with this exact issue. I can only manually reproduce it when executing my rsync command with tripe verbosity: rsync -avvv --delete /source_dir /target_dir Manually calling rsync with less than triple verbosity runs the whole process as expected. However the hanging command used in cron is $ rsync -aq --delete /source_dir /target_dir > /dev/null $ strace -p 16857 16857 16:38:37 lstat("Saved/SavedArks/retracted.profilebak", {st_mode=S_IFREG|0600, st_size=22986, ...}) = 0 16857 16:38:37 write(1, "[sender] make_file(Saved/SavedArks/retracted.profilebak,*,2)\n", 69) = 69 16857 16:38:37 lstat("Saved/SavedArks/retracted.arkprofile", {st_mode=S_IFREG|0600, st_size=1810, ...}) = 0 16857 16:38:37 write(1, "[sender] make_file(Saved/SavedArks/retracted.arkprofile,*,2)\n", 69) = 69 16857 16:38:37 select(5, [], [4], [], {60, 0} 16858 16:39:36 <... select resumed> ) = 0 (Timeout) 16858 16:39:36 select(2, [], [1], [], {60, 0} 16859 16:39:37 <... select resumed> ) = 0 (Timeout) 16859 16:39:37 select(5, [], [4], [], {60, 0} 16857 16:39:37 <... select resumed> ) = 0 (Timeout) 16857 16:39:37 select(5, [], [4], [], {60, 0} $ lsof -p 15678 -ad 4,5 # note: I used multiple processes over multiple days, the PID will not be constant COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME rsync 15678 pamel4u unix 0x8f88f9fec400 0t0 44294 type=STREAM rsync 15678 pamel5u unix 0x8f88f9614800 0t0 44295 type=STREAM $ ls -l /proc/15678/fd/4 lrwx-- 1 pamel pamel 64 Mar 6 13:35 /proc/15678/fd/4 -> socket:[44294] $ ls -l /proc/15678/fd/5 lrwx-- 1 pamel pamel 64 Mar 6 13:35 /proc/15678/fd/5 -> socket:[44295] $ ss -nxp | grep -E '44294|44295' u_str ESTAB 0 59136 * 44296 * 44295 users:(("rsync",pid=15679,fd=1)) u_str ESTAB 0 97024 * 44294 * 44293 users:(("rsync",pid=15678,fd=4)) u_str ESTAB 82063 0 * 44293 * 44294 users:(("rsync",pid=15680,fd=0)) u_str ESTAB 53885 0 * 44295 * 44296 users:(("rsync",pid=15678,fd=5)) I have this issue on Ubuntu 17.04 with rsync 3.1.2, Debian 9.3 with rsync 3.1.2 and 3.1.3 (all as VM on ESXi 6.5). The only constants are the files that are being transferred: 6.6GB over 11'437 files. I am also certain that it does not hang on a specific file as it's sometimes a log file and sometimes a profile. I would say it happens 0.5s into the process after transferring about 44 files. $ rsync -avvv --delete /srv/ark/redacted/ShooterGame/Saved /srv/ark/backup/redacted/ [...] [sender] make_file(Saved/SavedArks/redacted.arkprofile,*,2) [sender] make_file(Saved/SavedArks/redacted.arktribe,*,2) [sender] make_file(Saved/SavedArks/redacted.arkprofile,*,2) send_files(29, /srv/ark/redacted/ShooterGame/Saved/Logs) Saved/Logs/ send_files(30, /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log) send_files mapped /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log of size 65472 calling match_sums /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log ^C [...] recv_file_name(Saved/SavedArks/redacted.profilebak) recv_file_name(Saved/SavedArks/redacted.arkprofile) recv_file_name(Saved/SavedArks/redacted.arkprofile) rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.3] [generator] _exit_cleanup(code=20, file=io.c, line=504): about to call exit(20) rsync: [generator] write error: Broken pipe (32) $ md5sum /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log 52596de045ba1759c68dfb8c1cd2d970 /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log $ id uid=1001(pamel) gid=1001(pamel) groups=1001(pamel),60(games) $ ls -lA /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log -rw--- 1 pamel pamel 65472 Apr 1 2017 /srv/ark/redacted/ShooterGame/Saved/Logs/ServerGame.10035.2016.10.27_07.23.01.log $ ls -lA /srv/ark/backup/ total 4 [...] drwxr-xr-x 3 pamel pamel 4096 Mar 6 13:25 redacted I've found other occurences of this issue but mostly people say "this sounds like a network issue". I'm only rsyncing between two local directories so I really hope it has nothing to do with network. Is there anything else I can do to further debug this issue? I can't really send 6.6GB of confidential data to replicate this issue and it's a really big issue that now has started to occur daily and requires me to manually abort the process and restart the services every morning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.laun
[Touch-packages] [Bug 1752123] Re: Force 8bit RGB config
This bug was fixed in the package mutter - 3.27.92-1 --- mutter (3.27.92-1) experimental; urgency=medium * New upstream release candidate (LP: #1752123, LP: #1718238) * Bump minimum wayland-protocols to 1.12 * Drop bump-api.patch: Applied in new release -- Jeremy Bicha Mon, 05 Mar 2018 20:38:24 -0500 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1752123 Title: Force 8bit RGB config Status in clutter package in Ubuntu: New Status in cogl package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: New mesa supports 10bit RGB configs, and this causes issues with cogl/mutter which get a random EGLConfig that breaks some autopkgtests. To fix this this merge request is needed for mutter https://gitlab.gnome.org/GNOME/mutter/merge_requests/36 and a similar one for cogl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter/+bug/1752123/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
This bug was fixed in the package mutter - 3.27.92-1 --- mutter (3.27.92-1) experimental; urgency=medium * New upstream release candidate (LP: #1752123, LP: #1718238) * Bump minimum wayland-protocols to 1.12 * Drop bump-api.patch: Applied in new release -- Jeremy Bicha Mon, 05 Mar 2018 20:38:24 -0500 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1744537] Re: Allocating size to GtkBox 0x563732796750 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
vte-0.51.92 includes the workaround, so the warning is no longer emitted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1744537 Title: Allocating size to GtkBox 0x563732796750 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Status in gtk+3.0 package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: After upgrading gnome-terminal to 3.26 (from 3.24), that error is still logged. Some old workarounds (might be irrelevant now): https://github.com/budgie-desktop/budgie-desktop/issues/532 https://github.com/budgie-desktop/budgie-desktop/commit/ff3d7c9c0fc17f4fb23c172f8c8874ab4a7d6602 Related upstream discussions: https://bugzilla.gnome.org/show_bug.cgi?id=771899; points to vte bad calls https://bugzilla.gnome.org/show_bug.cgi?id=791014 Doc: https://developer.gnome.org/vte/0.50/VteTerminal.html ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.26.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 21 07:58:18 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1744537/+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 1753752] Re: Blueish screen pixels after gnome on xorg login
I saw this with mutter 3.27.91 also. See https://ubuntuforums.org/showthread.php?t=2386454 which was reported before 3.27.92 was available. ** Also affects: xorg (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/1753752 Title: Blueish screen pixels after gnome on xorg login Status in mutter package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Report against mutter as it appear related to its 3.27.92 upgrades. What happen: - choose gnome on xorg login session - get a full pixelised blueish screen for a moment while hdd is fully active (~5 seconds), then the gnome-shell interface comes up. - checking journalctlctl, there are these plymouth errors: kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro plymouth:debug ... plymouth[646]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[646]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[646]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[646]: [./plymouth.c:1121] main:daemon not running plymouth[646]: [./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop plymouth[1008]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[1008]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[1008]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[1008]: [./plymouth.c:1121] main:daemon not running plymouth[1008]: [./plymouth.c:1132] main:no need to wait gdm3[1025]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused gdm3[1025]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol gdm3[1025]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused gdm3[1025]: [./plymouth.c:1121] main:daemon not running gdm3[1025]: [./plymouth.c:1124] main:ping failed That issue was not seen with mutter 3.27.91, and gdm3 is still at 3.27.90, plymouth is older. A wayland session does not expose this problem. That system is using xserver-xorg-video-intel. (2:2.99.917+git20171229-1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.27.92-1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 6 14:14:31 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1753752/+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 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"
I think you meant apparmor, not apport. ** Package changed: apport (Ubuntu) => apparmor (Ubuntu) -- 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/1751689 Title: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" Status in apparmor package in Ubuntu: Confirmed Bug description: currently able to scan with xsane utility. libreoffice is not able to scan because it cannot find the scanner. log shows Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 audit(1519613074.593:93): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 audit(1519613074.593:94): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 audit(1519613074.593:95): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001 this stopped working after latest "do-release-upgrade" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashReports: 664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload 600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded 640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash 640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash CurrentDesktop: XFCE Date: Sun Feb 25 22:00:01 2018 InstallationDate: Installed on 2017-04-19 (312 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751689/+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 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"
Hello, I think your mirrors may be out of date, this should have been addressed with: https://launchpad.net/ubuntu/+source/libreoffice/1:5.4.5-0ubuntu0.17.10.4 Please double-check to see what version you have installed: dpkg -l libreoffice | cat If you've got this version installed, please re-open this bug and run apport-collect 1751689 Thanks ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Changed in: apparmor (Ubuntu) Status: Confirmed => Invalid -- 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/1751689 Title: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" Status in apparmor package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Fix Released Bug description: currently able to scan with xsane utility. libreoffice is not able to scan because it cannot find the scanner. log shows Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 audit(1519613074.593:93): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 audit(1519613074.593:94): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 audit(1519613074.593:95): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001 this stopped working after latest "do-release-upgrade" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashReports: 664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload 600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded 640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash 640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash CurrentDesktop: XFCE Date: Sun Feb 25 22:00:01 2018 InstallationDate: Installed on 2017-04-19 (312 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751689/+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 1753216] Re: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdebi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1753216 Title: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor Status in gdebi package in Ubuntu: Confirmed Bug description: Fehlermeldung: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor beim Installieren eines deb-Paketes mit Paket-Instalaationsprogramm Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 gdebi: Installiert: 0.9.5.7+nmu2 Installationskandidat: 0.9.5.7+nmu2 Versionstabelle: *** 0.9.5.7+nmu2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1753216/+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 1753768] [NEW] graphics problem
Public bug reported: i have two displays connected, one to gtx 1060 and second one to integrated intel graphic card. Since now, i didn't have problem, but today, when i turned on my pc, it started cracking. Seems lke i insterted my psw, but i haven't and just went into infinite loop . After i disconected monitor from integrated graphic card, it worked fine :( ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 6 15:29:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-36-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-36-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3775] InstallationDate: Installed on 2018-03-04 (1 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=bd0e12cb-c7f9-40b1-907b-92f834e15695 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3403 dmi.board.asset.tag: Default string dmi.board.name: H110M-K 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.:bvr3403:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-K: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 1:0.9.12.3+16.04.20171116-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 N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A 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 N/A xserver.bootTime: Tue Mar 6 14:44:20 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(0): Error initialising acceleration. Falling back to NoAccel AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1753768 Title: graphics problem Status in xorg package in Ubuntu: New Bug description: i have two displays connected, one to gtx 1060 and second one to integrated intel graphic card. Since now, i didn't have problem, but today, when i turned on my pc, it started cracking. Seems lke i insterted my psw, but i haven't and just went into infinite loop . After i disconected monitor from integrated graphic card, it worked fine :( ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDr
[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla
--- Comment From ppaid...@in.ibm.com 2018-03-06 09:23 EDT--- I got access to P8 FSP system today, I have verified that lscpu segfaults after first CPU garded. root@:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):72 On-line CPU(s) list: 8-79 Thread(s) per core:8 Core(s) per socket:4 Socket(s): 2 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported Segmentation fault root@x:~# dmesg logs below errors: [ 57.463443] lscpu[2057]: unhandled signal 11 at nip 7128aba29b60 lr 7128aba29b38 code 30001 [ 61.664064] lscpu[2058]: unhandled signal 11 at nip 78c241109b60 lr 78c241109b38 code 30001 root@x:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null) CPU min MHz: (null) L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-31 NUMA node1 CPU(s): 32-55 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 == Comment: #1 - Pridhiviraj Paidipeddi - 2017-01-11 07:06:59 == root@p8wookie:~# dmesg |grep -i powernv [
[Touch-packages] [Bug 1753776] [NEW] After login the screen pixelates for few seconds on GNOME on X
Public bug reported: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: mu
[Touch-packages] [Bug 1753776] Re: After login the screen "crumbles" for few seconds
adding a picture of the screen after login ** Attachment added: "screen immediately after login" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1753776/+attachment/5070816/+files/DSC_2324rr.JPG -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be F
[Touch-packages] [Bug 1717769] Re: day of week in german despite i configured the system in english
I understood the mecanism (but not the involved code): This problem is easily reproductible: installing a fresh Ubuntu from CD, choosing "English" as the language and the keymap"Belgian", makes everytime the region language in German. ** Attachment added: "screenshot.png" https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+attachment/5070815/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1717769 Title: day of week in german despite i configured the system in english Status in language-pack-en package in Ubuntu: Incomplete Bug description: Description --- I chose the english language and live in Belgium. So I chose Brussels for the Time Zone, and the Belgian keymap. The Ubuntu date & time applet, in the top bar of the Ubuntu desktop interface shows me "Son HH:MM", Son standing for "Sonntag" which is german. I don't get why there is german in my interface since I configured this language nowhere but English. Expected Behavior -- Having the day of week in English. My configuration to reproduce the problem - Here is the region & language configuration as seen in the settings pannel: Language: English (United States) Formats : Belgien Input Sources: Belgian In the "Date & Time" settings: Time Zone: CEST (Brussels, Belgium) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies
ppaid...@in.ibm.com what version of the package did you test? We were looking for a verification that the new package does NOT segfault. It's unclear from your comment if you've tested the new version of the package and it failed verification, or if you were testing the previous, known-broken package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null) CPU min MHz: (null) L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-31 NUMA node1 CPU(s): 32-55 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 == Comment: #1 - Pridhiviraj Paidipeddi - 2017-01-11 07:06:59 == root@p8wookie:~# dmesg |grep -i powernv [0.00] Using PowerNV machine description [0.331564] EEH: PowerNV platform initialized [0.907250] powernv-rng: Registering arch random hook. [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0 [1.507167] powernv_idle_driver registered [ 34.184048] powernv_rng: Registered powernv hwrng. [ 34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree [ 34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, prod_id: 0x, dev_id
[Touch-packages] [Bug 1753776] Re: After login the screen "crumbles" for few seconds
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be
[Touch-packages] [Bug 1753776] Re: After login the screen "crumbles" for few seconds
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. d
[Touch-packages] [Bug 1753752] Re: Blueish screen pixels after gnome on xorg login
*** This bug is a duplicate of bug 1753776 *** https://bugs.launchpad.net/bugs/1753776 I hope you don't mind I marked this as a duplicate since the other bug includes more debug info and a screenshot. ** This bug has been marked a duplicate of bug 1753776 After login the screen "crumbles" for few seconds -- 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/1753752 Title: Blueish screen pixels after gnome on xorg login Status in mutter package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Report against mutter as it appear related to its 3.27.92 upgrades. What happen: - choose gnome on xorg login session - get a full pixelised blueish screen for a moment while hdd is fully active (~5 seconds), then the gnome-shell interface comes up. - checking journalctlctl, there are these plymouth errors: kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro plymouth:debug ... plymouth[646]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[646]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[646]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[646]: [./plymouth.c:1121] main:daemon not running plymouth[646]: [./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop plymouth[1008]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[1008]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[1008]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[1008]: [./plymouth.c:1121] main:daemon not running plymouth[1008]: [./plymouth.c:1132] main:no need to wait gdm3[1025]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused gdm3[1025]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol gdm3[1025]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused gdm3[1025]: [./plymouth.c:1121] main:daemon not running gdm3[1025]: [./plymouth.c:1124] main:ping failed That issue was not seen with mutter 3.27.91, and gdm3 is still at 3.27.90, plymouth is older. A wayland session does not expose this problem. That system is using xserver-xorg-video-intel. (2:2.99.917+git20171229-1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.27.92-1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 6 14:14:31 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1753752/+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 1753776] Re: After login the screen "crumbles" for few seconds
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.
[Touch-packages] [Bug 1753776] Re: After login the screen pixelates for few seconds on GNOME on X
I also have Intel graphics and can reproduce this bug with Ubuntu (on X) but not with Ubuntu on Wayland. ** Summary changed: - After login the screen "crumbles" for few seconds + After login the screen pixelates for few seconds on GNOME on X -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Fill
[Touch-packages] [Bug 1753776] Re: After login the screen "crumbles" for few seconds
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sy
[Touch-packages] [Bug 1753441] Re: [MIR] lame
Go for libmp3lame0, on the condition that CVE-2017-15019 be looked into. ** Changed in: lame (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: lame (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: lame (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Fix Committed Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1753576] Re: GDM freeze
I edited /etc/gdm3/custom.conf and put WaylandEnable=false back in (I had it enabled before to test). Greeter came right up on reboot and my external monitor works again. What is curious is that my session choice in both cases was/is Gnome on Xorg. So is it possible there's some change in the greeter's behavior? As to using wayland or not. -- 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/1753576 Title: GDM freeze Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: Here is what I know so far: After rebooting this morning on Bionic (after receiving the gnome theme updates, I think), upon reboot the CPU pegs and the greeter is never displayed (there is a graphics system running, but I'm not sure what it's doing). My num lock / caps lock keys work, but the touchpad on the laptop does nothing to the mouse. If I boot with nomodeset, greeter does not freeze. Finally, in either case, I am now unable to use my external monitor, which worked fine before (connected over a USB-C to HDMI dongle). 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Mar 5 11:47:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800] InstallationDate: Installed on 2015-12-17 (809 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80MK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet splash nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K45914 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Mon Mar 5 11:17:58 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] Re: GDM freeze
Hi Daniel, On Mon, Mar 5, 2018 at 9:56 PM, Daniel van Vugt wrote: > Nish, > > To figure the problem out you will need to be logged in already while > it's happening(!), so.. Yeah, tricky when the machine physically seems to be hung (no touchpad, no responsiveness to keyboard) > 1. Log into a VT (Ctrl+Alt+F4) or install openssh-server and log in from a > separate machine. > 2. Run 'top' to find the ID of the spinning process. > 3. Run: >kill -ABRT > 4. Wait a while for crash files to be written. > 5. Look in /var/crash for crash files and run: >ubuntu-bug /var/crash/YOURFILE.crash > 6. Add a comment here telling us the ID of the new bug. Thanks for the info! I just was wondering, as the responsiveness of the desktop feels very different, and it does seem like I'm now on an Xwayland session, even though I didn't change anything. I wonder if it's Wayland that's actually crashing? gdm 2795 0.0 0.0 190684 5496 tty1 Ssl+ Mar05 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart gdm 2878 0.0 0.3 563888 55076 tty1 Sl+ Mar05 0:00 /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 nacc 3428 0.0 0.0 190684 5408 tty2 Ssl+ Mar05 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session --session=gnome nacc 3502 0.0 0.3 565704 56056 tty2 Sl+ Mar05 0:02 /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 -- 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/1753576 Title: GDM freeze Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: Here is what I know so far: After rebooting this morning on Bionic (after receiving the gnome theme updates, I think), upon reboot the CPU pegs and the greeter is never displayed (there is a graphics system running, but I'm not sure what it's doing). My num lock / caps lock keys work, but the touchpad on the laptop does nothing to the mouse. If I boot with nomodeset, greeter does not freeze. Finally, in either case, I am now unable to use my external monitor, which worked fine before (connected over a USB-C to HDMI dongle). 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Mar 5 11:47:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800] InstallationDate: Installed on 2015-12-17 (809 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80MK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet splash nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K45914 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Mon Mar 5 11:17:58 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0:
[Touch-packages] [Bug 1753776] Re: After login the screen pixelates for few seconds on GNOME on X
Do you also get plymouth errors logged ? -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.
[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla
--- Comment From ppaid...@in.ibm.com 2018-03-06 10:49 EDT--- (In reply to comment #28) > ppaid...@in.ibm.com what version of the package did you test? We were > looking for a verification that the new package does NOT segfault. It's > unclear from your comment if you've tested the new version of the package > and it failed verification, or if you were testing the previous, > known-broken package. I have tested with latest proposed package 2.27.1-6ubuntu3.5 and it segfaults after CPU GUARD test, before test lscpu works fine. root@ltc-test-ci1:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):72 On-line CPU(s) list: 8-79 Thread(s) per core:8 Core(s) per socket:4 Socket(s): 2 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported Segmentation fault root@ltc-test-ci1:~# which lscpu /usr/bin/lscpu root@ltc-test-ci1:~# dpkg -S /usr/bin/lscpu util-linux: /usr/bin/lscpu root@ltc-test-ci1:~# dpkg -l | grep -i util-linux ii util-linux 2.27.1-6ubuntu3.5 ppc64el miscellaneous system utilities root@ltc-test-ci1:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null)
[Touch-packages] [Bug 1693038] Re: needs to support restart on Lubuntu and Xubuntu
** Branch linked: lp:software-properties -- 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/1693038 Title: needs to support restart on Lubuntu and Xubuntu Status in software-properties package in Ubuntu: Triaged Bug description: [Test Case] 1) sudo touch /var/run/reboot-required 2) sudo apt install umockdev gir1.2-umockdev-1.0 3) /usr/share/ubuntu-drivers-common/fake-devices-wrapper software-properties-gtk --open-tab 4 4) click the Restart button You should observe a dialog either confirming that you want to restart or with a restart button. It depends what desktop environment you are running. Original Description The fix for bug 1241210 only works in gnome-session based sessions. Let's make sure that the driver restart button works on Xubuntu and Lubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693038/+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 1693038] Re: needs to support restart on Lubuntu and Xubuntu
** Changed in: software-properties (Ubuntu) Status: Triaged => In Progress -- 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/1693038 Title: needs to support restart on Lubuntu and Xubuntu Status in software-properties package in Ubuntu: In Progress Bug description: [Test Case] 1) sudo touch /var/run/reboot-required 2) sudo apt install umockdev gir1.2-umockdev-1.0 3) /usr/share/ubuntu-drivers-common/fake-devices-wrapper software-properties-gtk --open-tab 4 4) click the Restart button You should observe a dialog either confirming that you want to restart or with a restart button. It depends what desktop environment you are running. Original Description The fix for bug 1241210 only works in gnome-session based sessions. Let's make sure that the driver restart button works on Xubuntu and Lubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693038/+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 1753532] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2018-03-06 11:48 EDT--- (In reply to comment #27) > I can only think of that you deleted the meta package on some servers, hence > there are only new kernel packages available, but no meta package to pull > them in. Actually, I couldn't see any new kernel packages available.. It showed nothing when I do apt list --upgradable. Also when I try to install a newer level of kernel, it also says couldn't find it. Below is an example. root@zml005:~# apt-get install linux-image-4.4.0-116-generic Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-image-4.4.0-116-generic E: Couldn't find any package by glob 'linux-image-4.4.0-116-generic' E: Couldn't find any package by regex 'linux-image-4.4.0-116-generic' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1753532 Title: apt-get update doesn't get new packages Status in apt package in Ubuntu: Incomplete Bug description: apt-get update and upgrade do not upgrade the system --Steps to Reproduce--- apt-get update and apt-get upgrade. It shows nothing to upgrade. But the kernel level is in an old version. New kernel packages are not shown in apt-cache. Somehow, the new packages are not being got from repo server when do apt-get update. Executed on 16.04.3 Btw, not all the Ubuntu servers have that issues. I crossed check the sources.list among the servers, there is no difference. So don't know what caused some of them cannot get any update from ubuntu repo. However, I can install individual packages via apt-get install command. There is not any error during the apt-get update && apt-get upgrade. It showed nothing to upgrade. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The servers were able to manually upgrade for a long time. But all the sudden, they are not upgradable. It looks it can not retrieve new kernel level packages during the apt-get update. The highest kernel level can be installed is 4.4.0-97.. not more higher.. HWS: I mirrored this problem description, to be able to get support for getting this fixed. Even it seems to be an environment problem. But direct Q&A will probably help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753532/+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 1753532] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2018-03-06 11:51 EDT--- (In reply to comment #28) > How do your apt config folders look like? > > $ ls -la /etc/apt/apt.conf.d/ > 00aptitude 01autoremove-kernels 15update-stamp > 70debconf > 00trustcdrom 01-vendor-ubuntu 20archive > 99update-notifier > 01autoremove 10periodic 50unattended-upgrades > > $ ls -la /etc/apt/preferences.d/ > total 8 > drwxr-xr-x 2 root root 4096 Apr 14 2016 . > drwxr-xr-x 6 root root 4096 Mar 6 03:45 .. > > Do you have special (maybe unwanted) files (for example for pinning) in > place? > > Do you notice a difference if using apt instead of apt-get? > sudo apt update > apt list --upgradable > and then maybe: > sudo apt upgrade > or: > sudo apt full-upgrade > > Btw. In your sources.list you have lot's of deb-src lines active - in case > you don't do development based on the package sources you should consider to > disable them (comment out). Below are the configurations on one of the servers.. root@zml005:~# ls -la /etc/apt/apt.conf.d/ total 44 drwxr-xr-x 2 root root 4096 Feb 22 08:22 . drwxr-xr-x 6 root root 4096 Feb 3 2016 .. -rw-r--r-- 1 root root 49 Feb 3 2016 00aptitude -rw-r--r-- 1 root root 40 Feb 3 2016 00trustcdrom -rw-r--r-- 1 root root 769 Dec 30 2015 01autoremove -r--r--r-- 1 root root 3291 Feb 22 08:22 01autoremove-kernels -rw-r--r-- 1 root root 42 Mar 8 2017 01-vendor-ubuntu -rw-r--r-- 1 root root 80 Jul 26 2017 20auto-upgrades -rw-r--r-- 1 root root 2656 Jul 12 2017 50unattended-upgrades -rw-r--r-- 1 root root 182 Nov 10 2015 70debconf -rw-r--r-- 1 root root 80 Jul 12 2017 90cloud-init-pipelining root@zml005:~# ls -la /etc/apt/preferences.d/ total 8 drwxr-xr-x 2 root root 4096 Dec 30 2015 . drwxr-xr-x 6 root root 4096 Feb 3 2016 .. There is nothing difference with apt-get and apt commands. root@zml005:~# apt list --upgradable Listing... Done root@zml005:~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@zml005:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1753532 Title: apt-get update doesn't get new packages Status in apt package in Ubuntu: Incomplete Bug description: apt-get update and upgrade do not upgrade the system --Steps to Reproduce--- apt-get update and apt-get upgrade. It shows nothing to upgrade. But the kernel level is in an old version. New kernel packages are not shown in apt-cache. Somehow, the new packages are not being got from repo server when do apt-get update. Executed on 16.04.3 Btw, not all the Ubuntu servers have that issues. I crossed check the sources.list among the servers, there is no difference. So don't know what caused some of them cannot get any update from ubuntu repo. However, I can install individual packages via apt-get install command. There is not any error during the apt-get update && apt-get upgrade. It showed nothing to upgrade. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. The servers were able to manually upgrade for a long time. But all the sudden, they are not upgradable. It looks it can not retrieve new kernel level packages during the apt-get update. The highest kernel level can be installed is 4.4.0-97.. not more higher.. HWS: I mirrored this problem description, to be able to get support for getting this fixed. Even it seems to be an environment problem. But direct Q&A will probably help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753532/+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 1753752] Re: Blueish screen pixels after gnome on xorg login
*** This bug is a duplicate of bug 1753776 *** https://bugs.launchpad.net/bugs/1753776 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1753752 Title: Blueish screen pixels after gnome on xorg login Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Report against mutter as it appear related to its 3.27.92 upgrades. What happen: - choose gnome on xorg login session - get a full pixelised blueish screen for a moment while hdd is fully active (~5 seconds), then the gnome-shell interface comes up. - checking journalctlctl, there are these plymouth errors: kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro plymouth:debug ... plymouth[646]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[646]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[646]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[646]: [./plymouth.c:1121] main:daemon not running plymouth[646]: [./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop plymouth[1008]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[1008]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[1008]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[1008]: [./plymouth.c:1121] main:daemon not running plymouth[1008]: [./plymouth.c:1132] main:no need to wait gdm3[1025]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused gdm3[1025]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol gdm3[1025]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused gdm3[1025]: [./plymouth.c:1121] main:daemon not running gdm3[1025]: [./plymouth.c:1124] main:ping failed That issue was not seen with mutter 3.27.91, and gdm3 is still at 3.27.90, plymouth is older. A wayland session does not expose this problem. That system is using xserver-xorg-video-intel. (2:2.99.917+git20171229-1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.27.92-1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 6 14:14:31 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1753752/+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 1753752] Re: Blueish screen pixels after gnome on xorg login
*** This bug is a duplicate of bug 1753776 *** https://bugs.launchpad.net/bugs/1753776 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1753752 Title: Blueish screen pixels after gnome on xorg login Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Report against mutter as it appear related to its 3.27.92 upgrades. What happen: - choose gnome on xorg login session - get a full pixelised blueish screen for a moment while hdd is fully active (~5 seconds), then the gnome-shell interface comes up. - checking journalctlctl, there are these plymouth errors: kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro plymouth:debug ... plymouth[646]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[646]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[646]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[646]: [./plymouth.c:1121] main:daemon not running plymouth[646]: [./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop plymouth[1008]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused plymouth[1008]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol plymouth[1008]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused plymouth[1008]: [./plymouth.c:1121] main:daemon not running plymouth[1008]: [./plymouth.c:1132] main:no need to wait gdm3[1025]: [./ply-boot-client.c:183] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused gdm3[1025]: [./ply-boot-client.c:184] ply_boot_client_connect:trying old fallback path /ply-boot-protocol gdm3[1025]: [./ply-boot-client.c:190] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused gdm3[1025]: [./plymouth.c:1121] main:daemon not running gdm3[1025]: [./plymouth.c:1124] main:ping failed That issue was not seen with mutter 3.27.91, and gdm3 is still at 3.27.90, plymouth is older. A wayland session does not expose this problem. That system is using xserver-xorg-video-intel. (2:2.99.917+git20171229-1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.27.92-1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 6 14:14:31 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1753752/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
just install libegl-mesa0 and tell what happens? -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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/libglvnd/+bug/1753663/+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 1746463] Re: apparmor profile load in stacked policy container fails
This bug was fixed in the package linux-gcp - 4.15.0-1001.1 --- linux-gcp (4.15.0-1001.1) bionic; urgency=medium * linux-gcp: 4.15.0-1001.1 -proposed tracker (LP: #1752101) * linux xenial derivatives fail to build (LP: #1691814) // Prepare linux-gcp for bionic (LP: #1752069) - [Packaging] Set do_tools_common in common vars * Prepare linux-gcp for bionic (LP: #1752069) - linux-gcp: Update base kernel version - [Config] linux-gcp: Reset config annotations to master - [Config] linux-gcp: Add annotations overlay - [Config] linux-gcp: updateconfigs after rebase to Ubuntu-4.15.0-10.11 - Ubuntu: linux-gcp: Revert build_arch=x86 - [Packaging] linux-gcp: Update Vcs-Git for bionic * CVE-2017-5715 (Spectre v2 retpoline) - [Config] linux-gcp: disable retpoline checks for first upload * [Packaging] Allow overlay of config annotations (LP: #1752072) - [Packaging] config-check: allow overlay annotations files [ Ubuntu: 4.15.0-10.11 ] * linux: 4.15.0-10.11 -proposed tracker (LP: #1749250) * "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10 (LP: #1749202) - swiotlb: suppress warning when __GFP_NOWARN is set - drm/ttm: specify DMA_ATTR_NO_WARN for huge page pools * linux-tools: perf incorrectly linking libbfd (LP: #1748922) - SAUCE: tools -- add ability to disable libbfd - [Packaging] correct disablement of libbfd * [Artful] Realtek ALC225: 2 secs noise when a headset plugged in (LP: #1744058) - ALSA: hda/realtek - update ALC225 depop optimize * [Artful] Support headset mode for DELL WYSE (LP: #1723913) - SAUCE: ALSA: hda/realtek - Add support headset mode for DELL WYSE * headset mic can't be detected on two Dell machines (LP: #1748807) - ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289 - ALSA: hda - Fix headset mic detection problem for two Dell machines * Bionic update to v4.15.3 stable release (LP: #1749191) - ip6mr: fix stale iterator - net: igmp: add a missing rcu locking section - qlcnic: fix deadlock bug - qmi_wwan: Add support for Quectel EP06 - r8169: fix RTL8168EP take too long to complete driver initialization. - tcp: release sk_frag.page in tcp_disconnect - vhost_net: stop device during reset owner - ipv6: addrconf: break critical section in addrconf_verify_rtnl() - ipv6: change route cache aging logic - Revert "defer call to mem_cgroup_sk_alloc()" - net: ipv6: send unsolicited NA after DAD - rocker: fix possible null pointer dereference in rocker_router_fib_event_work - tcp_bbr: fix pacing_gain to always be unity when using lt_bw - cls_u32: add missing RCU annotation. - ipv6: Fix SO_REUSEPORT UDP socket with implicit sk_ipv6only - soreuseport: fix mem leak in reuseport_add_sock() - net_sched: get rid of rcu_barrier() in tcf_block_put_ext() - net: sched: fix use-after-free in tcf_block_put_ext - media: mtk-vcodec: add missing MODULE_LICENSE/DESCRIPTION - media: soc_camera: soc_scale_crop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE - media: tegra-cec: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE - gpio: uniphier: fix mismatch between license text and MODULE_LICENSE - crypto: tcrypt - fix S/G table for test_aead_speed() - Linux 4.15.3 * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) // CVE-2018-126 - net: create skb_gso_validate_mac_len() - bnx2x: disable GSO where gso_size is too big for hardware * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567) - net: hns: add ACPI mode support for ethtool -p * CVE-2017-5715 (Spectre v2 Intel) - [Packaging] retpoline files must be sorted - [Packaging] pull in retpoline files * [Feature] PXE boot with Intel Omni-Path (LP: #1712031) - d-i: Add hfi1 to nic-modules * CVE-2017-5715 (Spectre v2 retpoline) - [Packaging] retpoline -- add call site validation - [Config] disable retpoline checks for first upload * Do not duplicate changelog entries assigned to more than one bug or CVE (LP: #1743383) - [Packaging] git-ubuntu-log -- handle multiple bugs/cves better [ Ubuntu: 4.15.0-9.10 ] * linux: 4.15.0-9.10 -proposed tracker (LP: #1748244) * Miscellaneous Ubuntu changes - [Debian] tests -- remove gcc-multilib dependency for arm64 [ Ubuntu: 4.15.0-8.9 ] * linux: 4.15.0-8.9 -proposed tracker (LP: #1748075) * Bionic update to v4.15.2 stable release (LP: #1748072) - KVM: x86: Make indirect calls in emulator speculation safe - KVM: VMX: Make indirect call speculation safe - module/retpoline: Warn about missing retpoline in module - x86/cpufeatures: Add CPUID_7_EDX CPUID leaf - x86/cpufeatures: Add Intel feature bits for Speculation Control - x86/cpufeatures: Add AMD feature bits for Speculation Control - x86/msr: Add definitions for new speculation control MSRs - x86/pti: Do
[Touch-packages] [Bug 1753796] [NEW] Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release)
Public bug reported: On Ubuntu 18.04 with the NVIDIA development repository PPA, installing cuda-drivers I get the following error during the installation of nvidia-390: dpkg: error processing archive /var/cache/apt/archives/nvidia-390_390.30-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package libglx-mesa0:amd64 18.0.0~rc4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglx-mesa0 18.0.0~rc4-1ubuntu3 ProcVersionSignature: User Name 4.15.0-1002.2-azure 4.15.3 Uname: Linux 4.15.0-1002-azure x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Tue Mar 6 17:38:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK210GL [Tesla K80] [10de:106c] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1002-azure root=UUID=950907d2-f8b1-431a-8195-e06fbf9a814b ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 94AF2AB7-6288-E94C-9C01-1305DF401054 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu uec-images -- 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/1753796 Title: Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre- release) Status in mesa package in Ubuntu: New Bug description: On Ubuntu 18.04 with the NVIDIA development repository PPA, installing cuda-drivers I get the following error during the installation of nvidia-390: dpkg: error processing archive /var/cache/apt/archives/nvidia-390_390.30-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package libglx-mesa0:amd64 18.0.0~rc4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglx-mesa0 18.0.0~rc4-1ubuntu3 ProcVersionSignature: User Name 4.15.0-1002.2-azure 4.15.3 Uname: Linux 4.15.0-1002-azure x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Tue Mar 6 17:38:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK210GL [Tesla K80] [10de:106c] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1002-azure root=UUID=950907d2-f8b1-431a-8195-e06fbf9a814b ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualM
[Touch-packages] [Bug 1753165] Re: packagekitd crashed with SIGSEGV in AptIntf::providesCodec()
*** This bug is a duplicate of bug 1739916 *** https://bugs.launchpad.net/bugs/1739916 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1739916, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1753165/+attachment/5068437/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753165/+attachment/5068439/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753165/+attachment/5068443/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753165/+attachment/5068444/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753165/+attachment/5068445/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753165/+attachment/5068446/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753165/+attachment/5068447/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1739916 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1753165 Title: packagekitd crashed with SIGSEGV in AptIntf::providesCodec() Status in packagekit package in Ubuntu: New Bug description: no idea why and when this was happen ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: packagekit 1.1.7-1 Uname: Linux 4.15.7-041507-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 Date: Sat Mar 3 21:10:53 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-02-15 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) ProcCmdline: /usr/lib/packagekit/packagekitd SegvAnalysis: Segfault happened at: 0x7f0b0102f646 <__strlen_sse2+38>: movdqu (%rax),%xmm4 PC (0x7f0b0102f646) ok source "(%rax)" (0x7f0b5593d770) not located in a known VMA region (needed readable region)! destination "%xmm4" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: packagekit StacktraceTop: AptIntf::providesCodec(PkgList&, char**) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 start_thread (arg=0x7f0aec7a9700) at pthread_create.c:463 Title: packagekitd crashed with SIGSEGV in AptIntf::providesCodec() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1753165/+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 1693038] Re: needs to support restart on Lubuntu and Xubuntu
This bug was fixed in the package software-properties - 0.96.24.23 --- software-properties (0.96.24.23) bionic; urgency=medium * SoftwarePropertiesGtk.py: After installing proprietary drivers provide the capability to restart on Lubuntu and Xubuntu. Add recommends on the packages which provide the restart tools. (LP: #1693038) -- Brian Murray Tue, 06 Mar 2018 08:06:33 -0800 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1693038 Title: needs to support restart on Lubuntu and Xubuntu Status in software-properties package in Ubuntu: Fix Released Bug description: [Test Case] 1) sudo touch /var/run/reboot-required 2) sudo apt install umockdev gir1.2-umockdev-1.0 3) /usr/share/ubuntu-drivers-common/fake-devices-wrapper software-properties-gtk --open-tab 4 4) click the Restart button You should observe a dialog either confirming that you want to restart or with a restart button. It depends what desktop environment you are running. Original Description The fix for bug 1241210 only works in gnome-session based sessions. Let's make sure that the driver restart button works on Xubuntu and Lubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693038/+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 1753450] Re: [MIR] mpg123
mpg123 1.25.8-1 in bionic: universe/sound -> main libmpg123-0 1.25.8-1 in bionic amd64: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic arm64: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic armhf: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic i386: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic ppc64el: universe/libs/optional/100% -> main libmpg123-0 1.25.8-1 in bionic s390x: universe/libs/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic amd64: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic arm64: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic armhf: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic i386: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic ppc64el: universe/libdevel/optional/100% -> main libmpg123-dev 1.25.8-1 in bionic s390x: universe/libdevel/optional/100% -> main libout123-0 1.25.8-1 in bionic amd64: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic arm64: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic armhf: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic i386: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic ppc64el: universe/libs/optional/100% -> main libout123-0 1.25.8-1 in bionic s390x: universe/libs/optional/100% -> main mpg123 1.25.8-1 in bionic amd64: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic arm64: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic armhf: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic i386: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic ppc64el: universe/sound/optional/100% -> main mpg123 1.25.8-1 in bionic s390x: universe/sound/optional/100% -> main Override [y|N]? y 25 publications overridden. ** Changed in: mpg123 (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: mpg123 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 Status in mpg123 package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/mpg123 https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in 1.25.8-1. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/mpg123 https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=mpg123 Dependencies We need libmpg123-0 in main, and this depends on libc6 only. Standards compliance 4.1.2. debian/rules is slightly complicated because it generates some wrapper scripts for some old binary names. Those binaries don't go in a package that we need in main. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+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 1753441] Re: [MIR] lame
lame 3.100-2 in bionic: universe/sound -> main lame 3.100-2 in bionic amd64: universe/sound/optional/100% -> main lame 3.100-2 in bionic arm64: universe/sound/optional/100% -> main lame 3.100-2 in bionic armhf: universe/sound/optional/100% -> main lame 3.100-2 in bionic i386: universe/sound/optional/100% -> main lame 3.100-2 in bionic ppc64el: universe/sound/optional/100% -> main lame 3.100-2 in bionic s390x: universe/sound/optional/100% -> main lame-doc 3.100-2 in bionic amd64: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic arm64: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic armhf: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic i386: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic ppc64el: universe/doc/optional/100% -> main lame-doc 3.100-2 in bionic s390x: universe/doc/optional/100% -> main libmp3lame-dev 3.100-2 in bionic amd64: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic arm64: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic armhf: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic i386: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic ppc64el: universe/libdevel/optional/100% -> main libmp3lame-dev 3.100-2 in bionic s390x: universe/libdevel/optional/100% -> main libmp3lame0 3.100-2 in bionic amd64: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic arm64: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic armhf: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic i386: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic ppc64el: universe/libs/optional/100% -> main libmp3lame0 3.100-2 in bionic s390x: universe/libs/optional/100% -> main Override [y|N]? y 25 publications overridden. ** Changed in: lame (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: lame (Ubuntu) Assignee: Iain Lane (laney) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame Status in lame package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into gst-plugins-good. These are installed by default, and so now we can have MP3 support in the default install. The desktop team would like this feature. For that, it uses some libraries and we'll need to put them in main. Security There are some CVEs in the history of the project. https://security-tracker.debian.org/tracker/source-package/lame https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html The Ubuntu CVE page lists some 'needed' ones but from looking at those ones in Debian they are duplicates and should be fixed already. Quality assurance = Desktop team is subscribed. Bugs https://bugs.launchpad.net/ubuntu/+source/lame https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes&src=lame I think they are reasonably calm given that this is a well known project. Dependencies We need libmp3lame0 in main, and this depends on libc6 only. Standards compliance 4.1.1 and dh minimal style rules. Maintenance === Desktop team will maintain. In Debian this is maintained by the multimedia team, which is active. We don't envisage the package diverging from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+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 1752681] Re: wireless disconnect
In my case it works also by setting the IPV6 to "Automatic, address only". Try like this. Turn off the connection, set it to Automatich, address only or "Ignore" and then re-enable the connection. In my case this procedure works (see attachment) ** Attachment added: "Istantanea_2018-03-06_19-03-28.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752681/+attachment/5070976/+files/Istantanea_2018-03-06_19-03-28.png -- 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/1752681 Title: wireless disconnect Status in network-manager package in Ubuntu: Confirmed Bug description: There are many problems reported about random and quick disconnect/reconnect of the wireless connection in ubuntu. Some say, disabling the ipv6 is the solution but it isn't! I really do want to find a way to debug what happens that the wireless connection drops randomly. But I couldn't find a tool for that. The output of the following commands are attached: uname -a ifconfig cat /proc/sys/net/ipv6/conf/all/disable_ipv6 iwconfig lsmod dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752681/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
$ apt install libegl-mesa0 libmirclient9 libcapnp-0.6.1 libmircommon7 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: libboost-filesystem1.65.1:i386 libboost-system1.65.1:i386 libmircore1:i386 Verwenden Sie »apt autoremove«, um sie zu entfernen. Die folgenden zusätzlichen Pakete werden installiert: libmircore1 Die folgenden Pakete werden ENTFERNT: libcapnp-0.6.1:i386 libegl-mesa0:i386 libegl1:i386 libegl1-mesa:i386 libgtk-3-0:i386 libmikmod3:i386 libmirclient9:i386 libmircommon7:i386 libsdl-mixer1.2:i386 libsdl2-2.0-0:i386 libwayland-egl1-mesa:i386 Die folgenden NEUEN Pakete werden installiert: libcapnp-0.6.1 libegl-mesa0 libmirclient9 libmircommon7 libmircore1 0 aktualisiert, 5 neu installiert, 11 zu entfernen und 0 nicht aktualisiert. Es müssen 1.045 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 12,1 MB Plattenplatz freigegeben. I had to add some packages to get apt on the right way. I'll tell after a restart what happened, I just wanted to write down what apt did ;-) -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-co
[Touch-packages] [Bug 1753776] Re: After login the screen pixelates for few seconds on GNOME on X
problem does NOT occur with Gnome 3.27.92 and a different Intel graphics: mao@mao-p6-bb:~$ inxi -Fx System:Host: mao-p6-bb Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x serial: N/A UEFI: American Megatrends v: F3 date: 04/24/2013 CPU: Dual core Intel Core i3-4130 (-MT-MCP-) arch: Haswell rev.3 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13569 clock speeds: max: 3400 MHz 1: 915 MHz 2: 1260 MHz 3: 1224 MHz 4: 1259 MHz Graphics: Card: Intel 4th Generation Core Integrated Graphics Controller bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1680x1050@59.88hz OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card-1 Intel 8 Series/C220 Series High Def. Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0 IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 94:de:80:7e:90:a7 Drives:HDD Total Size: 1000.2GB (1.2% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.0G (14%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C Fan Speeds (in rpm): cpu: N/A Info: Processes: 237 Uptime: 7 min Memory: 1431.8/7856.5MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 mao@mao-p6-bb:~$ -- 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/1753776 Title: After login the screen pixelates for few seconds on GNOME on X Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSigna
[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
Excellent, thanks - that is perfect justification to change it to Depends:, I'll get the upload going soon. -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
And it worked :-) Thanks for the hint! -- 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/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe Status in libglvnd package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: As requested in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill a new bug. Even after getting the fixed packages in https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get no 3D acceleration. Seems to be some mixup with nvidia drivers. $glxinfo ... Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x) Device: llvmpipe (LLVM 5.0, 256 bits) (0x) Version: 18.0.0 Accelerated: no Video memory: 15963MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 ... $ vdpauinfo display: :1 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 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 .tmp.unity_support_test.1: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Mar 6 08:00:28 2018 DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 5500 [8086:1616] MachineType: www.51nb.com X62 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago) dmi.bios.date: 12/10/2016 dmi.bios.vendor: 51NB dmi.bios.version: 5.011 dmi.board.asset.tag: X62 dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: X62. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: X62 dmi.product.name: X62 dmi.product.version: V10 dmi.sys.vendor: www.51nb.com version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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/libglvnd/+bug/1753663/+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 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"
Hi, I can confirm the last batch of libreoffice (1:5.4.5-0ubuntu0.17.10.4) fixes concerning apparmor fixed the many warnings mentioned in my logs. Merci/Thks -- 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/1751689 Title: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" Status in apparmor package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Fix Released Bug description: currently able to scan with xsane utility. libreoffice is not able to scan because it cannot find the scanner. log shows Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 audit(1519613074.593:93): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 audit(1519613074.593:94): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 audit(1519613074.593:95): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001 this stopped working after latest "do-release-upgrade" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashReports: 664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload 600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded 640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash 640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash CurrentDesktop: XFCE Date: Sun Feb 25 22:00:01 2018 InstallationDate: Installed on 2017-04-19 (312 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751689/+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 940030] Re: rsyslog stops working after logrotate until restarted
I've tested this on Ubuntu 16.04 with rsyslog version 8.16.0-1ubuntu3 on an install with systemd and I also tested it on the Bionic Beaver, which will become Ubuntu 18.04, with rsyslog version 8.16.0-1ubuntu10 on an install also with systemd and was unable to recreate the bug my test case on both releases follows. 1) Run 'sudo logrotate --force /etc/logrotate.conf /etc/logrotate.d/rsyslog' 2) Observe /var/log/syslog with recent timestamp 3) Run 'sudo service cups restart' 4) 'cat /var/log/syslog' 5) Observe messages regarding the restart of cups in the log file In the event that anyone is still experiencing this issue please include detailed information about the version of rsyslog you have installed, whether or not using are using systemd, and the release of Ubuntu which you are running. ** Changed in: rsyslog (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: rsyslog (Ubuntu Bionic) Assignee: girish (sajjanarg) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Fix Released Bug description: This could otherwise be titled, rsyslog reload does not create log files; only restart does. This is happening on a number of machines I work on. It's happening on 10.04 and 11.04. It might be similar to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 But in my case after the restart there is no /var/log/syslog being created, nor auth.log, kern.log, etc. The files are rotated, rsyslog is reloaded, and none of the log files are created and nothing is being logged. This has been plaguing my systems since moving from syslog-ng, which I may return to as it seems it was actually production ready. Without manually restarting those files don't exist so here's what I did on an 11.04 system: logrotate --force --verbose /etc/logrotate.conf gives: rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log /var/log/syslog does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log /var/log/kern.log does not exist -- skipping considering log /var/log/auth.log log /var/log/auth.log does not exist -- skipping considering log /var/log/user.log log /var/log/user.log does not exist -- skipping considering log /var/log/lpr.log log /var/log/lpr.log does not exist -- skipping considering log /var/log/cron.log log /var/log/cron.log does not exist -- skipping considering log /var/log/debug log /var/log/debug does not exist -- skipping considering log /var/log/messages log /var/log/messages does not exist -- skipping not running postrotate script, since no logs were rotated Then /sbin/reload rsyslog logger -i testing At this point there is no /var/log/syslog Then: /sbin/restart rsyslog And voila there is a /var/log/syslog beginning with: Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg started. Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com";] (re)start Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114 Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108 Then to recreate: logrotate --force --verbose /etc/logrotate.conf rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log needs rotating rotating log /var/log/syslog, log->rotateCount is 7 dateext suffix '-20120223' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' compressing log with: /bin/gzip renaming /var/log/syslog to /var/log/syslog-20120223 running postrotate script removing old log /var/log/syslog-20111219.gz rot