[Touch-packages] [Bug 1746012] Re: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."
Affected on 16.04 as well. -- 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/1746012 Title: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..." Status in rsyslog package in Ubuntu: Fix Released Bug description: I've noticed this for a long time but never looked into it. My logs have a bunch of entries of the form: rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29 04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] This is caused by these lines in /etc/rsyslog.d/50-default.conf: # The named pipe /dev/xconsole is for the `xconsole' utility. To use it, # you must invoke `xconsole' with the `-file' option: # #$ xconsole -file /dev/xconsole [...] # # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. # daemon.*;mail.*;\ news.err;\ *.=debug;*.=info;\ *.=notice;*.=warn |/dev/xconsole /dev/xconsole is not setup by default in Ubuntu. Commenting out the above and restarting rsyslog resolves the issue. This issue was reported to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492 and they disabled xconsole configuration by default in 8.14.0-2, however subsequent Ubuntu merges left the configuration in debian/50-default.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1746012/+subscriptions -- Mailing list: https://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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: ubuntu-z-systems Status: Incomplete => Fix Committed -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Committed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://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 1814992] [NEW] Getting "Authentication Failed" and "Switch to greeter" message on login screen
Public bug reported: A few months back I had the same problem, then I installed lightdm and ran it and since then bug was gone. But 2 days back I got the same bug, I tried running lightdm again, so to stop it I ran sudo stop lightdm but it gives out the message "unable to connect to upstart" and ends. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 7 09:42:53 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-06-07 (244 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1814992 Title: Getting "Authentication Failed" and "Switch to greeter" message on login screen Status in lightdm package in Ubuntu: New Bug description: A few months back I had the same problem, then I installed lightdm and ran it and since then bug was gone. But 2 days back I got the same bug, I tried running lightdm again, so to stop it I ran sudo stop lightdm but it gives out the message "unable to connect to upstart" and ends. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 7 09:42:53 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-06-07 (244 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1814992/+subscriptions -- Mailing list: https://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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
See if you have any *cups* packages installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- Mailing list: https://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 1813833] Re: User without read permission on cron.allow can execute crontab
Hello Brandon, I wasn't able to use an untrusted user account to induce this behaviour. So, I'm making this bug public so that more people can be made aware of the misconfiguration that is being encouraged. It's unfortunate that the providers of this advice never actually tested it themselves. It's unfortunate that the cron manpages don't detail proper permissions for these files. It's unfortunate that crontab(1) doesn't perform this access control check while it has root privileges. It's perhaps most especially unfortunate that this check isn't actually performed by cron(8) at all -- a user listed in /etc/cron.deny isn't actually denied running cron jobs, but is denied managing cron jobs. Existing configurations would keep working. (Probably this is not news to most sysadmins but I'd long since forgotten this detail.) So now, the question is what remediation do we take? - adjusting cron(8) feels like a good idea but would take a fair chunk of effort to not be silly about the implementation. It might also break configurations using the 'gatekeeping' feature of crontab(1). - adjusting crontab(1). I'm not sure how much work this would take but feels like a good approach. - fixing the manpages to describe the correct permissions. This feels like a good idea regardless of changes we may make to crontab(1). Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1813833 Title: User without read permission on cron.allow can execute crontab Status in cron package in Ubuntu: New Bug description: /etc/cron.allow is meant to list the users who are allowed to execute crontab. For a user who is not listed, the output should be: $ crontab -e You (ubuntu) are not allowed to use this program (crontab) See crontab(1) for more information When /etc/cron.allow is not readable by that user, though, it's treated as though the file doesn't exist at all: $ sudo chmod o-r /etc/cron.allow $ crontab -e crontab: installing new crontab The obvious workaround is to ensure that /etc/cron.allow is world readable, but unfortunately there are a lot of security tools and documentation out there that explicitly require both using cron.allow and also setting the permission on cron-related files to 600. Examples include https://secscan.acron.pl/ubuntu1604/5/1/8 and the CIS Level 1 benchmark for Ubuntu. The result of this bug is that a sysadmin attempting to lock down cron by following standard security guidance will fail to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1813833/+subscriptions -- Mailing list: https://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 1813833] Re: User without read permission on cron.allow can execute crontab
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1813833 Title: User without read permission on cron.allow can execute crontab Status in cron package in Ubuntu: New Bug description: /etc/cron.allow is meant to list the users who are allowed to execute crontab. For a user who is not listed, the output should be: $ crontab -e You (ubuntu) are not allowed to use this program (crontab) See crontab(1) for more information When /etc/cron.allow is not readable by that user, though, it's treated as though the file doesn't exist at all: $ sudo chmod o-r /etc/cron.allow $ crontab -e crontab: installing new crontab The obvious workaround is to ensure that /etc/cron.allow is world readable, but unfortunately there are a lot of security tools and documentation out there that explicitly require both using cron.allow and also setting the permission on cron-related files to 600. Examples include https://secscan.acron.pl/ubuntu1604/5/1/8 and the CIS Level 1 benchmark for Ubuntu. The result of this bug is that a sysadmin attempting to lock down cron by following standard security guidance will fail to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1813833/+subscriptions -- Mailing list: https://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 1811248] Re: systemd--networkd mounts denied for lxc guest
https://github.com/lxc/lxd/issues/5439#issuecomment-461257784 > The fix in LXD is only partial because there's currently no safe way for us to fix that for privileged containers due to an apparmor parser bug that the AppArmor team is still working on. So we've made the change only to the unprivileged policy for now as the AppArmor bug isn't causing too much damage in that case. There's no such distinction in profile in LXC, so putting those same lines in the LXC policy would allow every user to bypass all mount protections, which isn't acceptable from a security point of view. So the LXC fix is effectively blocked on the AppArmor security bug being resolved first. ** This bug is no longer a duplicate of bug 1813622 systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd ** Bug watch added: LXD bug tracker #5439 https://github.com/lxc/lxd/issues/5439 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions -- Mailing list: https://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 1814986] Re: lxd/apparmor: Tweak default set of rules
This is a LXD commit, not a LXC one. LXC cannot be fixed in the same way as it has a single apparmor policy covering both privileged and unprivileged containers, until such time as the apparmor security issue is resolved, there's nothing we can do to fix this issue without causing a giant security hole in the process. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1814986 Title: lxd/apparmor: Tweak default set of rules Status in lxc package in Ubuntu: Invalid Bug description: branches cosmic & disco the impact of current lxc aa rules in conjunction with systemd v240 is outlined here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10 Whilst LXC committed the patch to its master https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f it has not arrived downstream and thus would be appreciated to be merged, both in cosmic and disco since impacting users of both branches, e.g. arch linux guest that already deploy systemd v240 without this patch particular ubuntu patch https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1814986/+subscriptions -- Mailing list: https://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 1814905] Re: dash exits when receiving wall message
Hello Imre, thanks for the report. I can't reproduce this issue myself,
nor could I find anything in the source code that would suggest dash
would try to quit. In fact I'm not even sure that dash knows that it's
happened.
Here's the tail end of strace output (run on the same terminal as dash,
to force intermingling of syscall output and terminal output), showing
dash handling a write(1) without trouble, and checking for completed
jobs after I hit enter several times:
geteuid() = 1000
getegid() = 1000
rt_sigaction(SIGINT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55a82089e200, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGQUIT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGQUIT, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGTERM, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTERM, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR)= 3
fcntl(3, F_DUPFD, 10) = 10
close(3)= 0
fcntl(10, F_SETFD, FD_CLOEXEC) = 0
ioctl(10, TIOCGPGRP, [23306]) = 0
getpgrp() = 23306
rt_sigaction(SIGTSTP, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTSTP, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGTTOU, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTTOU, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGTTIN, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTTIN, {sa_handler=SIG_DFL, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
setpgid(0, 23308) = 0
ioctl(10, TIOCSPGRP, [23308]) = 0
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0,
Message from sarnold@hunt on pts/13 at 17:41 ...
hello
EOF
"\n", 8192) = 1
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0,
"\n", 8192) = 1
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0, ^C0x55a820aa9a60, 8192) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
rt_sigprocmask(SIG_SETMASK, [], ~[KILL STOP RTMIN RT_1], 8) = 0
write(2, "\n", 1
) = 1
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0, "", 8192) = 0
write(2, "\n", 1
) = 1
ioctl(10, TIOCSPGRP, [23306]) = 0
setpgid(0, 23306) = 0
close(10) = 0
exit_group(0) = ?
+++ exited with 0 +++
I tried both dash in a terminal (urxvt) and ssh -t sarnold@localhost /bin/dash
-- both behaved identically.
Could you try to reproduce this while you're attached to the shell with
gdb or perhaps perf trace?
Thanks
** Changed in: dash (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1814905
Title:
dash exits when receiving wall message
Status in dash package in Ubuntu:
Incomplete
Bug description:
When using "/bin/sh" (dash) as a shell for ssh, or just starting
/bin/sh in a terminal, when the shell receives a wall message (from
another user or root), it just quits.
How to reproduce:
- start a terminal (xterm, gnome-terminal, etc), usually starts with bash
- from bash run 'sh' command to open a dash shell
- start another terminal, and run: echo "foo" | wall
- the broadcast message appears on both terminals
- in the first terminal you are thrown back to bash, because dash exits
I've tried this on Ubuntu 14.04, 16.04, 18.04 (64bits) latest updates
and it's happening on all of them. I've also tried with latest dash
from git, compiled on Ubuntu 16.04, same problem, that's why I don't
think it's dash's problem.
Also tried on CentOS 7, there is no problem there.
The problem appears this morning (6 February) after updating to latest
version of 16.04, 18.04. I also have a box with 16.04 but not the
latest updates, and on that box the problem does not
[Touch-packages] [Bug 1814986] [NEW] lxd/apparmor: Tweak default set of rules
Public bug reported: branches cosmic & disco the impact of current lxc aa rules in conjunction with systemd v240 is outlined here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10 Whilst LXC committed the patch to its master https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f it has not arrived downstream and thus would be appreciated to be merged, both in cosmic and disco since impacting users of both branches, e.g. arch linux guest that already deploy systemd v240 without this patch particular ubuntu patch https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1814986 Title: lxd/apparmor: Tweak default set of rules Status in lxc package in Ubuntu: New Bug description: branches cosmic & disco the impact of current lxc aa rules in conjunction with systemd v240 is outlined here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10 Whilst LXC committed the patch to its master https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f it has not arrived downstream and thus would be appreciated to be merged, both in cosmic and disco since impacting users of both branches, e.g. arch linux guest that already deploy systemd v240 without this patch particular ubuntu patch https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1814986/+subscriptions -- Mailing list: https://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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
If anyone knows a way to pinpoint some process which sends some specific packets, I'd be glad to investigate further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- Mailing list: https://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 1814980] Re: timedatectl set-timezone UTC Fails
** Description changed: Sorry for the pre-mature post. First time using this interface. - I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. - ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ``` - Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` + If there's anything else that you need, let me know!. - If there's anything else that you need, let me know!. + EDIT: + + + ``` + ubuntu@ip-172-31-26-66:~$ timedatectl --version + systemd 237 + +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid + ``` + + (hostname is different because this is a new instance, same AMI) -- 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/1814980 Title: timedatectl set-timezone UTC Fails Status in systemd package in Ubuntu: New Bug description: Sorry for the pre-mature post. First time using this interface. I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ``` Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` If there's anything else that you need, let me know!. EDIT: ``` ubuntu@ip-172-31-26-66:~$ timedatectl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid ``` (hostname is different because this is a new instance, same AMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814980/+subscriptions -- Mailing list: https://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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I experience the same symptoms on Ubuntu 19.04 disco, but there is no cups* packages installed: # apt-cache policy cups*| grep Installed | grep -v none # The issue is definitely unrelated to CUPS. Some other process sends many strange IPv6/UDP packets to all IPv6 local nodes with 2 different types; the wireshark trace shows 2 types of "Discover scanner commands": 1. source port 8612 (canon-bjnp2) --> dest port 8610 (canon-mfnp) 2. source port 8612 (canon-bjnp2) --> dest port 8612 (canon-bjnp2) I have no canon device on the network nor on the server and no USB device connected on the server. There is no canon related package/kernel module installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- Mailing list: https://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 1814980] [NEW] timedatectl set-timezone UTC Fails
Public bug reported: Sorry for the pre-mature post. First time using this interface. I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic ``` Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` If there's anything else that you need, let me know!. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: + Sorry for the pre-mature post. First time using this interface. + + + I noticed this today; an automated AMI build process failed. + + The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- + eks/k8s_1.10/images/hvm-ssd/ubuntu- + bionic-18.04-amd64-server-20190204.2). + + The automated build process uses a t2.micro, if that's helpful. + + + ``` + ubuntu@ip-172-31-29-182:~$ lsb_release --all + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu 18.04.1 LTS + Release: 18.04 + Codename: bionic + ``` + + + Here's the bug: + ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl - Local time: Thu 2019-02-07 00:10:43 UTC - Universal time: Thu 2019-02-07 00:10:43 UTC - RTC time: Thu 2019-02-07 00:10:44 -Time zone: n/a (UTC, +) -System clock synchronized: yes + Local time: Thu 2019-02-07 00:10:43 UTC + Universal time: Thu 2019-02-07 00:10:43 UTC + RTC time: Thu 2019-02-07 00:10:44 + Time zone: n/a (UTC, +) + System clock synchronized: yes systemd-timesyncd.service active: yes - RTC in local TZ: no + RTC in local TZ: no + ``` + + + If there's anything else that you need, let me know!. -- 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/1814980 Title: timedatectl set-timezone UTC Fails Status in systemd package in Ubuntu: New Bug description: Sorry for the pre-mature post. First time using this interface. I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ``` Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` If there's anything else that you need, let me know!. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814980/+subscriptions -- Mailing list: https://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 1814905] Re: dash exits when receiving wall message
** Package changed: ubuntu => dash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1814905 Title: dash exits when receiving wall message Status in dash package in Ubuntu: New Bug description: When using "/bin/sh" (dash) as a shell for ssh, or just starting /bin/sh in a terminal, when the shell receives a wall message (from another user or root), it just quits. How to reproduce: - start a terminal (xterm, gnome-terminal, etc), usually starts with bash - from bash run 'sh' command to open a dash shell - start another terminal, and run: echo "foo" | wall - the broadcast message appears on both terminals - in the first terminal you are thrown back to bash, because dash exits I've tried this on Ubuntu 14.04, 16.04, 18.04 (64bits) latest updates and it's happening on all of them. I've also tried with latest dash from git, compiled on Ubuntu 16.04, same problem, that's why I don't think it's dash's problem. Also tried on CentOS 7, there is no problem there. The problem appears this morning (6 February) after updating to latest version of 16.04, 18.04. I also have a box with 16.04 but not the latest updates, and on that box the problem does not happen. If one uses dash as a login shell, and enters on a remote box with SSH for example, the connection can be terminated by another user simply wall'ing a broadcast message (or a system daemon like NUT). This could be taken as a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1814905/+subscriptions -- Mailing list: https://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 1814905] [NEW] dash exits when receiving wall message
You have been subscribed to a public bug: When using "/bin/sh" (dash) as a shell for ssh, or just starting /bin/sh in a terminal, when the shell receives a wall message (from another user or root), it just quits. How to reproduce: - start a terminal (xterm, gnome-terminal, etc), usually starts with bash - from bash run 'sh' command to open a dash shell - start another terminal, and run: echo "foo" | wall - the broadcast message appears on both terminals - in the first terminal you are thrown back to bash, because dash exits I've tried this on Ubuntu 14.04, 16.04, 18.04 (64bits) latest updates and it's happening on all of them. I've also tried with latest dash from git, compiled on Ubuntu 16.04, same problem, that's why I don't think it's dash's problem. Also tried on CentOS 7, there is no problem there. The problem appears this morning (6 February) after updating to latest version of 16.04, 18.04. I also have a box with 16.04 but not the latest updates, and on that box the problem does not happen. If one uses dash as a login shell, and enters on a remote box with SSH for example, the connection can be terminated by another user simply wall'ing a broadcast message (or a system daemon like NUT). This could be taken as a potential security issue. ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- dash exits when receiving wall message https://bugs.launchpad.net/bugs/1814905 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814586] Re: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The easiest way to get that is to unpack a tarball, zip, package, etc., using sudo. Chances are really good *other* files and directories also have incorrect owner or permissions. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1814586 Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Invalid Bug description: I have installed all updates to my system recently. Then I tried to connect to this system from my LAN and was unable to connect. So I tried to restart ssh service: sudo service ssh restart Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Service hold-off time over, scheduling restart. фев 04 23:22:00 norbert-vaio systemd[1]: Stopped OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Start request repeated too quickly. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'start-limit-hit'. Then I tried to reinstall it $ sudo apt-get install --reinstall openssh-server Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/335 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 878149 files and directories currently installed.) Preparing to unpack .../openssh-server_1%3a7.2p2-4ubuntu2.6_amd64.deb ... Unpacking openssh-server (1:7.2p2-4ubuntu2.6) over (1:7.2p2-4ubuntu2.6) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu21.15) ... Processing triggers for ufw (0.35-0ubuntu2) ... WARN: uid is 0 but '/' is owned by 1004 WARN: / is group writable! Processing triggers for man-db (2.7.5-1) ... Setting up openssh-server (1:7.2p2-4ubuntu2.6) ... Unsafe symlinks encountered in /var/run/sshd, refusing. initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused 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' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' 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 "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Пн 2019-02-04 23:28:33 MSK; 9ms ago Process: 23843 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) Main PID: 23206 (code=exited, status=0/SUCCESS) фев 04 23:28:33 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:28:33 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:28:33 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) and got this bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.6 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: openssh-server: Install
[Touch-packages] [Bug 1814964] [NEW] No audio when logging in as second user. Only dummy audio device seen
Public bug reported: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: New Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor:
[Touch-packages] [Bug 1814895] Re: display blinking and showing content of screen on sleep mode
** Information type changed from Private Security to Public Security -- 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/1814895 Title: display blinking and showing content of screen on sleep mode Status in xorg package in Ubuntu: New Bug description: In previous versions of Ubuntu(18.04) when I close the laptop by flipping my display, it automatically goes to sleep mode and to turn it on, I have to enter the password. But in this version, when I close(flip the laptop display and make it in sleep mode), and again open and hit enter, it shows a blinking screen which shows all the content of screen without login and doesn't work anything on the screen. To come out from this issue I have to press the lock button from the keyboard and then it goes to the login screen. I should go to sleep mode and should not blink and show the content. 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 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 18:31:06 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] InstallationDate: Installed on 2019-02-05 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SV ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=978388c7-13b2-4d73-90c2-0bc7490d3638 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN30WW:bd04/09/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_ dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 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-1ubuntu1 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/xorg/+bug/1814895/+subscriptions -- Mailing list: https://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 1273524] Re: LXDE guest session shows error message "no session for pid "
Any workaround? Tried editing /etc/apparmor.d/lightdm-guest-session with the suggested change but doesn't work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1273524 Title: LXDE guest session shows error message "no session for pid " Status in One Hundred Papercuts: Triaged Status in Light Display Manager: Triaged Status in Light Display Manager 1.18 series: Triaged Status in lightdm package in Ubuntu: Confirmed Status in lxsession package in Ubuntu: Triaged Status in lightdm source package in Xenial: Confirmed Status in lxsession source package in Xenial: Confirmed Bug description: EXPECTED RESULTS: Log into guest session with no error messages. ACTUAL RESULTS: Upon log in to guest session, an error "no session for pid " is printed. STEPS TO REPRODUCE: 1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual hardware, log into guest session. 2. After being logged in, see error message. AFFECTED VERSIONS: lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-10-18 (384 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=Lubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to load user image: Failed to open file '/home/brendy/.face': No such file or directory NonfreeKernelModules: wl Package: lxsession PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+subscriptions -- Mailing list: https://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 1814958] [NEW] package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
Public bug reported: Hi, I'm not sure this issue is really a bug. Since August 2018, I try to upgrade 16.04.5 to 18.04 LTS with no success. Each upgrades are aborted with a loop detected when installing python's packages. Since PPAs was purged, and I left only one line uncommented in sources.list : deb http://fr.archive.ubuntu.com/ubuntu/ bionic main restricted So, this is the first time my do-release-upgrade has gone so far, I think almost at the end of the upgrade. Regards, ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Feb 6 01:01:48 2019 ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2016-08-16 (904 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 062a:4102 Creative Labs Bus 001 Device 002: ID 04b4:8328 Cypress Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-142-generic.efi.signed root=/dev/mapper/vgubuntu16-lvroot ro Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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: systemd Title: package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: Upgraded to bionic on 2019-02-06 (0 days ago) dmi.bios.date: 09/10/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0052.2016.0910.1456 dmi.board.asset.tag: �=\� dmi.board.name: NUC6i3SYB dmi.board.vendor: Intel corporation dmi.board.version: H81132-503 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0052.2016.0910.1456:bd09/10/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i3SYB:rvrH81132-503:cvn:ct3:cvr: mtime.conffile..etc.systemd.journald.conf: 2018-07-22T13:41:52 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814958 Title: package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in systemd package in Ubuntu: New Bug description: Hi, I'm not sure this issue is really a bug. Since August 2018, I try to upgrade 16.04.5 to 18.04 LTS with no success. Each upgrades are aborted with a loop detected when installing python's packages. Since PPAs was purged, and I left only one line uncommented in sources.list : deb http://fr.archive.ubuntu.com/ubuntu/ bionic main restricted So, this is the first time my do-release-upgrade has gone so far, I think almost at the end of the upgrade. Regards, ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Feb 6 01:01:48 2019 ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2016-08-16 (904 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 062a:4102 Creative Labs Bus 001 Device 002: ID 04b4:8328 Cypress Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-142-generic.efi.signed root=/dev/mapper/vgubuntu16-lvroot ro Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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: systemd Title: package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: Upgraded to bionic on 2019-02-06 (0 days ago) dmi.bios.date: 09/10/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0052.2016.0910.1456 dmi.board.asset.tag: �=\� dmi.board.name: NUC6i3SYB dmi.board.vendor: Intel corporation dmi.board.version: H81132-503 dmi.chassis.type: 3
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
The new stable version indicate the fix mentioned by seb128 is there but no indication has been made in the debian/changelog to automatically change the status, which breaks the SRU machinery for this particular bug. --- network-manager-1.10.6/src/nm-manager.c 2018-03-12 08:59:48.0 -0400 +++ network-manager-1.10.14/src/nm-manager.c2018-11-20 05:23:31.0 -0500 + if ( old_state == NM_DEVICE_STATE_UNMANAGED + && new_state > NM_DEVICE_STATE_UNMANAGED) + retry_connections_for_parent_device (self, device); + I'll change the bug status from "Incomplete" to "Fix Committed" as the package is now found in bionic-proposed. - Eric ** Changed in: network-manager (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: network-manager (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Olivier Tilloy (osomon) ** Tags added: verification-needed verification-needed-bionic ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: network-manager (Ubuntu Bionic) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: network-manager (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy
[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte
** Description changed:
+ [Impact]
+ Ubuntu crash reports and package installation failures may not include
DpkgTerminalLog.txt if there is a UnicodeDecodeError trying to read the dpkg
log file.
+
+ [Test Case]
+ Because the fix is simple and its complicated to have a dpkg log file with
unicode in it we'll just test that truncating of a dpkg log file still works.
+
+ 1) Install 2vcard (so we have a recent dpkg log entry)
+ 2) Run update-manager
+ 3) Kill it with signal 11 e.g. kill -11 $PID of update-manager
+ 4) Run ubuntu-bug /var/crash/_usr_bin_update-manager.1000.crash
+ 5) Observe DpkgTerminalLog.txt only contains a log entry regarding the
installation of 2vcard and matches the content in /var/log/apt/term.log.
+
+ [Regression Potential]
+ Its possible that the code to replace the DpkgTerminalLog contents of the
report is wrong but the test case above ensures that it isn't.
+
+ [Original Description]
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
- symb['add_info'](report, ui)
- File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
- check_attachment_for_errors(report, attachment)
- File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
- trim_dpkg_log(report)
- File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
- report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
- File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
- report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
+ File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
+ symb['add_info'](report, ui)
+ File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
+ check_attachment_for_errors(report, attachment)
+ File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
+ trim_dpkg_log(report)
+ File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
+ report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
+ File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
+ report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070:
invalid continuation byte
It can also be seen here:
- https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
+ https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
+ ProblemType: BugDistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
-
+
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
- TERM=xterm
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
- SourcePackage: apport
+ TERM=xterm
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bashSourcePackage: apport
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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1766337
Title:
uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
decode byte; invalid continuation byte
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
In Progress
Bug description:
[Impact]
Ubuntu crash reports and package installation failures may not include
DpkgTerminalLog.txt if there is a UnicodeDecodeError trying to read the dpkg
log file.
[Test Case]
Because the fix is simple and its complicated to have a dpkg log file with
unicode in it we'll just test that truncating of a dpkg log file still works.
1) Install 2vcard (so we have a recent dpkg log entry)
2) Run update-manager
3) Kill it with signal 11 e.g. kill -11 $PID of update-manager
4) Run ubuntu-bug /var/crash/_usr_bin_update-manager.1000.crash
5) Observe DpkgTerminalLog.txt only contains a log entry regarding the
installation of 2vcard and matches the content in /var/log/apt/term.log.
[Regression Potential]
Its possible that the code to replace the DpkgTerminalLog contents of the
report is wrong but the test case above ensures that it isn't.
[Original Description]
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
[Touch-packages] [Bug 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+subscriptions -- Mailing list: https://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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
Thanks for the update, closing! ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Fix Released Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- Mailing list: https://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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+subscriptions -- Mailing list: https://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 1814586] Re: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Finally I have ran `sudo chmod g-w /` to be completely sure and rebooted again. As the result I can connect to this machine from my LAN. Just curious - why did I have 1004:1004 rights on /? ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- 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/1814586 Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Invalid Bug description: I have installed all updates to my system recently. Then I tried to connect to this system from my LAN and was unable to connect. So I tried to restart ssh service: sudo service ssh restart Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Service hold-off time over, scheduling restart. фев 04 23:22:00 norbert-vaio systemd[1]: Stopped OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Start request repeated too quickly. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'start-limit-hit'. Then I tried to reinstall it $ sudo apt-get install --reinstall openssh-server Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/335 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 878149 files and directories currently installed.) Preparing to unpack .../openssh-server_1%3a7.2p2-4ubuntu2.6_amd64.deb ... Unpacking openssh-server (1:7.2p2-4ubuntu2.6) over (1:7.2p2-4ubuntu2.6) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu21.15) ... Processing triggers for ufw (0.35-0ubuntu2) ... WARN: uid is 0 but '/' is owned by 1004 WARN: / is group writable! Processing triggers for man-db (2.7.5-1) ... Setting up openssh-server (1:7.2p2-4ubuntu2.6) ... Unsafe symlinks encountered in /var/run/sshd, refusing. initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused 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' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' 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 "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Пн 2019-02-04 23:28:33 MSK; 9ms ago Process: 23843 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) Main PID: 23206 (code=exited, status=0/SUCCESS) фев 04 23:28:33 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:28:33 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:28:33 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) and got this bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.6 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu Bionic)
Status: Triaged => In Progress
--
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/1766337
Title:
uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
decode byte; invalid continuation byte
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
In Progress
Bug description:
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070:
invalid continuation byte
It can also be seen here:
https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766337/+subscriptions
--
Mailing list: https://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 1814586] Re: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I have checked about 1004 and got: ls -ld / drwxrwxr-x 32 1004 1004 4096 Dec 9 23:22 / - it is really strange. So I ran sudo chown root: / ls -ld / drwxrwxr-x 32 root root 4096 Dec 9 23:22 / And reinstalled SSHD again: sudo apt-get install --reinstall openssh-server without errors: $ systemctl status sshd.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) since Ср 2019-02-06 22:02:53 MSK; 51s ago Process: 5011 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 5031 (sshd) CGroup: /system.slice/ssh.service └─5031 /usr/sbin/sshd -D Feb 06 22:02:53 norbert-vaio systemd[1]: Starting OpenBSD Secure Shell server... Feb 06 22:02:53 norbert-vaio sshd[5031]: Server listening on 0.0.0.0 port 22. Feb 06 22:02:53 norbert-vaio sshd[5031]: Server listening on :: port 22. Feb 06 22:02:53 norbert-vaio systemd[1]: Started OpenBSD Secure Shell server. then rebooted. -- 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/1814586 Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Invalid Bug description: I have installed all updates to my system recently. Then I tried to connect to this system from my LAN and was unable to connect. So I tried to restart ssh service: sudo service ssh restart Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Service hold-off time over, scheduling restart. фев 04 23:22:00 norbert-vaio systemd[1]: Stopped OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Start request repeated too quickly. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'start-limit-hit'. Then I tried to reinstall it $ sudo apt-get install --reinstall openssh-server Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/335 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 878149 files and directories currently installed.) Preparing to unpack .../openssh-server_1%3a7.2p2-4ubuntu2.6_amd64.deb ... Unpacking openssh-server (1:7.2p2-4ubuntu2.6) over (1:7.2p2-4ubuntu2.6) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu21.15) ... Processing triggers for ufw (0.35-0ubuntu2) ... WARN: uid is 0 but '/' is owned by 1004 WARN: / is group writable! Processing triggers for man-db (2.7.5-1) ... Setting up openssh-server (1:7.2p2-4ubuntu2.6) ... Unsafe symlinks encountered in /var/run/sshd, refusing. initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused 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' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' 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 "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Пн 2019-02-04 23:28:33 MSK; 9ms ago Process: 23843 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) Main PID: 23206 (code=exited, status=0/SUCCESS) фев 04 23:28:33
[Touch-packages] [Bug 1814925] Re: Bluetooth mouse stops responding after extended deep sleep
More detailed information on this issue is below: The customer has Ubuntu OEM through Dell. The laptop goes into deep sleep over night and they can no longer use their BT devices. You click on bt via GUI and try to toggle on and it looks like it is doing something and goes right back to off. BIOS 1.6.3 XPS 13 9370 Ubuntu 18.04- Kernel 4.15.0-43-generic Lspci shows 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) lsusb Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bluetooth show Controller 9C:B6:D0:8D:D2:C8 (public) Name: dell-XPS-13-9370 Alias: dell-XPS-13-9370 Class: 0x001c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: yes ... [HP Bluetooth Mouse X4000b]# list Controller 9C:B6:D0:8D:D2:C8 dell-XPS-13-9370 [default] rtlwifi_new$ hciconfig -a hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:8D:D2:C8 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:1189167 acl:6900 sco:0 events:36422 errors:0 TX bytes:31398 acl:80 sco:0 commands:3310 errors:0 Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'dell-XPS-13-9370' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.2 (0x8) Revision: 0x0 LMP Version: 4.2 (0x8) Subversion: 0x25a Manufacturer: Qualcomm (29) dell@dell-XPS-13-9370:~/rtlwifi_new$ lsusb Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai lsusb -v -d 0489:e0a2 Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x0489 Foxconn / Hon Hai idProduct 0xe0a2 bcdDevice0.01 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 177 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7
[Touch-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
This bug is solved in 18.04 LTS. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- Mailing list: https://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 1814941] Re: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-i
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1814941 Title: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in libxml2 package in Ubuntu: New Bug description: i don't know i was just updating the os and i had this issue and i am not familiar with linux so i just reported it . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Feb 6 18:59:15 2019 DuplicateSignature: package:libxml2:amd64:2.9.3+dfsg1-1ubuntu0.6 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libxml2:amd64 (--configure): package libxml2:amd64 is not ready for configuration ErrorMessage: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-07-07 (213 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 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/libxml2/+bug/1814941/+subscriptions -- Mailing list: https://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 1814941] [NEW] package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half
Public bug reported: i don't know i was just updating the os and i had this issue and i am not familiar with linux so i just reported it . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Feb 6 18:59:15 2019 DuplicateSignature: package:libxml2:amd64:2.9.3+dfsg1-1ubuntu0.6 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libxml2:amd64 (--configure): package libxml2:amd64 is not ready for configuration ErrorMessage: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-07-07 (213 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (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 libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1814941 Title: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in libxml2 package in Ubuntu: New Bug description: i don't know i was just updating the os and i had this issue and i am not familiar with linux so i just reported it . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Feb 6 18:59:15 2019 DuplicateSignature: package:libxml2:amd64:2.9.3+dfsg1-1ubuntu0.6 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libxml2:amd64 (--configure): package libxml2:amd64 is not ready for configuration ErrorMessage: package libxml2:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-07-07 (213 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.6 failed to install/upgrade: package libxml2:amd64 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/libxml2/+bug/1814941/+subscriptions -- Mailing list: https://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 1662244] Re: lightdm causes all greeters to fail to start
Seen on 18.04.1. WorkARound? * soft memlock 262144 * hard memlock 262144 # End of file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start Status in Light Display Manager: Invalid Status in LightDM GTK+ Greeter: Invalid Status in lightdm package in Ubuntu: Invalid Status in unity-greeter package in Ubuntu: Invalid Bug description: lightdm is failing to start. Best guess is because of unity-session- manager. This is from .xsession-errors. dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment upstart: click-user-hooks main process (4028) terminated with status 1 upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon respawning too fast, stopped upstart: indicator-application main process ended, respawning upstart: indicator-application main process ended, respawning upstart: indicator-application respawning too fast, stopped xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name upstart: dbus main process (4023) killed by TERM signal I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've reverted kernel versions and that didn't work. I've moved aside $HOME/.cache and that didn't work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Feb 6 10:21:29 2017 InstallationDate: Installed on 2015-07-20 (566 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+subscriptions -- Mailing list: https://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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
No, it would have been impossible for any desktop image (even pending) to contain the new systemd on the 31st of January. The first image that contains the new systemd is from 20190204 or later. ** Changed in: systemd (Ubuntu Disco) Status: Fix Committed => Fix Released -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) [Regression potential] Minimal. Originally, one failing mount point blocked the processing of the rest due to how the return codes were handled for every line in /proc/self/mountinfo. This patch removes this "dependency" and keeps the failure local to the affected mount point, allowing the rest to be processed normally. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10874 Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3 [Original Description] netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm=""
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
** Changed in: systemd (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814933] [NEW] Ambiance/Radiance: path-bar is broken with nautilus > 3.30
Public bug reported: Nautilus 3.30 has new path-bar. And hence it doesn't look good with current design. I had several ideas to solve the problem. Hence opened a discussion thread in community hub to get opinions from developers and users. See: I will open a merge once this gets finalized. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814933 Title: Ambiance/Radiance: path-bar is broken with nautilus > 3.30 Status in ubuntu-themes package in Ubuntu: New Bug description: Nautilus 3.30 has new path-bar. And hence it doesn't look good with current design. I had several ideas to solve the problem. Hence opened a discussion thread in community hub to get opinions from developers and users. See: I will open a merge once this gets finalized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1814933/+subscriptions -- Mailing list: https://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 1814586] Re: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. There are some interesting warnings in the logs you provided: WARN: uid is 0 but '/' is owned by 1004 WARN: / is group writable! and Setting up openssh-server (1:7.2p2-4ubuntu2.6) ... Unsafe symlinks encountered in /var/run/sshd, refusing. More details should be present in /var/log/syslog, /var/log/auth.log and/or in the output of journalctl -xe. Could you please inspect those and report back, or attach them to this bug? ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1814586 Title: package openssh-server 1:7.2p2-4ubuntu2.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: I have installed all updates to my system recently. Then I tried to connect to this system from my LAN and was unable to connect. So I tried to restart ssh service: sudo service ssh restart Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Service hold-off time over, scheduling restart. фев 04 23:22:00 norbert-vaio systemd[1]: Stopped OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Start request repeated too quickly. фев 04 23:22:00 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:22:00 norbert-vaio systemd[1]: ssh.service: Failed with result 'start-limit-hit'. Then I tried to reinstall it $ sudo apt-get install --reinstall openssh-server Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/335 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 878149 files and directories currently installed.) Preparing to unpack .../openssh-server_1%3a7.2p2-4ubuntu2.6_amd64.deb ... Unpacking openssh-server (1:7.2p2-4ubuntu2.6) over (1:7.2p2-4ubuntu2.6) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu21.15) ... Processing triggers for ufw (0.35-0ubuntu2) ... WARN: uid is 0 but '/' is owned by 1004 WARN: / is group writable! Processing triggers for man-db (2.7.5-1) ... Setting up openssh-server (1:7.2p2-4ubuntu2.6) ... Unsafe symlinks encountered in /var/run/sshd, refusing. initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused 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' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' 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 "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Пн 2019-02-04 23:28:33 MSK; 9ms ago Process: 23843 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) Main PID: 23206 (code=exited, status=0/SUCCESS) фев 04 23:28:33 norbert-vaio systemd[1]: Failed to start OpenBSD Secure Shell server. фев 04 23:28:33 norbert-vaio systemd[1]: ssh.service: Unit entered failed state. фев 04 23:28:33 norbert-vaio systemd[1]: ssh.service: Failed with result 'exit-code'. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) and got this
[Touch-packages] [Bug 1176548] Re: nut-server fails if modemmanager is scanning serial ports
** Changed in: nut (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1176548 Title: nut-server fails if modemmanager is scanning serial ports Status in modemmanager package in Ubuntu: New Status in nut package in Ubuntu: Triaged Bug description: Similar to whatPaavo Leinonen reported in 031601ce2a49$20b2efe0$6218cfa0$@leinonen.fi on the NUT mailing list. See also my mail in reply. Ubuntu runs modemmanager as a native upstart service. nut-server ends up running in parallel (on my system, probably a matter of timing). When modemmanager scans the serial ports for modems, upsd is unable to open the port configured for an UPS. (It might be possible to exclude some ports from the scan, I didn't check because I have no modem it could configure, I just kicked the package. Please convert nut-server to a native upstart service to be able to have it wait for modemmanager. (I hope upstart is clever enough to have a service wait for an optional package and let it proceed if not installed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1176548/+subscriptions -- Mailing list: https://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 1814925] Re: Bluetooth mouse stops responding after extended deep sleep
** Description changed: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso - Bluetotth mouse tested with HP X4b BT Last mouse stops responding + Bluetooth mouse tested with HP X4b BT Last mouse stops responding after long extended deep sleep (24-48 hours). Bluetooth settings window which initially reported Bluetooth as connected now shows disconnected. Pushing the button within the settings window to reconnect takes me back to off. Switching back to on and off keeps bringing me back to off unless I reboot the device and or turn off the mouse via the underneath portion of the BT device. Demsg logs shows an extremely large number of "Bluetooth: hci:0 last event is not cmd complete (0x0f)" Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: bluez 5.48-0ubuntu3.1 XPS 13 9370 bios 1.6.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:16:07 2019 InstallationDate: Installed on 2019-01-03 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep initrdefi /acpi_override quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 9C:B6:D0:90:A0:16 ACL MTU: 1024:8 SCO MTU: 50:8 - UP RUNNING PSCAN ISCAN - RX bytes:748157 acl:263 sco:0 events:22281 errors:0 - TX bytes:15577 acl:124 sco:0 commands:1167 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 9C:B6:D0:90:A0:16 ACL MTU: 1024:8 SCO MTU: 50:8 + UP RUNNING PSCAN ISCAN + RX bytes:748157 acl:263 sco:0 events:22281 errors:0 + TX bytes:15577 acl:124 sco:0 commands:1167 errors:0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814925 Title: Bluetooth mouse stops responding after extended deep sleep Status in bluez package in Ubuntu: Confirmed Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso Bluetooth mouse tested with HP X4b BT Last mouse stops responding after long extended deep sleep (24-48 hours). Bluetooth settings window which initially reported Bluetooth as connected now shows disconnected. Pushing the button within the settings window to reconnect takes me back to off. Switching back to on and off keeps bringing me back to off unless I reboot the device and or turn off the mouse via the underneath portion of the BT device. Demsg logs shows an extremely large number of "Bluetooth: hci:0 last event is not cmd complete (0x0f)" Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: bluez 5.48-0ubuntu3.1 XPS 13 9370 bios 1.6.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:16:07 2019 InstallationDate: Installed on 2019-01-03 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep initrdefi /acpi_override quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity
*** This bug is a duplicate of bug 1814925 *** https://bugs.launchpad.net/bugs/1814925 running ubuntu-bug bluez; I received a new bug id 1814925. These bugs are all related. ** This bug has been marked a duplicate of bug 1814925 Bluetooth mouse stops responding after extended deep sleep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+subscriptions -- Mailing list: https://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 1814925] Re: Bluetooth mouse stops responding after extended deep sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814925 Title: Bluetooth mouse stops responding after extended deep sleep Status in bluez package in Ubuntu: Confirmed Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso Bluetooth mouse tested with HP X4b BT Last mouse stops responding after long extended deep sleep (24-48 hours). Bluetooth settings window which initially reported Bluetooth as connected now shows disconnected. Pushing the button within the settings window to reconnect takes me back to off. Switching back to on and off keeps bringing me back to off unless I reboot the device and or turn off the mouse via the underneath portion of the BT device. Demsg logs shows an extremely large number of "Bluetooth: hci:0 last event is not cmd complete (0x0f)" Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: bluez 5.48-0ubuntu3.1 XPS 13 9370 bios 1.6.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:16:07 2019 InstallationDate: Installed on 2019-01-03 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep initrdefi /acpi_override quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:90:A0:16 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN RX bytes:748157 acl:263 sco:0 events:22281 errors:0 TX bytes:15577 acl:124 sco:0 commands:1167 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1814925/+subscriptions -- Mailing list: https://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 1813208] Re: Paired bluetooth mice irregularities after resume from suspend
*** This bug is a duplicate of bug 1814925 *** https://bugs.launchpad.net/bugs/1814925 running ubuntu-bug bluez; I received a new bug id 1814925. These bugs are all related. ** This bug has been marked a duplicate of bug 1814925 Bluetooth mouse stops responding after extended deep sleep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1813208 Title: Paired bluetooth mice irregularities after resume from suspend Status in bluez package in Ubuntu: Incomplete Bug description: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813208/+subscriptions -- Mailing list: https://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 1814925] [NEW] Bluetooth mouse stops responding after extended deep sleep
Public bug reported: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso Bluetooth mouse tested with HP X4b BT Last mouse stops responding after long extended deep sleep (24-48 hours). Bluetooth settings window which initially reported Bluetooth as connected now shows disconnected. Pushing the button within the settings window to reconnect takes me back to off. Switching back to on and off keeps bringing me back to off unless I reboot the device and or turn off the mouse via the underneath portion of the BT device. Demsg logs shows an extremely large number of "Bluetooth: hci:0 last event is not cmd complete (0x0f)" Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: bluez 5.48-0ubuntu3.1 XPS 13 9370 bios 1.6.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:16:07 2019 InstallationDate: Installed on 2019-01-03 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep initrdefi /acpi_override quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:90:A0:16 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN RX bytes:748157 acl:263 sco:0 events:22281 errors:0 TX bytes:15577 acl:124 sco:0 commands:1167 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814925 Title: Bluetooth mouse stops responding after extended deep sleep Status in bluez package in Ubuntu: Confirmed Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso Bluetooth mouse tested with HP X4b BT Last mouse stops responding after long extended deep sleep (24-48 hours). Bluetooth settings window which initially reported Bluetooth as connected now shows disconnected. Pushing the button within the settings window to reconnect takes me back to off. Switching back to on and off keeps bringing me back to off unless I reboot the device and or turn off the mouse via the underneath portion of the BT device. Demsg logs shows an extremely large number of "Bluetooth: hci:0 last event is not cmd complete (0x0f)" Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: bluez 5.48-0ubuntu3.1 XPS 13 9370 bios 1.6.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:16:07 2019 InstallationDate: Installed on 2019-01-03 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep initrdefi /acpi_override quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:90:A0:16 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN RX bytes:748157 acl:263 sco:0 events:22281 errors:0 TX bytes:15577 acl:124 sco:0 commands:1167
[Touch-packages] [Bug 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity
Daniel, my name is Jill and I have the customer's capture so I have to run the apport-collect from the customer's system. Juan is our back line engineer that opened the case with you so we could have Canonical and Dell collaborate. If this is not correct. How can I get you the data? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+subscriptions -- Mailing list: https://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 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity
1813208 is a duplicate of this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+subscriptions -- Mailing list: https://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 1813208] Re: Paired bluetooth mice irregularities after resume from suspend
I am asking our colleague Juan to respond but yes these are 2 bugs that are duplicate of each other. Let Juan know what you need from us to take this further? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1813208 Title: Paired bluetooth mice irregularities after resume from suspend Status in bluez package in Ubuntu: Incomplete Bug description: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813208/+subscriptions -- Mailing list: https://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 1811580] Re: systemd fails to start sshd at reboot
@cadirol most likely your system is broken, insecure and vulnerable to the relevant CVE. Please provide output from journal logs, and permissions of the root directory $ ls -latr / $ journalctl -b -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://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 1814808] Re: 18.04 update to libglapi-mesa/libglx-mesa0 causes vlc crash
Installing mesa 18.2.8 from the updates ppa fixes the problem. -- 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/1814808 Title: 18.04 update to libglapi-mesa/libglx-mesa0 causes vlc crash Status in mesa package in Ubuntu: Incomplete Status in vlc package in Ubuntu: New Bug description: OS: Ubuntu 18.04.1 running in a kvm VM under Ubuntu 18.04 with all latest updates. Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy vlc vlc: Installed: 3.0.4-1ubuntu0.2 Candidate: 3.0.4-1ubuntu0.2 Version table: *** 3.0.4-1ubuntu0.2 500 500 http://mirrors.namecheap.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.0.3-1-1ubuntu1 500 500 http://mirrors.namecheap.com/ubuntu bionic-security/universe amd64 Packages 3.0.1-3build1 500 500 http://mirrors.namecheap.com/ubuntu bionic/universe amd64 Packages apt-cache policy libglapi-mesa libglapi-mesa: Installed: 18.2.2-0ubuntu1~18.04.1 Candidate: 18.2.2-0ubuntu1~18.04.1 Version table: *** 18.2.2-0ubuntu1~18.04.1 500 500 http://mirrors.namecheap.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.0.0~rc5-1ubuntu1 500 500 http://mirrors.namecheap.com/ubuntu bionic/main amd64 Packages libglx-mesa0: Installed: 18.2.2-0ubuntu1~18.04.1 Candidate: 18.2.2-0ubuntu1~18.04.1 Version table: *** 18.2.2-0ubuntu1~18.04.1 500 500 http://mirrors.namecheap.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.0.0~rc5-1ubuntu1 500 500 http://mirrors.namecheap.com/ubuntu bionic/main amd64 Packages When I install the updated library versions listed above vlc crashes. I have experienced this with multiple mp4 files. When I revert these libraries to the following older versions, it works correctly: hi libglapi-mesa:amd6418.0.5-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library hi libglx-mesa0:amd64 18.0.5-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library I am enclosing a log of a gdb session including a backtrace. Thank You. Nataraj To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1814808/+subscriptions -- Mailing list: https://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 1778844] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2019-02-06 09:45 EDT--- Triggered crash with patch using crashkernel=8192M and did not see OOM traces and dump copied properly as below root@woo:/var/crash/201902060928# pwd /var/crash/201902060928 root@woo:/var/crash/201902060928# ls -l total 469212 -rw--- 1 root root114308 Feb 6 09:29 dmesg.201902060928 -rw--- 1 root root 480474149 Feb 6 09:29 dump.201902060928 root@woo:/var/crash/201902060928# date Wed Feb 6 09:44:42 EST 2019 root@woo:/var/crash/201902060928# Regards, Indira -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00:
[Touch-packages] [Bug 1778844] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2019-02-06 09:27 EDT--- (In reply to comment #82) > The system has too many devices, so too many drivers are using too much > memory. So, the system goes out-of-memory before makedumpfile is complete. > Please, reserve more memory on crashkernel, reboot the system and repeat the > crash test. > > To reserve more memory on crashkernel, edit file > /etc/default/grub.d/kdump-tools.cfg and change crashkernel value to > crashkernel=384M, for example, then run update-grub. > > Thanks. > Cascardo. Hi Cascardo As per SUSE document recommendation used 4096M crash kernel and with this value i have seen OOM traces during kdump. root@woo:~# free -h totalusedfree shared buff/cache available Mem: 251G7.2G243G 16M567M243G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=df4c0331-9e6c-4592-9e0c-84f431ecb1f7 ro splash quiet crashkernel=4096M Will try to increase to some more above 4096M and retry it. Regards, Indira -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
Good day Same issue here! After upgrade systemd from 229-4ubuntu21.10 to 229-4ubuntu21.15 and a reboot, ssh did not start anymore. As ugly workaround i ran #mkdir -p -m0755 /var/run/sshd && systemctl restart ssh.service $ uname -a Linux aws01.nts.ch 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/issue Ubuntu 16.04.5 LTS $ dpkg -l | grep systemd ii libpam-systemd:amd64 229-4ubuntu21.15 system and service manager - PAM module rc libsystemd-daemon0:amd64 204-5ubuntu20.19 systemd utility library rc libsystemd-login0:amd64 204-5ubuntu20.19 systemd login utility library ii libsystemd0:amd64229-4ubuntu21.15 systemd utility library ii python3-systemd 231-2build1 Python 3 bindings for systemd ii systemd 229-4ubuntu21.15 Do you provide a fix? what is the plan? -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://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 1742482] Re: firefox is used to open ftp share files
it's also discussed on https://gitlab.gnome.org/GNOME/nautilus/issues/713 ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1742482 Title: firefox is used to open ftp share files Status in glib2.0 package in Ubuntu: Triaged Bug description: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 Bluefish 2.2.10 When I open a .php file from a FTP server browsed with Nautilus, Chrome is opened instead of the default application Bluefish. Steps to reproduce: 1. Connect to an FTP server via Nautilus 2a. Double-click on a .php file: chrome opens and the file is downloaded 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected So, on the double-click from Nautilus the wrong app (chrome!) is opened even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742482/+subscriptions -- Mailing list: https://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 1742482] Re: firefox is used to open ftp share files
That's discussed upstream on https://gitlab.gnome.org/GNOME/glib/issues/1414 and basically their opinion is that firefox shouldn't claim to be a x-scheme-handler/ftp handler ** Summary changed: - Double-click doesn't open default application + firefox is used to open ftp share files ** Package changed: nautilus (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1742482 Title: firefox is used to open ftp share files Status in glib2.0 package in Ubuntu: Triaged Bug description: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 Bluefish 2.2.10 When I open a .php file from a FTP server browsed with Nautilus, Chrome is opened instead of the default application Bluefish. Steps to reproduce: 1. Connect to an FTP server via Nautilus 2a. Double-click on a .php file: chrome opens and the file is downloaded 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected So, on the double-click from Nautilus the wrong app (chrome!) is opened even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742482/+subscriptions -- Mailing list: https://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 1814885] Re: packagekitd crashed with SIGABRT in std::terminate()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1814885 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: I do not know how this happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 Uname: Linux 5.0.0-05rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Wed Feb 6 07:34:02 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-12-02 (65 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/sh Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: Upgraded to disco on 2018-12-02 (65 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1814885/+subscriptions -- Mailing list: https://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 1742482] [NEW] firefox is used to open ftp share files
You have been subscribed to a public bug: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 Bluefish 2.2.10 When I open a .php file from a FTP server browsed with Nautilus, Chrome is opened instead of the default application Bluefish. Steps to reproduce: 1. Connect to an FTP server via Nautilus 2a. Double-click on a .php file: chrome opens and the file is downloaded 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected So, on the double-click from Nautilus the wrong app (chrome!) is opened even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Low Status: Confirmed ** Tags: amd64 apport-bug bionic wayland-session -- firefox is used to open ftp share files https://bugs.launchpad.net/bugs/1742482 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1051952] Re: libgio's move-to-trash funciton freezes system when trashing files in kerberized, NFS mounted filesystems
Is that still an issue in current Ubuntu versions? ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1051952 Title: libgio's move-to-trash funciton freezes system when trashing files in kerberized, NFS mounted filesystems Status in glib2.0 package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Invalid Status in thunar package in Ubuntu: Confirmed Bug description: Description:Ubuntu 12.04.1 LTS Release:12.04 nautilus: Installed: 1:3.4.2-0ubuntu4 Candidate: 1:3.4.2-0ubuntu4 Version table: *** 1:3.4.2-0ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.4.1-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages thunar: Installed: 1.2.3-3ubuntu2 Candidate: 1.2.3-3ubuntu2 Version table: *** 1.2.3-3ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status The setting is: - the user joeuser has a home directory which is mounted via NFS Version 4 - the NFS4 mount uses Kerberos (-o sec=krb5) for authentication, which is the only non-default mount option - the user uses either Nautilus or Thunar as a graphical file manager - the user moves a small number of files to trash using either Thunar or Nautilus, after at most 20 times (independent on uptime or login time) the bug emerges: when the user moves file ~/foobar_21 to trash the operation takes a very long time (30 secs and longer) - during the wait we have observerd that nautious/thunar and other applications freeze or will not start -- top, as joeuser, will not start until the file ~/foobar_21 has been moved to trash -- cat ~/myfile.txt does not work until the file has been moved to trash -- the Thunar and Nautilus windows are not redrawn - ls does work and we can see that the original file ~/foobar_21 is deleted shortly before the end of the wait time The file managers Dolphin and Xfe work as expected taking well under a second to trash files. Other file managers have not been tested. FTR: dolphin: Installed: 4:4.8.4-0ubuntu0.1 Candidate: 4:4.8.4-0ubuntu0.1 Version table: *** 4:4.8.4-0ubuntu0.1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 4:4.8.2-0ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages xfe: Installed: 1.32.4-3 Candidate: 1.32.4-3 Version table: *** 1.32.4-3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status nfs-common: Installed: 1:1.2.5-3ubuntu3 Candidate: 1:1.2.5-3ubuntu3 Version table: *** 1:1.2.5-3ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status krb5-user: Installed: 1.10+dfsg~beta1-2ubuntu0.3 Candidate: 1.10+dfsg~beta1-2ubuntu0.3 Version table: *** 1.10+dfsg~beta1-2ubuntu0.3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10+dfsg~beta1-2 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages Linux HOSTNAME 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1051952/+subscriptions -- Mailing list: https://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 1814808] Re: 18.04 update to libglapi-mesa/libglx-mesa0 causes vlc crash
try the updates ppa, which has mesa 18.2.8: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1814808 Title: 18.04 update to libglapi-mesa/libglx-mesa0 causes vlc crash Status in mesa package in Ubuntu: Incomplete Status in vlc package in Ubuntu: New Bug description: OS: Ubuntu 18.04.1 running in a kvm VM under Ubuntu 18.04 with all latest updates. Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy vlc vlc: Installed: 3.0.4-1ubuntu0.2 Candidate: 3.0.4-1ubuntu0.2 Version table: *** 3.0.4-1ubuntu0.2 500 500 http://mirrors.namecheap.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.0.3-1-1ubuntu1 500 500 http://mirrors.namecheap.com/ubuntu bionic-security/universe amd64 Packages 3.0.1-3build1 500 500 http://mirrors.namecheap.com/ubuntu bionic/universe amd64 Packages apt-cache policy libglapi-mesa libglapi-mesa: Installed: 18.2.2-0ubuntu1~18.04.1 Candidate: 18.2.2-0ubuntu1~18.04.1 Version table: *** 18.2.2-0ubuntu1~18.04.1 500 500 http://mirrors.namecheap.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.0.0~rc5-1ubuntu1 500 500 http://mirrors.namecheap.com/ubuntu bionic/main amd64 Packages libglx-mesa0: Installed: 18.2.2-0ubuntu1~18.04.1 Candidate: 18.2.2-0ubuntu1~18.04.1 Version table: *** 18.2.2-0ubuntu1~18.04.1 500 500 http://mirrors.namecheap.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.0.0~rc5-1ubuntu1 500 500 http://mirrors.namecheap.com/ubuntu bionic/main amd64 Packages When I install the updated library versions listed above vlc crashes. I have experienced this with multiple mp4 files. When I revert these libraries to the following older versions, it works correctly: hi libglapi-mesa:amd6418.0.5-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library hi libglx-mesa0:amd64 18.0.5-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library I am enclosing a log of a gdb session including a backtrace. Thank You. Nataraj To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1814808/+subscriptions -- Mailing list: https://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 1797893] Re: batter management is not working properly on mac air
Bai Lee, Is this still an issue? Unless you provide us with more information about the hardware and Ubuntu version you are using we are unable to help. ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1797893 Title: batter management is not working properly on mac air Status in upower package in Ubuntu: Incomplete Bug description: battery status can not be trigger instantly when cable are wired or not. the volume of current battery is wrong. unable to charging properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1797893/+subscriptions -- Mailing list: https://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 1814827] Re: wireless hard blocked in ubuntu 18.04
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1814827 Title: wireless hard blocked in ubuntu 18.04 Status in linux package in Ubuntu: New Bug description: Wireless hard blocked in ubuntu 18.04 after installation. No wireless adapter found when go to network-manager interface to configure wireless. The wireless adapter is Centrino Wireless-N 2230 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 5 22:43:39 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-12 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.129 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 b4fa9513-155a-3f47-9743-4298b4e52e4b ethernet 1549402981 mar 05 feb 2019 22:43:01 CET yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0 ethernet connected/org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 b4fa9513-155a-3f47-9743-4298b4e52e4b /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- 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 started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814827/+subscriptions -- Mailing list: https://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 1738110] Re: RSS feed in Rhythmbox pulling images instead of mp3 files
There is a new version including that fix now ** Changed in: totem-pl-parser (Ubuntu) Importance: Undecided => Low ** Changed in: totem-pl-parser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1738110 Title: RSS feed in Rhythmbox pulling images instead of mp3 files Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: I reported this bug here: https://bugzilla.gnome.org/show_bug.cgi?id=791154 I was asked to report this bug report on launchpad.net and to state: "I am requesting the commit to be backported." I am not sure how this reporting all works. Thank you for looking into it. Nathaniel --- 1) Running fully updated Ubuntu 17.10 - Rhythmbox 3.4.1-2ubuntu5 2) apt-cache policy pkgname N: Unable to locate package pkgname 3) downloading mp3 file form rss feed 4) it is downloading the png file instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1738110/+subscriptions -- Mailing list: https://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 1778844] Re: nvme multipath does not report path relationships
The system has too many devices, so too many drivers are using too much memory. So, the system goes out-of-memory before makedumpfile is complete. Please, reserve more memory on crashkernel, reboot the system and repeat the crash test. To reserve more memory on crashkernel, edit file /etc/default/grub.d /kdump-tools.cfg and change crashkernel value to crashkernel=384M, for example, then run update-grub. Thanks. Cascardo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368
