[Touch-packages] [Bug 1432302] Re: [80E3, Conexant CX20751/2, Speaker, Internal] fails after a while
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1432302 Title: [80E3, Conexant CX20751/2, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Expired Bug description: Steps to reproduce: 1. Boot to ubuntu. 2. Change volume up and down using Fn volume keys several times. 3. Sound start shuttering and only reboot helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: boomer 2115 F pulseaudio /dev/snd/controlC0: boomer 2115 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 15 12:24:42 2015 InstallationDate: Installed on 2015-02-12 (30 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [80E3, Conexant CX20751/2, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN24WW(V1.06) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN24WW(V1.06):bd07/09/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1432302/+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 1813020] Re: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] There is no voice in headphone
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1813020 Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] There is no voice in headphone Status in alsa-driver package in Ubuntu: Expired Bug description: Suddenly my headphone stopped working. It is being detected when I plugged in. But there is no voice in headphone. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 23 19:15:32 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-29 (177 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-22T23:58:18.387600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813020/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1815750] Re: autopkgtest failure due to security update
** No longer affects: apt (Ubuntu Trusty) ** No longer affects: apt (Ubuntu Bionic) ** No longer affects: apt (Ubuntu Cosmic) ** Changed in: apt (Ubuntu) Status: New => Fix Released ** Changed in: apt (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815750 Title: autopkgtest failure due to security update Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Bug description: [impact] the security update for: SECURITY UPDATE: content injection in http method (CVE-2019-3462) (LP: #1812353) causes an autopkgtest failure for: Failed tests: test-cve-2019-3462-dequote-injection [test case] run autopkgtest on the security-patched version [regression potential] the test needs to be updated, so the regression potential is around the test continuing to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815750/+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 1815760] Re: Additional hooks for update
** No longer affects: apt (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update::Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** No longer affects: systemd (Ubuntu Trusty) ** No longer affects: systemd (Ubuntu Xenial) -- 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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflow the 512 byte maximum for a UDP DNS packet; e.g.: $ ping testing.irongiantdesign.com ping: testing.irongiantdesign.com: Temporary failure in name resolution Altern
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
** No longer affects: systemd (Ubuntu Xenial) -- 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/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+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 1705642] Re: [libgtk-3-doc] FIXME: MISSING XINCLUDE CONTENT
*** This bug is a duplicate of bug 1085976 *** https://bugs.launchpad.net/bugs/1085976 ** Tags added: libgtk-3-doc -- 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/1705642 Title: [libgtk-3-doc] FIXME: MISSING XINCLUDE CONTENT Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Run commands: apt-get install libgtk-3-doc firefox /usr/share/doc/libgtk-3-doc/gtk3/gtk-getting-started.html Read page. Instead of some content the message "FIXME: MISSING XINCLUDE CONTENT" showed. Please, rebuild package "libgtk-3-doc" correctly. Expected behaviour: show valid content instead of message "FIXME: MISSING XINCLUDE CONTENT". File name: pool/main/g/gtk+3.0/libgtk-3-doc_3.18.9-1ubuntu3.3_all.deb. OS: Ubuntu 16.04 (xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1705642/+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 1821822] Re: Temporary failure in name resolution in Python 3.7.2
** Description changed:
- My Python application works in 18.10 fine, but when upgrading to 19.10
- for development reasons the same script produces the errors reported
- below. I have checked on the Python bug tracker and there are no related
- bug reports.
-
- Traceback (most recent call last):
- File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
- encode_chunked=req.has_header('Transfer-encoding'))
- File "/usr/lib/python3.7/http/client.py", line 1229, in request
- self._send_request(method, url, body, headers, encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
- self.endheaders(body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
- self._send_output(message_body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
- self.send(msg)
- File "/usr/lib/python3.7/http/client.py", line 956, in send
- self.connect()
- File "/usr/lib/python3.7/http/client.py", line 1384, in connect
- super().connect()
- File "/usr/lib/python3.7/http/client.py", line 928, in connect
- (self.host,self.port), self.timeout, self.source_address)
- File "/usr/lib/python3.7/socket.py", line 707, in create_connection
- for res in getaddrinfo(host, port, 0, SOCK_STREAM):
- File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
- for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
- socket.gaierror: [Errno -3] Temporary failure in name resolution
-
- During handling of the above exception, another exception occurred:
-
- Traceback (most recent call last):
- File "/usr/lib/myapp/main.py", line 312, in
- win = GridWindow()
- File "/usr/lib/myapp/main.py", line 37, in __init__
- self.updates_frame = self.draw_updates_frame()
- File "/usr/lib/myapp/main.py", line 132, in draw_updates_frame
- if self.version_check() == True:
- File "/usr/lib/myapp/main.py", line 53, in version_check
- get_version = urlopen('https://urlchanged.com').read()
- File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
- return opener.open(url, data, timeout)
- File "/usr/lib/python3.7/urllib/request.py", line 525, in open
- response = self._open(req, data)
- File "/usr/lib/python3.7/urllib/request.py", line 543, in _open
- '_open', req)
- File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
- result = func(*args)
- File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open
- context=self._context, check_hostname=self._check_hostname)
- File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open
- raise URLError(err)
- urllib.error.URLError:
+ Fixed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1821822
Title:
Temporary failure in name resolution in Python 3.7.2
Status in python3-defaults package in Ubuntu:
New
Bug description:
Fixed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1821822/+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 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
FWIW this is the 'udevadm info' output on the primary slave:
root@node-1970:~# udevadm info /sys/class/net/ens4
P: /devices/pci:00/:00:04.0/net/ens4
E: DEVPATH=/devices/pci:00/:00:04.0/net/ens4
E: ID_BUS=pci
E: ID_MODEL_FROM_DATABASE=82599 Ethernet Controller Virtual Function
E: ID_MODEL_ID=0x10ed
E: ID_NET_DRIVER=ixgbevf
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME=ens4
E: ID_NET_NAME_MAC=enx02001701d517
E: ID_NET_NAME_PATH=enp0s4
E: ID_NET_NAME_SLOT=ens4
E: ID_PATH=pci-:00:04.0
E: ID_PATH_TAG=pci-_00_04_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_VENDOR_ID=0x8086
E: IFINDEX=9
E: INTERFACE=ens4
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens4 /sys/subsystem/net/devices/ens4
E: TAGS=:systemd:
E: USEC_INITIALIZED=199842925
E: net.ifnames=1
The ID_NET_DRIVER here is ixgbevf, but in general it can be driver name
for any netdev including virtio_net.
--
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/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
Status in netplan:
Triaged
Status in netplan.io package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Incomplete
Bug description:
This bug is a follow-up to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268
after applying the 0001-net_failover-delay-taking-over-primary-device-
to-acc.patch attached in that bug, the VF interface "eth0" is renamed
to "rename4" instead of "ens4". Log is showing that attempt to rename
"eth0" to "ens3" failed because of conflict with existing name, so
that's why it ends up with rename4.
vsbalakr@ubuntu-18:~$ uname -a
Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
vsbalakr@ubuntu-18:~$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noqueue state UP
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd
ff:ff:ff:ff:ff:ff
3: ens3nsby: mtu 1500 qdisc pfifo_fast
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff
4: rename4: mtu 1500 qdisc mq master ens3
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd
ff:ff:ff:ff:ff:ff
vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
...
Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]: [1552932112.9591]
device (rename4): carrier: link connected
Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]: [1552932112.9591]
device (rename4): enslaved to non-master-type device ens3; ignoring
Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface
name 'eth0' to 'ens3': Device or resource busy
Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4'
from 'eth0' to 'ens3': Device or resource busy
Within VM there's netplan config as below:
vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]
By running udevadm test, we can see the conflicting ens3 name comes
from netplan's /run/udev/rules.d/99-netplan-ens3.rules
vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"
vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add"
/sys/class/net/eth0
calling: test
version 237
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
Load module index
Parsed configuration file /lib/systemd/network/99-default.link
Parsed configuration file /run/systemd/network/10-netplan-ens3.link
Created link configuration context.
Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
..
Reading rules file: /lib/udev/rules.d/99-vmware-scsi-udev.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 38638 bytes strings
25317 strings (216160 bytes), 21957 de-duplicated (180883 bytes), 3361 trie
nodes used
RUN '/lib/open-iscsi/net-interface-handler start'
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
IMPORT builtin 'hwdb' /lib/udev/rules.d/75-net-description
[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
So what's your opinion for the disposition? I don't mind moving this bug
to initramfs-tools, but without having a way to identify the 3-netdev
master interface in netplan yaml config, thing still don't work there.
I'm not in a position to tell if it's possible for initramfs-tools to
remove the "match by mac" in the /run/netplan/.yaml config
file.
--
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/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
Status in netplan:
Triaged
Status in netplan.io package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Incomplete
Bug description:
This bug is a follow-up to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268
after applying the 0001-net_failover-delay-taking-over-primary-device-
to-acc.patch attached in that bug, the VF interface "eth0" is renamed
to "rename4" instead of "ens4". Log is showing that attempt to rename
"eth0" to "ens3" failed because of conflict with existing name, so
that's why it ends up with rename4.
vsbalakr@ubuntu-18:~$ uname -a
Linux ubuntu-18 4.15.0-1009-oracle #11+lp1815268 SMP Tue Mar 12 15:20:15 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
vsbalakr@ubuntu-18:~$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noqueue state UP
mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd
ff:ff:ff:ff:ff:ff
3: ens3nsby: mtu 1500 qdisc pfifo_fast
master ens3 state UP mode DEFAULT group default qlen 1000 link/ether
ba:fb:9f:12:2f:02 brd ff:ff:ff:ff:ff:ff
4: rename4: mtu 1500 qdisc mq master ens3
state UP mode DEFAULT group default qlen 1000 link/ether ba:fb:9f:12:2f:02 brd
ff:ff:ff:ff:ff:ff
vsbalakr@ubuntu-18:~$ egrep -i '(rename4|busy)' /var/log/syslog
...
Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]: [1552932112.9591]
device (rename4): carrier: link connected
Mar 18 11:01:52 ubuntu-18 NetworkManager[1294]: [1552932112.9591]
device (rename4): enslaved to non-master-type device ens3; ignoring
Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: error changing net interface
name 'eth0' to 'ens3': Device or resource busy
Mar 18 11:01:53 ubuntu-18 systemd-udevd[2463]: could not rename interface '4'
from 'eth0' to 'ens3': Device or resource busy
Within VM there's netplan config as below:
vsbalakr@ubuntu-18:~$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: yes
gateway4: 10.211.8.1
nameservers:
addresses: [10.211.11.1,10.209.76.197]
By running udevadm test, we can see the conflicting ens3 name comes
from netplan's /run/udev/rules.d/99-netplan-ens3.rules
vsbalakr@ubuntu-18:~$ cat /run/udev/rules.d/99-netplan-ens3.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"
vsbalakr@ubuntu-18:/lib/udev/rules.d$ udevadm test --action="add"
/sys/class/net/eth0
calling: test
version 237
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
Load module index
Parsed configuration file /lib/systemd/network/99-default.link
Parsed configuration file /run/systemd/network/10-netplan-ens3.link
Created link configuration context.
Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
..
Reading rules file: /lib/udev/rules.d/99-vmware-scsi-udev.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 38638 bytes strings
25317 strings (216160 bytes), 21957 de-duplicated (180883 bytes), 3361 trie
nodes used
RUN '/lib/open-iscsi/net-interface-handler start'
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
IMPORT builtin 'hwdb' /lib/udev/rules.d/75-net-description.rules:12
RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
IMPORT builtin 'path_id' /lib/udev/rules.d/80-net-setup-link.rules:5
IMPORT builtin 'net_setup_link' /lib/udev/rules.d/80-net-setup-link.rules:9
Config file /lib/systemd/network/99-default.link applies to device eth0
link_config: autonegotiation is unset or enabled, the speed and duplex are
not writable.
link_config: could not set ethtool features for eth0
Could not set offload features of eth0: Operation not permitted
NAME 'ens4' /lib/udev/rules.d/80-net-setup-link.rules:11
NAME 'ens3' /run/udev/rules.d/99-netplan-ens3.rules:1
RUN '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name
[Touch-packages] [Bug 1821822] Re: Temporary failure in name resolution in Python 3.7.2
** Description changed:
My Python application works in 18.10 fine, but when upgrading to 19.10
for development reasons the same script produces the errors reported
below. I have checked on the Python bug tracker and there are no related
bug reports.
Traceback (most recent call last):
- File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
- encode_chunked=req.has_header('Transfer-encoding'))
- File "/usr/lib/python3.7/http/client.py", line 1229, in request
- self._send_request(method, url, body, headers, encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
- self.endheaders(body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
- self._send_output(message_body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
- self.send(msg)
- File "/usr/lib/python3.7/http/client.py", line 956, in send
- self.connect()
- File "/usr/lib/python3.7/http/client.py", line 1384, in connect
- super().connect()
- File "/usr/lib/python3.7/http/client.py", line 928, in connect
- (self.host,self.port), self.timeout, self.source_address)
- File "/usr/lib/python3.7/socket.py", line 707, in create_connection
- for res in getaddrinfo(host, port, 0, SOCK_STREAM):
- File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
- for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
+ File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
+ encode_chunked=req.has_header('Transfer-encoding'))
+ File "/usr/lib/python3.7/http/client.py", line 1229, in request
+ self._send_request(method, url, body, headers, encode_chunked)
+ File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
+ self.endheaders(body, encode_chunked=encode_chunked)
+ File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
+ self._send_output(message_body, encode_chunked=encode_chunked)
+ File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
+ self.send(msg)
+ File "/usr/lib/python3.7/http/client.py", line 956, in send
+ self.connect()
+ File "/usr/lib/python3.7/http/client.py", line 1384, in connect
+ super().connect()
+ File "/usr/lib/python3.7/http/client.py", line 928, in connect
+ (self.host,self.port), self.timeout, self.source_address)
+ File "/usr/lib/python3.7/socket.py", line 707, in create_connection
+ for res in getaddrinfo(host, port, 0, SOCK_STREAM):
+ File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
+ for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
- File "/usr/lib/pihole-panel/main.py", line 312, in
- win = GridWindow()
- File "/usr/lib/pihole-panel/main.py", line 37, in __init__
- self.updates_frame = self.draw_updates_frame()
- File "/usr/lib/pihole-panel/main.py", line 132, in draw_updates_frame
- if self.version_check() == True:
- File "/usr/lib/pihole-panel/main.py", line 53, in version_check
- get_version = urlopen('https://urlchanged.com').read()
- File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
- return opener.open(url, data, timeout)
- File "/usr/lib/python3.7/urllib/request.py", line 525, in open
- response = self._open(req, data)
- File "/usr/lib/python3.7/urllib/request.py", line 543, in _open
- '_open', req)
- File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
- result = func(*args)
- File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open
- context=self._context, check_hostname=self._check_hostname)
- File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open
- raise URLError(err)
+ File "/usr/lib/myapp/main.py", line 312, in
+ win = GridWindow()
+ File "/usr/lib/myapp/main.py", line 37, in __init__
+ self.updates_frame = self.draw_updates_frame()
+ File "/usr/lib/myapp/main.py", line 132, in draw_updates_frame
+ if self.version_check() == True:
+ File "/usr/lib/myapp/main.py", line 53, in version_check
+ get_version = urlopen('https://urlchanged.com').read()
+ File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
+ return opener.open(url, data, timeout)
+ File "/usr/lib/python3.7/urllib/request.py", line 525, in open
+ response = self._open(req, data)
+ File "/usr/lib/python3.7/urllib/request.py", line 543, in _open
+ '_open', req)
+ File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
+ result = func(*args)
+ File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open
+ context=self._context, check_hostname=self._check_hostname)
+ File "/usr/lib/python3.7/urllib/request
[Touch-packages] [Bug 1689582] Re: Mouse pointer shows trail
Bug seems not to be reproduced in Ubuntu 18.10. -- 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/1689582 Title: Mouse pointer shows trail Status in xorg package in Ubuntu: Won't Fix Bug description: This bug occurs in my case in Ubuntu Gnome 16.10 and 17.04 with Xorg. No artifacts in 16.04.2. Using Intel i915 driver and Intel J3710 processor (ASRock J3710-ITX). Dual monitor setting. Phenomenon occurs after executing programs with high memory usage. I was not able to reproduce it with Gnome Wayland. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 9 17:31:19 2017 DistUpgraded: 2017-04-21 23:26:05,151 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Uitvoeren van dochterproces ‘./xorg_fix_proprietary.py’ is mislukt (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1] InstallationDate: Installed on 2017-04-21 (17 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=43d43e4c-38c7-4c32-bcfe-d89ab33ccf3f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-04-21 (17 days ago) dmi.bios.date: 03/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: J3710-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ3710-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1689582/+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 294830] Re: latest pcscd causes crash of firefox
... [New Thread 0x7fffe18ff700 (LWP 5650)] *** buffer overflow detected ***: /usr/lib/firefox/firefox terminated Thread 411 "SSL Cert #32" received signal SIGABRT, Aborted. [Switching to Thread 0x7fffd35be700 (LWP 5576)] 0x779d2fb7 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) backtrace #0 0x779d2fb7 in raise () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x779b4535 in abort () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x77a1b7b6 in () at /lib/x86_64-linux-gnu/libc.so.6 #3 0x77abe76f in () at /lib/x86_64-linux-gnu/libc.so.6 #4 0x77abe791 in () at /lib/x86_64-linux-gnu/libc.so.6 #5 0x77abd0c0 in () at /lib/x86_64-linux-gnu/libc.so.6 #6 0x77abe677 in () at /lib/x86_64-linux-gnu/libc.so.6 #7 0x7fffe2e3cb06 in () at /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 #8 0x7fffe2e3cc56 in () at /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 #9 0x7fffe2e3a405 in SCardEstablishContext () at /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 #10 0x7fffdea43729 in CPCSCDeviceManager::getDevices() () at /usr/local/AWP/lib/libOcsCryptoki.so #11 0x7fffdea24bde in CVirtualSlotManager::getSlots(bool, int&, unsigned long*) () at /usr/local/AWP/lib/libOcsCryptoki.so #12 0x7fffdea154b2 in CCryptoki::getSlotList(unsigned char, unsigned long*, unsigned long*) () at /usr/local/AWP/lib/libOcsCryptoki.so #13 0x7fffdea23570 in C_GetSlotList () at /usr/local/AWP/lib/libOcsCryptoki.so #14 0x7fffdeefcf05 in C_GetSlotList () at /usr/local/AWP/lib/libOcsPKCS11Wrapper.so #15 0x7756913c in SECMOD_UpdateSlotList () at /usr/lib/firefox/libnss3.so #16 0x7154ab5b in () at /usr/lib/firefox/libxul.so #17 0x7fffee39c9c0 in () at /usr/lib/firefox/libxul.so #18 0x7fffee39e3f9 in () at /usr/lib/firefox/libxul.so #19 0x7152cd7d in () at /usr/lib/firefox/libxul.so #20 0x7152ed9c in () at /usr/lib/firefox/libxul.so #21 0x7fffee43a07f in () at /usr/lib/firefox/libxul.so #22 0x7fffee438a7e in () at /usr/lib/firefox/libxul.so #23 0x7fffee43acc8 in () at /usr/lib/firefox/libxul.so #24 0x7fffee89daaa in () at /usr/lib/firefox/libxul.so #25 0x7fffee872205 in () at /usr/lib/firefox/libxul.so #26 0x7fffee43af71 in () at /usr/lib/firefox/libxul.so #27 0x775eb984 in () at /usr/lib/firefox/libnspr4.so #28 0x77d84182 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #29 0x77aacfaf in clone () at /lib/x86_64-linux-gnu/libc.so.6 (gdb) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: latest pcscd causes crash of firefox Status in pcsc-lite package in Ubuntu: Confirmed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
The fix (workaround) for this bug in bionic and cosmic was to add 'options edns0' to the /etc/resolv.conf file via the systemd stub- resolv.conf file. However, when the resolvconf package is installed, due to bug 1817903, the 'options edns0' is stripped out of the /etc/resolv.conf file. This means anyone on bionic or cosmic that has the resolvconf package installed will not have 'options edns0' in their /etc/resolv.conf file, and will again experience this bug. In disco, systemd-resolved has DNS TCP pipelining correctly implemented, so this bug will not affect disco, regardless of whether edns0 is specified in /etc/resolv.conf. -- 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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection,
[Touch-packages] [Bug 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command
** Branch linked: lp:~brian-murray/apport/whoopsie-upload-more -- 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/1820132 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@162:collect_info:process_report:add_gdb_info:gdb_command Status in apport package in Ubuntu: Triaged Status in apport source package in Disco: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu23, the problem page at https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1820132/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
ubuntu@lp1817903-c:~$ dpkg -l |grep resolvconf ii resolvconf 1.79ubuntu10.18.10.2 all name server information handler ubuntu@lp1817903-c:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 search lxd ubuntu@lp1817903-c:~$ dpkg -l |grep resolvconf ii resolvconf 1.79ubuntu10.18.10.3 all name server information handler ubuntu@lp1817903-c:~$ 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 127.0.0.53 search lxd ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in resolvconf source package in Trusty: Invalid Status in systemd source package in Trusty: Invalid Status in resolvconf source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in resolvconf source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Status in resolvconf source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Invalid Status in resolvconf source package in Disco: Fix Released Status in systemd source package in Disco: Invalid Bug description: [impact] systems upgraded from pre-Bionic releases to Bionic or later will continue to use ifupdown/resolvconf for network conf and management, but resolvconf has a new systemd service in Bionic and later that pulls systemd-resolved stub-resolv.conf into its local configuration. With the recent addition of edns0 option to the stub resolver conf in systemd to fix bug 1811471, this means resolvconf now sets up the /etc/resolv.conf file to include upstream servers but also use edns. For any systems where the upstream resolver(s) don't support edns, dns lookups will break. [test case] == upgrade from pre-bionic (e.g. xenial) to bionic or later == 1) create a xenial system with ifupdown/resolvconf. The ifupdown config needs to include an upstream name server (must be static). At this point, once the network is configured and up, the resolvconf should have put the upstream name server(s) and search domain into the /etc/resolv.conf. As is usual for pre-systemd releases, there should be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should not be included) at this point. 2) upgrade the system to bionic (alternately it should be possible to install bionic, then remove netplan and install/configure ifupdown and resolvconf, but I have not specifically tested this). The upgrade will retain the ifupdown/resolvconf configuration, and will not change to netplan/systemd-networkd. After upgrade is finished, the /etc/resolv.conf will contain: a) the upstream name server(s) b) options edns0 c) the local stub resolver (127.0.0.53) d) search domain the fixed resolvconf will remove (b). As mentioned, this case also should cover the situation of a native Bionic install, where netplan is removed and ifupdown/resolvconf is manually installed. == bionic or later install == with a bionic install, ifupdown is not installed, instead netplan /systemd-networkd handle networking. In this case, systemd-networkd manages the /etc/resolv.conf, and symlinks it to networkd's stub- resolv.conf which always contains only the local stub resolver (127.0.0.53) and (recently) options edns0, and local search domain. If resolvconf is installed while systemd-networkd is managing the network, then currently the resolv.conf contents will remain completely unchanged, still pointing to the local stub resolver. This resolvconf change will alter that, to remove 'options edns0'. No
Re: [Touch-packages] [Bug 1822370] Re: 19.04 beta openssh-client broken pipe
Running the echo command on those hosts gives me: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 Protocol mismatch. I can ping those hosts If I use the linux version of putty on the system I can ssh into those hosts Not seeing anything related in dmesg On 3/29/19 2:33 PM, Seth Arnold wrote: > Hello, > > Are there any messages in dmesg that look related? Can you ping those > hosts? Do you get ssh banners if you run: > > echo "" | nc x.x.x.x 22 > > ? > > Thanks > -- 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/1822370 Title: 19.04 beta openssh-client broken pipe Status in openssh package in Ubuntu: New Bug description: Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1822370] Re: 19.04 beta openssh-client broken pipe
Hello, Are there any messages in dmesg that look related? Can you ping those hosts? Do you get ssh banners if you run: echo "" | nc x.x.x.x 22 ? Thanks -- 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/1822370 Title: 19.04 beta openssh-client broken pipe Status in openssh package in Ubuntu: New Bug description: Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Changed in: gnome-control-center Status: New => Fix Released -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: Fix Released Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 294830] Re: latest pcscd causes crash of firefox
Had same problem, constant firefox crashes. Crashed thread had always same pattern: libOcsCryptoki.so -> libpcsclite.so.1.0.0 -> libc-2.29.so -> crash Managed to get rid of firefox crashes by replacing: pcscd 1.8.24-1 libpcsclite1 1.8.24-1 versions with debian: pcscd 1.8.25-1 https://packages.debian.org/sid/pcscd libpcsclite1 1.8.25-1 https://packages.debian.org/sid/libpcsclite1 I suggest updating ubuntu package versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: latest pcscd causes crash of firefox Status in pcsc-lite package in Ubuntu: Confirmed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+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 1822370] [NEW] 19.04 beta openssh-client broken pipe
Public bug reported: Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1822370 Title: 19.04 beta openssh-client broken pipe Status in openssh package in Ubuntu: New Bug description: Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 294830] Re: latest pcscd causes crash of firefox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsc-lite (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: latest pcscd causes crash of firefox Status in pcsc-lite package in Ubuntu: Confirmed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+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 1795857] Re: enable CONFIG_DRM_BOCHS
What was the host system (ie: what version of qemu)? I want to be sure this works going back as far as we support (so, trusty hosts). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package
** Description changed: - The newly added wsl seed includes the packages to be installed by - default on Ubuntu running in the Windows Subsystem for Linux. In - addition to the packages in ubuntu-minimal the added ubuntu-wsl - metapackage depends on on utilities useful only in the WSL environment. + [Impact] + * The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. - Please consider accepting this new binary package to Disco, because it - needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage - will allow adding new packages for WSL installations only when more - integration utilities become available. + [Test Case] + * The package is a new metapackage, just try installing it + + [Fix] + * The change add the new package and also adds the wsl seed to watch. + + [Regression potential] + * Nothing, it is a new meta package, with no breaks, etc. + + [Other Info] + * Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE][SRU] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: [Impact] * The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. [Test Case] * The package is a new metapackage, just try installing it [Fix] * The change add the new package and also adds the wsl seed to watch. [Regression potential] * Nothing, it is a new meta package, with no breaks, etc. [Other Info] * Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
root, version 1:7.6p1-4ubuntu0.1 was published to the archive on November 6th 2018: https://launchpad.net/ubuntu/+source/openssh/1:7.6p1-4ubuntu0.1 https://lists.ubuntu.com/archives/bionic-changes/2018-November/017000.html https://usn.ubuntu.com/3809-1/ A default configuration of Ubuntu 18.04 LTS with unattended-upgrades installed would have received this update within the next 36 hours or so. If you installed before November 6th, then you probably received the update November 6th or 7th. If you installed after November 6th, then you probably received the update during installation. You can check /var/log/dpkg.log* files to find the exact date and time you received the update. Thanks -- 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/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Fix Released Status in openssh source package in Xenial: Fix Released Status in openssh source package in Bionic: Fix Released Status in openssh source package in Cosmic: Fix Released Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1822335] Re: test general
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1822335 Title: test general Status in xorg package in Ubuntu: New Bug description: test general. thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 29 15:34:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-03-09 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2349IP5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=29ebe1d0-5356-4a16-ac13-b48aa7be1b2e ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349IP5 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET91WW(2.51):bd01/09/2013:svnLENOVO:pn2349IP5:pvrThinkPadT430:rvnLENOVO:rn2349IP5:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349IP5 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Fri Mar 22 09:18:08 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822335/+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 1795857] Re: enable CONFIG_DRM_BOCHS
I have tested that the module loads and works fine on POWER, on a KVM guest on top of a Power8 system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1821863] Re: Need to add Intel CML related pci-id's
This bug was fixed in the package libdrm - 2.4.97-1ubuntu1 --- libdrm (2.4.97-1ubuntu1) disco; urgency=medium * sync-i915-pciids.diff: Sync pci-ids with the kernel. (LP: #1821863) -- Timo Aaltonen Fri, 29 Mar 2019 11:21:10 +0200 ** Changed in: libdrm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New 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: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1822314] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1822313 *** https://bugs.launchpad.net/bugs/1822313 ** This bug has been marked a duplicate of bug 1822313 PCI/internal sound card not detected -- 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/1822314 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822314/+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 1822315] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1822313 *** https://bugs.launchpad.net/bugs/1822313 ** This bug has been marked a duplicate of bug 1822313 PCI/internal sound card not detected -- 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/1822315 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822315/+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 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
Still a problem for Ubuntu MATE 19.04 beta2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in mate-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+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 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat
If I remember correctly David was having a similar issue when upgrading some charm systems. Is that right David? ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat Status in apt package in Ubuntu: New Bug description: I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1
This bug was fixed in the package xserver-xorg-video-ati - 1:19.0.1-0ubuntu1 --- xserver-xorg-video-ati (1:19.0.1-0ubuntu1) disco; urgency=medium * Sync with debian git. xserver-xorg-video-ati (1:19.0.1-1) UNRELEASED; urgency=medium * New bugfix release. (Closes: #924540) (LP: #1822075) -- Timo Aaltonen Thu, 28 Mar 2019 13:15:14 +0200 ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1822075 Title: tooltips and combo boxes in webbrowsers are all garbage in xserver- xorg-video-radeon 1:19.0.0-1 Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: Disco up to date With Chrome and Firefox tooltips and combo boxes are all garbage and make the browser unusable. Cf screenshots. Graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] I tried gtk2 and gtk3 demos and the combo boxes are broken in the same way. I also tried FF as a snap and as a deb and the problem is the same. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 11:51:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1717 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+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 1821904] Re: Gnome Shell always started muted on Disco
Just to confirm, I also did this upgrade path (18.04 -> 18.10 -> 19.04) on my desktop and I get the same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1821904 Title: Gnome Shell always started muted on Disco Status in pulseaudio package in Ubuntu: Incomplete Bug description: On Disco, Gnome Shell always starts muted. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe4766 F pulseaudio /dev/snd/pcmC0D0p: joe4766 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-09-15 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco wayland-session Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+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 1822341] Re: [FFE] Please add ubuntu-wsl binary package
Build log: $ dpkg-buildpackage dpkg-buildpackage: info: source package ubuntu-meta dpkg-buildpackage: info: source version 1.431 dpkg-buildpackage: info: source distribution disco dpkg-buildpackage: info: source changed by Balint Reczey dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build . fakeroot debian/rules clean dh clean --with germinate dh_germinate_clean dh_clean dpkg-source -b . dpkg-source: info: using source format '3.0 (native)' dpkg-source: info: building ubuntu-meta in ubuntu-meta_1.431.tar.xz dpkg-source: info: building ubuntu-meta in ubuntu-meta_1.431.dsc debian/rules build dh build --with germinate dh_update_autotools_config dh_autoreconf create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary --with germinate dh_testroot dh_prep dh_installdocs dh_installchangelogs dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_strip dh_makeshlibs dh_shlibdeps dh_germinate_metapackage dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'ubuntu-minimal' in '../ubuntu-minimal_1.431_amd64.deb'. dpkg-deb: building package 'ubuntu-server' in '../ubuntu-server_1.431_amd64.deb'. dpkg-deb: building package 'ubuntu-desktop-minimal' in '../ubuntu-desktop-minimal_1.431_amd64.deb'. dpkg-deb: building package 'ubuntu-standard' in '../ubuntu-standard_1.431_amd64.deb'. dpkg-deb: building package 'ubuntu-wsl' in '../ubuntu-wsl_1.431_amd64.deb'. dpkg-deb: building package 'ubuntu-desktop' in '../ubuntu-desktop_1.431_amd64.deb'. Install log: $ sudo apt install ../ubuntu-wsl_1.431_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'ubuntu-wsl' instead of '../ubuntu-wsl_1.431_amd64.deb' The following additional packages will be installed: wslu The following NEW packages will be installed: ubuntu-wsl wslu 0 upgraded, 2 newly installed, 0 to remove and 62 not upgraded. Need to get 42.2 kB/87.1 kB of archives. After this operation, 258 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 /home/rbalint/ubuntu-wsl_1.431_amd64.deb ubuntu-wsl amd64 1.431 [44.9 kB] Get:2 http://at.archive.ubuntu.com/ubuntu disco/main amd64 wslu all 2.0.0-0ubuntu2 [42.2 kB] Fetched 42.2 kB in 0s (174 kB/s) Selecting previously unselected package wslu. (Reading database ... 242784 files and directories currently installed.) Preparing to unpack .../wslu_2.0.0-0ubuntu2_all.deb ... Unpacking wslu (2.0.0-0ubuntu2) ... Selecting previously unselected package ubuntu-wsl. Preparing to unpack .../ubuntu-wsl_1.431_amd64.deb ... Unpacking ubuntu-wsl (1.431) ... Setting up wslu (2.0.0-0ubuntu2) ... Setting up ubuntu-wsl (1.431) ... Processing triggers for man-db (2.8.5-2) ... The binary package is new and does not break any other package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE][SRU] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1822341] Re: [FFE] Please add ubuntu-wsl binary package
Also there is an open MR for the seed update: https://code.launchpad.net/~rbalint/ubuntu- seeds/+git/ubuntu/+merge/365253 ** Summary changed: - [FFE] Please add ubuntu-wsl binary package + [FFE][SRU] Please add ubuntu-wsl binary package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE][SRU] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1822341] Re: [FFE] Please add ubuntu-wsl binary package
The attached patch also include updates from the current seed, and was artificially crafted because until ubuntu-meta package does not exist in the archive germinate does not pick it from the seed, hence does not include the packages contained through the minimal seed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1822341] Re: [FFE] Please add ubuntu-wsl binary package
** Patch added: "ubuntu-meta_1.431.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+attachment/5250676/+files/ubuntu-meta_1.431.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1795857] Re: enable CONFIG_DRM_BOCHS
I'm rejecting the kmod upload in the disco queue until the above comment is addressed, so we don't get into a revert war. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1795857] Re: enable CONFIG_DRM_BOCHS
The original bug report was on PowerKVM (ppc64el qemu). In testing that it was okay to revert this wholesale in both kmod and kernel, did anyone test POWER? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1822118] Re: Kernel Panic while rebooting cloud instance
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1822270] Re: Debconf readline frontend does not show options
** Changed in: debconf (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: New Bug description: AFFECTED RELEASE: Bionic PACKAGE VERSION: debconf - 1.5.66 DESCRIPTION: When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1822341] [NEW] [FFE] Please add ubuntu-wsl binary package
Public bug reported: The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1795857] Re: enable CONFIG_DRM_BOCHS
I've send a patch for the kernel part of this request: https://lists.ubuntu.com/archives/kernel-team/2019-March/099704.html Additionally to it the kmod's "blacklist bochs-drm" entry from it's /etc/modprobe.d/blacklist-framebuffer.conf file it ships would need to get removed. With this I can successfully start VMs wit stdvga as display under QEMU and/or QEMU/KVM again. Without this it's completely broken, but note that the installation itself works, you'll only see the issues after you boot in the fresh installed system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
The fix works as expected in B/C: #COSMIC ubuntu@c-ufw:~$ dpkg -l | grep ufw ii ufw 0.36-0ubuntu0.18.10.1 all program for managing a Netfilter firewall ubuntu@c-ufw:~$ sudo ufw status numbered Status: active To Action From -- -- [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 ubuntu@c-ufw:~$ sudo ufw prepend deny from 6.7.8.9 Rule inserted ubuntu@c-ufw:~$ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1 Rule inserted (v6) ubuntu@c-ufw:~$ sudo ufw status numbered Status: active To Action From -- -- [ 1] Anywhere DENY IN 6.7.8.9 [ 2] 22/tcp ALLOW INAnywhere [ 3] Anywhere ALLOW IN1.2.3.4 [ 4] Anywhere (v6) DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1 [ 5] 22/tcp (v6)ALLOW INAnywhere (v6) [ 6] Anywhere (v6) ALLOW IN2001:db8::/32 #BIONIC ubuntu@b-ufw:~$ dpkg -l | grep ufw ii ufw 0.36-0ubuntu0.18.04.1 all program for managing a Netfilter firewall ubuntu@b-ufw:~$ sudo ufw status numbered Status: active To Action From -- -- [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 ubuntu@b-ufw:~$ sudo ufw prepend allow from 2001:db8::/32 Skipping inserting existing rule (v6) ubuntu@b-ufw:~$ sudo ufw status numbered Status: active To Action From -- -- [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 ubuntu@b-ufw:~$ sudo ufw prepend deny from 6.7.8.9 Rule inserted ubuntu@b-ufw:~$ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1 Rule inserted (v6) ubuntu@b-ufw:~$ sudo ufw status numbered Status: active To Action From -- -- [ 1] Anywhere DENY IN 6.7.8.9 [ 2] 22/tcp ALLOW INAnywhere [ 3] Anywhere ALLOW IN1.2.3.4 [ 4] Anywhere (v6) DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1 [ 5] 22/tcp (v6)ALLOW INAnywhere (v6) [ 6] Anywhere (v6) ALLOW IN2001:db8::/32 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw's 'insert' command is designed to work with 'ufw status numbered' to insert rules in specific places in the ruleset. This makes it more difficult than it should be for using ufw as part of an IPS/dynamic firewall (eg, fail2ban) since if the firewall already has an IPv4 rule then the user/IPS must calculate the position of an IPv6-only rule before inserting it. From the git commit: " add 'prepend' command Introduce 'prepend' command to add rules to the top of the IPv4 and/or IPv6 chains. This is particularly useful for dynamic firewalls/IPS (eg, fail2ban). Unlike 'insert', 'prepend' does not require knowledge about the IPv6 rule number so integration into IPS is much easier. " [Test Case] $ sudo ufw allow 22/tcp $ sudo ufw allow from 1.2.3.4 $ sudo ufw allow from 2001:db8::/32 $ sudo ufw enable $ sudo ufw status numbered ... [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 # unchanged from 0.35 $ sudo ufw insert 1 deny
[Touch-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) 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/1778566 Title: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When Wayland is activated in GDM, nothing happens when selecting an account with the keyboard or typing in the password. I have to type, then wait, then move the mouse around for the characters to appears. Because I wouldn't believe this report, I made a video of the problem: https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf- f2a74f952ca5 Moving from Wayland to X makes the issue disappear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 18:39:19 2018 InstallationDate: Installed on 2018-06-17 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+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 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1778566 Title: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When Wayland is activated in GDM, nothing happens when selecting an account with the keyboard or typing in the password. I have to type, then wait, then move the mouse around for the characters to appears. Because I wouldn't believe this report, I made a video of the problem: https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf- f2a74f952ca5 Moving from Wayland to X makes the issue disappear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 18:39:19 2018 InstallationDate: Installed on 2018-06-17 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+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 1759014] Re: Netplan has no way to control DHCP client
Verified using netplan.io 0.96-0ubuntu0.18.04.2 and systemd
237-3ubuntu10.15 with
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
match:
macaddress: fa:16:3e:28:d1:28
set-name: ens3
ens4:
dhcp4: true
dhcp4-overrides:
use-routes: false
use-dns: false
route-metric:
match:
macaddress: fa:16:3e:d7:41:1b
set-name: ens4
Resulting DNS and routes configured as expected, but interface ens4
remains in state 'configuring' due to known issue of systemd v237.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in netplan.io source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Confirmed
Status in netplan.io source package in Cosmic:
Fix Committed
Status in systemd source package in Cosmic:
Confirmed
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Confirmed
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1759014] Re: Netplan has no way to control DHCP client
Verified using netplan.io 0.96-0ubuntu0.18.10.2 and systemd
239-7ubuntu10.10 with
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
match:
macaddress: fa:16:3e:34:e2:ff
set-name: ens3
ens4:
dhcp4: true
dhcp4-overrides:
use-routes: false
use-dns: false
route-metric:
match:
macaddress: fa:16:3e:cd:a4:90
set-name: ens4
Resulting DNS and routes configured as expected.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in netplan.io source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Confirmed
Status in netplan.io source package in Cosmic:
Fix Committed
Status in systemd source package in Cosmic:
Confirmed
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Confirmed
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1759014] Re: Netplan has no way to control DHCP client
Short installation instructions for the netplan.io 0.96 package on
Ubuntu 18.04:
sudo echo "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted
main multiverse universe" > /etc/apt/sources.list.d/proposed-updates.list
sudo apt update
sudo apt-get install -y netplan.io/bionic-proposed
sudo rm /etc/apt/sources.list.d/proposed-updates.list
sudo apt update
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in netplan.io source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Confirmed
Status in netplan.io source package in Cosmic:
Fix Committed
Status in systemd source package in Cosmic:
Confirmed
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Confirmed
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1530807] Re: Bluetooth cannot be activated on several devices
** Summary changed: - Can you buy Ambien without a script in Miami? + Bluetooth cannot be activated on several devices ** Description changed: Using RC proposed 04/01/2016 bluetooth cannot be enabled. - - https://usapillspharma.com Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Fix Committed Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Fix Committed Status in indicator-bluetooth package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1822313] [NEW] PCI/internal sound card not detected
Public bug reported: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** 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/1822313 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822313/+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 1822314] [NEW] PCI/internal sound card not detected
Public bug reported: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** 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/1822314 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822314/+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 1822315] [NEW] PCI/internal sound card not detected
Public bug reported: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** 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/1822315 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: my sound system is not working I did the basic troubleshooting list at https://help.ubuntu.com/community/SoundTroubleshooting and my sound system is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 13:40:15 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822315/+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 1530807] Re: Can you buy Ambien without a script in Miami?
** Summary changed: - Bluetooth cannot be activated on several devices + Can you buy Ambien without a script in Miami? ** Description changed: Using RC proposed 04/01/2016 bluetooth cannot be enabled. + + https://usapillspharma.com Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list - Experienced behavior: + Experienced behavior: Bluetooth slider is moved to on - Activity spinners appear + Activity spinners appear Bluetooth slider moves to off. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Can you buy Ambien without a script in Miami? Status in The Avila project: Fix Committed Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Fix Committed Status in indicator-bluetooth package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. https://usapillspharma.com Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+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 1330770] Re: click packages rely upon tls for integrity and authenticity
** Summary changed: - Indications of Anxiety Disorder and Depression + click packages rely upon tls for integrity and authenticity ** Description changed: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. - - https://usapillspharma.com/ Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at-rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update servers -- packages in flight within our network can be corrupted for many reasons, packages on disk can be corrupted for many reasons. A signature mechanism can protect against internal network faults, storage faults, and provide assurance months or years later that an uploaded package was uploaded by someone in control of a corresponding private key. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1330770 Title: click packages rely upon tls for integrity and authenticity Status in Canonical System Image: Fix Released Status in Click Package Index: Fix Released Status in Software Center Agent: Fix Released Status in click package in Ubuntu: Fix Released Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu: Fix Released Status in ubuntu-download-manager source package in Vivid: New Bug description: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at- rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update ser
[Touch-packages] [Bug 1822270] Re: Debconf readline frontend does not show options
** Tags added: id-5c919ca2a4ae741f19d59ad9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: New Bug description: AFFECTED RELEASE: Bionic PACKAGE VERSION: debconf - 1.5.66 DESCRIPTION: When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
** Summary changed: - Buy Tramadol Online and Familiarize Yourself with Pain Medication + After release upgrade, the user loses permissions for several basic actions in the system ** Description changed: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. - - https://usapillspharma.com/ RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+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 1099184] Re: Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback
** Summary changed: - Buy Utram Online No Prescription | Tramadol For Joint Pain + Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback ** Description changed: lsb_release -rd - Description:Ubuntu 12.04.1 LTS - Release:12.04 + Description: Ubuntu 12.04.1 LTS + Release: 12.04 - avahi-daemon 0.6.30-5ubuntu2 cups 1.5.3-0ubuntu6 - Avahi for default publishes services also in IPv6 as in /etc/avahi/avahi-daemon.conf there is + Avahi for default publishes services also in IPv6 as in /etc/avahi/avahi-daemon.conf there is use-ipv6=yes At the same time services are listening on IPv4 addresses only. Cups is able to discover published printers via dnssd protocol but its ipp backend prints only on the IPv6 resolved address which does not answer and it does not try the IPv4 address. - Excerpt from "avahi-browse -a -t -r" to show the IPv6 and IPv4 addresses + Excerpt from "avahi-browse -a -t -r" to show the IPv6 and IPv4 addresses - + wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local - + wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local - + wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d] Workstation local - + wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation local + + wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local + + wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local + + wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d] Workstation local + + wlan0 IPv6 hjemme [00:40:f4:ff:55:32] Workstation local [] - = wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local - hostname = [hjemme.local] - address = [fe80::240:f4ff:feff:5532] - port = [631] - txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=https://rxsecureweb.com/"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] - = wlan0 IPv6 hjemmeRemote Disk Management local - hostname = [hjemme.local] - address = [fe80::240:f4ff:feff:5532] - port = [22] - txt = [] - = wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation local - hostname = [hjemme.local] - address = [fe80::240:f4ff:feff:5532] - port = [9] - txt = [] - = wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local - hostname = [hjemme.local] - address = [192.168.1.2] - port = [631] - txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=https://rxsecureweb.com/"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] + = wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local +hostname = [hjemme.local] +address = [fe80::240:f4ff:feff:5532] +port = [631] +txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] + = wlan0 IPv6 hjemme Remote Disk Management local +hostname = [hjemme.local] +address = [fe80::240:f4ff:feff:5532] +port = [22] +txt = [] + = wlan0 IPv6 hjemme [00:40:f4:ff:55:32] Workstation local +hostname = [hjemme.local] +address = [fe80::240:f4ff:feff:5532] +port = [9] +txt = [] + = wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local +hostname = [hjemme.local] +address = [192.168.1.2] +port = [631] +txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copi
[Touch-packages] [Bug 1330770] Re: Indications of Anxiety Disorder and Depression
** Summary changed: - click packages rely upon tls for integrity and authenticity + Indications of Anxiety Disorder and Depression ** Description changed: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. + + https://usapillspharma.com/ Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at-rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update servers -- packages in flight within our network can be corrupted for many reasons, packages on disk can be corrupted for many reasons. A signature mechanism can protect against internal network faults, storage faults, and provide assurance months or years later that an uploaded package was uploaded by someone in control of a corresponding private key. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1330770 Title: Indications of Anxiety Disorder and Depression Status in Canonical System Image: Fix Released Status in Click Package Index: Fix Released Status in Software Center Agent: Fix Released Status in click package in Ubuntu: Fix Released Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu: Fix Released Status in ubuntu-download-manager source package in Vivid: New Bug description: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. https://usapillspharma.com/ Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at- rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages t
[Touch-packages] [Bug 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks
** Description changed: Install Kubuntu Feisty Set the ip address to dhcp for eth0 (ethernet port) make sure the host name and domain name are set Hostname computer1 DomainName mydomain.local allow DHCP to assign the IP address Ensure the computer details are registered in DNS for mydomain.local... - computer names registered in DNS (FQDN) + computer names registered in DNS (FQDN) computer1.mydomain.local computer2.mydomain.local computer3.mydomain.local computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP. if I issue the following comands on computer2 or computer3, it works correctly: ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (response received - ping good) ping computer3.mydomain.local (response received - ping good) if i issue the same commands from the feisty box (computer1), these are the results.. ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (unknown host) ping computer3.mydomain.local (unknown host) for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!) It can resolve the host name only though, and will return the fully qualified domain name in the response. cheers Rod. ** Description changed: Install Kubuntu Feisty Set the ip address to dhcp for eth0 (ethernet port) make sure the host name and domain name are set Hostname computer1 DomainName mydomain.local - + https://rxsecureweb.com allow DHCP to assign the IP address Ensure the computer details are registered in DNS for mydomain.local... computer names registered in DNS (FQDN) computer1.mydomain.local computer2.mydomain.local computer3.mydomain.local computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP. if I issue the following comands on computer2 or computer3, it works correctly: ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (response received - ping good) ping computer3.mydomain.local (response received - ping good) if i issue the same commands from the feisty box (computer1), these are the results.. ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (unknown host) ping computer3.mydomain.local (unknown host) - - for some reason if you try to ping the fully qualified domain name on - feisty, it cant resolve it, yet it can resolve it using both static IP - Addressing and DHCP addressing on Dapper. (i set the IP to static as - well for the test) Static and DHCP on Dapper works fine. Static and DHCP - wont resolve fully qualified domain names on Feisty. (computer1, - computer2 and computer 3 are all Kubuntu machines. DNS Server is a - Windows 2003 Server (that will be changed a kubuntu server very soon - though!) + https://rxsecureweb.com + for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!) It can resolve the host name only though, and will return the fully qualified domain name in the response. cheers Rod. ** Summary changed: - Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks + How Can I Buy Soma Online? | Order Carisoprodol Online -- 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/80900 Title: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks Status in avahi package in Ubuntu: Triaged Status in nss-mdns package in Ubuntu: Confirmed Status in avahi package in Debian: New Bug description: Install Kubuntu Feisty Set the ip address to dhcp for eth0 (ether
[Touch-packages] [Bug 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks
** Summary changed: - How Can I Buy Soma Online? | Order Carisoprodol Online + Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks ** Description changed: Install Kubuntu Feisty Set the ip address to dhcp for eth0 (ethernet port) make sure the host name and domain name are set Hostname computer1 DomainName mydomain.local - https://rxsecureweb.com allow DHCP to assign the IP address Ensure the computer details are registered in DNS for mydomain.local... computer names registered in DNS (FQDN) computer1.mydomain.local computer2.mydomain.local computer3.mydomain.local computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP. if I issue the following comands on computer2 or computer3, it works correctly: ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (response received - ping good) ping computer3.mydomain.local (response received - ping good) if i issue the same commands from the feisty box (computer1), these are the results.. ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (unknown host) ping computer3.mydomain.local (unknown host) - https://rxsecureweb.com for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!) It can resolve the host name only though, and will return the fully qualified domain name in the response. cheers Rod. -- 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/80900 Title: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks Status in avahi package in Ubuntu: Triaged Status in nss-mdns package in Ubuntu: Confirmed Status in avahi package in Debian: New Bug description: Install Kubuntu Feisty Set the ip address to dhcp for eth0 (ethernet port) make sure the host name and domain name are set Hostname computer1 DomainName mydomain.local allow DHCP to assign the IP address Ensure the computer details are registered in DNS for mydomain.local... computer names registered in DNS (FQDN) computer1.mydomain.local computer2.mydomain.local computer3.mydomain.local computer2 and computer3 are both running Kubuntu Dapper and are both using DHCP. if I issue the following comands on computer2 or computer3, it works correctly: ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (response received - ping good) ping computer3.mydomain.local (response received - ping good) if i issue the same commands from the feisty box (computer1), these are the results.. ping computer2 (response received - ping good) ping computer3 (response received - ping good) ping computer2.mydomain.local (unknown host) ping computer3.mydomain.local (unknown host) for some reason if you try to ping the fully qualified domain name on feisty, it cant resolve it, yet it can resolve it using both static IP Addressing and DHCP addressing on Dapper. (i set the IP to static as well for the test) Static and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu server very soon though!) It can resolve the host name only though, and will return the fully qualified domain name in the response. cheers Rod. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+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 327362] Re: Order Ambien Online to Manage Irregular Sleep-Wake Rhythm Disorder
** Summary changed: - Some ISPs have .local domain which disables avahi-daemon + Order Ambien Online to Manage Irregular Sleep-Wake Rhythm Disorder -- 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/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+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 327362] Re: Some ISPs have .local domain which disables avahi-daemon
** Summary changed: - Order Ambien Online to Manage Irregular Sleep-Wake Rhythm Disorder + Some ISPs have .local domain which disables avahi-daemon -- 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/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
This is something that is currently fixing just a build failure, not something that the end user is affected... Marking as verification done (and I'm using the package because my system is on bionic) ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1099184] Re: Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback
** Description changed: lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 - avahi-daemon 0.6.30-5ubuntu2 cups 1.5.3-0ubuntu6 - Avahi for default publishes services also in IPv6 as in /etc/avahi/avahi-daemon.conf there is use-ipv6=yes At the same time services are listening on IPv4 addresses only. Cups is able to discover published printers via dnssd protocol but its ipp backend prints only on the IPv6 resolved address which does not answer and it does not try the IPv4 address. Excerpt from "avahi-browse -a -t -r" to show the IPv6 and IPv4 addresses + wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local + wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local + wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d] Workstation local + wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation local [] = wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local -hostname = [hjemme.local] -address = [fe80::240:f4ff:feff:5532] -port = [631] -txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] + hostname = [hjemme.local] + address = [fe80::240:f4ff:feff:5532] + port = [631] + txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] = wlan0 IPv6 hjemmeRemote Disk Management local -hostname = [hjemme.local] -address = [fe80::240:f4ff:feff:5532] -port = [22] -txt = [] + hostname = [hjemme.local] + address = [fe80::240:f4ff:feff:5532] + port = [22] + txt = [] = wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation local -hostname = [hjemme.local] -address = [fe80::240:f4ff:feff:5532] -port = [9] -txt = [] + hostname = [hjemme.local] + address = [fe80::240:f4ff:feff:5532] + port = [9] + txt = [] = wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local -hostname = [hjemme.local] -address = [192.168.1.2] -port = [631] -txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] + hostname = [hjemme.local] + address = [192.168.1.2] + port = [631] + txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] Excerpt from /var/log/cups/error_log to show that only IPv6 address is tried I [13/Jan/2013:18:02:55 +0100] [Job 61] Started backend /usr/lib/cups/backend/dnssd (PID 7179) D [13/Jan/2013:18:02:55 +0100] [Job 61] Resolving "Hewlett-Packard HP LaserJet 1100 @ hjemme._ipp._tcp.local"... D [13/Jan/2013:18:02:55 +0100] [Job 61] STAT
[Touch-packages] [Bug 1240336] Re: Buy Tramadol Online and Familiarize Yourself with Pain Medication
** Summary changed: - After release upgrade, the user loses permissions for several basic actions in the system + Buy Tramadol Online and Familiarize Yourself with Pain Medication ** Description changed: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. + + https://usapillspharma.com/ RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1240336 Title: Buy Tramadol Online and Familiarize Yourself with Pain Medication Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. https://usapillspharma.com/ RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+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 1822306] [NEW] PCI/internal sound card not detected
Public bug reported: Can't open "alsamixer". Can't fix my laptop's sound. My laptop sound stoped working after upgrading Ubuntu 14.04.6 LTS. I checked Alsamixer but I could't open it. I tryed to reinstall pulse audio and Alsa but yet, Alsamixer doesn't open. I'm getting the following error message when I try to open Alsamixer: me@me-Inspiron-15-3552:~$ alsamixer cannot open mixer: No such file or directory I would appreciate some help ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 12:38:04 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** 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/1822306 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Can't open "alsamixer". Can't fix my laptop's sound. My laptop sound stoped working after upgrading Ubuntu 14.04.6 LTS. I checked Alsamixer but I could't open it. I tryed to reinstall pulse audio and Alsa but yet, Alsamixer doesn't open. I'm getting the following error message when I try to open Alsamixer: me@me-Inspiron-15-3552:~$ alsamixer cannot open mixer: No such file or directory I would appreciate some help ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-167.217-generic 3.13.11-ckt39 Uname: Linux 3.13.0-167-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 29 12:38:04 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-08-22 (948 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 01M0MH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn01M0MH:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822306/+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 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
** Summary changed: - Buy Ambien Online for Handling Short-Term Treatment of Insomnia + juju bootstrap fail behind a proxy when a gpg key must be imported ** Description changed: This is related to a Maas environment hosted behind a proxy. - - https://usapillspharma.com I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK ubuntu@zookeeper:/var/log$ echo $? 0 On the zookeeper node, python-software-properties is version 0.82.7.3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 12 14:40:21 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported Status in software-properties package in Ubuntu: Triaged Bug description: This is related to a Maas environment hosted behind a proxy. I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg'
[Touch-packages] [Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
** Description changed: This is related to a Maas environment hosted behind a proxy. + + https://usapillspharma.com I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. - - https://usapillspharma.com Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK ubuntu@zookeeper:/var/log$ echo $? 0 On the zookeeper node, python-software-properties is version 0.82.7.3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 12 14:40:21 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago) ** Summary changed: - juju bootstrap fail behind a proxy when a gpg key must be imported + Buy Ambien Online for Handling Short-Term Treatment of Insomnia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported Status in software-properties package in Ubuntu: Triaged Bug description: This is related to a Maas environment hosted behind a proxy. I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyri
[Touch-packages] [Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
** Description changed: - This is related to a Maas environment hosted behind a proxy. I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: - mymaas: - type: maas - maas-server: 'http://192.168.124.2:80/MAAS' - maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' - admin-secret: 'nothing' - default-series: precise - juju-origin: ppa + mymaas: + type: maas + maas-server: 'http://192.168.124.2:80/MAAS' + maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' + admin-secret: 'nothing' + default-series: precise + juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. + + https://usapillspharma.com Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK ubuntu@zookeeper:/var/log$ echo $? 0 On the zookeeper node, python-software-properties is version 0.82.7.3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 12 14:40:21 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: Buy Ambien Online for Handling Short-Term Treatment of Insomnia Status in software-properties package in Ubuntu: Triaged Bug description: This is related to a Maas environment hosted behind a proxy. https://usapillspharma.com I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$
[Touch-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco
Um, good question. The volume in Gnome shell top right panel, as well in Gnome settings, appears muted (and it is muted when I try to play things). All I need to do is unmute / press volume up or down to fix this, it's just a small niggle. The only extension that I have is extended-gestures. The startup applications are `Snap user application autostart helper` and `SSH Key Agent`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1821904 Title: Gnome Shell always started muted on Disco Status in pulseaudio package in Ubuntu: Incomplete Bug description: On Disco, Gnome Shell always starts muted. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe4766 F pulseaudio /dev/snd/pcmC0D0p: joe4766 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-09-15 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco wayland-session Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+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 1813587] Please test proposed package
Hello Matthias, or anyone else affected, Accepted libunistring into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libunistring/0.9.10-1ubuntu1.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libidn into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.33-2.1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: libunistring (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libidn into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.33-2.2ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: In Progress Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
@seth, apt-upgrade doesnt update even in 18.04, I had to compile new ver 7.9p1 and replace the sshd bin file..!, don't know why it is still not pushed to the main repo!. -- 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/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Fix Released Status in openssh source package in Xenial: Fix Released Status in openssh source package in Bionic: Fix Released Status in openssh source package in Cosmic: Fix Released Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option
Note: coreutils verions as shown by dpkg -l command: $ dpkg -l coreutils 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 coreutils 8.21-1ubuntu5.4 amd64 GNU core utilities -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option Status in coreutils package in Ubuntu: New Bug description: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+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 1822269] [NEW] mktemp does not handle -p option when --tmpdir option goes after -p option
Public bug reported: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option Status in coreutils package in Ubuntu: New Bug description: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+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 1822270] [NEW] Debconf readline frontend does not show options
Public bug reported: AFFECTED RELEASE: Bionic PACKAGE VERSION: debconf - 1.5.66 DESCRIPTION: When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: New Bug description: AFFECTED RELEASE: Bionic PACKAGE VERSION: debconf - 1.5.66 DESCRIPTION: When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1821863] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1821863 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New 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: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1821863] Re: Need to add Intel CML related pci-id's
** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem package in Ubuntu: New 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: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1821863] Re: Need to add Intel CML related pci-id's
leaving cosmic out, this will only be needed in disco and bionic. ** Description changed: + [Impact] + Please make it happen in the coming oem-kernel as there will be a flood - of Intel CML platforms that would need it. Thank you. + of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. + + [Test case] + + Test that i915 graphics works on CML. + + [Regression potential] + + None really, these only add a bunch of new pci-id's across the stack. ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libdrm (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xorg-server (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Description changed: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. + + CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and + doesn't need other changes than pci-id's and support for the PCH + (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem package in Ubuntu: New 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: New Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1822261] Re: Upgrade of procps disables net.ipv4.ip_forward=1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1822261 Title: Upgrade of procps disables net.ipv4.ip_forward=1 Status in procps package in Ubuntu: Confirmed Bug description: Expected behavior: Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a prompt if the original file should be overwritten. What happened: After performing an upgrade of package procps IPv4Forwarding was disabled in /etc/sysctl.conf without asking: # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 I was able to reproduce this behavior by using unattended-upgrades and also by upgrading manually (apt-get upgrade) My system: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy procps procps: Installed: 2:3.3.12-3ubuntu1.1 Candidate: 2:3.3.12-3ubuntu1.1 Version table: *** 2:3.3.12-3ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1822261/+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 1821882] Re: Screen is very dark and brightness cannot be adjusted
Is this a regression from older releases? when you say that disabling switchable graphics makes it use nvidia, I'd doubt that.. it should use intel then? ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (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/1821882 Title: Screen is very dark and brightness cannot be adjusted Status in linux package in Ubuntu: Incomplete Bug description: Device: Dell Precision 7530 In the BIOS, the Switchable Graphics option is deactived, which means only the nVidia GPU is used. When booting 19.04 beta live USB, the screen becomes very dark and brightness cannot be adjusted. (The same issue happens with 18.04.2) There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no intel_backlight): $ ll /sys/class/backlight/ total 0 drwxr-xr-x 2 root root 0 Mar 27 09:36 ./ drwxr-xr-x 74 root root 0 Mar 27 09:28 ../ lrwxrwxrwx 1 root root 0 Mar 27 09:28 nv_backlight -> ../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/ Trying to manually change brightness doesn't do anything: $ sudo su root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight root@ubuntu:/sys/class/backlight/nv_backlight# ll total 0 drwxr-xr-x 3 root root0 Mar 27 09:28 ./ drwxr-xr-x 4 root root0 Mar 27 09:28 ../ -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/ -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness drwxr-xr-x 2 root root0 Mar 27 09:28 power/ lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> ../../../../../../../../class/backlight/ -r--r--r-- 1 root root 4096 Mar 27 09:28 type -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness 50 Although the value is changed, the screen brightness doesn't change. in dmesg, I can see the following: [0.241878] ACPI: Added _OSI(Module Device) [0.241878] ACPI: Added _OSI(Processor Device) [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions) [0.241878] ACPI: Added _OSI(Processor Aggregator Device) [0.241878] ACPI: Added _OSI(Linux-Dell-Video) [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [0.286326] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.286336] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287096] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287102] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287858] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287864] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.288614] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.288619] ACPI: Skipping parse of AML
[Touch-packages] [Bug 1822261] [NEW] Upgrade of procps disables net.ipv4.ip_forward=1
Public bug reported: Expected behavior: Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a prompt if the original file should be overwritten. What happened: After performing an upgrade of package procps IPv4Forwarding was disabled in /etc/sysctl.conf without asking: # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 I was able to reproduce this behavior by using unattended-upgrades and also by upgrading manually (apt-get upgrade) My system: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy procps procps: Installed: 2:3.3.12-3ubuntu1.1 Candidate: 2:3.3.12-3ubuntu1.1 Version table: *** 2:3.3.12-3ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: procps (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: Expected behavior: Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a prompt if the original file should be overwritten. What happened: After performing an upgrade of package procps IPv4Forwarding was disabled in /etc/sysctl.conf without asking: # Uncomment the next line to enable packet forwarding for IPv4 - net.ipv4.ip_forward=1 + #net.ipv4.ip_forward=1 I was able to reproduce this behavior by using unattended-upgrades and also by upgrading manually (apt-get upgrade) My system: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy procps procps: - Installed: 2:3.3.12-3ubuntu1.1 - Candidate: 2:3.3.12-3ubuntu1.1 - Version table: - *** 2:3.3.12-3ubuntu1.1 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2:3.3.12-3ubuntu1 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 2:3.3.12-3ubuntu1.1 + Candidate: 2:3.3.12-3ubuntu1.1 + Version table: + *** 2:3.3.12-3ubuntu1.1 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2:3.3.12-3ubuntu1 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1822261 Title: Upgrade of procps disables net.ipv4.ip_forward=1 Status in procps package in Ubuntu: Confirmed Bug description: Expected behavior: Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a prompt if the original file should be overwritten. What happened: After performing an upgrade of package procps IPv4Forwarding was disabled in /etc/sysctl.conf without asking: # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 I was able to reproduce this behavior by using unattended-upgrades and also by upgrading manually (apt-get upgrade) My system: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy procps procps: Installed: 2:3.3.12-3ubuntu1.1 Candidate: 2:3.3.12-3ubuntu1.1 Version table: *** 2:3.3.12-3ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1822261/+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 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
Yes, I just removed the mouse under gnome-control-center, went into `bluetoothctl` and tried to pair it again: [bluetooth]# scan on Discovery started [NEW] Device 49:4E:A7:0B:A0:51 49-4E-A7-0B-A0-51 [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 Failed to pair: org.bluez.Error.AlreadyExists [bluetooth]# connect 34:88:5D:3E:A1:A4 Attempting to connect to 34:88:5D:3E:A1:A4 Failed to connect: org.bluez.Error.Failed [bluetooth]# version Version 5.50 [bluetooth]# quit $ uname -a Linux michal-laptop 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux bluetoothctl claims it pairs it, but then disconnects again. The mouse continues to blink, remaining in pairing mode. Even when it does pair successfully, only every 10 times or so does the pairing "persist" across suspend/reboot cycles. Most often I have to re- pair from scratch every boot/resume. -- 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/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: Incomplete Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2
[Touch-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
When it does pair, bluetoothctl doesn't report "ServicesResolved: no" or "Connected: no". -- 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/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: Incomplete Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+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 1821939] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
FYI - Might be: - bug 1811580 Or broken /var/run / /run connection which is related to - https://askubuntu.com/questions/1109934 - https://serverfault.com/questions/941855 You might pickup some hints about the issue in general there. As paride said let us know if you identified a bug in Ubuntu itself, but so far it was always a system setup issue. -- 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/1821939 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Mar 27 15:11:18 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (65 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1821939/+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
