[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
And then I changed the file below and now have a working connection:
sneumann@msbi-corei:/lib/udev/rules.d$ rcsdiff -u
./77-mm-huawei-net-port-types.rules
===
RCS file: ./77-mm-huawei-net-port-types.rules,v
retrieving revision 1.1
diff -u -r1.1 ./77-mm-huawei-net-port-types.rules
--- ./77-mm-huawei-net-port-types.rules 2018/09/06 05:09:56 1.1
+++ ./77-mm-huawei-net-port-types.rules 2018/09/06 05:37:49
@@ -24,4 +24,7 @@
# Airtel branded E3372h-607, using huawei-cdc-ncm driver but with unresponsive
cdc-wdm port
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_MM_HUAWEI_NDISDUP_SUPPORTED}="1"
+# https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981
+ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", ATTR{bNumConfigurations}=="3",
ATTR{bConfigurationValue}!="3" ATTR{bConfigurationValue}="3"
+
LABEL="mm_huawei_port_types_end"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735981
Title:
Huawei ME936 mobile broadband can't connect
Status in modemmanager package in Ubuntu:
Confirmed
Bug description:
Hi, I have an Acer Travelmate P648 with a Huawei ME936
internal USB mobile broadband card, and can't connect.
This didn't work in 17.04, and still does not work in 17.10.
The USB device is successfully connected,
ModemManager gets as far as "Simple connect state (8/8): All done"
During the setup ModemManager complains with "Couldn't find associated
cdc-wdm port for 'net/wwp0s20f0u9c2'"
DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed
out".
IP6 is set to "automatically" in the network settings for this configuration.
and finally connection fails with
"device (ttyUSB0): state change: ip-config -> failed (reason
'ip-config-unavailable', internal state 'managed')"
I checked that there are enough credits left in my account with the
provider.
Any ideas what else to check ?
Yours,
Steffen
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: modemmanager 1.6.8-1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 3 11:27:49 2017
InstallationDate: Installed on 2017-04-24 (222 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, just an update, no connectivity out-of-the-box with 18.04: Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615] device (ttyUSB0): Activation: starting connection 'E-Plus connection' (bfe0f53f--cafebf693838) Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6624] audit: op="connection-activate" uuid="bfe0f53f-ccd2-45b6-b35b-cafebf693838" name="E-Plus connection" pid=17739 uid=1000 result="success" Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6637] device (ttyUSB0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6673] device (ttyUSB0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6774] device (ttyUSB0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (locked -> initializing) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load Operator name: 'Operation not supported' Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load current Bands: 'Unknown error' Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (initializing -> disabled) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8852] modem["ttyUSB0"]: modem state changed, 'locked' --> 'disabled' (reason: unknown) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8856] modem["ttyUSB0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference) Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disabled -> enabling) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB2): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect started... Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect state (4/8): Wait to get fully enabled Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (unknown -> idle) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabling -> enabled) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Simple connect state (5/8): Register Sep 06 07:02:14 msbi-corei NetworkManager[1299]: [1536210134.5790] modem["ttyUSB0"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (idle -> registering) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (registering -> home) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabled -> registered) Sep 06 07:02:15 msbi-corei NetworkManager[1299]: [1536210135.7173] modem["ttyUSB0"]: modem state changed, 'enabled' --> 'registered' (reason: unknown) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (6/8): Bearer Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (7/8): Connect Sep 06 07:02:18 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2' Sep 06 07:02:18 msbi-corei NetworkManager[1299]: [1536210138.1869] modem["ttyUSB0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) Sep 06 07:03:19 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> registered) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1425] modem["ttyUSB0"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1428] modem-broadband[ttyUSB0]: failed to connect modem: Connection attempt timed out Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1430] device (ttyUSB0): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface-state: 'managed') Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.147
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Thanks Iain, everything you wrote makes sense to me (including that I should have used the Debian bug tracker). Everything works fine after apt-get install --reinstall libappstream4. Best, Johannes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1024276] Re: lightdm doesn't start if weston is activated (system-compositor ppa, nouveau)
The trouble persists after uninstall. -- 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/1024276 Title: lightdm doesn't start if weston is activated (system-compositor ppa, nouveau) Status in lightdm package in Ubuntu: Invalid Bug description: On my system, lightdm fails to start whenever I try to start it with enabled "type=weston" under "[SeatDefaults]" in my lightdm.conf. The logs are from my current system start, where the weston-option was enabled at startup, and I disabled it afterwards to start lightdm. lightdm version: 1.3.1-0ubuntu2+compositor1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024276/+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 1024276] Re: lightdm doesn't start if weston is activated (system-compositor ppa, nouveau)
I have this bug in Armbian Stretch and Armbian Bionic. Lightdm shows only the black screen after installing weston. -- 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/1024276 Title: lightdm doesn't start if weston is activated (system-compositor ppa, nouveau) Status in lightdm package in Ubuntu: Invalid Bug description: On my system, lightdm fails to start whenever I try to start it with enabled "type=weston" under "[SeatDefaults]" in my lightdm.conf. The logs are from my current system start, where the weston-option was enabled at startup, and I disabled it afterwards to start lightdm. lightdm version: 1.3.1-0ubuntu2+compositor1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect
Hi, just an update, no connectivity out-of-the-box with 18.04: Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6615] device (ttyUSB0): Activation: starting connection 'E-Plus connection' (bfe0f53f--cafebf693838) Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6624] audit: op="connection-activate" uuid="bfe0f53f-ccd2-45b6-b35b-cafebf693838" name="E-Plus connection" pid=17739 uid=1000 result="success" Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6637] device (ttyUSB0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6673] device (ttyUSB0): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei NetworkManager[1299]: [1536210126.6774] device (ttyUSB0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 06 07:02:06 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:09 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (locked -> initializing) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load Operator name: 'Operation not supported' Sep 06 07:02:13 msbi-corei ModemManager[1205]: couldn't load current Bands: 'Unknown error' Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (initializing -> disabled) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8852] modem["ttyUSB0"]: modem state changed, 'locked' --> 'disabled' (reason: unknown) Sep 06 07:02:13 msbi-corei NetworkManager[1299]: [1536210133.8856] modem["ttyUSB0"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference) Sep 06 07:02:13 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disabled -> enabling) Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB0): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: (ttyUSB2): port attributes not fully set Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect started... Sep 06 07:02:13 msbi-corei ModemManager[1205]: Simple connect state (4/8): Wait to get fully enabled Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (unknown -> idle) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabling -> enabled) Sep 06 07:02:14 msbi-corei ModemManager[1205]: Simple connect state (5/8): Register Sep 06 07:02:14 msbi-corei NetworkManager[1299]: [1536210134.5790] modem["ttyUSB0"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (idle -> registering) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: 3GPP Registration state changed (registering -> home) Sep 06 07:02:15 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (enabled -> registered) Sep 06 07:02:15 msbi-corei NetworkManager[1299]: [1536210135.7173] modem["ttyUSB0"]: modem state changed, 'enabled' --> 'registered' (reason: unknown) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (6/8): Bearer Sep 06 07:02:18 msbi-corei ModemManager[1205]: Simple connect state (7/8): Connect Sep 06 07:02:18 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting) Sep 06 07:02:18 msbi-corei ModemManager[1205]: Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2' Sep 06 07:02:18 msbi-corei NetworkManager[1299]: [1536210138.1869] modem["ttyUSB0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) Sep 06 07:03:19 msbi-corei ModemManager[1205]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> registered) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1425] modem["ttyUSB0"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested) Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1428] modem-broadband[ttyUSB0]: failed to connect modem: Connection attempt timed out Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.1430] device (ttyUSB0): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface-state: 'managed') Sep 06 07:03:19 msbi-corei NetworkManager[1299]: [1536210199.147
[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
Package: avahi-daemon Version: 0.7-3.1ubuntu1.1 Works. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Fix Released Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in strongswan package in Ubuntu: Invalid Status in avahi source package in Bionic: Fix Committed Status in bind9 source package in Bionic: Confirmed Status in avahi source package in Cosmic: Fix Released Status in bind9 source package in Cosmic: Confirmed Status in avahi package in Debian: New Bug description: [Impact] * Network connections for some users fail (in some cases a direct interface, in others when connecting a VPN) because the 'host' command to check for .local in DNS called by /usr/lib/avahi/avahi-daemon- check-dns.sh never times out like it should - leaving the script hanging indefinitely blocking interface up and start-up. This appears to be a bug in host caused in some circumstances however we implement a workaround to call it under 'timeout' as the issue with 'host' has not easily been identified, and in any case acts as a fall-back. [Test Case] * Multiple people have been unable to create a reproducer on a generic machine (e.g. it does not occur in a VM), I have a specific machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM) by simply "ifdown br0; ifup br0" and there are clearly 10s of other users affected in varying circumstances that all involve the same symptoms but no clear test case exists. Best I can suggest is that I test the patch on my system to ensure it works as expected, and the change is only 1 line which is fairly easily auditible and understandable. [Regression Potential] * The change is a single line change to the shell script to call host with "timeout". When tested on working and non-working system this appears to function as expected. I believe the regression potential for this is subsequently low. * In attempt to anticipate possible issues, I checked that the timeout command is in the same path (/usr/bin) as the host command that is already called without a path, and the coreutils package (which contains timeout) is an Essential package. I also checked that timeout is not a built-in in bash, for those that have changed /bin/sh to bash (just in case). [Other Info] * N/A [Original Bug Description] On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1790993] Re: Graphics Issues
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790993 Title: Graphics Issues Status in Ubuntu: Incomplete Bug description: It says it is installed. But I am facing an issue in LibreOffice. My Excel file page layout size gets reduced here. I am attaching a screen shot. kindly find. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Sep 6 07:31:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed rtl8192eu, 1.0, 4.15.0-33-generic, x86_64: installed (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics [103c:80bb] InstallationDate: Installed on 2018-08-25 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP 240 G4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=e08aeb4b-3a84-41f3-8767-c4e85e846a2f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BB dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG5521WL4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1A:bd10/13/2015:svnHP:pnHP240G4NotebookPC:pvrCNB1:rvnHP:rn80BB:rvrKBCVersion94.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=240 dmi.product.name: HP 240 G4 Notebook PC dmi.product.version: CNB1 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1790993/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Summary changed: - Triple 4K monitor display failed (modesetting driver) + Triple 4K monitor display failed (modesetting driver limited to 8192x8192) -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Bionic) Status: New => Confirmed -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Bionic) Status: New => Confirmed -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1790993] [NEW] Graphics Issues
Public bug reported: It says it is installed. But I am facing an issue in LibreOffice. My Excel file page layout size gets reduced here. I am attaching a screen shot. kindly find. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Sep 6 07:31:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed rtl8192eu, 1.0, 4.15.0-33-generic, x86_64: installed (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics [103c:80bb] InstallationDate: Installed on 2018-08-25 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP 240 G4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=e08aeb4b-3a84-41f3-8767-c4e85e846a2f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BB dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG5521WL4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1A:bd10/13/2015:svnHP:pnHP240G4NotebookPC:pvrCNB1:rvnHP:rn80BB:rvrKBCVersion94.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=240 dmi.product.name: HP 240 G4 Notebook PC dmi.product.version: CNB1 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "Screenshot from 2018-09-06 07-35-30.png" https://bugs.launchpad.net/bugs/1790993/+attachment/5185261/+files/Screenshot%20from%202018-09-06%2007-35-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790993 Title: Graphics Issues Status in xorg package in Ubuntu: New Bug description: It says it is installed. But I am facing an issue in LibreOffice. My Excel file page layout size gets reduced here. I am attaching a screen shot. kindly find. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Sep 6 07:31:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed rtl8192eu, 1.0, 4.15.0-33-generic, x86_64: installed (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics [103c:80bb] InstallationDate: Installed on 2018-08-25 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP 240 G4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=e08aeb4b-3a84-41f3-8767-c4e85e846a2f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BB dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG5521WL4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.ver
[Touch-packages] [Bug 1790390] Re: Xorg cannot exceed pipeline dimensions reported by kernel
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1790390
Title:
Xorg cannot exceed pipeline dimensions reported by kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790390/+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 1790870] Re: No X display - gdm3 crash with segfault
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790870 Title: No X display - gdm3 crash with segfault Status in gdm3 package in Ubuntu: Incomplete Bug description: This desktop was running 16.04.5 version and started few weeks ago to have the desktop crashing. In dmesg I saw compiz segfault at 0 ip [...] error 4. I decide to upgrade to 18.04.1 to solve this problem but it's still there: gnome-shell at 0 ip [...] error 4 In 18.04 i even don't get the desktop, only the mouse indicator is visible, disappearing from time to time (seems on each crash). Attached is the output of an radeontool dump. The desktop is unusable in graphic mode. Daniel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Wed Sep 5 14:40:14 2018 DistUpgraded: 2018-09-05 13:03:08,966 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2016-03-03 (916 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160227) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=8c2df27f-cbc4-4c8d-a4f1-dc7994b41016 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) dmi.bios.date: 04/18/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.22 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8312220 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.22:bd04/18/2007:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 5 08:36:00 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 inputHP WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages Mor
[Touch-packages] [Bug 1790881] Re: ubuntu 18.04 LTS does not load onboard intel 82G33/G31 graphics controller
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1727356, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1727356 Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790881 Title: ubuntu 18.04 LTS does not load onboard intel 82G33/G31 graphics controller Status in xorg package in Ubuntu: New Bug description: upgraded from Ubuntu 16.04 LTS to 18.04 LTS but graphic display has failed and is extremely slow. $ glxinfo|grep OpenGL gives below output: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5 OpenGL core profile shading language version string: 3.30 $ lshw | grep display gives below output: *-display UNCLAIMED Onboard intel graphics controller worked perfectly on 16.04 but failed on upgrading to 18.04 Kindly suggest a workaround to re-enable onboard intel 82G33/G31 Integrated Graphics Controller (rev 10) on ubuntu 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 5 19:02:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2015-07-19 (1144 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.5-041805-generic root=UUID=8d00030d-c1a2-47fd-8b97-b7813c6e7ef6 ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection dmi.bios.date: 09/29/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd09/29/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790881/+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 1638634] Re: Print Job with Authentication is postponed until queue is opened manually
Thanks for changing the status and importance, C. Have a great day! :) G -- 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/1638634 Title: Print Job with Authentication is postponed until queue is opened manually Status in cups package in Ubuntu: Triaged Bug description: Ubuntu version 16.04 16.04 (cups 2.1.3-4ubuntu0.5). system-config-printer-common 1.5.7+20160212-0ubuntu2. Hplip 3.16.3+repack0-1. Problem is reproducable by the bug reporter. All print jobs from many different applications Bug triager is unable to reproduce the bug. Steps to reproduce: 1. Print an any document from an any application's print dialog (e.g. evince, Okular, GIMP, ReText,...). 2. Printing does not happen. 3. Open "system-config-printer” 4. Open the printer's print queue 5. All documents in the queue are processed, i.e. printed immediately. Expected behaviour: the document prints immediately. Actual behaviour: the document is held in the queue until the print queue is opened through "system-config-printer.” Additional notes: Printer is a RICOH MP C3003 situated on a large network. CUPS interface on local computer indicates that job is stopped but “release job” button is ignored. Opening the queue in “system-config-printer” on local computer immediately starts the job. Reporter has uploaded tail of access.log which mentions authentication successful, only after the reporter opened the queue in “system-config-printer” --- Triager searched for dups - none found. (original description follows) I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. CurrentDesktop: UnityDistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-09-15 (1077 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for 0_prost: lpd://prost.uni-koblenz.de/ device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 MachineType: LENOVO 20BX000XGE Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied grep: /etc/cups/ppd/0_prost.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Tags: xenial Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp vboxusers _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+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 1790618] Re: Update to 3.24.0
This bug was fixed in the package gtk+3.0 - 3.24.0-1ubuntu1
---
gtk+3.0 (3.24.0-1ubuntu1) cosmic; urgency=medium
* Merge from Debian experimental (LP: #1790618). Remaining changes:
+ Install a settings.ini file to set our themes
+ Update debian/libgtk-3-0.symbols
+ debian/control.in:
- Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/rules: Mark additional known test failures:
- box-shadow-changes-modify-clip.ui
- label-text-shadow-changes-modify-clip.ui
+ Ubuntu-specific patches:
- 073_treeview_almost_fixed.patch
- bzg_gtkcellrenderer_grabbing_modifier.patch
- ubuntu_gtk_custom_menu_items.patch
- print-dialog-show-options-of-remote-dnssd-printers.patch
- uimanager-guard-against-nested-node-updates.patch
- x-canonical-accel.patch
- message-dialog-restore-traditional-look-on-unity.patch
- 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
- restore_filechooser_typeaheadfind.patch
- 0001-calendar-always-emit-day-selected-once.patch
- 0001-gtkwindow-set-transparent-background-color.patch
- unity-border-radius.patch
- unity-headerbar-maximized-mode.patch
* debian/settings.ini: Update the default (fallback) GTK theme name to Yaru
gtk+3.0 (3.24.0-1) unstable; urgency=medium
[ Simon McVittie ]
* debian/libgtk-3-0.bug-control:
When bugs are reported against GTK+, include details of various
engines, modules and LD_PRELOADs if installed
* Don't install ChangeLog, which currently just says
"A git checkout and git-log is required to generate this file";
even if it was complete, Policy 4.2.0 does not require detailed
changelogs to be installed. Please see NEWS for a summary of changes,
or the upstream git repository https://gitlab.gnome.org/GNOME/gtk
for a comprehensive change history.
[ Iain Lane ]
* Revert "debian/{control{,.in},gbp.conf,watch}: Update for experimental"
This reverts commit 99b78e089c952661fcf3c4897769dd7a463c5cb7.
* New upstream stable release 3.24.0
+ GtkApplication can now track screensaver state
+ Deprecate a few APIs that are gone in GTK+ 4:
- focus chains in GtkContainer
- stepper sensitivity in GtkRange
+ Allow picking colors under kwin
* debian/control{,.in}: Bump Standards-Version to 4.2.1, no changes required
* debian/libgtk-3-0.symbols: Update for this release
-- Iain Lane Wed, 05 Sep 2018 09:37:45 +0100
** Changed in: gtk+3.0 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1790618
Title:
Update to 3.24.0
Status in gtk+3.0 package in Ubuntu:
Fix Released
Bug description:
Do it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1790618/+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 1752053] Re: nvidia-390 fails to boot graphical display
I know it's kind of rude just to "+1" on an issue. But whoever is responsible for these NVidia drivers deserved it. So, +1. Issue is not fixed. Blank screen on upgrade from 16.04. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1790963] Re: Unable to connect with openssh 7.8 client and certificates
Updated the description - specifically, this appears to affect certificate authentication and be related to rsa- sha2-512-cert-...@openssh.com and rsa-sha2-256-cert-...@openssh.com which are present in 7.8 server, but not earlier versions (nor are valid to add to the configuration manually). ** Summary changed: - Unable to connect with openssh 7.8 client + Unable to connect with openssh 7.8 client and certificates ** Description changed: - Users are unable to connect to Ubuntu when using openssh client 7.8. We - have seen this with both xenial and bionic, but this affects connecting - to ANY host running openssh server <7.8. + Users are unable to connect to Ubuntu when using openssh client 7.8 and + certificates. We have seen this with both xenial and bionic, but this + affects connecting to ANY host running openssh server <7.8. + + It appears to be specific to using certificate authentication. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm + + When comparing the list returned from a 7.6 server and a 7.8 server via + "ssh -Q key", we find that 7.8 returns rsa-sha2-512-cert-...@openssh.com + and rsa-sha2-256-cert-...@openssh.com which are not present (or valid) + for the earlier version server. It appears that the change noted here in the release notes[1] for 7.8 is related: * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). + This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 [1] https://www.openssh.com/txt/release-7.8 -- 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/1790963 Title: Unable to connect with openssh 7.8 client and certificates Status in openssh package in Ubuntu: Confirmed Bug description: Users are unable to connect to Ubuntu when using openssh client 7.8 and certificates. We have seen this with both xenial and bionic, but this affects connecting to ANY host running openssh server <7.8. It appears to be specific to using certificate authentication. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm When comparing the list returned from a 7.6 server and a 7.8 server via "ssh -Q key", we find that 7.8 returns rsa- sha2-512-cert-...@openssh.com and rsa-sha2-256-cert-...@openssh.com which are not present (or valid) for the earlier version server. It appears that the change noted here in the release notes[1] for 7.8 is related: * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 [1] https://www.openssh.com/txt/release-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1790963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lis
[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems
In MAAS we have provided a work around in LP: #1773698
** Changed in: maas
Milestone: 2.5.0beta1 => 2.5.0beta2
** No longer affects: maas
** No longer affects: maas/2.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
Unknown
Status in avahi package in Ubuntu:
Confirmed
Bug description:
I see avahi-browser choking on non-utf8 characters in my rackd.log:
==> rackd.log <==
2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS
observation process started.
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
Traceback (most recent call last):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/maas/maas-common", line 87, in
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
main()
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/maas/maas-common", line 83, in main
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
run()
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/maas/maas-common", line 52, in run
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
from provisioningserver.__main__ import main
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55,
in
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
main()
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line
91, in __call__
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
self.execute(argv)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line
86, in execute
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
args.handler.run(args)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
221, in run
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
_observe_mdns(reader, output, args.verbose)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
145, in _observe_mdns
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
for event in observer(events):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
161, in _observe_resolver_found
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
for event in filter(_p_resolver_found, events):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
125, in _extract_mdns_events
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
for event in map(parse_avahi_event, lines):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3.5/codecs.py", line 321, in decode
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
(result, consumed) = self._buffer_decode(data, self.errors, final)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240:
invalid continuation byte
2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS
observation process failed.
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a
probable error condition: process ended with exit code 1.
==> regiond.log <==
2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
==> maas.log <==
Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82
Similar traceback when running from command line:
maasuser@MAAS-RC01:~$ maas-rack observe-mdns
{"hostname": "Apple-TV", "interface": "ens33", "address": "192.168.1.81"}
Got SIGTERM, quitting.
Traceback (most recent call last):
File "/usr/sbin/maas-rac
[Touch-packages] [Bug 1767747] Re: lvm2-activation-generator crashed with SIGSEGV
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747/+attachment/5129861/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1767747 Title: lvm2-activation-generator crashed with SIGSEGV Status in lvm2 package in Ubuntu: Confirmed Bug description: This error occurred on reboot after 18.04 upgrade ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat Apr 28 17:20:51 2018 ExecutablePath: /lib/systemd/system-generators/lvm2-activation-generator InstallationDate: Installed on 2015-05-24 (1070 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcCmdline: /lib/systemd/system-generators/lvm2-activation-generator /run/systemd/generator /run/systemd/generator.early /run/systemd/generator.late ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7ff3ea9db856:add%al,(%rax) PC (0x7ff3ea9db856) ok source "%al" ok destination "(%rax)" (0x0012) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: lvm2 StacktraceTop: ?? () from /lib/x86_64-linux-gnu/liblvm2app.so.2.2 ?? () ?? () ?? () ?? () Title: lvm2-activation-generator crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747/+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 1752737] Re: [2.3.0-6434] mDNS observer problems
** Changed in: maas
Milestone: 2.5.0 => 2.5.0beta1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
Unknown
Status in MAAS:
Triaged
Status in MAAS 2.4 series:
Triaged
Status in avahi package in Ubuntu:
Confirmed
Bug description:
I see avahi-browser choking on non-utf8 characters in my rackd.log:
==> rackd.log <==
2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS
observation process started.
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
Traceback (most recent call last):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/maas/maas-common", line 87, in
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
main()
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/maas/maas-common", line 83, in main
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
run()
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/maas/maas-common", line 52, in run
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
from provisioningserver.__main__ import main
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55,
in
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
main()
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line
91, in __call__
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
self.execute(argv)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line
86, in execute
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
args.handler.run(args)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
221, in run
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
_observe_mdns(reader, output, args.verbose)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
145, in _observe_mdns
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
for event in observer(events):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
161, in _observe_resolver_found
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
for event in filter(_p_resolver_found, events):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line
125, in _extract_mdns_events
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
for event in map(parse_avahi_event, lines):
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
File "/usr/lib/python3.5/codecs.py", line 321, in decode
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
(result, consumed) = self._buffer_decode(data, self.errors, final)
2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240:
invalid continuation byte
2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS
observation process failed.
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a
probable error condition: process ended with exit code 1.
==> regiond.log <==
2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
==> maas.log <==
Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82
Similar traceback when running from command line:
maasuser@MAAS-RC01:~$ maas-rack observe-mdns
{"hostname": "Apple-TV", "interface": "ens33", "address": "192.168.1.81"}
Got SIGTERM, quitting.
Traceback (most recent call last):
File "/usr/sbin/maas-rack", line 87, in
main()
File "/usr/sbin/maas-rac
[Touch-packages] [Bug 1790963] Re: Unable to connect with openssh 7.8 client
** Description changed: Users are unable to connect to Ubuntu when using openssh client 7.8. We have seen this with both xenial and bionic, but this affects connecting - to ANY host running openssh <7.8. + to ANY host running openssh server <7.8. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm It appears that the change noted here in the release notes[1] for 7.8 is related: - * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar -HostbasedAcceptedKeyTypes options have changed. These now specify -signature algorithms that are accepted for their respective -authentication mechanism, where previously they specified accepted -key types. This distinction matters when using the RSA/SHA2 -signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their -certificate counterparts. Configurations that override these -options but omit these algorithm names may cause unexpected -authentication failures (no action is required for configurations -that accept the default for these options). + * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar + HostbasedAcceptedKeyTypes options have changed. These now specify + signature algorithms that are accepted for their respective + authentication mechanism, where previously they specified accepted + key types. This distinction matters when using the RSA/SHA2 + signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their + certificate counterparts. Configurations that override these + options but omit these algorithm names may cause unexpected + authentication failures (no action is required for configurations + that accept the default for these options). This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 - [1] https://www.openssh.com/releasenotes.html + [1] https://www.openssh.com/txt/release-7.8 -- 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/1790963 Title: Unable to connect with openssh 7.8 client Status in openssh package in Ubuntu: Confirmed Bug description: Users are unable to connect to Ubuntu when using openssh client 7.8. We have seen this with both xenial and bionic, but this affects connecting to ANY host running openssh server <7.8. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm It appears that the change noted here in the release notes[1] for 7.8 is related: * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 [1] https://www.openssh.com/txt/release-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1790963/+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 1790963] Re: Unable to connect with openssh 7.8 client
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- 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/1790963 Title: Unable to connect with openssh 7.8 client Status in openssh package in Ubuntu: Confirmed Bug description: Users are unable to connect to Ubuntu when using openssh client 7.8. We have seen this with both xenial and bionic, but this affects connecting to ANY host running openssh server <7.8. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm It appears that the change noted here in the release notes[1] for 7.8 is related: * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 [1] https://www.openssh.com/txt/release-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1790963/+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 1790963] [NEW] Unable to connect with openssh 7.8 client
Public bug reported: Users are unable to connect to Ubuntu when using openssh client 7.8. We have seen this with both xenial and bionic, but this affects connecting to ANY host running openssh <7.8. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm It appears that the change noted here in the release notes[1] for 7.8 is related: * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 [1] https://www.openssh.com/releasenotes.html ** Affects: openssh (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1790963 Title: Unable to connect with openssh 7.8 client Status in openssh package in Ubuntu: Confirmed Bug description: Users are unable to connect to Ubuntu when using openssh client 7.8. We have seen this with both xenial and bionic, but this affects connecting to ANY host running openssh <7.8. The only known recourse at this time is either downgrade clients to 7.7 or a previous version of openssh, or create new keys/certificates with a different alg that is acceptable for both the older server and newer client. The error message via ssh -vvv is: debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:REDACTED debug1: send_pubkey_test: no mutual signature algorithm It appears that the change noted here in the release notes[1] for 7.8 is related: * sshd(8): the semantics of PubkeyAcceptedKeyTypes and the similar HostbasedAcceptedKeyTypes options have changed. These now specify signature algorithms that are accepted for their respective authentication mechanism, where previously they specified accepted key types. This distinction matters when using the RSA/SHA2 signature algorithms "rsa-sha2-256", "rsa-sha2-512" and their certificate counterparts. Configurations that override these options but omit these algorithm names may cause unexpected authentication failures (no action is required for configurations that accept the default for these options). This is also affecting other Linux distributions as well: https://bugzilla.redhat.com/show_bug.cgi?id=1623929 https://bugs.archlinux.org/task/59838 [1] https://www.openssh.com/releasenotes.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1790963/+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 1790952] [NEW] package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: [ 76.316071] radeon :01:00.0: ring 0 stalled for more than 10240msec [ 76.316079] radeon :01:00.0: GPU lockup (current fence id 0x0285 last fence id 0x02a7 on ring 0) [ 76.316158] radeon :01:00.0: failed to get a new IB (-35) [ 76.316206] [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to get ib ! [ 76.428184] radeon :01:00.0: Saved 1079 dwords of commands on ring 0. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jvbpds 1462 F pulseaudio /dev/snd/controlC2: jvbpds 1462 F pulseaudio /dev/snd/controlC0: jvbpds 1462 F pulseaudio /dev/snd/controlC1: jvbpds 1462 F pulseaudio Date: Wed Sep 5 16:27:38 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=b8772eec-ebd7-414b-b70d-c2b22c23511f InstallationDate: Installed on 2016-06-19 (807 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 5474A5P ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=UUID=b71a7e54-3008-43c2-90b3-5fc7c8ada0df ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3 RfKill: SourcePackage: initramfs-tools StagingDrivers: r8188eu Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to bionic on 2018-07-23 (44 days ago) dmi.bios.date: 02/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 5JKT39AUS dmi.board.vendor: LENOVO dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr5JKT39AUS:bd02/26/2010:svnLENOVO:pn5474A5P:pvrThinkCentreM90:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 5474A5P dmi.product.version: ThinkCentre M90 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic staging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1790952 Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: [ 76.316071] radeon :01:00.0: ring 0 stalled for more than 10240msec [ 76.316079] radeon :01:00.0: GPU lockup (current fence id 0x0285 last fence id 0x02a7 on ring 0) [ 76.316158] radeon :01:00.0: failed to get a new IB (-35) [ 76.316206] [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to get ib ! [ 76.428184] radeon :01:00.0: Saved 1079 dwords of commands on ring 0. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jvbpds 1462 F pulseaudio /dev/snd/controlC2: jvbpds 1462 F pulseaudio /dev/snd/controlC0: jvbpds 1462 F pulseaudio /dev/snd/controlC1: jvbpds 1462 F pulseaudio Date: Wed Sep 5 16:27:38 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=b8772eec-ebd7-414b-b70d-c2b22c23511f InstallationDate: Installed on 2016-06-19 (807 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 5474A5P ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=UUID=b71a7e54-3008-43c2-90b3-5fc7c8ada0df ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 Relate
[Touch-packages] [Bug 1790948] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: The problem appeared during upgrading from 16.04 to 18.04 Similar problems were reported, but for upgrade 14.04 to 16.04, so I decided to open a new bug. The upgrade left the system in a broken state: root@storage:~# apt update Hit:1 http://ro.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://ro.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://ro.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 2446 packages can be upgraded. Run 'apt list --upgradable' to see them. root@storage:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: audacious : Depends: libaudcore5 (= 3.9-2) but it is not installed audacious-plugins : Depends: audacious-plugins-data (= 3.9-1build2) but 3.6.2-2ubuntu1 is installed Depends: libaudcore5 (>= 3.9) but it is not installed Depends: libaudgui5 (>= 3.9) but it is not installed Depends: libaudtag3 (>= 3.8) but it is not installed Depends: libfluidsynth1 (>= 1.1.6-4~) but 1.1.6-3 is installed bogofilter-bdb : Depends: libgsl2 but it is not installable checkbox-converged : Depends: qtdeclarative5-ubuntu-ui-toolkit-plugin but it is not installable debconf : Breaks: update-notifier-common (< 3.187~) but 3.168.9 is installed gnupg : Breaks: software-properties-common (<= 0.96.24.3) but 0.96.20.7 is installed kdeconnect-plasma : Depends: plasma-workspace but it is not installed libavogadro1 : Depends: libglew2.0 (>= 1.12.0) but it is not installed libguvcview-1.1-1 : Depends: libgsl2 but it is not installable liboxideqtquick0 : Depends: liboxideqtcore0 (= 1.21.5-0ubuntu0.16.04.1) but it is not installable libunity-webapps0 : Depends: unity-webapps-service but it is not installable mplayer : Depends: libdirectfb-1.7-7 (>= 1.7.7) but it is not installed phonon4qt5-backend-gstreamer : Depends: phonon-backend-gstreamer-common (= 4:4.9.0-1) but 4:4.8.2-0ubuntu2 is installed software-properties-kde : Depends: python3-pyqt5 but it is not installed unity-control-center-signon : Depends: unity-control-center but it is not installed unity-webapps-qml : Depends: qtdeclarative5-ubuntu-ui-toolkit-plugin but it is not installable or qtdeclarative5-ubuntu-ui-toolkit-plugin-gles but it is not installable update-notifier : Depends: update-notifier-common (= 3.192.1.3) but 3.168.9 is installed xaos : Depends: libgsl2 but it is not installable xorg : Depends: xserver-xorg (>= 1:7.7+19ubuntu7.1) but 1:7.7+13ubuntu3.1 is installed E: Unmet dependencies. Try using -f. Details: 1) Description:Ubuntu 18.04.1 LTS Release:18.04 2) fontconfig: Installed: 2.11.94-0ubuntu1.1 Candidate: 2.12.6-0ubuntu2 Version table: 2.12.6-0ubuntu2 500 500 http://ro.archive.ubuntu.com/ubuntu bionic/main amd64 Packages *** 2.11.94-0ubuntu1.1 100 100 /var/lib/dpkg/status 3) I expected a successful upgrade from 16.04 to 18.04 4) Now I have a broken system :) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Sep 5 22:11:25 2018 ErrorMessage: triggers looping, abandoned RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1790948 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: The problem appeared during upgrading from 16.04 to 18.04 Similar problems were reported, but for upgrade 14.04 to 16.04, so I decided to open a new bug. The upgrade left the system in a broken state: root@storage:~# apt update Hit:1 http://ro.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://ro.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://ro.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Build
[Touch-packages] [Bug 1790944] [NEW] [HP 250 G6 Notebook PC, Realtek ALC3227, Speaker, Internal] No sound at all
Public bug reported: sound problem ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 3241 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 5 22:51:21 2018 InstallationDate: Installed on 2015-03-18 (1267 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 3241 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP 250 G6 Notebook PC, Realtek ALC3227, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.40 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.24:bd09/25/2017:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.40:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G6 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1790944 Title: [HP 250 G6 Notebook PC, Realtek ALC3227, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: sound problem ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 3241 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 5 22:51:21 2018 InstallationDate: Installed on 2015-03-18 (1267 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 3241 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP 250 G6 Notebook PC, Realtek ALC3227, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.40 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.24:bd09/25/2017:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.40:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G6 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790926] Re: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW
run term sudo gedit .bashrc add line in this text config file .bashrc " export NO_AT_BRIDGE=1 fi " and next sudo su press you pass and wrote dbus-uuidgen > /var/lib/dbus/machine-id exit sudo apt-get download dbus sudo dpkg -i *.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1790926 Title: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW Status in dbus package in Ubuntu: New Bug description: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 20:34:37 2018 InstallationDate: Installed on 2018-06-18 (78 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1790926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790936] [NEW] [HP 250 G6 Notebook PC, Intel ID 2809, Digital Out, HDMI] No sound at all
Public bug reported: sound problem ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: user 3241 F...m pulseaudio /dev/snd/controlC0: user 3241 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 5 22:11:47 2018 InstallationDate: Installed on 2015-03-18 (1267 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 3241 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [HP 250 G6 Notebook PC, Intel ID 2809, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.40 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.24:bd09/25/2017:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.40:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G6 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1790936 Title: [HP 250 G6 Notebook PC, Intel ID 2809, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: sound problem ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: user 3241 F...m pulseaudio /dev/snd/controlC0: user 3241 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 5 22:11:47 2018 InstallationDate: Installed on 2015-03-18 (1267 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 3241 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [HP 250 G6 Notebook PC, Intel ID 2809, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.40 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.24:bd09/25/2017:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.40:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G6 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790936/+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 1770248] Re: console-setup fails intermittently due to a missing file in /tmp
This behavior is also presenting on Bionic. ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1770248 Title: console-setup fails intermittently due to a missing file in /tmp Status in console-setup package in Ubuntu: Confirmed Status in console-setup source package in Xenial: Confirmed Bug description: In our testing of cloud images, we intermittently see an error along the lines of: May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.7L3GEu: No such file This only happens from time-to-time which suggests that it's a race condition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.3 ProcVersionSignature: User Name 4.13.0-1015.19-gcp 4.13.16 Uname: Linux 4.13.0-1015-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed May 9 19:29:50 2018 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1770248/+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 1789422] Re: iso-codes 4.0 doesn't include XML files
** Changed in: iso-codes (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iso-codes in Ubuntu. https://bugs.launchpad.net/bugs/1789422 Title: iso-codes 4.0 doesn't include XML files Status in iso-codes package in Ubuntu: Fix Released Status in iso-codes package in Debian: Fix Released Bug description: I'm filing this bug in case iso-codes 4 gets synced to Ubuntu. We shouldn't allow it in Ubuntu until at least this issue is fixed: https://gitlab.gnome.org/GNOME/gnome-software/issues/454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1789422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790926] [NEW] pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW
Public bug reported: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 20:34:37 2018 InstallationDate: Installed on 2018-06-18 (78 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1790926 Title: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW Status in dbus package in Ubuntu: New Bug description: pport-gtk:3498): dbind-WARNING **: 20:34:35.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GodlCLzxbW ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 20:34:37 2018 InstallationDate: Installed on 2018-06-18 (78 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1790926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
seems related to the file /etc/ppp/ip-up.d/usepeerdns on line 23-24 cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" mv -f "$REALRESOLVCONF.tmp" "$REALRESOLVCONF" the cp command doesn't preserve file ownership -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1638634] Re: Print Job with Authentication is postponed until queue is opened manually
setting to Triaged/Low per request on #ubuntu-bugs. Description updated as in comment #24. ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Triaged ** Description changed: + Ubuntu version 16.04 + 16.04 (cups 2.1.3-4ubuntu0.5). system-config-printer-common 1.5.7+20160212-0ubuntu2. Hplip 3.16.3+repack0-1. + Problem is reproducable by the bug reporter. All print jobs from many different applications + Bug triager is unable to reproduce the bug. + + Steps to reproduce: + 1. Print an any document from an any application's print dialog (e.g. evince, Okular, GIMP, ReText,...). + 2. Printing does not happen. + 3. Open "system-config-printer” + 4. Open the printer's print queue + 5. All documents in the queue are processed, i.e. printed immediately. + + Expected behaviour: the document prints immediately. + + Actual behaviour: the document is held in the queue until the print + queue is opened through "system-config-printer.” + + Additional notes: + Printer is a RICOH MP C3003 situated on a large network. + CUPS interface on local computer indicates that job is stopped but “release job” button is ignored. + Opening the queue in “system-config-printer” on local computer immediately starts the job. + Reporter has uploaded tail of access.log which mentions authentication successful, only after the reporter opened the queue in “system-config-printer” + --- + + Triager searched for dups - none found. + + (original description follows) + I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer. - --- + --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: - E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. - E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. - E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. - E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. - E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. - CurrentDesktop: Unity - DistroRelease: Ubuntu 16.04 + E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. + E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. + E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. + E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. + E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. + CurrentDesktop: UnityDistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-09-15 (1077 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: - device for 0_prost: lpd://prost.uni-koblenz.de/ - device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 - device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 + device for 0_prost: lpd://prost.uni-koblenz.de/ + device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 + device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 MachineType: LENOVO 20BX000XGE Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: - Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied - grep: /etc/cups/ppd/0_prost.ppd: Permission denied + Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied + grep: /etc/cups/ppd/0_prost.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Tags: xenial Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp vboxusers _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Infor
[Touch-packages] [Bug 1764779] Re: Nautilus crashed open Windows-partition [assertion failed: (location != NULL)]
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/354342 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1764779 Title: Nautilus crashed open Windows-partition [assertion failed: (location != NULL)] Status in glib2.0 package in Ubuntu: In Progress Status in nautilus package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] if I open a new partition from the Hard-drive (Windows in this case) Nautilus crash, report him self and after reopen it, the partition is normal available as nothing would be https://errors.ubuntu.com/problem/f49deb51a98d691e3e040d7f7334ad08d1e0e54c https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938 https://errors.ubuntu.com/problem/00db9958203affb0a98a2842bb2bd91547e6bd5a https://errors.ubuntu.com/problem/818d3ad2d9fe9f9f64f32fcb5f10da4126d3827d [ Test case ] * Open nautilus and select an external hd that is not mounted from the sidebar * Nautilus sould not crash (in case showing an error message) [ Regression potential ] Partitions that have been actually mounted, are not shown or an error is prompted. - Issue from the log: Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount point cleanup: Process reported exit code 5: Failed to start clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit media-username-12F6CC77F6CC5D1B.mount not found. Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: assertion 'G_IS_MOUNT (mount)' failed Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ** Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: (location != NULL) - ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 16:45:30 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-move-to-trash-shortcut-changed-dialog' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'" InstallationDate: Installed on 2018-03-16 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1764779/+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 1790253] Re: ubuntu-bug causes GTK-message
** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: apport (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1790253 Title: ubuntu-bug causes GTK-message Status in apport package in Ubuntu: Confirmed Bug description: ~$ ubuntu-bug update-manager Gtk-Message: 11:31:48.137: GtkDialog mapped without a transient parent. This is discouraged. that appears with others as well: ~$ ubuntu-bug software-updater dpkg-query: no packages found matching software-updater Gtk-Message: 11:29:10.135: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:41:51 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1790253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
Also just started seeing this after updating from Ubuntu GNOME 16.04 to Ubuntu 18.04. The only relevant thing I can think of, is that I may have changed the default login manager to GDM. Otherwise, can't think of anything that might have triggered this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790390] Re: Intel i915 GPU driver has wrong max resolution output for certain models
Update. This is a functional regression as a result of switching to
modesetting.
Source: https://bugs.freedesktop.org/show_bug.cgi?id=107840#c1
** Package changed: linux-signed-oem (Ubuntu) => xorg (Ubuntu)
** Tags removed: kernel-bug
** Summary changed:
- Intel i915 GPU driver has wrong max resolution output for certain models
+ Xorg cannot exceed pipeline dimensions reported by kernel
** Bug watch added: freedesktop.org Bugzilla #107840
https://bugs.freedesktop.org/show_bug.cgi?id=107840
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1790390
Title:
Xorg cannot exceed pipeline dimensions reported by kernel
Status in xorg package in Ubuntu:
New
Bug description:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven
by running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790390/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790253] Re: ubuntu-bug causes GTK-message
** Package changed: linux (Ubuntu) => apport (Ubuntu) ** Changed in: apport (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1790253 Title: ubuntu-bug causes GTK-message Status in apport package in Ubuntu: New Bug description: ~$ ubuntu-bug update-manager Gtk-Message: 11:31:48.137: GtkDialog mapped without a transient parent. This is discouraged. that appears with others as well: ~$ ubuntu-bug software-updater dpkg-query: no packages found matching software-updater Gtk-Message: 11:29:10.135: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:41:51 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1790253/+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 1790390] [NEW] Intel i915 GPU driver has wrong max resolution output for certain models
You have been subscribed to a public bug:
The i915 driver in the Linux kernel misrepresents the max output of
certain, newer, GPUs.
The output should be 16384x16384 for newer models (on at least 7th and
8th gen Intel CPUs) but it is stuck in 8192x8192.
The problem lies in:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c
The conditional branch which is wrong is:
/* maximum framebuffer dimensions */
if (IS_GEN2(dev_priv)) {
dev->mode_config.max_width = 2048;
dev->mode_config.max_height = 2048;
} else if (IS_GEN3(dev_priv)) {
dev->mode_config.max_width = 4096;
dev->mode_config.max_height = 4096;
} else {
dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 8192;
}
While I'm not certain which generations specifically allows the higher
output it is most certainly true of all iGPUs on the 7th and 8th
generation CPUs.
This is corroborated by Intel's own hardware pages, and can be proven by
running Wayland which ignores the limitation in the driver.
Bug is present both on all Ubuntu releases, including 18.04.
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: kernel-bug
--
Intel i915 GPU driver has wrong max resolution output for certain models
https://bugs.launchpad.net/bugs/1790390
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364522] Re: Firefox crashes sometimes when using webgl with nouveau driver
Bernhard, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Do you still see a problem related to the one that you reported? Please let us know if you do. If we do not hear from you this bug report will expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1364522 Title: Firefox crashes sometimes when using webgl with nouveau driver Status in firefox package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Visiting with Firefox e.g. https://developer.mozilla.org/de/demos/detail/orange-slice/launch makes firefox crash. Program received signal SIGSEGV, Segmentation fault. nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at ../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226 226if (screen->fence.current->state < NOUVEAU_FENCE_STATE_EMITTING) (gdb) bt #0 nouveau_fence_next (screen=screen@entry=0x5a5a5a5a) at ../../../../../../src/gallium/drivers/nouveau/nouveau_fence.c:226 #1 0x9b5b7fc0 in nv30_context_kick_notify (push=0x9b8f62b0) at ../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:48 #2 0xa0a0ea3e in pushbuf_submit (push=push@entry=0x9b8f62b0, chan=, chan=) at ../../nouveau/pushbuf.c:325 #3 0xa0a0ed7a in pushbuf_flush (push=push@entry=0x9b8f62b0) at ../../nouveau/pushbuf.c:402 #4 0xa0a0faca in nouveau_pushbuf_kick (push=0x9b8f62b0, chan=0xa40c5420) at ../../nouveau/pushbuf.c:774 #5 0x9b5b811f in PUSH_KICK (push=) at ../../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:56 #6 nv30_context_flush (pipe=0x9b986000, fence=0x0, flags=0) at ../../../../../../src/gallium/drivers/nouveau/nv30/nv30_context.c:83 #7 0x9b4b4e1c in st_flush (st=st@entry=0x989e8000, fence=fence@entry=0x0, flags=flags@entry=0) at ../../../../src/mesa/state_tracker/st_cb_flush.c:87 #8 0x9b4b4e82 in st_glFlush (ctx=0x98844000) at ../../../../src/mesa/state_tracker/st_cb_flush.c:121 #9 0x9b3b3065 in _mesa_flush (ctx=ctx@entry=0x98844000) at ../../../../src/mesa/main/context.c:1691 #10 0x9b3b3130 in _mesa_make_current (newCtx=newCtx@entry=0x0, drawBuffer=drawBuffer@entry=0x0, readBuffer=readBuffer@entry=0x0) at ../../../../src/mesa/main/context.c:1503 #11 0x9b4dee74 in st_api_make_current (stapi=0x9b779700 , stctxi=0x0, stdrawi=0x0, streadi=0x0) at ../../../../src/mesa/state_tracker/st_manager.c:746 #12 0x9b59d9ee in dri_unbind_context (cPriv=0x994e3120) at ../../../../../../../src/gallium/state_trackers/dri/drm/dri_context.c:215 #13 0x9b38db93 in driUnbindContext (pcp=0x994e3120) at ../../../../../../../src/mesa/drivers/dri/common/dri_util.c:578 #14 0x9b7df149 in dri2_unbind_context (context=0x9b9cbc20, new=0x0) at ../../../../src/glx/dri2_glx.c:184 #15 0x9b7b7985 in MakeContextCurrent (dpy=dpy@entry=0xb7191000, draw=draw@entry=0, read=read@entry=0, gc_user=gc_user@entry=0x0) at ../../../../src/glx/glxcurrent.c:245 #16 0x9b7b7a73 in glXMakeCurrent (dpy=0xb7191000, draw=0, gc=0x0) at ../../../../src/glx/glxcurrent.c:293 #17 0xb3d3916d in mozilla::gl::GLXLibrary::xMakeCurrent (this=0xb6e58470 , display=0xb7191000, drawable=drawable@entry=0, context=context@entry=0x0) at /build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:525 #18 0xb3d39d92 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, __in_chrg=) at /build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:836 #19 0xb3d39e12 in mozilla::gl::GLContextGLX::~GLContextGLX (this=0x988dc800, __in_chrg=) at /build/buildd/firefox-31.0+build1/gfx/gl/GLContextProviderGLX.cpp:845 #20 0xb3d38ea0 in mozilla::detail::GenericRefCounted<(mozilla::detail::RefCountAtomicity)0>::Release (this=0x988dc800) at ../../dist/include/mozilla/GenericRefCounted.h:95 #21 0xb3ddc635 in nsRefPtr::assign_assuming_AddRef (this=this@entry=0x9b8eb84c, newPtr=newPtr@entry=0x0) at ../../dist/include/nsAutoPtr.h:882 #22 0xb4561170 in assign_with_AddRef (rawPtr=0x0, this=0x9b8eb84c) at ../../../dist/include/nsAutoPtr.h:866 #23 operator= (rhs=0x0, this=0x9b8eb84c) at ../../../dist/include/nsAutoPtr.h:964 #24 mozilla::WebGLContext::DestroyResourcesAndContext (this=this@entry=0x9b8eb800) at /build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:284 #25 0xb45611bb in mozilla::WebGLContext::~WebGLContext (this=0x9b8eb800, __in_chrg=) at /build/buildd/firefox-31.0+build1/content/canvas/src/WebGLContext.cpp:203 #26 0xb455e330 in mozilla::WebGL1Context::~WebGL1Context (this=0x9b8eb800,
[Touch-packages] [Bug 1790253] [NEW] ubuntu-bug causes GTK-message
You have been subscribed to a public bug: ~$ ubuntu-bug update-manager Gtk-Message: 11:31:48.137: GtkDialog mapped without a transient parent. This is discouraged. that appears with others as well: ~$ ubuntu-bug software-updater dpkg-query: no packages found matching software-updater Gtk-Message: 11:29:10.135: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:41:51 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- ubuntu-bug causes GTK-message https://bugs.launchpad.net/bugs/1790253 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790881] [NEW] ubuntu 18.04 LTS does not load onboard intel 82G33/G31 graphics controller
Public bug reported: upgraded from Ubuntu 16.04 LTS to 18.04 LTS but graphic display has failed and is extremely slow. $ glxinfo|grep OpenGL gives below output: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5 OpenGL core profile shading language version string: 3.30 $ lshw | grep display gives below output: *-display UNCLAIMED Onboard intel graphics controller worked perfectly on 16.04 but failed on upgrading to 18.04 Kindly suggest a workaround to re-enable onboard intel 82G33/G31 Integrated Graphics Controller (rev 10) on ubuntu 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 5 19:02:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2015-07-19 (1144 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.5-041805-generic root=UUID=8d00030d-c1a2-47fd-8b97-b7813c6e7ef6 ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection dmi.bios.date: 09/29/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd09/29/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790881 Title: ubuntu 18.04 LTS does not load onboard intel 82G33/G31 graphics controller Status in xorg package in Ubuntu: New Bug description: upgraded from Ubuntu 16.04 LTS to 18.04 LTS but graphic display has failed and is extremely slow. $ glxinfo|grep OpenGL gives below output: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5 OpenGL core profile shading language version string: 3.30 $ lshw | grep display gives below output: *-display UNCLAIMED Onboard intel graphics controller worked perfectly on 16.04 but failed on upgrading to 18.04 Kindly suggest a workaround to re-enable onboard intel 82G33/G31 Integrated Graphics Controller (rev 10) on ubuntu 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 5 19:02:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2015-07-19 (1144 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "
[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot
I've hit that 'retrigger' button 2 more times and have not seen failures.
I just did again. Don't know what to do. :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788188
Title:
transient systemd ordering cycle in boot with overlayroot
Status in systemd package in Ubuntu:
Confirmed
Bug description:
open-iscsi test utilizes overlayroot to boot a cloud-image with root
filesystem on a read-only iscsi server.
The /etc/fstab file in the image looks like this:
LABEL=cloudimg-rootfs /ext4 defaults0 0
#LABEL=UEFI /boot/efi vfatdefaults0 0
when init takes over from the initramfs, we have
/proc/cmdline:
nomodeset iscsi_initiator=maas-enlist
iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
iscsi_target_port=3260 iscsi_initiator=maas-enlist
ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
overlayroot=tmpfs console=ttyS0
ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash
/etc/fstab:
# cat /etc/fstab
#
# This fstab is in an overlay. The real one can be found at
# /media/root-ro/etc/fstab
# The original entry for '/' and other mounts have been updated to be
placed
# under /media/root-ro.
# To permanently modify this (or any other file), you should change-root
into
# a writable view of the underlying filesystem using:
# sudo overlayroot-chroot
#
#LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
/media/root-ro/ / overlay
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
#LABEL=UEFI /boot/efi vfat defaults 0 0
/root/root-ro/etc/fstab:
LABEL=cloudimg-rootfs /ext4 defaults0 0
#LABEL=UEFI /boot/efi vfatdefaults0 0
/proc/mounts:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
/media/root-ro ext4 ro,relatime 0 0
tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
overlayroot / overlay
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
0 0
/proc/1/mountinfo:
21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev
rw,size=233748k,nr_inodes=58437,mode=755
24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts
rw,gid=5,mode=620,ptmxmode=000
25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs
rw,size=49288k,mode=755
26 28 8:1 / /media/root-ro ro,relatime - ext4
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
28 0 0:24 / / ro,relatime - overlay overlayroot
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
read-only mount of block device on mount point '$ROOTMNT'
(ROOTMNT=/root). In order to set up the overlayroot, it does the
following:
mkdir /media/root-ro /media/root-rw # in the initramfs
mount -t tmpfs tmpfs-root /media/root-rw
mkdir /media/root-rw/overlay-workdir/_
mount --move $ROOTMNT /media/root-ro
mount -t overlay -o
lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
overlayroot /root
mkdir $ROOTMNT/media/root-ro
mkdir $ROOTMNT/media/root-rw
mount --move /media/root-ro "${ROOTMNT}/media/root-ro"
mount --move /media/root-rw "${ROOTMNT}/media/root-rw"
# then, if 'ro' on the command line, it mounts /root read-only.
mount -o remount,ro $ROOTMNT
The script then exits, as ROOTMNT is now set up with a read-only mount
of the overlayroot. All the mounts it has done have been moved
under ROOTMNT.
On failure systemd reports:
[ 104.098833] systemd[1]: media-root\x2dro.mount: Found ordering cycle on
-.mount/start
[ 104.109897] systemd[1]: media-root\x2dro.mount: Found dependency on
media-root\x2dro.mount/start
[ 104.121386] systemd[1]: media-root\x2dro.mount: Unable to break cycle
starting with media-root\x2dro.mount/start
[ 104.137591] systemd[1]: Requested transaction contains an unfixable
cyclic ordering dependency: Resource de
[Touch-packages] [Bug 1769893] Re: CUPS Unauthorized when using Chrome browser in Ubuntu 18.04
This allowed me to add a Canon IP7200 via the local CUPS httpd: https://forum.manjaro.org/t/latest-chrome-unauthorized-to-alter- cups/45286 I could print a test page from CUPS via the webpage. Unfortunately still not able to add via the system device dialogs - CUPS internal server error -- 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/1769893 Title: CUPS Unauthorized when using Chrome browser in Ubuntu 18.04 Status in cups package in Ubuntu: Confirmed Bug description: Using Chrome Version 66.0.3359.139 (Official Build) (64-bit) I am able to access and add a printer through Chrome by going to the page http://localhost:631/admin/login and I can add a printer fine. But I cannot add the printer if I go directly to http://localhost:631/admin and bypass the login. If I need to change any defaults of the printer through the same pages it gives me the "Unauthorized" and will not change anything. I can change it in Firefox and the printers control panel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 (Authentication failure) E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Tue May 8 07:18:47 2018 InstallationDate: Installed on 2018-05-05 (2 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Deskjet_3520_series_75C0A7_: ipp://HP6C3BE575C0A7.local:631/ipp/print device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253 MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', '/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 biosdevname=0 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769893/+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 1790664] Re: routing policy not always applied on systemd-networkd restart
** Changed in: systemd (Ubuntu) Status: Incomplete => In Progress ** Changed in: systemd (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1790664 Title: routing policy not always applied on systemd-networkd restart Status in systemd package in Ubuntu: New Bug description: We are using ubuntu 18.04 in an environment with two NIC in the same subnet. As part of network configuration we have created a routing table for each NIC. Every other time that we restart networkd we lose connectivity to eth0. After tcpdump we noticed the reason we lose connectivity to eht0 is routing problem. All connection will always go out from eht1. If we restart netowrkd one more time this will fix the routing issue instantly. Also on each reboot routing policy applies correctly. The problem only appears when we restart netwrokd every other time. We already have raised this issue with Netplan and they suggest this is a systemd bug. Please find the debugs in the attachments. Please don't hesitate to ask if you require any further logs. Regards Arash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+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 1790870] [NEW] No X display - gdm3 crash with segfault
Public bug reported: This desktop was running 16.04.5 version and started few weeks ago to have the desktop crashing. In dmesg I saw compiz segfault at 0 ip [...] error 4. I decide to upgrade to 18.04.1 to solve this problem but it's still there: gnome-shell at 0 ip [...] error 4 In 18.04 i even don't get the desktop, only the mouse indicator is visible, disappearing from time to time (seems on each crash). Attached is the output of an radeontool dump. The desktop is unusable in graphic mode. Daniel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Wed Sep 5 14:40:14 2018 DistUpgraded: 2018-09-05 13:03:08,966 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2016-03-03 (916 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160227) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=8c2df27f-cbc4-4c8d-a4f1-dc7994b41016 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) dmi.bios.date: 04/18/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.22 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8312220 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.22:bd04/18/2007:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 5 08:36:00 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 inputHP WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "regdump_broke.txt" https://bugs.launchpad.net/bugs/1790870/+attachment/5184947/+files/regdump_broke.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790870 Title: No X display - gdm3 crash with segfault Status in xorg package in Ubuntu: New Bug description: This desktop was running 16.04.5 version and started few weeks ago to have the desktop crashing. In dmesg I saw compiz segfault at 0 ip [...] error 4. I decide to upgrade to 18.04.1 to solve this problem but it's still there: gnome-shell at 0 ip [...] error 4 In 18.04 i even don't get the desktop, only the mouse indicator is visible, disappearing from time to time (seems on each crash). Attached is the output of an radeontool dump. The desktop is unusable in graphic mode. Daniel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Wed Sep 5 14:40:14 2018 DistUpgraded: 2018-09-05 13:03:08,966 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
As said in comment #3 I opened an issue #2944 on github. Here is the link https://github.com/curl/curl/issues/2944. ** Bug watch added: github.com/curl/curl/issues #2944 https://github.com/curl/curl/issues/2944 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Can anyone from maintainers work on this bug, Please ? As said in comment #3, is there anyone who can at least point me on where to solve this issue. I know things get frustrating when maintainers get comments like #4. Now would you guys please let go and solve this bug. It will help folks like me. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Description changed: - There are some new Intel GPU pci-id's that need to be added to several - places: + [Impact] + There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. + + [Test case] + Check that the user session uses the proper driver on these systems. + + [Regression potential] + none, these just add pci-id's and platform definitions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
Swapon is not working with swap file or swap partion. Mkswap with Kernel 4.15.0-30-gernic and swapon with Kernel 4.15.0-33-gernic is even not working. VMware ESXi 6.0 + Ubuntu 18.04 (32Bit) - Linux 4.15.0-33-generic (i686) affected VMware ESXi 6.0 + Ubuntu 18.04 (32Bit) - Linux 4.15.0-30-generic (i686) not affected VMware ESXi 6.0 + Ubuntu 18.04 (64Bit) - Linux 4.15.0-33-generic (x86_64) not affected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
Note that there is no UI to set sector-size in the installer, and the installer does not generate sector-size option in the crypttab either. I kind of wish sector-size could just be autodetected, and e.g. used by default on 4k native drives. But I'll check if this option can be added to partman-crypto. -- 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/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+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 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- 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/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: Invalid Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.50-0ubuntu0ppa1 amd64
[Touch-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Tried the bluez PPA before, but it didn't help. Since I don't own this notebook anymore, this issue is resolved for me. -- 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/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: Incomplete Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Description changed: There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 + + and to make future additions easier, add platform definitions for + Whiskey Lake and Amber Lake too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Post on askubuntu: https://askubuntu.com/questions/1072273/hdajackretask-gives-new-audio- settings-in-alsamixer-but-they-dont-work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Thanks Iain! That fixed it for me: $ sudo apt install appstream/cosmic libappstream4/cosmic $ dpkg -l appstream libappstream4 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=-=== ii appstream 0.12.2-2 amd64 Software component metadata management ii libappstream4:amd64 0.12.2-2 amd64 Library to access AppStream services $ sudo appstreamcli refresh-cache --force AppStream cache update completed successfully. Greetings, Lars -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
On Wed, Sep 05, 2018 at 06:08:23AM -, Johannes Niediek wrote: > I still see the problem on Debian, could you elaborate which package > contains the fix? Firstly, for Debian bugs, please use the Debian bug tracker. > Info: > > > dpkg-query -s appstream You need to make sure libappstream4 is updated to 0.12.2-2 - the fix for the bug I point out below is in the library and not the tool itself. > > appstreamcli refresh-cache > > (appstreamcli:3963): GLib-CRITICAL **: 09:07:57.805: > g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || > GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite > (GVSB(builder)->type)' failed Secondly, this is actually a different error to the one this bug was talking about. If this were an Ubuntu bug, it should be a new one. Your problem looks like Debian bug #906538 to me, which happily is fixed in both Debian and Ubuntu already. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
got an update today, issue is back and `sudo kbd_mode -s` does not fix it anymore... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790816] [NEW] Terrible sound after update to 18.04
Public bug reported: The sound just is extremely distorted after update to 18.04. Like an old radio that's not picking up the station right. I saw a webpage about the same device I am using and tried their solution. That didn't help at all. Hope I didn't make things worse. I saw a page that mentioned the lspci command. Based on that, I guess I am using an Intel 82801 JD/DO audio card. One site said that requires an snd_hda_intel driver, but all I could find in Synaptic Package Manager was that an alsa driver and pulse audio were installed. Could the correct driver have been removed with the new installation? This computer has been kind of buggy as of late, but the audio had been working. I had problems installing this OS. Mostly it seems to be working otherwise though. 1) Description: Ubuntu 18.04.1 LTS Release:18.04 2) N: Unable to locate package pkgname 3) What you expected to happen: sound to work properly 4) What happened instead: sound distorted Hope my attempt to fix it doesn't screw up the bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: szettner 2030 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 5 03:07:08 2018 InstallationDate: Installed on 2017-06-28 (433 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [OptiPlex 760, Analog Devices AD1984A, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-09-02 (2 days ago) dmi.bios.date: 12/03/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0D517D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/03/2008:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0D517D:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1790816 Title: Terrible sound after update to 18.04 Status in alsa-driver package in Ubuntu: New Bug description: The sound just is extremely distorted after update to 18.04. Like an old radio that's not picking up the station right. I saw a webpage about the same device I am using and tried their solution. That didn't help at all. Hope I didn't make things worse. I saw a page that mentioned the lspci command. Based on that, I guess I am using an Intel 82801 JD/DO audio card. One site said that requires an snd_hda_intel driver, but all I could find in Synaptic Package Manager was that an alsa driver and pulse audio were installed. Could the correct driver have been removed with the new installation? This computer has been kind of buggy as of late, but the audio had been working. I had problems installing this OS. Mostly it seems to be working otherwise though. 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) N: Unable to locate package pkgname 3) What you expected to happen: sound to work properly 4) What happened instead: sound distorted Hope my attempt to fix it doesn't screw up the bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: szettner 2030 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 5 03:07:08 2018 InstallationDate: Installed on 2017-06-28 (433 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [OptiPlex 760, Analog Devices AD1984A, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-09-02 (2 days ago) dmi.bios.date: 12/03/2008 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1790806] [NEW] file -i command reports "text/x-c" mime type for .srt file (Subtitle / Plain Text file)
Public bug reported: 1. Bug is on Ubuntu 14.04.5 LTS and Ubuntu 16.04.5 LTS 2. file: Installiert: 1:5.25-2ubuntu1.1 file: Installiert: 1:5.14-2ubuntu3.4 3. command: "file -i test_mime.srt" Actual result: "text/x-c" Expected result: "text/plain" or "application/x-subrip" In line 8 of the attached file is the word "extern". therefore, the file is incorrectly identified as c code ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Affects: hhvm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "test_mime.srt.zip" https://bugs.launchpad.net/bugs/1790806/+attachment/5184798/+files/test_mime.srt.zip ** Also affects: hhvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1790806 Title: file -i command reports "text/x-c" mime type for .srt file (Subtitle / Plain Text file) Status in file package in Ubuntu: New Status in hhvm package in Ubuntu: New Bug description: 1. Bug is on Ubuntu 14.04.5 LTS and Ubuntu 16.04.5 LTS 2. file: Installiert: 1:5.25-2ubuntu1.1 file: Installiert: 1:5.14-2ubuntu3.4 3. command: "file -i test_mime.srt" Actual result: "text/x-c" Expected result: "text/plain" or "application/x-subrip" In line 8 of the attached file is the word "extern". therefore, the file is incorrectly identified as c code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1790806/+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
