[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Ubuntu 18.04.1. Jabra Elite Sport v2. Impossible to get A2DP to stick. Have to go through multiple jumps to get it to work. E.g., 1) Shut down and start bluetooth a few times after suspend or reboot. Sometimes i try to shutdown the Jabra device as well. 2) Then connect to the device, which always fails at minimum 3 times when using the slider for connecting, and then it might add a sound device or not. It takes a long time for this to happen in any situation after successful connect. Often the sound device is not even selected if it is added, which require a second user interaction to solve. However, this step works much better using blueman. I.e., the interface and bluetooth solution in Ubuntu is buggy to say the least. At least a few bugs must exist in the interface solution considered blueman works better. 3) If connection is working and a sound device is added then the A2DP is never selected. Using the Ubuntu drop down menu to change to A2DP is pointless, it will never work, and blueman cant change profile either. Thus going back to step one and and trying again is the only solution. This process takes up to 15 minutes or more to complete. By pure luck, the A2DP setting will stick until next suspend These errors have existed for at least 12 months in my case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Confirmed Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1194176] Re: Allow service icons at service level, not just application level
[Expired for gnome-control-center-signon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center-signon (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1194176 Title: Allow service icons at service level, not just application level Status in gnome-control-center-signon package in Ubuntu: Expired Bug description: evolution-data-server-uoa 3.8.3-0ubuntu4 provides several different services and a single icon isn't sufficient to represent all of them. They don't want to use the evolution icon since EDS is more than just Evolution (it's also used by Thunderbird, GNOME Contacts, etc.). This was discussed at https://bugzilla.gnome.org/701964 Services provided by eds-uoa --- google-calendar.service google-contacts.service google-gmail.service yahoo-calendar.service yahoo-mail.service Currently, it appears that UOA only looks at the .desktop for an icon but evolution-data-server-uoa.desktop doesn't have an icon. However, /usr/share/accounts/services/google-calendar.service sets calendar /usr/share/accounts/service_types/calendar.service-type sets x-office-calendar I believe the current behavior for settings the service icon is something like: 1. Use the .desktop icon 2. If not set, don't show an icon at all. This makes the eds services look out of place. Suggested improved behavior 1. Use an icon in the /services/*.service 2. If not set, fallback to the .desktop icon 3. If not set, fallback to the icon set by the corresponding service_types/*.service_type 4. Set a generic icon ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Mon Jun 24 11:30:31 2013 InstallationDate: Installed on 2013-06-14 (10 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: gnome-control-center-signon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1194176/+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 1791090] Re: Xorg fails to start with radeon
Hmm, your monitor is 1920x1080 and yet the kernel says "texture bo too small" with "1920 1152": sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) It sounds like a texture that's 1152 tall would actually be too big, not too small. Regardless, this seems to confirm there's a bug/disagreement somewhere between Xorg and the kernel. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Xorg fails to start with radeon + Xorg fails to start with radeon (kernel rejects radeon command stream from Xorg) ** Tags added: radeon -- 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/1791090 Title: Xorg fails to start with radeon (kernel rejects radeon command stream from Xorg) Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The shell fails to start with latest version of xorg and radeon drivers. From the journal: sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: (II) RADEON(0): Setting screen physical size to 508 x 285 sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: radeon: The kernel rejected CS, see dmesg for more information (-22). sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) sept. 06 08:06:26 sark kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! The shell starts normally under wayland. Downgrading the following packages fixed the problem: xserver-xorg-video-qxl:amd64 (0.1.5-2build2, 0.1.5-2build1) xserver-xorg-video-vesa:amd64 (1:2.4.0-1, 1:2.3.4-1build3) xserver-xorg-video-amdgpu:amd64 (18.0.1-1build1, 18.0.1-1) xserver-xorg-core:amd64 (2:1.20.1-1ubuntu1, 2:1.19.6-1ubuntu4) xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.4.4-1build6) xserver-xorg-video-intel:amd64 (2:2.99.917+git20171229-1build1, 2:2.99.917+git20171229-1) xserver-xorg-video-vmware:amd64 (1:13.3.0-2build1, 1:13.2.1-1build1) xserver-xorg-video-ati:amd64 (1:18.0.1-1build1, 1:18.0.1-1) xserver-xorg-video-radeon:amd64 (1:18.0.1-1build1, 1:18.0.1-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xserver-xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 15:03:11 2018 DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:1482] InstallationDate: Installed on 2014-07-15 (1514 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-03-24 (165 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.93-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1791196] [NEW] [USB-Audio - US122 MKII, recording] Recording problem
Public bug reported: Can't get the US122 MKII listed as an input device. Not in pavucontrol, nor in sound settings nor in jackd. May be this helps, alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII jackdmp 1.9.12 ... Acquire audio card Audio1 creating alsa driver ... hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode ... Please let me know if you need further information. Regards, Alfredo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alfredo7890 F pulseaudio /dev/snd/controlC1: alfredo7890 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 22:02:55 2018 InstallationDate: Installed on 2018-03-03 (187 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 8 8 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: TASCAM US-122mkII - US122 MKII Symptom_Type: None of the above Title: [USB-Audio - US122 MKII, recording] Recording problem UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago) dmi.bios.date: 03/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1791196 Title: [USB-Audio - US122 MKII, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Can't get the US122 MKII listed as an input device. Not in pavucontrol, nor in sound settings nor in jackd. May be this helps, alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII jackdmp 1.9.12 ... Acquire audio card Audio1 creating alsa driver ... hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode ... Please let me know if you need further information. Regards, Alfredo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alfredo7890 F pulseaudio /dev/snd/controlC1: alfredo7890 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 22:02:55 2018 InstallationDate: Installed on 2018-03-03 (187 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 8 8 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: TASCAM US-122mkII - US122 MKII Symptom_Type: None of the above Title: [USB-Audio - US122 MKII, recording] Recording problem UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago) dmi.bios.date: 03/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version
[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor
I'm using Bionic. (18.04.1 LTS) x64
--
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/1698693
Title:
cups-pdf blocked by apparmor
Status in cups package in Ubuntu:
Incomplete
Bug description:
cups-pdf cannot create the ~/PDF directory if it does not exist and
fails with no indication to the user.
It should however be pointed out that cups-pdf allows the system
administrator to change it's output directory by changing the Out key
in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
if the admin changes the Out key to some other location outside of the
${HOME}/PDF directory. (It's default setting.)
cups-pdf also does not have an #include for using local overrides in
it's apparmor config. As such any fixes that the local admin makes
will be overwritten by the next update to the cups package, breaking
it again.
Description: Ubuntu 16.04.2 LTS
Release: 16.04
printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
*** 2.6.1-21 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
*** 2.1.3-4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
What happened:
cups-pdf when installed for the first time fails with the following apparmor
denials:
[ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED"
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015
comm="cups-pdf" family="unix" sock_type="stream" protocol=0
requested_mask="send receive" denied_mask="send receive" addr=none
peer_addr=none peer="/usr/sbin/cupsd"
[ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED"
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf"
family="unix" sock_type="stream" protocol=0 requested_mask="send receive"
denied_mask="send receive" addr=none peer_addr=none
peer="/usr/lib/cups/backend/cups-pdf"
[ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED"
operation="open" profile="/usr/lib/cups/backend/cups-pdf"
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
[ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED"
operation="open" profile="/usr/lib/cups/backend/cups-pdf"
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
[ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED"
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf"
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf"
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
What I expected to happen:
cups-pdf creates the pdf file it was supposed to.
As a workaround, I set cups-pdf to use the third-party settings from the cups
profile, then it worked as expected.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-11-24 (281 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64
(20171018)
Lpstat:
device for EPSONET-4550:
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
device for PDF: cups-pdf:/
MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
NonfreeKernelModules: nvidia_modeset nvidia
Package: cups 2.2.7-1ubuntu2.1
PackageArchitecture: amd64
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd:
Permission denied
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal
quiet splash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal
quiet splash
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Tags: bionic apparmor apparmor apparmor apparmor
Uname: Linux 4.15.0-33-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F21
dmi.board.asset.tag: Default string
dmi.board.name: A320M-S2H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Touch-packages] [Bug 1791174] Re: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus err
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: pam (Ubuntu) Importance: Undecided => Low ** Changed in: pam (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1791174 Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped Status in pam package in Ubuntu: Invalid Bug description: lots of package failures after upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-runtime 1.1.8-3.6ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 23:33:15 2018 ErrorMessage: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-03-17 (173 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped UpgradeStatus: Upgraded to bionic on 2018-09-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1791174/+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 1791192] [NEW] Desktop doesnt display through Chrome Remote Desktop after upgrade to 18.04
Public bug reported: Had used Chrome Remote Desktop to connect to Ubuntu Desktop when I needed to access the GUI. After upgrade the screen doesnt display. Everything else works, am able to connect over SSH, but Chrome Remote Desktop alone doesnt work. Tried installing vnc, but got error saying dont have a Display running. Have tried switching from gdm3 to lightdm. Both doesnt work after upgrade. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 6 19:28:19 2018 InstallationDate: Installed on 2016-11-08 (667 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2018-09-05 (1 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Screenshot of Chrome Remote Desktop" https://bugs.launchpad.net/bugs/1791192/+attachment/5185829/+files/Screen%20Shot%202018-09-06%20at%208.05.09%20PM.png -- 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/1791192 Title: Desktop doesnt display through Chrome Remote Desktop after upgrade to 18.04 Status in lightdm package in Ubuntu: New Bug description: Had used Chrome Remote Desktop to connect to Ubuntu Desktop when I needed to access the GUI. After upgrade the screen doesnt display. Everything else works, am able to connect over SSH, but Chrome Remote Desktop alone doesnt work. Tried installing vnc, but got error saying dont have a Display running. Have tried switching from gdm3 to lightdm. Both doesnt work after upgrade. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 6 19:28:19 2018 InstallationDate: Installed on 2016-11-08 (667 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2018-09-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1791192/+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 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package libdrm - 2.4.94-1 --- libdrm (2.4.94-1) unstable; urgency=medium [ Guido Günther ] * Enable etnaviv on arm64 (Closes: #906915) [ Timo Aaltonen ] * New upstream release. (LP: #1789924) * Update libdrm-amdgpu1.symbols and shlibs. -- Timo Aaltonen Thu, 30 Aug 2018 21:18:04 +0300 ** Changed in: libdrm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1770686] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Bug description: [Impact] Some distributions ship software-properties-gtk but not gnome-control-center. Considering that Livepatch strictly depends on the online account panel in gnome-control-center we should not show the option to enable Livepatch if those distributions, otherwise enabling Livepatch will fail and it will seem buggy. [Test Case] 1. Start xubuntu (Bionic) 2. Open software-properties-gtk 3. Go to "Updates" tab 4. Make sure no Livepatch UI is displayed [Regression Potential] Please make sure the Livepatch UI is correctly displayed in vanilla Bionic. [Original Bug Report] Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+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 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center
This bug was fixed in the package software-properties - 0.96.24.32.5 --- software-properties (0.96.24.32.5) bionic; urgency=medium * SoftwarePropertiesGtk.py: Hide livepatch widgets in flavors without an online account panel in gnome-control-center (LP: #1770686) -- Andrea Azzarone Fri, 17 Aug 2018 09:56:07 + ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Bug description: [Impact] Some distributions ship software-properties-gtk but not gnome-control-center. Considering that Livepatch strictly depends on the online account panel in gnome-control-center we should not show the option to enable Livepatch if those distributions, otherwise enabling Livepatch will fail and it will seem buggy. [Test Case] 1. Start xubuntu (Bionic) 2. Open software-properties-gtk 3. Go to "Updates" tab 4. Make sure no Livepatch UI is displayed [Regression Potential] Please make sure the Livepatch UI is correctly displayed in vanilla Bionic. [Original Bug Report] Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+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 1772629] Re: Automatic logout when resuming from suspend on Xubuntu 18.04
Were you able to identify the cause of the crash? ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1772629 Title: Automatic logout when resuming from suspend on Xubuntu 18.04 Status in systemd package in Ubuntu: Incomplete Bug description: When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind automatically logs out of the current session if the laptop has stayed suspended for more than a couple of hours. If the interval between suspend and resume is short, it doesn't log out. I still haven't discovered how long this interval has to be in order to cause the logout. I enabled debug on the systemd-logind.service, creating file _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_: [Service] Environment=SYSTEMD_LOG_LEVEL=debug which causes systemd-logind to log all D-Bus messages it handles, but couldn't spot anything that might have caused the logout. I scanned all systemd journal messages (`journalctl`) before systemd- logind starts killing the current session, investigated all that looked suspicious but couldn't find anything that might influence an automatic logout. Here are some of the messages that striked me as suspicious (they are not sequential, but pulled from different occasions): upowerd[1600]: unhandled action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0 polkitd(authority=local)[840]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.46, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) wpa_supplicant[811]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed wpa_supplicant[811]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none at-spi-bus-launcher[7031]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[7031]: after 30333 requests (30333 known processed) with 0 events remaining. systemd-logind[779]: Inhibitor xfce4-power-manager (xfce4-power-manager handles these events) pid=8611 uid=1000 mode=block stopped systemd-logind[779]: Electing new display for user paulo systemd-logind[779]: Ignoring session c8 logind config doesn't have anything that might cause this: paulo:~$ loginctl show-session EnableWallMessages=no NAutoVTs=6 KillUserProcesses=no RebootToFirmwareSetup=no IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key DelayInhibited=sleep InhibitDelayMaxUSec=5s HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=ignore HoldoffTimeoutUSec=30s IdleAction=ignore IdleActionUSec=30min PreparingForShutdown=no PreparingForSleep=no Docked=no RemoveIPC=yes RuntimeDirectorySize=615313408 InhibitorsMax=8192 NCurrentInhibitors=5 SessionsMax=8192 NCurrentSessions=1 UserTasksMax=10813 I can't find any anything that might cause an automatic logout after a time interval. I'm really stumped. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 07:36:59 2018 InstallationDate: Installed on 2018-04-28 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08FDW5 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1772629/+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 1791174] Re: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus err
The error in your log is: Setting up libpam-runtime (1.1.8-3.6ubuntu2) ... ESC[1mdpkg:ESC[0m error processing package libpam-runtime (--configure): installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped This is a very well-exercised shell script, running on an architecture (amd64) that should not be emitting SIGBUS. Is your hardware failing? ** Changed in: pam (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1791174 Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped Status in pam package in Ubuntu: Incomplete Bug description: lots of package failures after upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-runtime 1.1.8-3.6ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 23:33:15 2018 ErrorMessage: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-03-17 (173 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped UpgradeStatus: Upgraded to bionic on 2018-09-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1791174/+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 1789502] Re: Update to 0.6.50
Le 06/09/2018 à 21:25, Robert Ancell a écrit : > LightDM 1.26 uses the AccountsService extention mechanism to store > this data, so the patch is obsolete. It looks like indicator-messages still use XHasMessages, in which case that would need to be ported to the new api? https://bazaar.launchpad.net/~indicator-applet-developers/indicator- messages/trunk.16.10/view/head:/src/im-accounts-service.c#L189 It looks like BackgroudFile is fine since you ported unity-settings-daemon to the new API Unsure where KeyboardLayouts is being used, indicator-keyboard and unity-settings-daemon don't seem to reference to it -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1771340] Re: sshd failed on config reload
Could you provide links indicating that this is fixed in both Ubuntu 18.10 and Ubuntu 18.04? Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: In Progress Bug description: [Impact] sshd doesn't check the configuration when reloading. If a user generates an invalid configuration file, sshd will shut down and not come back up when the user issues a reload. [Test Case] $ lxc launch ubuntu:xenial tester $ lxc exec tester bash # echo "blah blah" >>/etc/ssh/sshd_config # systemctl reload sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-08-21 18:15:41 UTC; 19s ago * The service should have checked the config file, failed to reload, but remained active in its current configuration. In this case ssh has shut down. [Regression Potential] This code will only trigger on an invalid configuration file (in which case sshd would not load anyway), so there should be no regressions. [Other Info] autopkgtest [13:45:46]: test regress: ---] autopkgtest [13:45:47]: test regress: - - - - - - - - - - results - - - - - - - - - - regress PASS autopkgtest [13:45:47]: summary regress PASS [Original Description] After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 7536 (code=exited, status=255) ~~~ I would expect that a warning or error message is returned when the service fails while reloading it's configuration. A fix for this behaviour would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39 Uname: Linux 3.13.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 15 10:18:25 2018 InstallationDate: Installed on 2013-01-10 (1950 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago) mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771340/+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 1789924] Re: Missing Intel GPU pci-id's
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1791174] [NEW] package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus e
Public bug reported: lots of package failures after upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-runtime 1.1.8-3.6ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 23:33:15 2018 ErrorMessage: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-03-17 (173 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped UpgradeStatus: Upgraded to bionic on 2018-09-06 (0 days ago) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1791174 Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped Status in pam package in Ubuntu: New Bug description: lots of package failures after upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-runtime 1.1.8-3.6ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 23:33:15 2018 ErrorMessage: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-03-17 (173 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess was killed by signal (Bus error), core dumped UpgradeStatus: Upgraded to bionic on 2018-09-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1791174/+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 1788188] Re: transient systemd ordering cycle in boot with overlayroot
I uploaded open-iscsi_2.0.874-5ubuntu8 which has the debug code
that we were toying with included. It also includes a fix for
FTBFS bug 1791154.
--
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/1788188
Title:
transient systemd ordering cycle in boot with overlayroot
Status in systemd package in Ubuntu:
Confirmed
Bug description:
open-iscsi test utilizes overlayroot to boot a cloud-image with root
filesystem on a read-only iscsi server.
The /etc/fstab file in the image looks like this:
LABEL=cloudimg-rootfs /ext4 defaults0 0
#LABEL=UEFI /boot/efi vfatdefaults0 0
when init takes over from the initramfs, we have
/proc/cmdline:
nomodeset iscsi_initiator=maas-enlist
iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
iscsi_target_port=3260 iscsi_initiator=maas-enlist
ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
overlayroot=tmpfs console=ttyS0
ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash
/etc/fstab:
# cat /etc/fstab
#
# This fstab is in an overlay. The real one can be found at
# /media/root-ro/etc/fstab
# The original entry for '/' and other mounts have been updated to be
placed
# under /media/root-ro.
# To permanently modify this (or any other file), you should change-root
into
# a writable view of the underlying filesystem using:
# sudo overlayroot-chroot
#
#LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
/media/root-ro/ / overlay
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
#LABEL=UEFI /boot/efi vfat defaults 0 0
/root/root-ro/etc/fstab:
LABEL=cloudimg-rootfs /ext4 defaults0 0
#LABEL=UEFI /boot/efi vfatdefaults0 0
/proc/mounts:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
/media/root-ro ext4 ro,relatime 0 0
tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
overlayroot / overlay
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
0 0
/proc/1/mountinfo:
21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev
rw,size=233748k,nr_inodes=58437,mode=755
24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts
rw,gid=5,mode=620,ptmxmode=000
25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs
rw,size=49288k,mode=755
26 28 8:1 / /media/root-ro ro,relatime - ext4
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
28 0 0:24 / / ro,relatime - overlay overlayroot
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
read-only mount of block device on mount point '$ROOTMNT'
(ROOTMNT=/root). In order to set up the overlayroot, it does the
following:
mkdir /media/root-ro /media/root-rw # in the initramfs
mount -t tmpfs tmpfs-root /media/root-rw
mkdir /media/root-rw/overlay-workdir/_
mount --move $ROOTMNT /media/root-ro
mount -t overlay -o
lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
overlayroot /root
mkdir $ROOTMNT/media/root-ro
mkdir $ROOTMNT/media/root-rw
mount --move /media/root-ro "${ROOTMNT}/media/root-ro"
mount --move /media/root-rw "${ROOTMNT}/media/root-rw"
# then, if 'ro' on the command line, it mounts /root read-only.
mount -o remount,ro $ROOTMNT
The script then exits, as ROOTMNT is now set up with a read-only mount
of the overlayroot. All the mounts it has done have been moved
under ROOTMNT.
On failure systemd reports:
[ 104.098833] systemd[1]: media-root\x2dro.mount: Found ordering cycle on
-.mount/start
[ 104.109897] systemd[1]: media-root\x2dro.mount: Found dependency on
media-root\x2dro.mount/start
[ 104.121386] systemd[1]: media-root\x2dro.mount: Unable to break cycle
starting with media-root\x2dro.mount/start
[ 104.137591] systemd[1]: Requested transaction contains an unfixable
cyclic
[Touch-packages] [Bug 1791166] [NEW] Programs using the libqt5gui5 library do not start.
Public bug reported:
Programs using the libqt5gui5 library do not start.
Running in the terminal displays the message:
"VirtualBox: supR3HardenedMainGetTrustedMain:
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot
open shared object file: No such file or directory"
or
"smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot
open shared object file: No such file or directory"
My distribution is Ubuntu 18.04.1.
** Affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1791166
Title:
Programs using the libqt5gui5 library do not start.
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
Programs using the libqt5gui5 library do not start.
Running in the terminal displays the message:
"VirtualBox: supR3HardenedMainGetTrustedMain:
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot
open shared object file: No such file or directory"
or
"smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot
open shared object file: No such file or directory"
My distribution is Ubuntu 18.04.1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1791166/+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 1791168] [NEW] package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 2
Public bug reported: Several DPKG tasks were spawned and the apt upgrade process could not fork. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 6 16:49:07 2018 ErrorMessage: installed avahi-daemon package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-05-20 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: avahi Title: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1791168 Title: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 2 Status in avahi package in Ubuntu: New Bug description: Several DPKG tasks were spawned and the apt upgrade process could not fork. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: avahi-daemon 0.7-3.1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 6 16:49:07 2018 ErrorMessage: installed avahi-daemon package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-05-20 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: avahi Title: package avahi-daemon 0.7-3.1ubuntu1.1 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1791168/+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 1791156] Re: /usr/share/apport/apport-gtk:UnicodeDecodeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:known:known
Here's the Traceback:
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 597, in
app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 687, in run_argv
return self.run_crashes()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 244, in run_crashes
self.run_crash(f)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 288, in run_crash
self.collect_info()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1096, in collect_info
known_thread.exc_raise()
File "/usr/lib/python3/dist-packages/apport/REThread.py", line 63, in
exc_raise
raise self._exception[1].with_traceback(self._exception[2])
File "/usr/lib/python3/dist-packages/apport/REThread.py", line 33, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line
891, in known
url = apport.crashdb.CrashDatabase.known(self, report)
File "/usr/lib/python3/dist-packages/apport/crashdb.py", line 282, in known
contents = f.read().decode('UTF-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa3 in position 7793:
invalid start byte
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
--
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/1791156
Title:
/usr/share/apport/apport-gtk:UnicodeDecodeError:/usr/share/apport
/apport-
gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:known:known
Status in apport package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.9-0ubuntu7.3, the problem page at
https://errors.ubuntu.com/problem/ed1b5a271c91539c7dc5b75a2c72efcbd23a7829
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/ubuntu/+source/apport/+bug/1791156/+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 1791157] [NEW] can't run apt commands because apport/python are corrupt
Public bug reported: Running update/upgrade/autoremove Running apt install --reinstall * Running apt install * Running apt remove * All yield very similar errors to this. This one in particular is sudo apt install python. Preparing to unpack .../apport_2.20.9-0ubuntu7.3_all.deb ... Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site dpkg: warning: old apport package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Failed to stop apport-autoreport.path: Unit apport-autoreport.path not loaded. Failed to stop apport-autoreport.service: Unit apport-autoreport.service not loaded. Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site dpkg: error processing archive /var/cache/apt/archives/apport_2.20.9-0ubuntu7.3_all.deb (--unpack): new apport package pre-removal script subprocess returned error exit status 1 Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site dpkg: error while cleaning up: installed apport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/apport_2.20.9-0ubuntu7.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1791157 Title: can't run apt commands because apport/python are corrupt Status in apport package in Ubuntu: New Bug description: Running update/upgrade/autoremove Running apt install --reinstall * Running apt install * Running apt remove * All yield very similar errors to this. This one in particular is sudo apt install python. Preparing to unpack .../apport_2.20.9-0ubuntu7.3_all.deb ... Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site dpkg: warning: old apport package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Failed to stop apport-autoreport.path: Unit apport-autoreport.path not loaded. Failed to stop apport-autoreport.service: Unit apport-autoreport.service not loaded. Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site dpkg: error processing archive /var/cache/apt/archives/apport_2.20.9-0ubuntu7.3_all.deb (--unpack): new apport package pre-removal script subprocess returned error exit status 1 Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] ImportError: No module named site dpkg: error while cleaning up: installed apport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/apport_2.20.9-0ubuntu7.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1791157/+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 1789502] Re: Update to 0.6.50
On Thu, Sep 6, 2018 at 9:42 PM Sebastien Bacher wrote: > Hey Robert, > > Le 06/09/2018 à 10:27, Robert Ancell a écrit : > > I'm also looking at dropping the XHasMessages, BackgroundFile and > > KeyboardLayouts patches, as these are all obsolete with LightDM 1.26 - > > Is there anywhere else that might be using them? > > How "obsolete"? XHasMessages is (was?) using by unity-greeter to > indicate with an icon that there are pending messages in the session. > Did that feature got removed or superseeded? > > LightDM 1.26 uses the AccountsService extention mechanism to store this data, so the patch is obsolete. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1791156] [NEW] /usr/share/apport/apport-gtk:UnicodeDecodeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:known:known
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.9-0ubuntu7.3, the problem page at https://errors.ubuntu.com/problem/ed1b5a271c91539c7dc5b75a2c72efcbd23a7829 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/. ** Affects: apport (Ubuntu) Importance: Medium Status: New ** Tags: bionic xenial yakkety zesty -- 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/1791156 Title: /usr/share/apport/apport-gtk:UnicodeDecodeError:/usr/share/apport /apport- gtk@597:run_argv:run_crashes:run_crash:collect_info:exc_raise:run:known:known Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.9-0ubuntu7.3, the problem page at https://errors.ubuntu.com/problem/ed1b5a271c91539c7dc5b75a2c72efcbd23a7829 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/ubuntu/+source/apport/+bug/1791156/+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 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package xorg-server - 2:1.20.1-1ubuntu2 --- xorg-server (2:1.20.1-1ubuntu2) cosmic; urgency=medium * prime-sync-refactor.diff: Fix crash on modesetting+amdgpu hybrid. (LP: #1789913) * sync-i965-pciids.diff: Update intel pci-id's. (LP: #1789924) -- Timo Aaltonen Wed, 05 Sep 2018 14:13:19 +0300 ** Changed in: xorg-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Or can you elaborate a bit more how you have this setup? And, before I forget, do you have a crash file somewhere in /var/crash? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd Status in gssproxy package in Ubuntu: New Status in krb5 package in Ubuntu: New Status in libselinux package in Ubuntu: New Bug description: I have apache configured to perform a kerberized NFS4 mount using rpc.gssd and gssproxy. If I request a web page that requires NFS4 access, then gssproxy crashes, reporting a segfault in libselinux.so.1 and the web request generates a 403 error. gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150 error 4 in libselinux.so.1[7f2f5bb0d000+25000] If I run gssproxy at debug level = 3, and then load a web page, I can see the uid/principal request for www-data come in from rpc.gssd: # gssproxy -d --debug-level=3 -i -C /etc/gssproxy [2018/08/22 17:51:40]: Debug Enabled (level: 3) [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) [2018/08/22 17:52:06]: connected (fd = 10)[2018/08/22 17:52:06]: (pid = 4548) (uid = 33) (gid = 33)Segmentation fault (core dumped) Since gssproxy is required to initiate kerberos principals for any local application services - Ubuntu 18.04 does not currently support running application services with NFS4 kerberos dependencies. This has a fairly significant impact on anyone attempting to implement kerberos on Ubuntu 18.04 Ubuntu 18.04.1 LTS gssproxy 0.8.0-1 libselinux1:amd64 2.7-2build2 libgssrpc4:amd64 1.16-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+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 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Can you simplify the configuration needed to reproduce this bug? For example, does it happen when using gssapi authentication with apache, without the NFSv4 bit? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd Status in gssproxy package in Ubuntu: New Status in krb5 package in Ubuntu: New Status in libselinux package in Ubuntu: New Bug description: I have apache configured to perform a kerberized NFS4 mount using rpc.gssd and gssproxy. If I request a web page that requires NFS4 access, then gssproxy crashes, reporting a segfault in libselinux.so.1 and the web request generates a 403 error. gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150 error 4 in libselinux.so.1[7f2f5bb0d000+25000] If I run gssproxy at debug level = 3, and then load a web page, I can see the uid/principal request for www-data come in from rpc.gssd: # gssproxy -d --debug-level=3 -i -C /etc/gssproxy [2018/08/22 17:51:40]: Debug Enabled (level: 3) [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) [2018/08/22 17:52:06]: connected (fd = 10)[2018/08/22 17:52:06]: (pid = 4548) (uid = 33) (gid = 33)Segmentation fault (core dumped) Since gssproxy is required to initiate kerberos principals for any local application services - Ubuntu 18.04 does not currently support running application services with NFS4 kerberos dependencies. This has a fairly significant impact on anyone attempting to implement kerberos on Ubuntu 18.04 Ubuntu 18.04.1 LTS gssproxy 0.8.0-1 libselinux1:amd64 2.7-2build2 libgssrpc4:amd64 1.16-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+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 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
Thanks everyone! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: Fix Released Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+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 1791132] [NEW] package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of pa
Public bug reported: Don't think I changed the configuration file manually ever. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.23.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17 Uname: Linux 4.17.0-9-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Thu Sep 6 18:36:08 2018 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2011-10-14 (2519 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu4 apt 1.7.0~alpha3 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: Upgraded to cosmic on 2018-07-30 (38 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- 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/1791132 Title: package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 Status in gtk+3.0 package in Ubuntu: New Bug description: Don't think I changed the configuration file manually ever. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.23.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17 Uname: Linux 4.17.0-9-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Thu Sep 6 18:36:08 2018 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2011-10-14 (2519 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu4 apt 1.7.0~alpha3 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: Upgraded to cosmic on 2018-07-30 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1791132/+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 1789472] Re: SRU 2.56.2 to bionic
The network-monitor-race test is racy (amusingly). I retried and all except armhf tests pass. This is supposed to be fixed with 2.56.3 which is scheduled to be out soon (we'd want to check that is true before uploading). I propose that we let this one slide for this SRU. udisks2 seems to have been broken by something else - the results triggered from cryptsetup also fail in the same way, so I think those are also Not Our Problem™. I think/hope Marco's looking at the rest. Hopefully they are flaky and I'll retry any as necessary, just let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1789472 Title: SRU 2.56.2 to bionic Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Various fixes in multiple places (see https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789472/+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 1791118] [NEW] No sound output on Medion Akoya S2218 Z3735F subnotebook
Public bug reported: Hello, the Medion Akoya S2218 is a Z3735F-based subnotebook. It is possible to install Ubuntu on it, but some devices are not properly supported. I have installed a vanilla 18.04 Ubuntu 64 bit system on it and then updated to the current development version of 18.10. I have also tried the distribution's current 4.17.0-9-generic #10-Ubuntu kernel as well as current 4.19.0-rc kernels. There is no sound output. These audio-related modules are being loaded: snd_soc_sst_cht_bsw_rt5645 snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_atom_hifi2_platform snd_soc_rt5645 snd_soc_acpi snd_soc_acpi_intel_match snd_soc_rl6231 snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_pcm snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore These are blacklisted: blacklist r8723bs blacklist snd_hdmi_lpe_audio Pulseaudio still reports a "dummy device". I have tried finding solutions on the internet. There are various fixes for other Z3735F-based devices, including the tip to blacklist the snd_hdmi_lpe_audio module. None of those fixes helped for mine. I tried getting help at https://github.com/plbossart/UCM/issues/32 with no response. /var/log/syslog reports Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:36 akoya pulseaudio[1075]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:36 akoya pulseaudio[1075]: W: [pulseaudio] module-udev-detect.c: Tried to configure /devices/platform/80860F28:00/cht-bsw-rt5645/sound/card0 (alsa_card.platform-cht-bsw-rt5645) more often than 5 times in 10s Sep 6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. Sep 6 16:59:55 akoya pulseaudio[1732]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-cht-bsw-rt5645" card_name="alsa_card.platform-cht-bsw-rt5645" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Sep 6 16:59:55 akoya pulseaudio[1732]:
[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics
The !35 has some side effect for other distribution, after discuss, I made a new patch !44, it was accepted by upstream. https://gitlab.gnome.org/GNOME/gdm/merge_requests/35 https://gitlab.gnome.org/GNOME/gdm/merge_requests/44 -- 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/1780076 Title: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics Status in gdm3 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219 We found the login screen is blur, with Huawei's chip. 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) When we set the Wayland to disable, it could login. [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+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 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Changed in: iproute2 (Ubuntu)
Status: Expired => Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1791102] [NEW] udev postinst fails because kvm group already exists and is not a system group
Public bug reported: The udev postinst failed like this on an upgrade in cosmic from 237-3ubuntu10.3 to 239-7ubuntu7: Setting up udev (239-7ubuntu7) ... Installing new version of config file /etc/udev/udev.conf ... The group `kvm' already exists and is not a system group. Exiting. dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 The postinst script seemd to blindly add the kvm group. It is relying on the fact that the groups it's trying to add are already system groups, in which case addgroup --system doesn't fail case "$1" in configure) # update/create hwdb before we (re)start udev update_hwdb # Add new system group used by udev rules addgroup --quiet --system input # Make /dev/kvm accessible to kvm group addgroup --quiet --system kvm But on this machine "kvm" has a high gid, so it's not deemed to be a system group, in which case addgroup fails. root@diamond:~# getent group input kvm input:x:106: kvm:x:1001: root@diamond:~# addgroup --quiet --system input;echo $? 0 root@diamond:~# addgroup --quiet --system kvm;echo $? The group `kvm' already exists and is not a system group. Exiting. 1 Someone, or some package, probably did an addgroup without --system some time ago. A quick grep in /var/lib/dpkg/info shows at least 3 packages trying to add a group called kvm: root@diamond:~# grep -E "addgroup.*kvm" /var/lib/dpkg/info/* /var/lib/dpkg/info/libvirt-daemon-system.postinst:addgroup --quiet --system kvm /var/lib/dpkg/info/qemu-system-common.postinst:addgroup --quiet --system kvm || true /var/lib/dpkg/info/qemu-system-common.preinst:addgroup --quiet --system kvm || true /var/lib/dpkg/info/udev.postinst:addgroup --quiet --system kvm || /bin/true ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1791102 Title: udev postinst fails because kvm group already exists and is not a system group Status in systemd package in Ubuntu: New Bug description: The udev postinst failed like this on an upgrade in cosmic from 237-3ubuntu10.3 to 239-7ubuntu7: Setting up udev (239-7ubuntu7) ... Installing new version of config file /etc/udev/udev.conf ... The group `kvm' already exists and is not a system group. Exiting. dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 The postinst script seemd to blindly add the kvm group. It is relying on the fact that the groups it's trying to add are already system groups, in which case addgroup --system doesn't fail case "$1" in configure) # update/create hwdb before we (re)start udev update_hwdb # Add new system group used by udev rules addgroup --quiet --system input # Make /dev/kvm accessible to kvm group addgroup --quiet --system kvm But on this machine "kvm" has a high gid, so it's not deemed to be a system group, in which case addgroup fails. root@diamond:~# getent group input kvm input:x:106: kvm:x:1001: root@diamond:~# addgroup --quiet --system input;echo $? 0 root@diamond:~# addgroup --quiet --system kvm;echo $? The group `kvm' already exists and is not a system group. Exiting. 1 Someone, or some package, probably did an addgroup without --system some time ago. A quick grep in /var/lib/dpkg/info shows at least 3 packages trying to add a group called kvm: root@diamond:~# grep -E "addgroup.*kvm" /var/lib/dpkg/info/* /var/lib/dpkg/info/libvirt-daemon-system.postinst:addgroup --quiet --system kvm /var/lib/dpkg/info/qemu-system-common.postinst:addgroup --quiet --system kvm || true /var/lib/dpkg/info/qemu-system-common.preinst:addgroup --quiet --system kvm || true /var/lib/dpkg/info/udev.postinst:addgroup --quiet --system kvm || /bin/true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791102/+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 1791090] Re: Xorg fails to start with radeon
** Tags added: rls-cc-incoming -- 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/1791090 Title: Xorg fails to start with radeon Status in xorg package in Ubuntu: New Bug description: The shell fails to start with latest version of xorg and radeon drivers. From the journal: sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: (II) RADEON(0): Setting screen physical size to 508 x 285 sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: radeon: The kernel rejected CS, see dmesg for more information (-22). sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) sept. 06 08:06:26 sark kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! The shell starts normally under wayland. Downgrading the following packages fixed the problem: xserver-xorg-video-qxl:amd64 (0.1.5-2build2, 0.1.5-2build1) xserver-xorg-video-vesa:amd64 (1:2.4.0-1, 1:2.3.4-1build3) xserver-xorg-video-amdgpu:amd64 (18.0.1-1build1, 18.0.1-1) xserver-xorg-core:amd64 (2:1.20.1-1ubuntu1, 2:1.19.6-1ubuntu4) xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.4.4-1build6) xserver-xorg-video-intel:amd64 (2:2.99.917+git20171229-1build1, 2:2.99.917+git20171229-1) xserver-xorg-video-vmware:amd64 (1:13.3.0-2build1, 1:13.2.1-1build1) xserver-xorg-video-ati:amd64 (1:18.0.1-1build1, 1:18.0.1-1) xserver-xorg-video-radeon:amd64 (1:18.0.1-1build1, 1:18.0.1-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xserver-xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 15:03:11 2018 DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:1482] InstallationDate: Installed on 2014-07-15 (1514 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-03-24 (165 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.93-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1791090/+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 1791094] [NEW] package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een
Public bug reported: keyboard-configuration console-setup-linux console-setup libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 6 15:10:31 2018 DpkgHistoryLog: Start-Date: 2018-09-06 15:10:30 Commandline: apt-get install Requested-By: frans (1000) DpkgTerminalLog: Instellen van keyboard-configuration (1.178ubuntu2.6) ... /var/lib/dpkg/info/keyboard-configuration.config: 13: /etc/default/keyboard: Syntax error: Unterminated quoted string dpkg: fout bij verwerken van pakket keyboard-configuration (--configure): geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 ErrorMessage: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 InstallationDate: Installed on 2018-06-20 (77 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1791094 Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post- installation script subproces meldde een fout afsluitstatus 2 Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration console-setup-linux console-setup libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 6 15:10:31 2018 DpkgHistoryLog: Start-Date: 2018-09-06 15:10:30 Commandline: apt-get install Requested-By: frans (1000) DpkgTerminalLog: Instellen van keyboard-configuration (1.178ubuntu2.6) ... /var/lib/dpkg/info/keyboard-configuration.config: 13: /etc/default/keyboard: Syntax error: Unterminated quoted string dpkg: fout bij verwerken van pakket keyboard-configuration (--configure): geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 ErrorMessage: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 InstallationDate: Installed on 2018-06-20 (77 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 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/1791094/+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 1791095] [NEW] package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een
Public bug reported: keyboard-configuration console-setup-linux console-setup libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 6 15:10:31 2018 DpkgHistoryLog: Start-Date: 2018-09-06 15:10:30 Commandline: apt-get install Requested-By: frans (1000) DpkgTerminalLog: Instellen van keyboard-configuration (1.178ubuntu2.6) ... /var/lib/dpkg/info/keyboard-configuration.config: 13: /etc/default/keyboard: Syntax error: Unterminated quoted string dpkg: fout bij verwerken van pakket keyboard-configuration (--configure): geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 ErrorMessage: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 InstallationDate: Installed on 2018-06-20 (77 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1791095 Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post- installation script subproces meldde een fout afsluitstatus 2 Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration console-setup-linux console-setup libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 6 15:10:31 2018 DpkgHistoryLog: Start-Date: 2018-09-06 15:10:30 Commandline: apt-get install Requested-By: frans (1000) DpkgTerminalLog: Instellen van keyboard-configuration (1.178ubuntu2.6) ... /var/lib/dpkg/info/keyboard-configuration.config: 13: /etc/default/keyboard: Syntax error: Unterminated quoted string dpkg: fout bij verwerken van pakket keyboard-configuration (--configure): geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 ErrorMessage: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 InstallationDate: Installed on 2018-06-20 (77 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 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/1791095/+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 1791090] Re: Xorg fails to start with radeon
Journal from a failed boot. ** Attachment added: "failed-boot-radeon.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1791090/+attachment/5185620/+files/failed-boot-radeon.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1791090 Title: Xorg fails to start with radeon Status in xorg package in Ubuntu: New Bug description: The shell fails to start with latest version of xorg and radeon drivers. From the journal: sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: (II) RADEON(0): Setting screen physical size to 508 x 285 sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: radeon: The kernel rejected CS, see dmesg for more information (-22). sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) sept. 06 08:06:26 sark kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! The shell starts normally under wayland. Downgrading the following packages fixed the problem: xserver-xorg-video-qxl:amd64 (0.1.5-2build2, 0.1.5-2build1) xserver-xorg-video-vesa:amd64 (1:2.4.0-1, 1:2.3.4-1build3) xserver-xorg-video-amdgpu:amd64 (18.0.1-1build1, 18.0.1-1) xserver-xorg-core:amd64 (2:1.20.1-1ubuntu1, 2:1.19.6-1ubuntu4) xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.4.4-1build6) xserver-xorg-video-intel:amd64 (2:2.99.917+git20171229-1build1, 2:2.99.917+git20171229-1) xserver-xorg-video-vmware:amd64 (1:13.3.0-2build1, 1:13.2.1-1build1) xserver-xorg-video-ati:amd64 (1:18.0.1-1build1, 1:18.0.1-1) xserver-xorg-video-radeon:amd64 (1:18.0.1-1build1, 1:18.0.1-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xserver-xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 15:03:11 2018 DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:1482] InstallationDate: Installed on 2014-07-15 (1514 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-03-24 (165 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.93-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1791090/+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 1791090] [NEW] Xorg fails to start with radeon
Public bug reported: The shell fails to start with latest version of xorg and radeon drivers. >From the journal: sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: (II) RADEON(0): Setting screen physical size to 508 x 285 sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: radeon: The kernel rejected CS, see dmesg for more information (-22). sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) sept. 06 08:06:26 sark kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! The shell starts normally under wayland. Downgrading the following packages fixed the problem: xserver-xorg-video-qxl:amd64 (0.1.5-2build2, 0.1.5-2build1) xserver-xorg-video-vesa:amd64 (1:2.4.0-1, 1:2.3.4-1build3) xserver-xorg-video-amdgpu:amd64 (18.0.1-1build1, 18.0.1-1) xserver-xorg-core:amd64 (2:1.20.1-1ubuntu1, 2:1.19.6-1ubuntu4) xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.4.4-1build6) xserver-xorg-video-intel:amd64 (2:2.99.917+git20171229-1build1, 2:2.99.917+git20171229-1) xserver-xorg-video-vmware:amd64 (1:13.3.0-2build1, 1:13.2.1-1build1) xserver-xorg-video-ati:amd64 (1:18.0.1-1build1, 1:18.0.1-1) xserver-xorg-video-radeon:amd64 (1:18.0.1-1build1, 1:18.0.1-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xserver-xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 15:03:11 2018 DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:1482] InstallationDate: Installed on 2014-07-15 (1514 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-03-24 (165 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.93-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic regression reproducible 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/1791090 Title: Xorg fails to start with radeon Status in xorg package in Ubuntu: New Bug description: The shell fails to start with latest version of xorg and radeon drivers. From the journal: sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: (II) RADEON(0): Setting screen physical size to 508 x 285 sept. 06 08:06:26 sark /usr/lib/gdm3/gdm-x-session[6404]: radeon: The kernel rejected CS, see dmesg for more information (-22). sept. 06 08:06:26 sark kernel: radeon :01:00.0: evergreen_cs_track_validate_texture:855 texture bo too small (layer size 8847360, offset 0, max layer 1, depth 1, bo size 4096) (1920 1152) sept. 06 08:06:26 sark kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! The shell starts normally under wayland. Downgrading the following packages fixed the problem: xserver-xorg-video-qxl:amd64 (0.1.5-2build2, 0.1.5-2build1)
[Touch-packages] [Bug 1790951] Re: Black vertical line on Right Side of the Screen
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790951 Title: Black vertical line on Right Side of the Screen Status in xorg package in Ubuntu: New Bug description: The OS appears to not recognize the monitors size and no mater if I select the native resolution, the black line still there. I've notice also that there are 2 display options, LVDS and VGA, but the problem is that the VGA doesn't exist, only the LVDS. I've already done the xrandr commands, and added the resolutions witch fitted better to the machine, but my guess is that it is not the resolution, it is a miscommunication between the OS and the hardware. Please help, I'm a linux user with less experience, but I like it a lot and I wish to stay in Ubuntu(even with that black line, but it would be better to not). Thanks for your awesome work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 5 14:57:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics Controller [104d:9044] Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics Controller [104d:9044] InstallationDate: Installed on 2018-08-31 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Sony Corporation VGC-JS160J ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=d74eae8d-b73a-4fd9-ac75-8f3ea6bed617 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0201T4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 13 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0201T4:bd08/29/2008:svnSonyCorporation:pnVGC-JS160J:pvrC6U09RL6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct13:cvrN/A: dmi.product.family: N/A dmi.product.name: VGC-JS160J dmi.product.version: C6U09RL6 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790951/+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 1790747] Re: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- 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/1790747 Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 127 Status in console-setup package in Ubuntu: Confirmed Bug description: When I upgrade, this happens. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 08:32:45 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-06-22 (74 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 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/1790747/+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 1790960] Re: I ve installed ubuntu and upgraded it + some apps.
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790960 Title: I ve installed ubuntu and upgraded it + some apps. Status in xorg package in Ubuntu: New Bug description: I don't know from where I catch that bug. Can U help me terminate it ? Thanks . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Sep 5 22:22:09 2018 DistUpgraded: 2018-09-02 10:47:36,007 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 7340] [103c:188b] InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP 255 G1 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=41406866-69b5-46b7-b891-b3c847e2be2b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-02 (3 days ago) dmi.bios.date: 06/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 188B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 69.18 dmi.chassis.asset.tag: 5CG33351SV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.37:bd06/26/2013:svnHewlett-Packard:pnHP255G1NotebookPC:pvr08881330591620110:rvnHewlett-Packard:rn188B:rvrKBCVersion69.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN dmi.product.name: HP 255 G1 Notebook PC dmi.product.version: 08881330591620110 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Sep 2 03:55:29 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790960/+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 1790926] Re: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW
Bug error occurs only when running and used xfce desktop If the gnome environment is used Bedbug does not occur The system does not report an error when the gnome graphics environment is used -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1790926 Title: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW Status in dbus package in Ubuntu: New Bug description: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 20:34:37 2018 InstallationDate: Installed on 2018-06-18 (78 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1790926/+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 1791061] [NEW] package perl-base 5.22.1-9ubuntu16.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat
Public bug reported: an error occurred broken count>0 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-base 5.22.1-9ubuntu0.5 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Sep 6 16:54:24 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DpkgTerminalLog: dpkg: error processing package perl-base (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-07-07 (60 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package perl-base 5.22.1-9ubuntu0.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (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 perl in Ubuntu. https://bugs.launchpad.net/bugs/1791061 Title: package perl-base 5.22.1-9ubuntu16.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in perl package in Ubuntu: New Bug description: an error occurred broken count>0 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-base 5.22.1-9ubuntu0.5 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Sep 6 16:54:24 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DpkgTerminalLog: dpkg: error processing package perl-base (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-07-07 (60 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package perl-base 5.22.1-9ubuntu0.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1791061/+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 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center
@sill2100 sorry about that. I tested 0.96.24.32.5 both in vanilla bionic and in xubuntu bionic. I performed the following verification steps as per description: Xubuntu: " [Test Case] 1. Start xubuntu (Bionic) 2. Open software-properties-gtk 3. Go to "Updates" tab 4. Make sure no Livepatch UI is displayed " Vanilla ubuntu: Xubuntu: " [Test Case] 1. Start ubuntu (Bionic) 2. Open software-properties-gtk 3. Go to "Updates" tab 4. Make sure Livepatch UI is displayed " Screenshot attached for xubuntu. ** Attachment added: "Screenshot from 2018-09-06 13-31-58.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+attachment/5185576/+files/Screenshot%20from%202018-09-06%2013-31-58.png -- 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/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: [Impact] Some distributions ship software-properties-gtk but not gnome-control-center. Considering that Livepatch strictly depends on the online account panel in gnome-control-center we should not show the option to enable Livepatch if those distributions, otherwise enabling Livepatch will fail and it will seem buggy. [Test Case] 1. Start xubuntu (Bionic) 2. Open software-properties-gtk 3. Go to "Updates" tab 4. Make sure no Livepatch UI is displayed [Regression Potential] Please make sure the Livepatch UI is correctly displayed in vanilla Bionic. [Original Bug Report] Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+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 1790948] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1790948 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: The problem appeared during upgrading from 16.04 to 18.04 Similar problems were reported, but for upgrade 14.04 to 16.04, so I decided to open a new bug. The upgrade left the system in a broken state: root@storage:~# apt update Hit:1 http://ro.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://ro.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://ro.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 2446 packages can be upgraded. Run 'apt list --upgradable' to see them. root@storage:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: audacious : Depends: libaudcore5 (= 3.9-2) but it is not installed audacious-plugins : Depends: audacious-plugins-data (= 3.9-1build2) but 3.6.2-2ubuntu1 is installed Depends: libaudcore5 (>= 3.9) but it is not installed Depends: libaudgui5 (>= 3.9) but it is not installed Depends: libaudtag3 (>= 3.8) but it is not installed Depends: libfluidsynth1 (>= 1.1.6-4~) but 1.1.6-3 is installed bogofilter-bdb : Depends: libgsl2 but it is not installable checkbox-converged : Depends: qtdeclarative5-ubuntu-ui-toolkit-plugin but it is not installable debconf : Breaks: update-notifier-common (< 3.187~) but 3.168.9 is installed gnupg : Breaks: software-properties-common (<= 0.96.24.3) but 0.96.20.7 is installed kdeconnect-plasma : Depends: plasma-workspace but it is not installed libavogadro1 : Depends: libglew2.0 (>= 1.12.0) but it is not installed libguvcview-1.1-1 : Depends: libgsl2 but it is not installable liboxideqtquick0 : Depends: liboxideqtcore0 (= 1.21.5-0ubuntu0.16.04.1) but it is not installable libunity-webapps0 : Depends: unity-webapps-service but it is not installable mplayer : Depends: libdirectfb-1.7-7 (>= 1.7.7) but it is not installed phonon4qt5-backend-gstreamer : Depends: phonon-backend-gstreamer-common (= 4:4.9.0-1) but 4:4.8.2-0ubuntu2 is installed software-properties-kde : Depends: python3-pyqt5 but it is not installed unity-control-center-signon : Depends: unity-control-center but it is not installed unity-webapps-qml : Depends: qtdeclarative5-ubuntu-ui-toolkit-plugin but it is not installable or qtdeclarative5-ubuntu-ui-toolkit-plugin-gles but it is not installable update-notifier : Depends: update-notifier-common (= 3.192.1.3) but 3.168.9 is installed xaos : Depends: libgsl2 but it is not installable xorg : Depends: xserver-xorg (>= 1:7.7+19ubuntu7.1) but 1:7.7+13ubuntu3.1 is installed E: Unmet dependencies. Try using -f. Details: 1) Description:Ubuntu 18.04.1 LTS Release:18.04 2) fontconfig: Installed: 2.11.94-0ubuntu1.1 Candidate: 2.12.6-0ubuntu2 Version table: 2.12.6-0ubuntu2 500 500 http://ro.archive.ubuntu.com/ubuntu bionic/main amd64 Packages *** 2.11.94-0ubuntu1.1 100 100 /var/lib/dpkg/status 3) I expected a successful upgrade from 16.04 to 18.04 4) Now I have a broken system :) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Sep 5 22:11:25 2018 ErrorMessage: triggers looping, abandoned RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1790948/+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 1790339] Re: vim package not installed properly
This appears to be a packaging problem with vim. Package vim-common installs /usr/share/applications/vim.desktop, and its exec line points to "vim", which isn't necessarily installed. ** Package changed: gnome-software (Ubuntu) => vim (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1790339 Title: vim package not installed properly Status in vim package in Ubuntu: New Bug description: Linux carbon 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux TO REPRODUCE: 1. Install fresh Xubuntu bionic beaver 18.04.1 LTS 2. Go to main menu and select "Software" to start gnome-software 3. Click down arrow to reveal accessories and select 4. Find Vim entry and enter; Vim is reported as installed 5. Click on "Launch" and nothing happens 6. Type Super T to launch a terminal and type "vim" enter; Command 'vim' not found 7. Type "gvim" enter; Command 'gvim' not found 8. Type "man vim" and a vim command is reported (but obviously not available) 9. Type sudo fin / -name '*vim*' | grep bin; only /usr/bin/vim.tiny shows up EXPECTED BEHAVIOUR: - Selecting "launch" vim in Gnome Software is expected to launch vim - Type "vim" command in a terminal is expected to launch vim, especially when "man vim" says that command is available - If the Vim package is installed a full vim is expected FIX: - Run "sudo apt update", "sudo apt install vim" and vim is then available from gnome software and terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 2 11:51:00 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-09-01 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.2 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1790339/+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 1790339] [NEW] vim package not installed properly
You have been subscribed to a public bug: Linux carbon 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux TO REPRODUCE: 1. Install fresh Xubuntu bionic beaver 18.04.1 LTS 2. Go to main menu and select "Software" to start gnome-software 3. Click down arrow to reveal accessories and select 4. Find Vim entry and enter; Vim is reported as installed 5. Click on "Launch" and nothing happens 6. Type Super T to launch a terminal and type "vim" enter; Command 'vim' not found 7. Type "gvim" enter; Command 'gvim' not found 8. Type "man vim" and a vim command is reported (but obviously not available) 9. Type sudo fin / -name '*vim*' | grep bin; only /usr/bin/vim.tiny shows up EXPECTED BEHAVIOUR: - Selecting "launch" vim in Gnome Software is expected to launch vim - Type "vim" command in a terminal is expected to launch vim, especially when "man vim" says that command is available - If the Vim package is installed a full vim is expected FIX: - Run "sudo apt update", "sudo apt install vim" and vim is then available from gnome software and terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 2 11:51:00 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-09-01 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.2 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- vim package not installed properly https://bugs.launchpad.net/bugs/1790339 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim 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
Re: [Touch-packages] [Bug 1789502] Re: Update to 0.6.50
Hey Robert, Le 06/09/2018 à 10:27, Robert Ancell a écrit : > I'm also looking at dropping the XHasMessages, BackgroundFile and > KeyboardLayouts patches, as these are all obsolete with LightDM 1.26 - > Is there anywhere else that might be using them? How "obsolete"? XHasMessages is (was?) using by unity-greeter to indicate with an icon that there are pending messages in the session. Did that feature got removed or superseeded? -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie
This bug was fixed in the package apport - 2.20.9-0ubuntu7.3 --- apport (2.20.9-0ubuntu7.3) bionic; urgency=medium [ Didier Roche ] * Add a remember option to whoopsie so that users can diminish crash interactions (LP: #1778497) * Move apport autoreport service files to apport binary package. Having them in apport-noui was creating a bug where autoreport wasn't working on desktop. As we check in the launched script for whoopsie and autoreport file, we don't autoreport by default. (LP: #1778694) apport-noui still touches the file to enable autoreport on install. * Remove upstart service and watershed dependency. * Assume if no whoopsie that crash reporting is enabled: As the old configuration that was a whoopsie configuration file that was that was never updated by the whoopsie API, we assume that no whoopsie installed (not the default) == manual send report is allowed. If people want to disable crash reporting: - get whoopsie installed and disable crash reporting in g-c-c - uninstall apport [ Brian Murray ] * Start apport-autoreport after installing apport-noui which is part of improving apport's automatic crash reporing feature. (LP: #1778694) -- Didier Roche Tue, 10 Jul 2018 11:10:15 +0200 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1778694 Title: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Bug description: [ Impact ] * The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of apport binary package). We should move the unit to apport package itself. [ Test Case ] * Install the new apport package from proposed * Set in g-c-c, privacy panel, to report bugs automatically * Make one program dumping a core dump * Wait for a while, you should have a .upload and .uploaded files in addition to the .crash one in /var/crash [ Regression potential ] The systemd units were in apport-noui previously, we moved them and made them conditional to whoopsie being installed. apport-noui is still useful by turning autoreport on, so people upgrading shouldn't have any impact or difference. The units have been renamed to make sense and avoid package files overwrite. - There are 2 possible solutions: - promoting apport-noui to main, and seeding it. - or considering there is no reason anymore to have a separate apport-noui pacakge (no more phone factor), and so move the systemd units to apport, having a conditional file on whoopsie installed (no more dependency) and autoreport enabled, shipping those units binary package shipping those units (renamed to apport-autoreport.*) directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778694/+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 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
This bug was fixed in the package apport - 2.20.9-0ubuntu7.3 --- apport (2.20.9-0ubuntu7.3) bionic; urgency=medium [ Didier Roche ] * Add a remember option to whoopsie so that users can diminish crash interactions (LP: #1778497) * Move apport autoreport service files to apport binary package. Having them in apport-noui was creating a bug where autoreport wasn't working on desktop. As we check in the launched script for whoopsie and autoreport file, we don't autoreport by default. (LP: #1778694) apport-noui still touches the file to enable autoreport on install. * Remove upstart service and watershed dependency. * Assume if no whoopsie that crash reporting is enabled: As the old configuration that was a whoopsie configuration file that was that was never updated by the whoopsie API, we assume that no whoopsie installed (not the default) == manual send report is allowed. If people want to disable crash reporting: - get whoopsie installed and disable crash reporting in g-c-c - uninstall apport [ Brian Murray ] * Start apport-autoreport after installing apport-noui which is part of improving apport's automatic crash reporing feature. (LP: #1778694) -- Didier Roche Tue, 10 Jul 2018 11:10:15 +0200 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1778694] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1778694 Title: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] * The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. apport-noui is just a set of systemd unit starting whoopsie-upload-all (part of apport binary package). We should move the unit to apport package itself. [ Test Case ] * Install the new apport package from proposed * Set in g-c-c, privacy panel, to report bugs automatically * Make one program dumping a core dump * Wait for a while, you should have a .upload and .uploaded files in addition to the .crash one in /var/crash [ Regression potential ] The systemd units were in apport-noui previously, we moved them and made them conditional to whoopsie being installed. apport-noui is still useful by turning autoreport on, so people upgrading shouldn't have any impact or difference. The units have been renamed to make sense and avoid package files overwrite. - There are 2 possible solutions: - promoting apport-noui to main, and seeding it. - or considering there is no reason anymore to have a separate apport-noui pacakge (no more phone factor), and so move the systemd units to apport, having a conditional file on whoopsie installed (no more dependency) and autoreport enabled, shipping those units binary package shipping those units (renamed to apport-autoreport.*) directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778694/+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 1778497] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1789472] Re: SRU 2.56.2 to bionic
The new glib2.0 upload seems to have a lot of autopkgtest regressions listed - could you take a look and assess which one of those can be real potential regressions? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1789472 Title: SRU 2.56.2 to bionic Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Various fixes in multiple places (see https://gitlab.gnome.org/GNOME/glib/blob/d4b603/NEWS) so various apps could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789472/+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 1789822] Re: Colour profile deactivated after interrupted screen fade-out
Ubuntu 16.04 is supported, but we have a rather confusing policy of marking all bugs as fixed as soon as any release exists with the fix. To get a fix into 16.04 we would still use this bug, but would need to find out *what* fixed it in 18.10 etc first. -- 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/1789822 Title: Colour profile deactivated after interrupted screen fade-out Status in colord package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: When power management blanks the screen out and the process is interrupted, the colour profile is deactivated and never set back. The profile has to be re-applied in 'Color' settings manually. Expected behaviour: Colour profile remains active during and after a screen fade-out. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.54 Tue Aug 14 19:02:34 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1~16.04) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Aug 30 08:03:53 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f6] MachineType: LENOVO 244759G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=cf56f770-2527-47cc-bf3b-a1815c6c2a09 ro quiet splash acpi_osi=Linux acpi_backlight=none vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 244759G dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA6WW(2.66):bd08/24/2016:svnLENOVO:pn244759G:pvrThinkPadW530:rvnLENOVO:rn244759G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 244759G dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 29 13:40:48 2018 xserver.configfile: default xserver.errors: evdev: Logitech USB Laser Mouse: Unable to open evdev device "/dev/input/event16". evdev: HID 046a:0023: Unable to open evdev device "/dev/input/event17". evdev: HID 046a:0023: Unable to open evdev device "/dev/input/event18". xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1789822/+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 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma
This bug was fixed in the package qtdeclarative-opensource-src - 5.9.5-0ubuntu1.1 --- qtdeclarative-opensource-src (5.9.5-0ubuntu1.1) bionic; urgency=medium * Cherry-pick upstream patch to fix memory leak in image slideshows in KDE Plasma (LP: #1761016). -- Dmitry Shachnev Sun, 26 Aug 2018 14:32:09 +0300 ** Changed in: qtdeclarative-opensource-src (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 qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: Fix Released Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+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 1761016] Update Released
The verification of the Stable Release Update for qtdeclarative- opensource-src has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1761016 Title: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src source package in Bionic: Fix Committed Bug description: [Impact] * Due to a Qt bug, using an image slideshow for the wallpaper causes a memory leak that eventually causes the system to freeze. The severity of the leak is proportional to the speed with which images are changed in the slideshow. * Given the popularity of the image slideshow wallpaper feature, this is a high-profile, easily reproducible issue. * See https://bugs.kde.org/show_bug.cgi?id=368838 and https://codereview.qt-project.org/#/c/224684/ * An attempt was made to backport the fix prior to Bionic's release, but this was overlooked or unsuccessful (see the history here). As a result, it now needs to be done as an SRU. [Test Case] * Use KDE Plasma * Right-click on the desktop and choose "Configure Desktop" * Change the wallpaper type to "Slideshow" and choose a folder full of images * Click Apply * Wait a few days; Plasma will eventually totally freeze [Regression Potential] * Regressions are unlikely given that the specific backport patch has been well-tested by many in https://bugs.kde.org/show_bug.cgi?id=368838, and the actual code fix in Qt was released to users in Qt 5.11 months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center
Please include a bit more information when performing verification! At least the version number of the package tested and some confirmation that the verification steps have been performed. Thank you! -- 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/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: [Impact] Some distributions ship software-properties-gtk but not gnome-control-center. Considering that Livepatch strictly depends on the online account panel in gnome-control-center we should not show the option to enable Livepatch if those distributions, otherwise enabling Livepatch will fail and it will seem buggy. [Test Case] 1. Start xubuntu (Bionic) 2. Open software-properties-gtk 3. Go to "Updates" tab 4. Make sure no Livepatch UI is displayed [Regression Potential] Please make sure the Livepatch UI is correctly displayed in vanilla Bionic. [Original Bug Report] Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+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 1134036] Update Released
The verification of the Stable Release Update for base-files has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: Fix Released Status in maas package in Ubuntu: Invalid Status in base-files source package in Bionic: Fix Released Status in maas source package in Bionic: New Bug description: [impact] The setup: 1) The user has LC_ALL set to a locale on their machine (or some other LC_* variable but it's usually LC_ALL). 2) This locale does not exist on an Ubuntu server. 3) The user sshes into the server. ssh (at least with the settings that are default on Debian and Ubuntu and Fedora) send the value of LC_ALL to the remote server, where the default settings on Ubuntu allow this to be set in the environment of the process it launches. Because we are now in a situation where LC_ALL is set to a value that is not valid for the system, various undesirable things happen, including ugly messages from cloud-init and perl complaining every time a perl process starts and the bug that the original description below describes. [test case] Configure the setup as described above. Ssh into the server and run "perl < /dev/null" and check for warnings. [regression potential] This adds a step to the startup of every login shell, which obviously is not entirely trivial. However, the new executable being invoked is very simple and even if it fails, the startup of the shell should not be inhibited. [original description] If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+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 1134036] Re: Failure when using ssh with a locale that is not configured on the server
This bug was fixed in the package base-files - 10.1ubuntu2.3 --- base-files (10.1ubuntu2.3) bionic; urgency=medium * Install locale-check command to /usr/bin and invoke it from /etc/profile.d/01-locale-fix.sh to ensure locale related environment variables are set to valid values. (LP: #1134036) -- Michael Hudson-Doyle Mon, 20 Aug 2018 11:44:58 +1200 ** Changed in: base-files (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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: Fix Released Status in maas package in Ubuntu: Invalid Status in base-files source package in Bionic: Fix Released Status in maas source package in Bionic: New Bug description: [impact] The setup: 1) The user has LC_ALL set to a locale on their machine (or some other LC_* variable but it's usually LC_ALL). 2) This locale does not exist on an Ubuntu server. 3) The user sshes into the server. ssh (at least with the settings that are default on Debian and Ubuntu and Fedora) send the value of LC_ALL to the remote server, where the default settings on Ubuntu allow this to be set in the environment of the process it launches. Because we are now in a situation where LC_ALL is set to a value that is not valid for the system, various undesirable things happen, including ugly messages from cloud-init and perl complaining every time a perl process starts and the bug that the original description below describes. [test case] Configure the setup as described above. Ssh into the server and run "perl < /dev/null" and check for warnings. [regression potential] This adds a step to the startup of every login shell, which obviously is not entirely trivial. However, the new executable being invoked is very simple and even if it fails, the startup of the shell should not be inhibited. [original description] If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+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 1789502] Re: Update to 0.6.50
I'm also looking at dropping the XHasMessages, BackgroundFile and KeyboardLayouts patches, as these are all obsolete with LightDM 1.26 - Is there anywhere else that might be using them? Does anyone know if the InputSources and FormatsLocale is still applicable and which components use it? If they are still used I'd like to fix those to use the AccountsService extension mechanism - then we can drop the patches. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
Patches are here: https://gitlab.freedesktop.org/rancell/accountsservice/tree/ubuntu Please test / look over. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1790098] Re: vlan created on bond fails auto activation on updating parent network bond
** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete -- 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/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it gets
[Touch-packages] [Bug 1752411] Update Released
The verification of the Stable Release Update for avahi has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Fix Released Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in strongswan package in Ubuntu: Invalid Status in avahi source package in Bionic: Fix Released Status in bind9 source package in Bionic: Confirmed Status in avahi source package in Cosmic: Fix Released Status in bind9 source package in Cosmic: Confirmed Status in avahi package in Debian: New Bug description: [Impact] * Network connections for some users fail (in some cases a direct interface, in others when connecting a VPN) because the 'host' command to check for .local in DNS called by /usr/lib/avahi/avahi-daemon- check-dns.sh never times out like it should - leaving the script hanging indefinitely blocking interface up and start-up. This appears to be a bug in host caused in some circumstances however we implement a workaround to call it under 'timeout' as the issue with 'host' has not easily been identified, and in any case acts as a fall-back. [Test Case] * Multiple people have been unable to create a reproducer on a generic machine (e.g. it does not occur in a VM), I have a specific machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM) by simply "ifdown br0; ifup br0" and there are clearly 10s of other users affected in varying circumstances that all involve the same symptoms but no clear test case exists. Best I can suggest is that I test the patch on my system to ensure it works as expected, and the change is only 1 line which is fairly easily auditible and understandable. [Regression Potential] * The change is a single line change to the shell script to call host with "timeout". When tested on working and non-working system this appears to function as expected. I believe the regression potential for this is subsequently low. * In attempt to anticipate possible issues, I checked that the timeout command is in the same path (/usr/bin) as the host command that is already called without a path, and the coreutils package (which contains timeout) is an Essential package. I also checked that timeout is not a built-in in bash, for those that have changed /bin/sh to bash (just in case). [Other Info] * N/A [Original Bug Description] On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64
[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
This bug was fixed in the package avahi - 0.7-3.1ubuntu1.1 --- avahi (0.7-3.1ubuntu1.1) bionic; urgency=medium [ Trent Lloyd ] * debian/avahi-daemon-check-dns.sh: On some hardware, the 'host' command gets stuck and does not timeout as it should leaving this script and boot-up hanging indefinitely. Launch host with 'timeout' to kill it after 5 seconds in these cases as a workaround. (LP: #1752411) -- Christian Ehrhardt Tue, 28 Aug 2018 11:37:21 +0200 ** Changed in: avahi (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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Fix Released Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in strongswan package in Ubuntu: Invalid Status in avahi source package in Bionic: Fix Released Status in bind9 source package in Bionic: Confirmed Status in avahi source package in Cosmic: Fix Released Status in bind9 source package in Cosmic: Confirmed Status in avahi package in Debian: New Bug description: [Impact] * Network connections for some users fail (in some cases a direct interface, in others when connecting a VPN) because the 'host' command to check for .local in DNS called by /usr/lib/avahi/avahi-daemon- check-dns.sh never times out like it should - leaving the script hanging indefinitely blocking interface up and start-up. This appears to be a bug in host caused in some circumstances however we implement a workaround to call it under 'timeout' as the issue with 'host' has not easily been identified, and in any case acts as a fall-back. [Test Case] * Multiple people have been unable to create a reproducer on a generic machine (e.g. it does not occur in a VM), I have a specific machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM) by simply "ifdown br0; ifup br0" and there are clearly 10s of other users affected in varying circumstances that all involve the same symptoms but no clear test case exists. Best I can suggest is that I test the patch on my system to ensure it works as expected, and the change is only 1 line which is fairly easily auditible and understandable. [Regression Potential] * The change is a single line change to the shell script to call host with "timeout". When tested on working and non-working system this appears to function as expected. I believe the regression potential for this is subsequently low. * In attempt to anticipate possible issues, I checked that the timeout command is in the same path (/usr/bin) as the host command that is already called without a path, and the coreutils package (which contains timeout) is an Essential package. I also checked that timeout is not a built-in in bash, for those that have changed /bin/sh to bash (just in case). [Other Info] * N/A [Original Bug Description] On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect
Re: [Touch-packages] [Bug 1789822] Re: Colour profile deactivated after interrupted screen fade-out
Do you mean that Gnome environment in Ubuntu 16.04 LTS is not (longer) supported? On Mon, 3 Sep 2018 at 04:30, Daniel van Vugt wrote: > > Using GNOME 3.29 on Ubuntu 18.10 it appears this bug is fixed. > > I'm not sure about Ubuntu 18.04 but do recommend you upgrade to 18.04 > ASAP anyway since it is our latest long term release that will be > getting the most GNOME fixes. > > ** Changed in: colord (Ubuntu) >Status: Incomplete => New > > ** Changed in: gnome-shell (Ubuntu) >Status: Incomplete => New > > ** Changed in: lightdm (Ubuntu) >Status: Incomplete => New > > ** Changed in: mutter (Ubuntu) >Status: Incomplete => New > > ** Changed in: colord (Ubuntu) >Status: New => Fix Released > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Fix Released > > ** Changed in: lightdm (Ubuntu) >Status: New => Fix Released > > ** Changed in: mutter (Ubuntu) >Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1789822 > > Title: > Colour profile deactivated after interrupted screen fade-out > > Status in colord package in Ubuntu: > Fix Released > Status in gnome-shell package in Ubuntu: > Fix Released > Status in lightdm package in Ubuntu: > Fix Released > Status in mutter package in Ubuntu: > Fix Released > > Bug description: > When power management blanks the screen out and the process is > interrupted, the colour profile is deactivated and never set back. The > profile has to be re-applied in 'Color' settings manually. > > Expected behaviour: > Colour profile remains active during and after a screen fade-out. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3.1 > ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18 > Uname: Linux 4.15.0-32-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.54 Tue Aug 14 > 19:02:34 PDT 2018 >GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1~16.04) > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: GNOME > Date: Thu Aug 30 08:03:53 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f6] > MachineType: LENOVO 244759G > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic > root=UUID=cf56f770-2527-47cc-bf3b-a1815c6c2a09 ro quiet splash acpi_osi=Linux > acpi_backlight=none vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/24/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: G5ETA6WW (2.66 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 244759G > dmi.board.vendor: LENOVO > dmi.board.version: Win8 Pro DPK TPG > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvrG5ETA6WW(2.66):bd08/24/2016:svnLENOVO:pn244759G:pvrThinkPadW530:rvnLENOVO:rn244759G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.family: ThinkPad W530 > dmi.product.name: 244759G > dmi.product.version: ThinkPad W530 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.91-2~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > xserver.bootTime: Wed Aug 29 13:40:48 2018 > xserver.configfile: default > xserver.errors: >evdev: Logitech USB Laser Mouse: Unable to open evdev device > "/dev/input/event16". >evdev: HID 046a:0023: Unable to open evdev device "/dev/input/event17". >evdev: HID 046a:0023:
[Touch-packages] [Bug 1791029] [NEW] cannot print pdf
Public bug reported: I cannot print pdfs on any printer. The file is processed in the printer dialogue and then disappears. without printing. I can print odf files on the same printer without issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.5 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Sep 6 11:10:50 2018 InstallationDate: Installed on 2018-02-01 (216 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n: hp:/net/HP_LaserJet_200_colorMFP_M276n?ip=192.168.1.2 device for Hewlett-Packard-HP-LaserJet-400-M401dne: hp:/net/HP_LaserJet_400_M401dne?zc=NPI13B8A2 MachineType: LENOVO 20281 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=18dad62c-a203-45d8-a228-4a2dfc8af342 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J6ET58WW (2.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20281 QB0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ6ET58WW(2.03):bd01/17/2014:svnLENOVO:pn20281:pvrM5400:rvnLENOVO:rn20281QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: M5400 dmi.product.name: 20281 dmi.product.version: M5400 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1791029 Title: cannot print pdf Status in cups package in Ubuntu: New Bug description: I cannot print pdfs on any printer. The file is processed in the printer dialogue and then disappears. without printing. I can print odf files on the same printer without issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.5 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Sep 6 11:10:50 2018 InstallationDate: Installed on 2018-02-01 (216 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n: hp:/net/HP_LaserJet_200_colorMFP_M276n?ip=192.168.1.2 device for Hewlett-Packard-HP-LaserJet-400-M401dne: hp:/net/HP_LaserJet_400_M401dne?zc=NPI13B8A2 MachineType: LENOVO 20281 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-200-colorMFP-M276n.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-400-M401dne.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=18dad62c-a203-45d8-a228-4a2dfc8af342 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J6ET58WW (2.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20281 QB0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ6ET58WW(2.03):bd01/17/2014:svnLENOVO:pn20281:pvrM5400:rvnLENOVO:rn20281QB0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: M5400 dmi.product.name: 20281 dmi.product.version: M5400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1791029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1218442] Re: IPv6 addresses are lost when an interface is shortly down
I am working with 2.6.32 kernel. keep_addr_on_down variable is not available with this version. How to overcome this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1218442 Title: IPv6 addresses are lost when an interface is shortly down Status in ifupdown package in Ubuntu: Confirmed Bug description: /etc/network/interfaces has been configured with IPv4 and IPv6 addresses on an interface. There are two networks each: $ ip -4 addr show dev eth0 2: eth0: mtu 1500 qdisc mq state UP qlen 1000 inet 10.1.1.51/24 brd 10.1.1.255 scope global eth0 inet 10.2.1.51/24 brd 10.2.1.255 scope global eth0 $ ip -6 addr show dev eth0 2: eth0: mtu 1500 qlen 1000 inet6 :::201::33/64 scope global valid_lft forever preferred_lft forever inet6 :::101::33/64 scope global valid_lft forever preferred_lft forever inet6 fe80:::aaff:febb:ccdd/64 scope link valid_lft forever preferred_lft forever (Global addresses and MAC address anonymized) Both are configured within "manual" entries in /etc/network/interfaces. When I turn down eth0 and bring it up again, the result is: $ ip -4 addr show dev eth0 2: eth0: mtu 1500 qdisc mq state UP qlen 1000 inet 10.1.1.51/24 brd 10.1.1.255 scope global eth0 inet 10.2.1.51/24 brd 10.2.1.255 scope global eth0 $ ip -6 addr show dev eth0 2: eth0: mtu 1500 qlen 1000 inet6 fe80:::aaff:febb:ccdd/64 scope link valid_lft forever preferred_lft forever That is, the global IPv6 addresses are lost. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ifupdown 0.7.5ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Aug 29 16:28:46 2013 InstallationDate: Installed on 2013-08-14 (14 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1218442/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
Hey all, Kubuntu (which means plasma and KDE) is no exception. Running default config. But for some time it worked. So it must have been in an update of the past few weeks, It's not just alt+arrow for me. Even alt+f1 through alt+f8 will switch (to) console. I guess this is a problem: $ sudo dumpkeys | grep -E '(\W+)alt(\W+)keycode.*Cons' alt keycode 59 = Console_1 shift alt keycode 59 = Console_13 control alt keycode 59 = Console_1 shift control alt keycode 59 = Console_13 alt keycode 60 = Console_2 shift alt keycode 60 = Console_14 control alt keycode 60 = Console_2 shift control alt keycode 60 = Console_14 alt keycode 61 = Console_3 shift alt keycode 61 = Console_15 control alt keycode 61 = Console_3 shift control alt keycode 61 = Console_15 alt keycode 62 = Console_4 shift alt keycode 62 = Console_16 control alt keycode 62 = Console_4 shift control alt keycode 62 = Console_16 alt keycode 63 = Console_5 shift alt keycode 63 = Console_17 control alt keycode 63 = Console_5 shift control alt keycode 63 = Console_17 alt keycode 64 = Console_6 shift alt keycode 64 = Console_18 control alt keycode 64 = Console_6 shift control alt keycode 64 = Console_18 alt keycode 65 = Console_7 shift alt keycode 65 = Console_19 control alt keycode 65 = Console_7 shift control alt keycode 65 = Console_19 alt keycode 66 = Console_8 shift alt keycode 66 = Console_20 control alt keycode 66 = Console_8 shift control alt keycode 66 = Console_20 alt keycode 67 = Console_9 shift alt keycode 67 = Console_21 control alt keycode 67 = Console_9 shift control alt keycode 67 = Console_21 alt keycode 68 = Console_10 shift alt keycode 68 = Console_22 control alt keycode 68 = Console_10 shift control alt keycode 68 = Console_22 alt keycode 87 = Console_11 shift alt keycode 87 = Console_23 control alt keycode 87 = Console_11 shift control alt keycode 87 = Console_23 alt keycode 88 = Console_12 shift alt keycode 88 = Console_24 control alt keycode 88 = Console_12 shift control alt keycode 88 = Console_24 alt keycode 99 = Last_Console shift alt keycode 99 = Last_Console altgr alt keycode 99 = Last_Console shift altgr alt keycode 99 = Last_Console alt keycode 105 = Decr_Console alt keycode 106 = Incr_Console -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
I just modified comment 31 (https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1508146/comments/31): $ sudo dumpkeys | grep -v -E '^(\W+)alt(\W+)keycode.*Cons' | sudo loadkeys Everything with alt at the beginning and Console will not switch (to) consoles anymore. ** Also affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1735981] Re: Huawei ME936 mobile broadband can't connect
And then I changed the file below and now have a working connection:
sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u
./77-mm-huawei-net-port-types.rules
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
diff -u -r1.1 ./77-mm-huawei-net-port-types.rules
--- ./77-mm-huawei-net-port-types.rules 2018/09/06 05:09:56 1.1
+++ ./77-mm-huawei-net-port-types.rules 2018/09/06 05:37:49
@@ -24,4 +24,7 @@
# Airtel branded E3372h-607, using huawei-cdc-ncm driver but with unresponsive
cdc-wdm port
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_MM_HUAWEI_NDISDUP_SUPPORTED}="1"
+# https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981
+ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", ATTR{bNumConfigurations}=="3",
ATTR{bConfigurationValue}!="3" ATTR{bConfigurationValue}="3"
+
LABEL="mm_huawei_port_types_end"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735981
Title:
Huawei ME936 mobile broadband can't connect
Status in modemmanager package in Ubuntu:
Confirmed
Bug description:
Hi, I have an Acer Travelmate P648 with a Huawei ME936
internal USB mobile broadband card, and can't connect.
This didn't work in 17.04, and still does not work in 17.10.
The USB device is successfully connected,
ModemManager gets as far as "Simple connect state (8/8): All done"
During the setup ModemManager complains with "Couldn't find associated
cdc-wdm port for 'net/wwp0s20f0u9c2'"
DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed
out".
IP6 is set to "automatically" in the network settings for this configuration.
and finally connection fails with
"device (ttyUSB0): state change: ip-config -> failed (reason
'ip-config-unavailable', internal state 'managed')"
I checked that there are enough credits left in my account with the
provider.
Any ideas what else to check ?
Yours,
Steffen
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: modemmanager 1.6.8-1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 3 11:27:49 2017
InstallationDate: Installed on 2017-04-24 (222 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+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 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, just an update, no connectivity out-of-the-box with 18.04: Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615] device (ttyUSB0): Activation: starting connection 'E-Plus connection' (bfe0f53f--cafebf693838) Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6624] audit: op="connection-activate" uuid="bfe0f53f-ccd2-45b6-b35b-cafebf693838" name="E-Plus connection" pid=17739 uid=1000 result="success" Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6637] device (ttyUSB0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6673] device (ttyUSB0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6774] device (ttyUSB0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (locked -> initializing) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load Operator name: 'Operation not supported' Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load current Bands: 'Unknown error' Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (initializing -> disabled) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8852] modem["ttyUSB0"]: modem state changed, 'locked' --> 'disabled' (reason: unknown) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8856] modem["ttyUSB0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference) Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disabled -> enabling) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB2): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect started... Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect state (4/8): Wait to get fully enabled Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (unknown -> idle) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabling -> enabled) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Simple connect state (5/8): Register Sep 06 07:02:14 msbi-corei NetworkManager[1299]: [1536210134.5790] modem["ttyUSB0"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (idle -> registering) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (registering -> home) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabled -> registered) Sep 06 07:02:15 msbi-corei NetworkManager[1299]: [1536210135.7173] modem["ttyUSB0"]: modem state changed, 'enabled' --> 'registered' (reason: unknown) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (6/8): Bearer Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (7/8): Connect Sep 06 07:02:18 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2' Sep 06 07:02:18 msbi-corei NetworkManager[1299]: [1536210138.1869] modem["ttyUSB0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) Sep 06 07:03:19 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> registered) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1425] modem["ttyUSB0"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1428] modem-broadband[ttyUSB0]: failed to connect modem: Connection attempt timed out Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1430] device (ttyUSB0): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface-state: 'managed') Sep 06 07:03:19 msbi-corei NetworkManager[1299]:
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Thanks Iain, everything you wrote makes sense to me (including that I should have used the Debian bug tracker). Everything works fine after apt-get install --reinstall libappstream4. Best, Johannes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+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
