Re: [Touch-packages] [Bug 1817527] Re: ufw status problem
because earlier status be active (running), anyway thanks On Fri, Mar 8, 2019 at 2:00 AM Jamie Strandboge wrote: > There is nothing you need to do. Everything is normal and fine and there > is nothing to fix. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1817527 > > Title: > ufw status problem > > Status in ufw package in Ubuntu: > Invalid > > Bug description: > I recently have a spontaneous problem when running the command "service > ufw status" and below picture is a result that shows me "active (exited)" > status how can fix it ??? > thanks a lot > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1817527/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1817527 Title: ufw status problem Status in ufw package in Ubuntu: Invalid Bug description: I recently have a spontaneous problem when running the command "service ufw status" and below picture is a result that shows me "active (exited)" status how can fix it ??? thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1817527/+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 1819183] [NEW] FFe: Update pygobject to 3.32
Public bug reported: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+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 1818530] Re: bluetooth always starts at startup
*** This bug is a duplicate of bug 1574311 *** https://bugs.launchpad.net/bugs/1574311 This is not a bug but just designed behaviour of TLP. You may change it by configuring: DEVICES_TO_DISABLE_ON_STARTUP="bluetooth" or RESTORE_DEVICE_STATE_ON_STARTUP=1 See https://linrunner.de/en/tlp/docs/tlp-configuration.html#radios -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1818530 Title: bluetooth always starts at startup Status in bluez package in Ubuntu: Incomplete Bug description: after every startup, I have to manually turn off bluetooth which is enabled at startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Mar 4 20:24:42 2019 InstallationDate: Installed on 2018-10-16 (139 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5d5 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcEnviron: LC_CTYPE=en_IN TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=0bb24ccc-6f8f-43ca-8a73-ccd2f46a3633 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br0xx dmi.product.sku: 2JR17PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:AF:BD:F0:13:69 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:1787 acl:0 sco:0 events:224 errors:0 TX bytes:43852 acl:0 sco:0 commands:224 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1818530/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
I forgot to tell you: this issue is only pressent on ubuntu, audio on Windows works fine -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1818802/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
I also see these on 18.04 bionic server installs ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Triaged Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1818902] Re: The io.elementary.camera package installs on Ubuntu Disk 19.04 normally, but does not open the video image.
Not related to camera-app (Ubuntu) but io.elementary.camera from the elementary OS PPA. ** Changed in: camera-app (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1818902 Title: The io.elementary.camera package installs on Ubuntu Disk 19.04 normally, but does not open the video image. Status in camera-app package in Ubuntu: Invalid Bug description: Hello guys I installed the io.elementary.camera package from Elementary OS on Ubuntu Disk 19.04 normally, but message appears that it does not recognize the webcam. Note I have the Juno Elementary OS installed on the same machine and the Webcam works normally. I installed through the repository: sudo add-apt-repository ppa: elementary-os / daily sudo apt update sudo apt install io.elementary.camera In the description, there is the option pantheon-camera, but this one says to be with broken package and does not install. Could it be this that does not let the webcam work? Look! sudo apt install pantheon-camera [sudo] password for edson: Reading package lists ... Ready Building dependency tree Reading status information ... Ready Some packages could not be installed. This may mean that you asked for an impossible situation or, if you are using the unstable distribution, that some required packages have not been created yet or have been removed from Incoming. The following information may help resolve the situation: The following packages have mismatched dependencies: pantheon-camera: Depends: io.elementary.camera but will not install E: Impossible to fix problems, you kept (hold) broken packages. Note When I enter synaptcis there is no broken package. If you uninstall io.elementary.camera and try to install the pantheon- camera the same broken package information appears. The installation of io.elementary.camera is performed successfully on Ubuntu 19.04 Disk, but does not appear the image of the video and nor does it recognize the webcam, video attachments. When you try to open the camera through the terminal the following error message appears: edson @ edson-p6540br: ~ $ io.elementary.camera (io.elementary.camera:10218): Clutter-WARNING **: 16: 43: 29.698: Whoever translated default: LTR did so wrongly. (io.elementary.camera:10218): Clutter-Gst-CRITICAL **: 16: 43: 29.753: Unable to setup device without element factory, node and name set 0x55a19aa51200 0x7fc2ec00e240 (nil) edson @ edson-p6540br: ~ $ I ask you to forward the responsible team so that the correction can be carried out. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1818902/+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 993292] Re: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all
** Changed in: poppler Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/993292 Title: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all Status in Poppler: New Status in poppler package in Ubuntu: New Bug description: pdftotext -htmlmeta does miss metadata from PDF catalog. pdfinfo does output all values known: e.g. a pdfinfo output: Title: Titel Author: Word Creator:WordToPDF 2.4 build 127 Producer: AFPL Ghostscript 8.54 CreationDate: Fri Jul 2 09:14:02 2007 ModDate:Fri Jul 2 09:14:02 2007 Tagged: no Pages: 6 Encrypted: no Page size: 595 x 842 pts (A4) File size: 104664 bytes Optimized: no PDF version:1.3 in contrast the meta section of the pdftotext -htmlmeta output: Titel Does not match and miss some meta data. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: poppler-utils 0.16.7-2ubuntu2 Uname: Linux 3.3.3-030303-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed May 2 15:44:06 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110427.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: poppler UpgradeStatus: Upgraded to oneiric on 2012-02-16 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/993292/+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 1819052] Re: tar makes full backup not incremental when not using "z"
** Description changed: - Using tar with: tar -czpf ... the incremtal function works right. - Using tar with: tar -cpf ... the incremtal function dont work. + Using tar with: tar -czpf ... -g ... the incremtal function works right. + Using tar with: tar -cpf ... -g ... the incremtal function dont work. Without compressing tar always produce a full backup archive. tar-version: GNU tar 1.29 on Ubuntu Bionic Beaver 18.04.2 Making achives over network using Samba cifs /etc/fstab: //192.168.178.165/x/home/asterix/carola cifs auto,rw,users,username=asterix,password=leo,uid=asterix,gid=asterix 0 0 Now i am using the compression, but thereby the backuptime is much longer. Thank you for Ubuntu/Linux :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1819052 Title: tar makes full backup not incremental when not using "z" Status in tar package in Ubuntu: New Bug description: Using tar with: tar -czpf ... -g ... the incremtal function works right. Using tar with: tar -cpf ... -g ... the incremtal function dont work. Without compressing tar always produce a full backup archive. tar-version: GNU tar 1.29 on Ubuntu Bionic Beaver 18.04.2 Making achives over network using Samba cifs /etc/fstab: //192.168.178.165/x/home/asterix/carola cifs auto,rw,users,username=asterix,password=leo,uid=asterix,gid=asterix 0 0 Now i am using the compression, but thereby the backuptime is much longer. Thank you for Ubuntu/Linux :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1819052/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
disabling 10bpc solved the problem, thanks -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly
** Description changed: [Impact] When attaching multiple IPs on secondary interface the routing policy rules do not apply for all IPs. The rules that are applied after restarting networkd are random. The issue has been reported and addressed upstream. [Test Case] Attach multiple IPs to secondary interface, config file: $ cat /etc/systemd/network/ens8.network [Match] Name=ens8 [Network] Address=172.31.28.195/20 Address=172.31.24.151/20 Address=172.31.24.152/20 Address=172.31.24.153/20 [Route] Destination=0.0.0.0/0 Gateway=172.31.16.1 Table=1000 [Route] Destination=172.31.24.153 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.28.195 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.151 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.152 Gateway=0.0.0.0 Scope=link Table=1000 [RoutingPolicyRule] From=172.31.24.153 Table=1000 [RoutingPolicyRule] From=172.31.28.195 Table=1000 [RoutingPolicyRule] From=172.31.24.152 Table=1000 [RoutingPolicyRule] From=172.31.24.151 Table=1000 $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart networkd $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.153 lookup 1000 0:from 172.31.28.195 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart again $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.152 lookup 1000 32766:from all lookup main 32767:from all lookup default The behaviour is random - [Regression Potential] May impact the systemd-networkd service functionality. - [Other] - Affects Disco and Bionic (probably Cosmic as well, but haven't tested it - yet). + Affects Disco Bionic and Cosmic. Upstream bug : https://github.com/systemd/systemd/issues/11280 Upstream fix : https://github.com/systemd/systemd/pull/11795/commits $ lsb_release -rd Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Systemd version : systemd: Installed: 240-6ubuntu1 Candidate: 240-6ubuntu1 Version table: *** 240-6ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- 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/1818282 Title: systemd-networkd - RoutingPolicyRule does not apply correctly Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] When attaching multiple IPs on secondary interface the routing policy rules do not apply for all IPs. The rules that are applied after restarting networkd are random. The issue has been reported and addressed upstream. [Test Case] Attach multiple IPs to secondary interface, config file: $ cat /etc/systemd/network/ens8.network [Match] Name=ens8 [Network] Address=172.31.28.195/20 Address=172.31.24.151/20 Address=172.31.24.152/20 Address=172.31.24.153/20 [Route] Destination=0.0.0.0/0 Gateway=172.31.16.1 Table=1000 [Route] Destination=172.31.24.153 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.28.195 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.151 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.152 Gateway=0.0.0.0 Scope=link Table=1000 [RoutingPolicyRule] From=172.31.24.153 Table=1000 [RoutingPolicyRule] From=172.31.28.195 Table=1000 [RoutingPolicyRule] From=172.31.24.152 Table=1000 [RoutingPolicyRule] From=172.31.24.151 Table=1000 $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart networkd $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.153 lookup 1000
[Touch-packages] [Bug 1819132] Re: DNS is broken after reboot or suspend
** Package changed: network-manager (Ubuntu) => systemd (Ubuntu) -- 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/1819132 Title: DNS is broken after reboot or suspend Status in systemd package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # 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. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819132/+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 1819189] [NEW] gtk_label_set_attributes core dump
Public bug reported:
Program terminated with signal SIGSEGV, Segmentation fault.
in gtk_label_set_attributes () from libgtk-3.so.0
gtk/gtklabel.c
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv = label->priv;
g_return_if_fail (GTK_IS_LABEL (label));
to
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv;
g_return_if_fail (GTK_IS_LABEL (label));
priv = label->priv;
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
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/1819189
Title:
gtk_label_set_attributes core dump
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Program terminated with signal SIGSEGV, Segmentation fault.
in gtk_label_set_attributes () from libgtk-3.so.0
gtk/gtklabel.c
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv = label->priv;
g_return_if_fail (GTK_IS_LABEL (label));
to
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv;
g_return_if_fail (GTK_IS_LABEL (label));
priv = label->priv;
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1819189/+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 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
After reading the comments for bug 1810583 closer, it is also a symptom of this bug, and keepalived >= 2.0.x would fix it (restore the VIPs). Thanks, - cameron -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+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 1794033]
(In reply to Mark Janes from comment #15) > Mesa CI reproduce these test failures immediately: > > https://mesa-ci.01.org/mesa_master/builds/15252/group/ > 63a9f0ea7bb98050796b649e85481845 > > Builds have fairly recent kernels: > > Linux otc-gfxtest-sklgt2-01 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 > (2018-12-22) x86_64 GNU/Linux Thanks for the info! I'll treat this as a mesa bug and since we are using your blacklist, we should be safe to just ignore it from our side. I'll close our kernel issue. Thanks to everyone involved! -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1794033]
The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1819183] Re: FFe: Update pygobject to 3.32
>From an pygobject upstream POV this cycle hasn't seen any high risk changes, so +1 from me in case that helps :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+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 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Bug 1815101 is a symptom of this bug. I do not think bug 1810583 is related, I do not think a backport of keepalived >= 2.0.x would fix bug 1810583. Thanks, - cameron -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+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 1809053] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Abort
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1809053 Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Aborted) Status in openssh package in Ubuntu: Expired Bug description: doesn't seem to be a major issue. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Tue Dec 18 08:31:24 2018 ErrorMessage: installed openssh-server package post-installation script subprocess was killed by signal (Aborted) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Aborted) UpgradeStatus: Upgraded to bionic on 2018-12-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1809053/+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 1718932] Re: Child windows do not have shadows in Gnome Shell
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718932 Title: Child windows do not have shadows in Gnome Shell Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: Some child windows do not have shadows. Test case: Open Thunderbird for the first time. A child window will appear to create a new account. It does not have shadows. Synaptic package manager also have the same issue. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 14:20:26 2017 InstallationDate: Installed on 2017-09-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1718932/+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 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- 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/1730184 Title: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Status in gnome-shell package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in gnome-shell package in Fedora: Unknown Bug description: Went to log into my fairly newly upgraded ubuntu artful system today but was presented with a new login instead of a login with all my applications running, similar to #1728474 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ), only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented with one when I came to log in in the morning. syslog gives a clue: Nov 5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Nov 5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost Nov 5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in libglib-2.0.so.0.5400.1[7fcceb6c6000+111000] This, followed by everything that was running failing to various degrees of cleanness. intel-microcode: Installed: 3.20170707.1 Candidate: 3.20170707.1 Version table: *** 3.20170707.1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/restricted amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-intel: Installed: 2:2.99.917+git20170309-0ubuntu1 Candidate: 2:2.99.917+git20170309-0ubuntu1 Version table: *** 2:2.99.917+git20170309-0ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status libglib2.0-0: Installed: 2.54.1-1ubuntu1 Candidate: 2.54.1-1ubuntu1 Version table: *** 2.54.1-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:27:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'libreoffice-calc.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']" b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-04-18 (200 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+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 1819132] [NEW] DNS is broken after reboot or suspend
Public bug reported: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # 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. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1819132 Title: DNS is broken after reboot or suspend Status in network-manager package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # 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. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog:
[Touch-packages] [Bug 1693724] Re: Context menus have no animation/fade-in under Gnome Shell
** Tags removed: artful gnome-17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693724 Title: Context menus have no animation/fade-in under Gnome Shell Status in gnome-shell package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: Confirmed Status in gnome-shell package in Arch Linux: New Bug description: Context menus have no animation/fade-in under Gnome Shell. The transitions under Unity7 for context menus look nicer, less abrupt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
Is there a 16.04 package? This was a regression there caused by an earlier update. I have users reporting the same bizarre behaviour I wasn't able to clearly describe before — essentially, DNS being sent out seemingly random interfaces (sometimes VPN, sometimes local). My advice to just install this package *and* manually set dns-priority=-1,dns-search=~. and get on with life even though you really shouldn't have to manually set the latter, doesn't work for the 16.04 users... And yes, when other things stop being on fire I need to undo those settings and try to work out what's going wrong. We aren't using systemd-resolve here because historically it also hasn't worked right while dnsmasq did. -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: * Impact When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not * Test case Configure the system to send all the traffic to a VPN, do a name resolution, the request should not go to the public DNS server (to be checked by capturing the traffic by example with wireshark) * Regression potential The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Any progress on this? It would be nice to get this fixed in distribution. -- 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/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Incomplete Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+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 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Also https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583 They all seem related. -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+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 1757091] Re: systemctl enable lightdm
Is there a workaround tip in order to re-enable lightdm in ubuntu 18.04 ? I am using systemd. -- 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/1757091 Title: systemctl enable lightdm Status in lightdm package in Ubuntu: Confirmed Bug description: Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable lightdm The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 11:44:46 2018 InstallationDate: Installed on 2018-01-22 (57 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757091/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions)
** Tags removed: artful -- 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/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions) Status in GTK+: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1755250] Re: backport statx syscall whitelist fix
Has this been released ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist fix Status in docker.io package in Ubuntu: Invalid Status in libseccomp package in Ubuntu: Fix Released Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Committed Status in docker.io source package in Cosmic: Invalid Status in libseccomp source package in Cosmic: Fix Released Bug description: [Impact] * Some newer workloads fail due to libseccomp as in Bionic lacking statx support * This backports the syscall definitions for statx to Bionic to allow to manage those [Test Case] # Note: I took a KVM image of Bionic to not spoil my system with Docker config for this test too much $ sudo apt install docker.io $ sudo usermod -a -G docker ubuntu $ cat > test-statx/Dockerfile << EOF FROM ubuntu:18.04 RUN apt-get update && apt-get install -y wget gcc WORKDIR /tmp RUN wget -q https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c RUN gcc test-statx.c -o test-statx RUN touch test-file RUN chmod +x ./test-statx RUN ./test-statx test-file EOF $ docker build test-statx With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic that yields [...] Step 8/8 : RUN ./test-statx test-file ---> Running in 6e60a82409e6 test-file: Operation not permitted statx(test-file) = -1 The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1 With the fix applied it would work and look like: Step 8/8 : RUN ./test-statx test-file ---> Running in a83bc043e7bd statx(test-file) = 0 results=fff Size: 0 Blocks: 0 IO Block: 4096regular file Device: 00:32 Inode: 261994 Links: 1 Access: (0644/-rw-r--r--) Uid: 0 Gid: 0 Access: 2019-02-08 07:57:42.0+ Modify: 2019-02-08 07:57:42.0+ Change: 2019-02-08 07:57:43.076507007+ Birth: 2019-02-08 07:57:43.076507007+ Attributes: ( -... .---.-..) Removing intermediate container a83bc043e7bd ---> d428d14cbc57 Successfully built d428d14cbc57 [Regression Potential] * This "only" defines a new syscall number for all the architectures. It does not make any other changes, thereby it should be rather safe. If anything software could now manage statx through libseccomp and behavior that was formerly failing (like the reported docker case) would not succeed and due to that be a change in behavior - but I think it is a wanted change. [Other Info] * n/a --- Hello maintainer, The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall which is needed to build qt >=5.10 applications: https://github.com/docker/for-linux/issues/208#issuecomment-372400859 Could this fix be backported in the ubuntu package ? https://github.com/moby/moby/pull/36417 regards, xan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+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 1818819] Re: Remove type-ahead patch.
> has no place in a modern operating system. LOL -- 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/1818819 Title: Remove type-ahead patch. Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: In the Ubuntu version of Gtk+ 3 type-ahead as been re-patched in. This causes unexpected behaviours for the file-chooser. The type-ahead patch should be removed for the following reasons: 1) In file-chooser when you try to search using the looking-glass icon search-dialogue the focus does not stay in the search box, so you have to click in the box each time you type a letter.[1] 2) A magically appearing type-ahead box is not expected and confusing. 3) This behaviour was removed from Nautilus, and from main-line Gtk+ years ago. Having this behaviour re-added is not something that should have happened. There is a search button for a reason. [2] It's better to make people use the less confusing search box than the very confusing type-ahead box. I understand that you might think it is good for the old-timers, but it is totally broken, and has no place in a modern operating system. --- [1] https://bugs.launchpad.net/ubuntu-gnome/+bug/1592177 , https://gitlab.gnome.org/GNOME/gtk/issues/1572 [2] It does not make sense when looking at HIG. And how most GNOME and Gtk+ apps are designed. It is a weird legacy design choice from before Gtk+ modernised and made things much clearer. https://developer.gnome.org/hig/stable/search.html.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1818819/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I, too, had this bug manifested on clean Ubuntu without PPAs and without AMDGPU. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Hello Agustin, or anyone else affected, Accepted upower into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/upower/0.99.7-2ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: upower (Ubuntu Bionic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
since the bug was recently filed upstream, it's seems clear that it's not fixed in cosmic or disco either, and the policy is to first fix it in the devel series.. so the SRU needs to wait for a bit ** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Disco) Importance: Undecided Assignee: Till Kamppeter (till-kamppeter) Status: Incomplete ** Also affects: cups (Ubuntu Cosmic) Importance: Undecided Status: New -- 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/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name:
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
meh, the fixes are from 2.2.8 which is in cosmic ** Changed in: cups (Ubuntu Cosmic) Status: New => Fix Released -- 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/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
sorry, looks like this is actually fixed upstream in 2.2.10, so I'm marking it fixed for disco Till, please upload a fix for cosmic too ** Changed in: cups (Ubuntu Disco) Status: Incomplete => Fix Released ** Changed in: cups (Ubuntu Bionic) Status: New => Fix Committed -- 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/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list:
[Touch-packages] [Bug 993292] Re: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all
** Bug watch added: gitlab.freedesktop.org/poppler/poppler/issues #136 https://gitlab.freedesktop.org/poppler/poppler/issues/136 ** Also affects: poppler via https://gitlab.freedesktop.org/poppler/poppler/issues/136 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/993292 Title: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all Status in Poppler: Unknown Status in poppler package in Ubuntu: New Bug description: pdftotext -htmlmeta does miss metadata from PDF catalog. pdfinfo does output all values known: e.g. a pdfinfo output: Title: Titel Author: Word Creator:WordToPDF 2.4 build 127 Producer: AFPL Ghostscript 8.54 CreationDate: Fri Jul 2 09:14:02 2007 ModDate:Fri Jul 2 09:14:02 2007 Tagged: no Pages: 6 Encrypted: no Page size: 595 x 842 pts (A4) File size: 104664 bytes Optimized: no PDF version:1.3 in contrast the meta section of the pdftotext -htmlmeta output: Titel Does not match and miss some meta data. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: poppler-utils 0.16.7-2ubuntu2 Uname: Linux 3.3.3-030303-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed May 2 15:44:06 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110427.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: poppler UpgradeStatus: Upgraded to oneiric on 2012-02-16 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/993292/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Hey, thanks for helping me, I got a few updates regarding this issue: - pidof is not changing - I uploaded the crash report, but its not listed in my bug tracker(chromium crash) - I found out that audio works perfectly fine when the laptop is plugged in or the battery % is above 20 - 40% Let me know if you need more details. -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1818802/+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 1819162] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returne
Public bug reported: this error was shown after restart of the device ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 08:29:55 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (883 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (185 days ago) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1819162 Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: this error was shown after restart of the device ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 08:29:55 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (883 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (185 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1819162/+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 1819162] Re: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returned
** Tags removed: need-duplicate-check -- 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/1819162 Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: this error was shown after restart of the device ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 08:29:55 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (883 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (185 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1819162/+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
