[Touch-packages] [Bug 1537056] Re: apt-add-repository always returns "user or team does not exist." for ppa repos
Hi,How did you finally solve this problem?
i am in add
sudo -E add-apt-repository ppa:mosquitto-dev/mosquitto-ppa
exception message:
Cannot add PPA: 'ppa:~mosquitto-dev/ubuntu/mosquitto-ppa'.
ERROR: '~mosquitto-dev' user or team does not exist.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1537056
Title:
apt-add-repository always returns "user or team does not exist." for
ppa repos
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
I have just installed a fresh Ubuntu 15.10 to my machine and run into
trouble with adding ppa repositories using apt-add-repository:
for e.g. running
apt-add-repository ppa:git-core/ppa
Cannot add PPA: 'ppa:~git-core/ubuntu/ppa'.
ERROR: '~git-core' user or team does not exist.
After debugging a lot of code, I found the trouble, the used proxy-
server needs authentification but the apt-add-repository does not
throw a correct error message fro this case:
The PPAException raised here seems to be interpreted as not available,
which is rather hard to debug.
def _get_https_content_py3(lp_url):
print("RETRIEVING URL: %s"%lp_url)
try:
request = urllib.request.Request(str(lp_url), headers={"Accept":"
application/json"})
lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
json_data = lp_page.read().decode("utf-8", "strict")
print("RV: %s"%str(json_data))
except (URLError, HTTPException) as e:
# HTTPException doesn't have a reason but might have a string
# representation
print(e)
reason = hasattr(e, "reason") and e.reason or e
raise PPAException("Error reading %s: %s" % (lp_url, reason), e)
The last print(e) gives me the hint what went wrong:
For the future it would be great to get a correct error message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1537056/+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 882878] Re: With IPv6 disabled, openssh will not forward X connections
Found this page while tracing for the fix to this very bug. I can't believe that after 6+ years, it is still not fixed. Hope it can be fixed soon... -- 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/882878 Title: With IPv6 disabled, openssh will not forward X connections Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Status in openssh package in openSUSE: Fix Released Bug description: If you disable IPv6 in /etc/sysctl.conf sshd will not forward X11. It logs the failue in /var/log/auth.log Oct 27 18:49:26 uscps002 sshd[14722]: Accepted password for root from 172.20.10.50 port 60322 ssh2 Oct 27 18:49:26 uscps002 sshd[14722]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 27 18:49:27 uscps002 sshd[14722]: error: Failed to allocate internet-domain X11 display socket. Aparently the compiled sshd version will not try an ipv4 localhost if an ipv6 localhost does not exist. Placing the following line in /etc/ssh/sshd_config fixes the issue X11UseLocalHost no root@uscps002:/var/log# lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 root@uscps002:/var/log# root@uscps002:/var/log# uname -a Linux uscps002 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/882878/+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 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output
That's an entirely different issue, as Manfred has put it, This is support for Ubuntu only, and not for other operating systems "based on Ubuntu" like elementary OS. No matter how close you think yours is to Ubuntu, if it is not then it is not. Please don't spill your own problem over to other unrelated issues. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1639513 Title: Pango-WARNING **: shaping failure, expect ugly output Status in pango1.0 package in Ubuntu: Confirmed Bug description: Exactly as reported in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which was marked as "Invalid" because it is reporting to the wrong package. The problem from that post: Console: $ evince (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'Ubuntu 11' (evince:8959): Pango-WARNING **: font_face status is: out of memory (evince:8959): Pango-WARNING **: scaled_font status is: out of memory (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Ubuntu 11', text='●' As for mine, it is basically the same: (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is '微软雅黑 9' (process:13924): Pango-WARNING **: font_face status is: file not found (process:13924): Pango-WARNING **: scaled_font status is: file not found (process:13924): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg' As the result, For the original reported, "some font and only displays squares in menus, text is displayed okay,", but for me, everything are displays as squares in menus, including English texts. However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly without any problem. The cause of the problem, is also exactly as described in the original post: It happens because of symlinks from /usr/share/fonts to a different partition. For the original reporter, some fonts are symlinked, and for me 微软雅黑 is symlinked to a different partition. Thus his is missing some text, while I'm missing everything. symlinking fonts to a different partition is quite harmless in my view, and Pango should not treat them any differently. This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK. My current Pango related packages that exhibit such problem: gir1.2-pango-1.0:amd64_1.38.1-1 libcogl-pango20:amd64_1.22.0-2 libpango-1.0-0:amd64_1.38.1-1 libpango-perl_1.227-1 libpango1.0-0:amd64_1.38.1-1 libpangocairo-1.0-0:amd64_1.38.1-1 libpangoft2-1.0-0:amd64_1.38.1-1 libpangomm-1.4-1v5:amd64_2.38.1-1 libpangox-1.0-0:amd64_0.0.2-5 libpangoxft-1.0-0:amd64_1.38.1-1 Please look into it. Thx. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+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 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output
Sorry, I apologize. One thing I didn't mention is that this issue was already nearly 2 years old, and has a clear cause, so it is very unlikely to relate to any other recent issues. But anyway. Sorry for my bad attitude. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1639513 Title: Pango-WARNING **: shaping failure, expect ugly output Status in pango1.0 package in Ubuntu: Confirmed Bug description: Exactly as reported in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which was marked as "Invalid" because it is reporting to the wrong package. The problem from that post: Console: $ evince (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'Ubuntu 11' (evince:8959): Pango-WARNING **: font_face status is: out of memory (evince:8959): Pango-WARNING **: scaled_font status is: out of memory (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Ubuntu 11', text='●' As for mine, it is basically the same: (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is '微软雅黑 9' (process:13924): Pango-WARNING **: font_face status is: file not found (process:13924): Pango-WARNING **: scaled_font status is: file not found (process:13924): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg' As the result, For the original reported, "some font and only displays squares in menus, text is displayed okay,", but for me, everything are displays as squares in menus, including English texts. However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly without any problem. The cause of the problem, is also exactly as described in the original post: It happens because of symlinks from /usr/share/fonts to a different partition. For the original reporter, some fonts are symlinked, and for me 微软雅黑 is symlinked to a different partition. Thus his is missing some text, while I'm missing everything. symlinking fonts to a different partition is quite harmless in my view, and Pango should not treat them any differently. This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK. My current Pango related packages that exhibit such problem: gir1.2-pango-1.0:amd64_1.38.1-1 libcogl-pango20:amd64_1.22.0-2 libpango-1.0-0:amd64_1.38.1-1 libpango-perl_1.227-1 libpango1.0-0:amd64_1.38.1-1 libpangocairo-1.0-0:amd64_1.38.1-1 libpangoft2-1.0-0:amd64_1.38.1-1 libpangomm-1.4-1v5:amd64_2.38.1-1 libpangox-1.0-0:amd64_0.0.2-5 libpangoxft-1.0-0:amd64_1.38.1-1 Please look into it. Thx. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+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 1948364] [NEW] Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot
Public bug reported: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl log about static IP" https://bugs.launchpad.net/bugs/1948364/+attachment/5534988/+files/Static_IP_loss_2021-10-22_10-27-30.log -- 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/1948364 Title: Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot Status in network-manager package in Ubuntu: New Bug description: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948364/+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 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
any suggestion to fix this?
I had tried below command.
root@plis231v:~# sudo dpkg -l | grep systemd
ii libpam-systemd:amd64 229-4ubuntu21.31+esm1
amd64system and service manager - PAM mod
ii libsystemd0:amd64 229-4ubuntu21.31+esm1
amd64systemd utility library
ii python3-systemd231-2build1
amd64Python 3 bindings for systemd
ii systemd229-4ubuntu21.31+esm1
amd64system and service manager
rc systemd-services 204-5ubuntu20.31
amd64systemd runtime services
ii systemd-shim 9-1bzr4ubuntu1
amd64shim for systemd
root@plis231v:~#
root@plis231v:~#
root@plis231v:~#
root@plis231v:~# apt-get install --reinstall systemd
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/3,659 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 77423 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu21.31+esm1_amd64.deb ...
Unpacking systemd (229-4ubuntu21.31+esm1) over (229-4ubuntu21.31+esm1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.6+esm1) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
ureadahead will be reprofiled on next reboot
Setting up systemd (229-4ubuntu21.31+esm1) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Operation failed: No such file or directory
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
root@plis231v:~# systemctl status
Failed to read server status: Invalid argument
root@plis231v:~#
root@plis231v:~#
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.
[Touch-packages] [Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
root@plis231v:~# ps -o cmd fp 1
CMD
/sbin/init
root@plis231v:~# sudo ls -lah /proc/1/exe
lrwxrwxrwx 1 root root 0 Feb 11 22:51 /proc/1/exe -> /sbin/upstart
root@plis231v:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-167-generic root=/dev/mapper/plis231v-root ro quiet
root@plis231v:~#
--
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/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
Status in snapd package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
>> logs
22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file:
/var/lib/ubuntu-advantage/notices.json
2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception,
please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in
wrapper
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
return args.action(args, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
return f(args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
retval = f(*args, cfg=cfg, **kwargs)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in
action_enable
ent_ret, reason = entitlement.enable()
File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line
197, in enable
ret = self._perform_enable(silent=silent)
File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py",
line 160, in _perform_ena
[snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
out, err = _subp(args, rcs, capture, timeout, env=env)
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
stderr=err.decode("utf-8"),
uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap
wait system seed.loaded' [sage: error: cannot communicate with server: Get
http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket:
connect: no such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-advantage-tools 27.4.1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-167-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm3
Architecture: amd64
Date: Fri Feb 11 23:01:08 2022
InstallationDate: Installed on 2010-12-02 (4089 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+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 1692338] [NEW] package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1
Public bug reported: sudo apt-get -f install 正在读取软件包列表... 完成 正在分析软件包的依赖关系树 正在读取状态信息... 完成 将会同时安装下列软件： apport 下列软件包将被升级： apport 升级了 1 个软件包，新安装了 0 个软件包，要卸载 0 个软件包，有 118 个软件包未被升级。 有 74 个软件包没有被完全安装或卸载。 需要下载 0 B/120 kB 的归档。 解压缩后会消耗 0 B 的额外空间。 您希望继续执行吗？ [Y/n] y (正在读取数据库 ... 系统当前共安装有 335730 个文件和目录。) 正准备解包 .../apport_2.20.1-0ubuntu2.4_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg：警告：子进程 旧的 pre-removal 脚本 返回错误状态 1 dpkg: 现在尝试使用新软件包所带的脚本... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg: 处理归档 /var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb (--unpack)时出错： 子进程 新的 pre-removal 脚本 返回错误状态 1 Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg：清理时出错: 子进程 已安装 post-installation 脚本 返回错误状态 1 在处理时有错误发生： /var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashReports: 600:0:116:85235:2017-05-22 09:00:58.731974601 +0800:2017-05-22 09:00:59.731974601 +0800:/var/crash/apport.0.crash 640:0:116:14080:2017-05-22 09:00:59.055974600 +0800:2017-05-22 09:00:59.055974600 +0800:/var/crash/_usr_bin_pyclean.0.crash Date: Mon May 22 09:00:59 2017 DpkgHistoryLog: Start-Date: 2017-05-22 09:00:56 Commandline: apt-get -f install Requested-By: nirvana (1000) Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.4) ErrorMessage: 子进程 新的 pre-removal 脚本 返回错误状态 1 InstallationDate: Installed on 2016-10-13 (220 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1692338 Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1 Status in apport package in Ubuntu: New Bug description: sudo apt-get -f install 正在读取软件包列表... 完成 正在分析软件包的依赖关系树 正在读取状态信息... 完成 将会同时安装下列软件： apport 下列软件包将被升级： apport 升级了 1 个软件包，新安装了 0 个软件包，要卸载 0 个软件包，有 118 个软件包未被升级。 有 74 个软件包没有被完全安装或卸载。 需要下载 0 B/120 kB 的归档。 解压缩后会消耗 0 B 的额外空间。 您希望继续执行吗？ [Y/n] y (正在读取数据库 ... 系统当前共安装有 335730 个文件和目录。) 正准备解包 .../apport_2.20.1-0ubuntu2.4_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg：警告：子进程 旧的 pre-removal 脚本 返回错误状态 1 dpkg: 现在尝试使用新软件包所带的脚本... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg: 处理归档 /var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb (--unpack)时出错： 子进程 新的 pre-removal 脚本 返回错误状态 1 Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg：清理时出错: 子进程 已安装 post-installation 脚本 返回错误状态 1 在处理时有错误发生： /var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashReports: 600:0:116:85235:2017-05-22 09:00:58.731974601 +0800:2017-05-22 09:00:59.731974601 +0800:/var/crash/apport.0.crash 640:0:116:14080:2017-05-22 09:00:59.055974600 +0800:2017-05-22 09:00:59.055974600 +0800:/var/crash/_usr_bin_pyclean.0.crash Date: Mon May 22 09:00:59 2017 DpkgHistoryLog: Start-Date: 2017-05-22 09:00:56 Commandline: apt-get -f install Requested-By: nirvana (1000) Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.4) ErrorMessage: 子进程 新的 pre-removal 脚本 返回错误状
[Touch-packages] [Bug 1387428] Re: Elantech Touchpad input device freezes in x
** Changed in: xorg (Ubuntu) Status: Expired => Confirmed -- 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/1387428 Title: Elantech Touchpad input device freezes in x Status in xorg package in Ubuntu: Confirmed Bug description: terminal switching fixes this problem but this is super annoying ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.46 Wed Sep 24 14:23:40 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [240G [234G[ OK ] * Starting early crypto disks... [240G [234G[ OK ] CurrentDesktop: Unity Date: Thu Oct 30 12:20:28 2014 DistUpgraded: 2014-10-29 13:02:20,451 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed nvidia-340, 340.46, 3.16.0-23-generic, x86_64: installed nvidia-340-uvm, 340.46, 3.16.0-23-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:131d] Subsystem: ASUSTeK Computer Inc. Device [1043:131d] InstallationDate: Installed on 2014-10-28 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed root=UUID=7842396f-3697-4d0f-ab35-a2f9ed87a17d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-29 (0 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LN.306:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141006.00847fa4-0ubuntu0ricotz version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20141023.065256df-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0~git20141023.065256df-0ubuntu0ricotz version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0+git20140806+server-1.16-branch.a793483e-0ubuntu0sarvatt version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141016.6b98f162-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Oct 29 22:08:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5572 vendor CMN xserver.version: 2:1.16.0+git20140806+server-1.16-branch.a793483e-0ubuntu0sarvatt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1387428/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
This issue doesn't reproduce on 22.04 Live server image, its '/usr/lib/systemd/system/systemd-networkd.socket' is same with 22.04 Desktop image, so looks like shutdown.target in systemd-networkd.socket is not the root cause. I think the systemd dependence is quite different between Desktop and Server images, please systemd experts look into this. By running below command on Ubuntu 21.04 Desktop, Ubuntu 22.04 Desktop and Ubuntu 22.04 Server VMs, got some .svg files, attached them in svg_files.zip to this bug for your reference. 1. systemd-analyze plot > plot2104_desktop.svg 2. systemd-analyze plot > plot2204_desktop.svg 3. systemd-analyze plot > plot2204_server.svg 4. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2104_desktop.svg 5. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2204_desktop.svg 6. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2204_server.svg According to the plot output, systemd-networkd starts late only on Ubuntu 22.04 Desktop VM, this leads to customization command 'netplan apply' fail. ** Attachment added: "svg files" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+attachment/5566877/+files/svg_files.zip -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
According to our investigation, I found that the issue is caused by the "mount" system call can not be allowed to execute. And after checking the upstream commit, the issue is introduced by the following patch, commit ee8f26180d01e3ddd4e5f20b03b81e5e737657ae Author: Lennart Poettering Date: Thu Apr 19 11:04:17 2018 +0200 units: switch from system call blacklist to whitelist This is generally the safer approach, and is what container managers (including nspawn) do, hence let's move to this too for our own services. This is particularly useful as this this means the new @system-service system call filter group will get serious real-life testing quickly. This also switches from firing SIGSYS on unexpected syscalls to returning EPERM. This would have probably been a better default anyway, but it's hard to change that these days. When whitelisting system calls SIGSYS is highly problematic as system calls that are newly introduced to Linux become minefields for services otherwise. Note that this enables a system call filter for udev for the first time, and will block @clock, @mount and @swap from it. Some downstream distributions might want to revert this locally if they want to permit unsafe operations on udev rules, but in general this shiuld be mostly safe, as we already set MountFlags=shared for udevd, hence at least @mount won't change anything. Before the patch，systemd-udevd.service has not set “SystemCallFilter=”，but after the patch，the “SystemCallFilter=@system- service @module @raw-io” was added diff --git a/units/systemd-udevd.service.in b/units/systemd-udevd.service.in index 2b9fa69d9b..6a3814e5d9 100644 --- a/units/systemd-udevd.service.in +++ b/units/systemd-udevd.service.in @@ -29,6 +29,8 @@ PrivateMounts=yes MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 +SystemCallFilter=@system-service @module @raw-io +SystemCallErrorNumber=EPERM SystemCallArchitectures=native LockPersonality=yes IPAddressDeny=any Because there is no "SystemCallFilter=@system-service @module @raw-io" in the /usr/lib/systemd/system/systemd-udevd.service on UBuntu20.04, we can not experience the same issue, but can reproduce the issue on UBuntu22.04. If we add "@mount" to "SystemCallFilter=" on UBuntu22.04, the issue can be fixed. Thanks, Regards, Jiwei -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in systemd package in Ubuntu: New Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966203/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
VMware internal bug for this is 2928681. -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Appreciate your help, Christian. I'm trying to find a way to reproduce this issue without vSphere, will post it here once get it. -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Yes, same here. I got the same good news with beta image. Christian, thanks for your help again. I think we can close this bug for now. -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Hi @Nick Rosbrook (enr0n) Will any modification(regarding snapd udev rule) be included in the Ubuntu 22.04 release version? Thanks, Regards, Jiwei -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 2022825] Re: motd-news.timer trigger motd-news.service even if disable
> The documentation tells users how to disable the service without having to know systemd service interfaces. Which is: > /etc/default/motd-news has an ENABLED=1 setting that if set to 0 will turn off this functionality. And this is not working, as reported by Nadav. My modt keep getting errors when i run commend "systemctl status" too. Mine is: $ sudo systemctl status motd-news.service à motd-news.service - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.service; static) Active: failed (Result: exit-code) since Sun 2023-09-24 12:40:01 EDT; 6h ago TriggeredBy: â motd-news.timer Docs: man:update-motd(8) Process: 375394 ExecStart=/etc/update-motd.d/50-motd-news --force (code=exited, status=203/EXEC) Main PID: 375394 (code=exited, status=203/EXEC) CPU: 9ms Sep 24 12:40:01 lplat systemd[1]: Starting Message of the Day... Sep 24 12:40:01 lplat systemd[375394]: motd-news.service: Failed to locate executable /etc/update-motd.d/50-motd-news: Permission> Sep 24 12:40:01 lplat systemd[375394]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permissio> Sep 24 12:40:01 lplat systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC Sep 24 12:40:01 lplat systemd[1]: motd-news.service: Failed with result 'exit-code'. Sep 24 12:40:01 lplat systemd[1]: Failed to start Message of the Day. $ sudo journalctl -u motd-news.service Aug 17 16:57:01 . systemd[1]: Starting Message of the Day... Aug 17 16:57:01 . systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC Aug 17 16:57:01 . systemd[1]: motd-news.service: Failed with result 'exit-code'. Aug 17 16:57:01 . systemd[1]: Failed to start Message of the Day. Aug 18 01:35:30 . systemd[52283]: motd-news.service: Failed to locate executable /etc/update-motd.d/50-motd-news: Permission denied Aug 18 01:35:30 . systemd[1]: Starting Message of the Day... Aug 18 01:35:30 . systemd[52283]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permission denied Aug 18 01:35:30 . systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC Aug 18 01:35:30 . systemd[1]: motd-news.service: Failed with result 'exit-code'. Aug 18 01:35:30 . systemd[1]: Failed to start Message of the Day. . . . $ ls -l /etc/update-motd.d/50-motd-news -rw-r--r-- 1 root root 5023 2021-10-15 06:06 /etc/update-motd.d/50-motd-news How did you disable the timer, Nadav? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2022825 Title: motd-news.timer trigger motd-news.service even if disable Status in base-files package in Ubuntu: Incomplete Bug description: Hello, guys, how are you? I notice motd-news.timer activate motd-news.service even when motd-new.service disable. I follow this doc's from UBUNTU: https://ubuntu.com/legal/motd /etc/default/motd-news has an ENABLED=1 setting that to 0 for disable. It's not working too… When you reboot the server and put sudo systemctl status motd-news.service Service look dead. (disable) but he got trigger by motd-news.timer after 10 - 20 minutes (screenshot): https://ibb.co/yXTpzGq if you look on the screenshot, you will see: TriggeredBy: ● motd-news.timer I can disable the motd-news.timer service, but i don't know if it will affect other services of UBUNTU. Anyway It's still a bug, even if i disable the timer service, it's not should be this way. Happened on 2 Different machines of UBUNTU 22.04 (Google Cloud Platform) Be happy for your recommendation before i disable the motd-new.timer with systemctl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2022825/+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 2024969] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned er
Public bug reported: / ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chuyues1133 F pulseaudio /dev/snd/controlC1: chuyues1133 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Jun 24 17:24:56 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 MachineType: Alienware Alienware Aurora R12 PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=a089e437-b437-482c-a957-d55995aae5a7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.1 dmi.bios.vendor: Alienware dmi.bios.version: 1.1.4 dmi.board.name: 0P0JWX dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.1.4:bd07/08/2021:br1.1:svnAlienware:pnAlienwareAuroraR12:pvr1.1.4:rvnAlienware:rn0P0JWX:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku0A63: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R12 dmi.product.sku: 0A63 dmi.product.version: 1.1.4 dmi.sys.vendor: Alienware ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2024969 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: / ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chuyues1133 F pulseaudio /dev/snd/controlC1: chuyues1133 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Jun 24 17:24:56 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 MachineType: Alienware Alienware Aurora R12 PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=a089e437-b437-482c-a957-d55995aae5a7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.1 dmi.bios.vendor: Alienware dmi.bios.version: 1.1.4 dmi.board.name: 0P0JWX dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.1.4:bd07/08/2021:br1.1:svnAlienware:pnAlienwareAuroraR12:pvr1.1.4:rvnAlienware:rn0P0JWX:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku0A63: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R12 dmi.product.sku: 0A63 dmi.product.version: 1.1.4 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024969/+subscriptions --
[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Thanks for the confirmation! -- 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/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Invalid Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1850775] [NEW] DNS info is not loaded by dhclient
Public bug reported: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: cloud-init (Ubuntu) => network-manager (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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1850775] Re: DNS info is not loaded by dhclient
Thanks Till, which systemd service's dependency got changed? I compared /lib/systemd/system/systemd-resolved.conf between 18.04 and 19.10, they are same. There is "After=systemd-sysusers.service systemd- networkd.service". I do NOT know when and who triggers /etc/dhcp/dhclient-enter- hooks.d/resolved script at boot, but it's possible that when this script executed, systemd-resolved.service is not ready for reload or restart. -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1850775] Re: DNS info is not loaded by dhclient
Thanks @Dan, I applied the patch https://launchpadlibrarian.net/448207988/resolved.patch to my VM, but the issue is still reproducing. The md5sum line is before creating "$statedir/isc-dhcp-v4-$interface.conf", while I can see the isc-dhcp-v4-$interface.conf file is created on my VM. I think the root cause is not same with bug 1849608 -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1850775] Re: DNS info is not loaded by dhclient
@Dan, The issue is resolved by your fix. Instead of only changing /etc/dhcp/dhclient-enter-hooks.d/resolved script, I added your repository "ppa:ddstreet/systemd" and updated/upgraded systemd, then the issue was NOT reproducing. -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1850775] Re: DNS info is not loaded by dhclient
@Dan, could you please confirm if your fix will be patched on Ubuntu19.10? If yes, when it will happen? -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1850775] Re: DNS info is not loaded by dhclient
@Balint, thanks a lot for the information. -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Hi team, Please let us know if this is as-designed or not, Ubuntu desktop version was using /etc/network/interfaces to configure static IP address and etc... Best regards, Pengpeng -- 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/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Hi Joshua, Thanks for your reply. Could you please confirm if all Ubuntu types uses Netplan from 19.10, I noticed from 17.10 to 19.04, Desktop type has ifupdown, Server and Live Server are using Netplan. Thanks, Pengpeng ** Changed in: network-manager (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: New Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Re-new this bug for requesting above confirmation. -- 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/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: New Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1414887] [NEW] dns query from localnetwork are blocked
Public bug reported: Hi, I followed the following to config dnsmasq as DHCP and DNS server http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation- configuration-5/ It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns query from localnetwork will always timeout. The configurations are exactly the same, What could be the problem? >From within localnetwork: ~~~ $ dig google.ca ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca ;; global options: +cmd ;; connection timed out; no servers could be reached dig @192.168.2.100 maroon ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ~~~ On the DNS sever itself: ~~~ $ dig google.ca @127.0.0.1 ... ;; ANSWER SECTION: google.ca. 299 IN A 173.194.43.111 ... ;; Query time: 50 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig @192.168.2.100 maroon ... ;; ANSWER SECTION: maroon. 0 IN A 192.168.2.100 ;; Query time: 1 msec ;; SERVER: 192.168.2.100#53(192.168.2.100) ... ~~~ This is the debug output from dnsmasq log: ~~~ Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119 Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120 *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** Jan 1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100 Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is 192.168.2.100 *** DEBUG 2015-01-01 13:28:19-05:00 DEBUG *** ~~~ All other dns queries from localnetwork did not generate any log entries. So, because the local dns query work, I think something is blocking the dnsmasq from sending the dns query results back to localnetwork. What could it be? I didn't limit the dnsmasq listen address: ~~~ $ grep listen-address /etc/dnsmasq.conf /etc/dnsmasq.d/* /etc/dnsmasq.conf:#listen-address= ~~~ My /etc/hosts.deny and hosts.allow files are untouched either, and I can ping my DNS server, and ssh into its IP address as well. So I think the blocking is only at the DNS level since other access are just fine. It is not because of iptables rules either: $ sudo iptables-save | wc 0 0 0 I've installed dnsmasq on two different machines, one being freshly installed today, and both of them are showing exactly the same symptom. Again, it only happens to Ubuntu 14.10. It was working well till Ubuntu 13.10 before. I've run out of all the possibilities. What could be the problem? Thanks $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic $ apt-cache policy dnsmasq dnsmasq: Installed: 2.71-1 Candidate: 2.71-1 Version table: *** 2.71-1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, - I following the following to config dnsmasq as DHCP and DNS server + I followed the following to config dnsmasq as DHCP and DNS server http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation- configuration-5/ - It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns - query from localnetwork will always timeout. The configurations are - exactly the same, What could be the problem? + It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns + query from localnetwork will always timeout. The configurations are + exactly the same, What could be the problem? From within localnetwork: ~~~ $ dig google.ca ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca ;; global options: +cmd ;; connection timed out; no servers could be reached dig @192.168.2.100 maroon ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ~~~ On the DNS sever itself: ~~~ $ dig google.ca @127.0.0.1 ... ;; ANSWER SECTION: google.ca. 299 IN A 173.194.43.111 ... ;; Query time: 50 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig @192.168.2.100 maroon ... ;; ANSWER SECTION: maroon. 0 IN A 192.168.2.100 ;; Query time: 1 msec ;; SERVER: 192.168.2.100#53(192.168.2.100) ... ~~~ This is the debug output from dnsmasq log: ~~~ Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119 Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120 - *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** + *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** Jan 1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100 - Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is + Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is 192.168.2.100 - *** DEBUG 201
[Touch-packages] [Bug 1414887] Re: dns query from localnetwork ignored
** Summary changed: - dns query from localnetwork are blocked + dns query from localnetwork ignored -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1414887 Title: dns query from localnetwork ignored Status in dnsmasq package in Ubuntu: Incomplete Bug description: Hi, I followed the following to config dnsmasq as DHCP and DNS server http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation- configuration-5/ It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns query from localnetwork will always timeout. The configurations are exactly the same, What could be the problem? From within localnetwork: ~~~ $ dig google.ca ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca ;; global options: +cmd ;; connection timed out; no servers could be reached dig @192.168.2.100 maroon ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ~~~ On the DNS sever itself: ~~~ $ dig google.ca @127.0.0.1 ... ;; ANSWER SECTION: google.ca. 299 IN A 173.194.43.111 ... ;; Query time: 50 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig @192.168.2.100 maroon ... ;; ANSWER SECTION: maroon. 0 IN A 192.168.2.100 ;; Query time: 1 msec ;; SERVER: 192.168.2.100#53(192.168.2.100) ... ~~~ This is the debug output from dnsmasq log: ~~~ Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119 Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120 *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** Jan 1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100 Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is 192.168.2.100 *** DEBUG 2015-01-01 13:28:19-05:00 DEBUG *** ~~~ All other dns queries from localnetwork did not generate any log entries. So, because the local dns query work, I think something is blocking the dnsmasq from sending the dns query results back to localnetwork. What could it be? I didn't limit the dnsmasq listen address: ~~~ $ grep listen-address /etc/dnsmasq.conf /etc/dnsmasq.d/* /etc/dnsmasq.conf:#listen-address= ~~~ My /etc/hosts.deny and hosts.allow files are untouched either, and I can ping my DNS server, and ssh into its IP address as well. So I think the blocking is only at the DNS level since other access are just fine. It is not because of iptables rules either: $ sudo iptables-save | wc 0 0 0 I've installed dnsmasq on two different machines, one being freshly installed today, and both of them are showing exactly the same symptom. Again, it only happens to Ubuntu 14.10. It was working well till Ubuntu 13.10 before. I've run out of all the possibilities. What could be the problem? Thanks $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic $ apt-cache policy dnsmasq dnsmasq: Installed: 2.71-1 Candidate: 2.71-1 Version table: *** 2.71-1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1414887/+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 1414887] Re: dns query from localnetwork ignored
Ah, thanks Thomas. You lead me to the right direction. As Simon Kelley, the author of dnsmasq said in the new dnsmasq manpag, `local-service` is intended to be set as a default on installation, to allow unconfigured installations to be useful... it will have no effect, but for otherwise-unconfigured installations, it stops dnsmasq from being vulnerable to DNS-reflection attacks, I'm changing this bug report to bear the purpose to have dnsmasq better configured out of box for Ubuntu (14.10+). - First, as suggested by the author of dnsmasq, the `local-service` should be in the default configuration. However, Ubuntu 14.10 doesn't have that: % cat /etc/dnsmasq.conf /etc/dnsmasq.d/network-manager | sed '/^$/d; /^#/d' bind-interfaces - Second, unlike its previous version, Ubuntu 14.10 now starts dnsmasq in a very restricted way. Here is what I found out how dnsmasq is started in Ubuntu 14.10: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf- file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d I.e., that ` --listen-address=127.0.1.1` will willfully ignore any dns queries from localnetwork. This is the exact reason causing the symptom that I reported. I believe this setting should not be there, because 1. for people that need the setting, it is very easy to put it into a conf file under /etc/dnsmasq.d/; 2. however, it will make it very very difficult for people who don't need it to get rid of it unless altering the package installation. 3. Ubuntu should really ship the default setting of `local-service` instead of `listen-address`, because it is a safer default and not invasive in the meantime. it will "have no effect" but for an otherwise-unconfigured installation. Please consider. Meanwhile, is there any better way to get rid of that ` --listen- address=127.0.1.1`? The least that I want is to altering the package installation. Thanks ** Changed in: dnsmasq (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1414887 Title: dns query from localnetwork ignored Status in dnsmasq package in Ubuntu: New Bug description: Hi, I followed the following to config dnsmasq as DHCP and DNS server http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation- configuration-5/ It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns query from localnetwork will always timeout. The configurations are exactly the same, What could be the problem? From within localnetwork: ~~~ $ dig google.ca ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca ;; global options: +cmd ;; connection timed out; no servers could be reached dig @192.168.2.100 maroon ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ~~~ On the DNS sever itself: ~~~ $ dig google.ca @127.0.0.1 ... ;; ANSWER SECTION: google.ca. 299 IN A 173.194.43.111 ... ;; Query time: 50 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) $ dig @192.168.2.100 maroon ... ;; ANSWER SECTION: maroon. 0 IN A 192.168.2.100 ;; Query time: 1 msec ;; SERVER: 192.168.2.100#53(192.168.2.100) ... ~~~ This is the debug output from dnsmasq log: ~~~ Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119 Jan 1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120 *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG *** Jan 1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100 Jan 1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is 192.168.2.100 *** DEBUG 2015-01-01 13:28:19-05:00 DEBUG *** ~~~ All other dns queries from localnetwork did not generate any log entries. So, because the local dns query work, I think something is blocking the dnsmasq from sending the dns query results back to localnetwork. What could it be? I didn't limit the dnsmasq listen address: ~~~ $ grep listen-address /etc/dnsmasq.conf /etc/dnsmasq.d/* /etc/dnsmasq.conf:#listen-address= ~~~ My /etc/hosts.deny and hosts.allow files are untouched either, and I can ping my DNS server, and ssh into its IP address as well. So I think the blocking is only at the DNS level since other access are just fine. It is not because of iptables rules either: $ sudo iptables-save | wc 0 0 0 I've installed dnsmasq on two different machines, one being freshly installed today, and both of them are showing exactly the same symptom. Again, it only happens to Ubuntu 14.
[Touch-packages] [Bug 1416728] [NEW] systemd-analyze failed: No such method 'ListUnits'
Public bug reported: Problem: % systemd-analyze dot > /tmp/systemd0.dot Failed to issue method call: No such method 'ListUnits' ^^ $ apt-cache policy systemd systemd: Installed: 208-8ubuntu8.2 Candidate: 208-8ubuntu8.2 Version table: *** 208-8ubuntu8.2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 100 /var/lib/dpkg/status 208-8ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages ProblemType: Bug ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Jan 31 14:35:18 2015 Dependencies: acl 2.2.52-1.1 adduser 3.113+nmu3ubuntu3 apt 1.0.9.2ubuntu2 apt-utils 1.0.9.2ubuntu2 busybox-initramfs 1:1.22.0-8ubuntu1 cgmanager 0.32-4ubuntu1 coreutils 8.23-2ubuntu3 cpio 2.11+dfsg-2ubuntu1 dbus 1.8.8-1ubuntu2 debconf 1.5.53ubuntu1 debianutils 4.4 dmsetup 2:1.02.77-6ubuntu2 dpkg 1.17.13ubuntu1 e2fslibs 1.42.10-1.1ubuntu1 e2fsprogs 1.42.10-1.1ubuntu1 findutils 4.4.2-9 gcc-4.9-base 4.9.1-16ubuntu6 gnupg 1.4.16-1.2ubuntu1 gpgv 1.4.16-1.2ubuntu1 ifupdown 0.7.48.1ubuntu5 init-system-helpers 1.20ubuntu3 initramfs-tools 0.103ubuntu8 initramfs-tools-bin 0.103ubuntu8 initscripts 2.88dsf-41ubuntu18 insserv 1.14.0-5ubuntu2 iproute2 3.16.0-2 isc-dhcp-client 4.2.4-7ubuntu14 isc-dhcp-common 4.2.4-7ubuntu14 klibc-utils 2.0.3-0ubuntu1 kmod 18-1ubuntu2 libacl1 2.2.52-1.1 libapparmor1 2.8.98-0ubuntu2 libapt-inst1.5 1.0.9.2ubuntu2 libapt-pkg4.12 1.0.9.2ubuntu2 libattr1 1:2.4.47-2 libaudit-common 1:2.3.7-1ubuntu1 libaudit1 1:2.3.7-1ubuntu1 libblkid1 2.25.1-3ubuntu4 libbz2-1.0 1.0.6-5ubuntu5 libc6 2.19-10ubuntu2 libcap-ng0 0.7.4-2 libcap2 1:2.24-0ubuntu2 libcap2-bin 1:2.24-0ubuntu2 libcgmanager0 0.32-4ubuntu1 libcomerr2 1.42.10-1.1ubuntu1 libcryptsetup4 2:1.6.1-1ubuntu3 libdb5.3 5.3.28-5 libdbus-1-3 1.8.8-1ubuntu2 libdevmapper1.02.1 2:1.02.77-6ubuntu2 libexpat1 2.1.0-6ubuntu1 libffi6 3.1-2 libgcc1 1:4.9.1-16ubuntu6 libgcrypt11 1.5.4-2ubuntu1 libgdbm3 1.8.3-13 libglib2.0-0 2.42.0-2 libglib2.0-data 2.42.0-2 libgpg-error0 1.13-4 libgpm2 1.20.4-6.1 libklibc 2.0.3-0ubuntu1 libkmod2 18-1ubuntu2 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.25.1-3ubuntu4 libncurses5 5.9+20140712-2ubuntu1 libncursesw5 5.9+20140712-2ubuntu1 libnih-dbus1 1.0.3-4ubuntu26 libnih1 1.0.3-4ubuntu26 libpam-cap 1:2.24-0ubuntu2 libpam-modules 1.1.8-3ubuntu4 libpam-modules-bin 1.1.8-3ubuntu4 libpam-runtime 1.1.8-3ubuntu4 libpam-systemd 208-8ubuntu8.2 libpam0g 1.1.8-3ubuntu4 libpcre3 1:8.35-3ubuntu1 libpng12-0 1.2.51-0ubuntu3 libprocps3 1:3.3.9-1ubuntu5 libreadline6 6.3-8ubuntu1 libselinux1 2.3-1build1 libsemanage-common 2.3-1 libsemanage1 2.3-1 libsepol1 2.3-2 libslang2 2.2.4-17ubuntu1 libsmartcols1 2.25.1-3ubuntu4 libss2 1.42.10-1.1ubuntu1 libstdc++6 4.9.1-16ubuntu6 libsystemd-daemon0 208-8ubuntu8.2 libsystemd-journal0 208-8ubuntu8.2 libsystemd-login0 208-8ubuntu8.2 libtinfo5 5.9+20140712-2ubuntu1 libudev1 208-8ubuntu8 libusb-0.1-4 2:0.1.12-24 libustr-1.0-1 1.0.4-3ubuntu2 libuuid1 2.25.1-3ubuntu4 libwrap0 7.6.q-25 libxml2 2.9.1+dfsg1-4ubuntu1 libxtables10 1.4.21-2ubuntu1 lsb-base 4.1+Debian11ubuntu8 module-init-tools 18-1ubuntu2 mount 2.25.1-3ubuntu4 multiarch-support 2.19-10ubuntu2 netbase 5.2 passwd 1:4.1.5.1-1.1ubuntu2 perl 5.20.1-1 perl-base 5.20.1-1 perl-modules 5.20.1-1 procps 1:3.3.9-1ubuntu5 psmisc 22.21-2 readline-common 6.3-8ubuntu1 sed 4.2.2-4ubuntu1 sensible-utils 0.0.9 sgml-base 1.26+nmu4ubuntu1 shared-mime-info 1.2-0ubuntu3 systemd 208-8ubuntu8.2 systemd-shim 8-1 sysv-rc 2.88dsf-41ubuntu18 sysvinit-utils 2.88dsf-41ubuntu18 tar 1.27.1-2 tcpd 7.6.q-25 tzdata 2014h-2 ubuntu-keyring 2012.05.19 udev 208-8ubuntu8 util-linux 2.25.1-3ubuntu4 uuid-runtime 2.25.1-3ubuntu4 xdg-user-dirs 0.15-2ubuntu2 xml-core 0.13+nmu2 zlib1g 1:1.2.8.dfsg-1ubuntu1 DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: systemd Tags: utopic Uname: Linux 3.19.0-031900rc6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1416728 Title: systemd-analyze failed: No such method 'ListUnits' Status in systemd package in Ubuntu: New Bug description: Problem: % systemd-analyze dot > /tmp/systemd0.dot Failed to issue method call: No such method 'ListUnits' ^^ $ apt-cache policy systemd systemd: Installed: 208-8ubuntu8.2 Candidate: 208-8ubuntu8.2 Version table: *** 208-8ubuntu8.2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages
[Touch-packages] [Bug 1416728] Re: systemd-analyze failed: No such method 'ListUnits'
** Attachment added: "apport.systemd._dnypx03.apport" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1416728/+attachment/4309511/+files/apport.systemd._dnypx03.apport -- 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/1416728 Title: systemd-analyze failed: No such method 'ListUnits' Status in systemd package in Ubuntu: New Bug description: Problem: % systemd-analyze dot > /tmp/systemd0.dot Failed to issue method call: No such method 'ListUnits' ^^ $ apt-cache policy systemd systemd: Installed: 208-8ubuntu8.2 Candidate: 208-8ubuntu8.2 Version table: *** 208-8ubuntu8.2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 100 /var/lib/dpkg/status 208-8ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages ProblemType: Bug ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Jan 31 14:35:18 2015 Dependencies: acl 2.2.52-1.1 adduser 3.113+nmu3ubuntu3 apt 1.0.9.2ubuntu2 apt-utils 1.0.9.2ubuntu2 busybox-initramfs 1:1.22.0-8ubuntu1 cgmanager 0.32-4ubuntu1 coreutils 8.23-2ubuntu3 cpio 2.11+dfsg-2ubuntu1 dbus 1.8.8-1ubuntu2 debconf 1.5.53ubuntu1 debianutils 4.4 dmsetup 2:1.02.77-6ubuntu2 dpkg 1.17.13ubuntu1 e2fslibs 1.42.10-1.1ubuntu1 e2fsprogs 1.42.10-1.1ubuntu1 findutils 4.4.2-9 gcc-4.9-base 4.9.1-16ubuntu6 gnupg 1.4.16-1.2ubuntu1 gpgv 1.4.16-1.2ubuntu1 ifupdown 0.7.48.1ubuntu5 init-system-helpers 1.20ubuntu3 initramfs-tools 0.103ubuntu8 initramfs-tools-bin 0.103ubuntu8 initscripts 2.88dsf-41ubuntu18 insserv 1.14.0-5ubuntu2 iproute2 3.16.0-2 isc-dhcp-client 4.2.4-7ubuntu14 isc-dhcp-common 4.2.4-7ubuntu14 klibc-utils 2.0.3-0ubuntu1 kmod 18-1ubuntu2 libacl1 2.2.52-1.1 libapparmor1 2.8.98-0ubuntu2 libapt-inst1.5 1.0.9.2ubuntu2 libapt-pkg4.12 1.0.9.2ubuntu2 libattr1 1:2.4.47-2 libaudit-common 1:2.3.7-1ubuntu1 libaudit1 1:2.3.7-1ubuntu1 libblkid1 2.25.1-3ubuntu4 libbz2-1.0 1.0.6-5ubuntu5 libc6 2.19-10ubuntu2 libcap-ng0 0.7.4-2 libcap2 1:2.24-0ubuntu2 libcap2-bin 1:2.24-0ubuntu2 libcgmanager0 0.32-4ubuntu1 libcomerr2 1.42.10-1.1ubuntu1 libcryptsetup4 2:1.6.1-1ubuntu3 libdb5.3 5.3.28-5 libdbus-1-3 1.8.8-1ubuntu2 libdevmapper1.02.1 2:1.02.77-6ubuntu2 libexpat1 2.1.0-6ubuntu1 libffi6 3.1-2 libgcc1 1:4.9.1-16ubuntu6 libgcrypt11 1.5.4-2ubuntu1 libgdbm3 1.8.3-13 libglib2.0-0 2.42.0-2 libglib2.0-data 2.42.0-2 libgpg-error0 1.13-4 libgpm2 1.20.4-6.1 libklibc 2.0.3-0ubuntu1 libkmod2 18-1ubuntu2 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.25.1-3ubuntu4 libncurses5 5.9+20140712-2ubuntu1 libncursesw5 5.9+20140712-2ubuntu1 libnih-dbus1 1.0.3-4ubuntu26 libnih1 1.0.3-4ubuntu26 libpam-cap 1:2.24-0ubuntu2 libpam-modules 1.1.8-3ubuntu4 libpam-modules-bin 1.1.8-3ubuntu4 libpam-runtime 1.1.8-3ubuntu4 libpam-systemd 208-8ubuntu8.2 libpam0g 1.1.8-3ubuntu4 libpcre3 1:8.35-3ubuntu1 libpng12-0 1.2.51-0ubuntu3 libprocps3 1:3.3.9-1ubuntu5 libreadline6 6.3-8ubuntu1 libselinux1 2.3-1build1 libsemanage-common 2.3-1 libsemanage1 2.3-1 libsepol1 2.3-2 libslang2 2.2.4-17ubuntu1 libsmartcols1 2.25.1-3ubuntu4 libss2 1.42.10-1.1ubuntu1 libstdc++6 4.9.1-16ubuntu6 libsystemd-daemon0 208-8ubuntu8.2 libsystemd-journal0 208-8ubuntu8.2 libsystemd-login0 208-8ubuntu8.2 libtinfo5 5.9+20140712-2ubuntu1 libudev1 208-8ubuntu8 libusb-0.1-4 2:0.1.12-24 libustr-1.0-1 1.0.4-3ubuntu2 libuuid1 2.25.1-3ubuntu4 libwrap0 7.6.q-25 libxml2 2.9.1+dfsg1-4ubuntu1 libxtables10 1.4.21-2ubuntu1 lsb-base 4.1+Debian11ubuntu8 module-init-tools 18-1ubuntu2 mount 2.25.1-3ubuntu4 multiarch-support 2.19-10ubuntu2 netbase 5.2 passwd 1:4.1.5.1-1.1ubuntu2 perl 5.20.1-1 perl-base 5.20.1-1 perl-modules 5.20.1-1 procps 1:3.3.9-1ubuntu5 psmisc 22.21-2 readline-common 6.3-8ubuntu1 sed 4.2.2-4ubuntu1 sensible-utils 0.0.9 sgml-base 1.26+nmu4ubuntu1 shared-mime-info 1.2-0ubuntu3 systemd 208-8ubuntu8.2 systemd-shim 8-1 sysv-rc 2.88dsf-41ubuntu18 sysvinit-utils 2.88dsf-41ubuntu18 tar 1.27.1-2 tcpd 7.6.q-25 tzdata 2014h-2 ubuntu-keyring 2012.05.19 udev 208-8ubuntu8 util-linux 2.25.1-3ubuntu4 uuid-runtime 2.25.1-3ubuntu4 xdg-user-dirs 0.15-2ubuntu2 xml-core 0.13+nmu2 zlib1g 1:1.2.8.dfsg-1ubuntu1 DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: systemd Tags: utopic Uname: Linux 3.19.0-031900rc6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1416728] Re: systemd-analyze failed: No such method 'ListUnits'
Oh, that's the reason. Yes, indeed I am running upstart. :-( Thanks -- 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/1416728 Title: systemd-analyze failed: No such method 'ListUnits' Status in systemd package in Ubuntu: Won't Fix Bug description: Problem: % systemd-analyze dot > /tmp/systemd0.dot Failed to issue method call: No such method 'ListUnits' ^^ $ apt-cache policy systemd systemd: Installed: 208-8ubuntu8.2 Candidate: 208-8ubuntu8.2 Version table: *** 208-8ubuntu8.2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 100 /var/lib/dpkg/status 208-8ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages ProblemType: Bug ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Jan 31 14:35:18 2015 Dependencies: acl 2.2.52-1.1 adduser 3.113+nmu3ubuntu3 apt 1.0.9.2ubuntu2 apt-utils 1.0.9.2ubuntu2 busybox-initramfs 1:1.22.0-8ubuntu1 cgmanager 0.32-4ubuntu1 coreutils 8.23-2ubuntu3 cpio 2.11+dfsg-2ubuntu1 dbus 1.8.8-1ubuntu2 debconf 1.5.53ubuntu1 debianutils 4.4 dmsetup 2:1.02.77-6ubuntu2 dpkg 1.17.13ubuntu1 e2fslibs 1.42.10-1.1ubuntu1 e2fsprogs 1.42.10-1.1ubuntu1 findutils 4.4.2-9 gcc-4.9-base 4.9.1-16ubuntu6 gnupg 1.4.16-1.2ubuntu1 gpgv 1.4.16-1.2ubuntu1 ifupdown 0.7.48.1ubuntu5 init-system-helpers 1.20ubuntu3 initramfs-tools 0.103ubuntu8 initramfs-tools-bin 0.103ubuntu8 initscripts 2.88dsf-41ubuntu18 insserv 1.14.0-5ubuntu2 iproute2 3.16.0-2 isc-dhcp-client 4.2.4-7ubuntu14 isc-dhcp-common 4.2.4-7ubuntu14 klibc-utils 2.0.3-0ubuntu1 kmod 18-1ubuntu2 libacl1 2.2.52-1.1 libapparmor1 2.8.98-0ubuntu2 libapt-inst1.5 1.0.9.2ubuntu2 libapt-pkg4.12 1.0.9.2ubuntu2 libattr1 1:2.4.47-2 libaudit-common 1:2.3.7-1ubuntu1 libaudit1 1:2.3.7-1ubuntu1 libblkid1 2.25.1-3ubuntu4 libbz2-1.0 1.0.6-5ubuntu5 libc6 2.19-10ubuntu2 libcap-ng0 0.7.4-2 libcap2 1:2.24-0ubuntu2 libcap2-bin 1:2.24-0ubuntu2 libcgmanager0 0.32-4ubuntu1 libcomerr2 1.42.10-1.1ubuntu1 libcryptsetup4 2:1.6.1-1ubuntu3 libdb5.3 5.3.28-5 libdbus-1-3 1.8.8-1ubuntu2 libdevmapper1.02.1 2:1.02.77-6ubuntu2 libexpat1 2.1.0-6ubuntu1 libffi6 3.1-2 libgcc1 1:4.9.1-16ubuntu6 libgcrypt11 1.5.4-2ubuntu1 libgdbm3 1.8.3-13 libglib2.0-0 2.42.0-2 libglib2.0-data 2.42.0-2 libgpg-error0 1.13-4 libgpm2 1.20.4-6.1 libklibc 2.0.3-0ubuntu1 libkmod2 18-1ubuntu2 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.25.1-3ubuntu4 libncurses5 5.9+20140712-2ubuntu1 libncursesw5 5.9+20140712-2ubuntu1 libnih-dbus1 1.0.3-4ubuntu26 libnih1 1.0.3-4ubuntu26 libpam-cap 1:2.24-0ubuntu2 libpam-modules 1.1.8-3ubuntu4 libpam-modules-bin 1.1.8-3ubuntu4 libpam-runtime 1.1.8-3ubuntu4 libpam-systemd 208-8ubuntu8.2 libpam0g 1.1.8-3ubuntu4 libpcre3 1:8.35-3ubuntu1 libpng12-0 1.2.51-0ubuntu3 libprocps3 1:3.3.9-1ubuntu5 libreadline6 6.3-8ubuntu1 libselinux1 2.3-1build1 libsemanage-common 2.3-1 libsemanage1 2.3-1 libsepol1 2.3-2 libslang2 2.2.4-17ubuntu1 libsmartcols1 2.25.1-3ubuntu4 libss2 1.42.10-1.1ubuntu1 libstdc++6 4.9.1-16ubuntu6 libsystemd-daemon0 208-8ubuntu8.2 libsystemd-journal0 208-8ubuntu8.2 libsystemd-login0 208-8ubuntu8.2 libtinfo5 5.9+20140712-2ubuntu1 libudev1 208-8ubuntu8 libusb-0.1-4 2:0.1.12-24 libustr-1.0-1 1.0.4-3ubuntu2 libuuid1 2.25.1-3ubuntu4 libwrap0 7.6.q-25 libxml2 2.9.1+dfsg1-4ubuntu1 libxtables10 1.4.21-2ubuntu1 lsb-base 4.1+Debian11ubuntu8 module-init-tools 18-1ubuntu2 mount 2.25.1-3ubuntu4 multiarch-support 2.19-10ubuntu2 netbase 5.2 passwd 1:4.1.5.1-1.1ubuntu2 perl 5.20.1-1 perl-base 5.20.1-1 perl-modules 5.20.1-1 procps 1:3.3.9-1ubuntu5 psmisc 22.21-2 readline-common 6.3-8ubuntu1 sed 4.2.2-4ubuntu1 sensible-utils 0.0.9 sgml-base 1.26+nmu4ubuntu1 shared-mime-info 1.2-0ubuntu3 systemd 208-8ubuntu8.2 systemd-shim 8-1 sysv-rc 2.88dsf-41ubuntu18 sysvinit-utils 2.88dsf-41ubuntu18 tar 1.27.1-2 tcpd 7.6.q-25 tzdata 2014h-2 ubuntu-keyring 2012.05.19 udev 208-8ubuntu8 util-linux 2.25.1-3ubuntu4 uuid-runtime 2.25.1-3ubuntu4 xdg-user-dirs 0.15-2ubuntu2 xml-core 0.13+nmu2 zlib1g 1:1.2.8.dfsg-1ubuntu1 DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: systemd Tags: utopic Uname: Linux 3.19.0-031900rc6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/
[Touch-packages] [Bug 1393271] [NEW] ibus can't select past the first five choices
Public bug reported: The ibus can't select past the first five choices. after turning to second page or more, pressing 1~5 will not get that corresponding character/word, but something entirely unrelated instead. 13.10下的ibus-googlepinyin就已经不能输入前五个选项以外的字词了--即，凡是要翻页的，翻页以后就不能正常选字、词了。13 .10下的ibus-table-wubi也有同样的问题。 All ibus related packages installed in my Ubuntu 13.10, problem shows up as early as: gir1.2-ibus-1.0_1.5.3-6ubuntu2.1 ibus_1.5.3-6ubuntu2.1 ibus-googlepinyin_0.1.2-2 ibus-pinyin_1.4.0-2ubuntu2 ibus-pinyin-db-open-phrase_1.4.0-2ubuntu2 ibus-table_1.5.0.is.1.5.0-0ubuntu1 ibus-table-wubi_1.4.0.20121008-1 libibus-1.0-5:amd64_1.5.3-6ubuntu2 libusb-0.1-4:amd64_2:0.1.12-23.2ubuntu1 libusb-1.0-0:amd64_2:1.0.16-3 libusbmuxd2_1.0.8-1ubuntu1 libustr-1.0-1:amd64_1.0.4-3ubuntu1 python-ibus_1.5.3-6ubuntu2.1 $ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 $ uname -rm 3.11.0-26-generic x86_64 ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Affects: ibus-googlepinyin (Ubuntu) Importance: Undecided Status: New ** Affects: ibus-table-wubi (Ubuntu) Importance: Undecided Status: New ** Also affects: ibus-googlepinyin (Ubuntu) Importance: Undecided Status: New ** Also affects: ibus-table-wubi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1393271 Title: ibus can't select past the first five choices Status in “ibus” package in Ubuntu: New Status in “ibus-googlepinyin” package in Ubuntu: New Status in “ibus-table-wubi” package in Ubuntu: New Bug description: The ibus can't select past the first five choices. after turning to second page or more, pressing 1~5 will not get that corresponding character/word, but something entirely unrelated instead. 13.10下的ibus-googlepinyin就已经不能输入前五个选项以外的字词了--即，凡是要翻页的，翻页以后就不能正常选字、词了。13 .10下的ibus-table-wubi也有同样的问题。 All ibus related packages installed in my Ubuntu 13.10, problem shows up as early as: gir1.2-ibus-1.0_1.5.3-6ubuntu2.1 ibus_1.5.3-6ubuntu2.1 ibus-googlepinyin_0.1.2-2 ibus-pinyin_1.4.0-2ubuntu2 ibus-pinyin-db-open-phrase_1.4.0-2ubuntu2 ibus-table_1.5.0.is.1.5.0-0ubuntu1 ibus-table-wubi_1.4.0.20121008-1 libibus-1.0-5:amd64_1.5.3-6ubuntu2 libusb-0.1-4:amd64_2:0.1.12-23.2ubuntu1 libusb-1.0-0:amd64_2:1.0.16-3 libusbmuxd2_1.0.8-1ubuntu1 libustr-1.0-1:amd64_1.0.4-3ubuntu1 python-ibus_1.5.3-6ubuntu2.1 $ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 $ uname -rm 3.11.0-26-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1393271/+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 1395343] [NEW] Ubuntu 14.10 Utopic suspend/resume not working for my Laptop
Public bug reported: The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I first tried with the Live CD, on failing that, and thinking that suspend might need some disk to write to for the suspend info, I did a HD installation. But still, suspend/resume is still not working. On second attempt (after HD installation), I switched to console and close my Laptop lid. It suspended well, as it has always been. On resume, I see the repeating errors of `sda1` "soft reset failure" (or something like that). Minutes later, I start to see all kinds of disk related errors, disk sector writing error, ext4 journal error, etc. I thus think the reason of `resume` not working is that the HD is not waken up. This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic. Any more info that I can provide? Thanks ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1395343 Title: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop Status in “pm-utils” package in Ubuntu: New Bug description: The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I first tried with the Live CD, on failing that, and thinking that suspend might need some disk to write to for the suspend info, I did a HD installation. But still, suspend/resume is still not working. On second attempt (after HD installation), I switched to console and close my Laptop lid. It suspended well, as it has always been. On resume, I see the repeating errors of `sda1` "soft reset failure" (or something like that). Minutes later, I start to see all kinds of disk related errors, disk sector writing error, ext4 journal error, etc. I thus think the reason of `resume` not working is that the HD is not waken up. This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic. Any more info that I can provide? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1395343/+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 1395343] Re: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop
Is there any workaround at the moment? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1395343 Title: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop Status in “pm-utils” package in Ubuntu: New Bug description: The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I first tried with the Live CD, on failing that, and thinking that suspend might need some disk to write to for the suspend info, I did a HD installation. But still, suspend/resume is still not working. On second attempt (after HD installation), I switched to console and close my Laptop lid. It suspended well, as it has always been. On resume, I see the repeating errors of `sda1` "soft reset failure" (or something like that). Minutes later, I start to see all kinds of disk related errors, disk sector writing error, ext4 journal error, etc. I thus think the reason of `resume` not working is that the HD is not waken up. This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic. Any more info that I can provide? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1395343/+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 1395343] Re: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop
This is a rarely used computer. I'm sure it is not disk errors, as it never gave any problem before, but failed to wake up the HD instead, each and every time that I tried. I got disk errors on other machines before, so I know what it means. I.e., if it is disk errors, the the error sequence reported above will be entirely different. No I can't use apport-collect, as it's function is to automatically generate crash reports for debugging. However my machine/SW does not crash, but freeze up entirely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1395343 Title: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop Status in “pm-utils” package in Ubuntu: New Bug description: The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I first tried with the Live CD, on failing that, and thinking that suspend might need some disk to write to for the suspend info, I did a HD installation. But still, suspend/resume is still not working. On second attempt (after HD installation), I switched to console and close my Laptop lid. It suspended well, as it has always been. On resume, I see the repeating errors of `sda1` "soft reset failure" (or something like that). Minutes later, I start to see all kinds of disk related errors, disk sector writing error, ext4 journal error, etc. I thus think the reason of `resume` not working is that the HD is not waken up. This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic. Any more info that I can provide? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1395343/+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 1639513] [NEW] Pango-WARNING **: shaping failure, expect ugly output
Public bug reported: Exactly as reported in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which was marked as "Invalid" because it is reporting to the wrong package. The problem from that post: Console: $ evince (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'Ubuntu 11' (evince:8959): Pango-WARNING **: font_face status is: out of memory (evince:8959): Pango-WARNING **: scaled_font status is: out of memory (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Ubuntu 11', text='●' As for mine, it is basically the same: (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is '微软雅黑 9' (process:13924): Pango-WARNING **: font_face status is: file not found (process:13924): Pango-WARNING **: scaled_font status is: file not found (process:13924): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg' As the result, For the original reported, "some font and only displays squares in menus, text is displayed okay,", but for me, everything are displays as squares in menus, including English texts. However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly without any problem. The cause of the problem, is also exactly as described in the original post: It happens because of symlinks from /usr/share/fonts to a different partition. For the original reporter, some fonts are symlinked, and for me 微软雅黑 is symlinked to a different partition. Thus his is missing some text, while I'm missing everything. symlinking fonts to a different partition is quite harmless in my view, and Pango should not treat them any differently. This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK. My current Pango related packages that exhibit such problem: gir1.2-pango-1.0:amd64_1.38.1-1 libcogl-pango20:amd64_1.22.0-2 libpango-1.0-0:amd64_1.38.1-1 libpango-perl_1.227-1 libpango1.0-0:amd64_1.38.1-1 libpangocairo-1.0-0:amd64_1.38.1-1 libpangoft2-1.0-0:amd64_1.38.1-1 libpangomm-1.4-1v5:amd64_2.38.1-1 libpangox-1.0-0:amd64_0.0.2-5 libpangoxft-1.0-0:amd64_1.38.1-1 Please look into it. Thx. ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1639513 Title: Pango-WARNING **: shaping failure, expect ugly output Status in pango1.0 package in Ubuntu: New Bug description: Exactly as reported in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which was marked as "Invalid" because it is reporting to the wrong package. The problem from that post: Console: $ evince (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'Ubuntu 11' (evince:8959): Pango-WARNING **: font_face status is: out of memory (evince:8959): Pango-WARNING **: scaled_font status is: out of memory (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Ubuntu 11', text='●' As for mine, it is basically the same: (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is '微软雅黑 9' (process:13924): Pango-WARNING **: font_face status is: file not found (process:13924): Pango-WARNING **: scaled_font status is: file not found (process:13924): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg' As the result, For the original reported, "some font and only displays squares in menus, text is displayed okay,", but for me, everything are displays as squares in menus, including English texts. However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly without any problem. The cause of the problem, is also exactly as described in the original post: It happens because of symlinks from /usr/share/fonts to a different partition. For the original reporter, some fonts are symlinked, and for me 微软雅黑 is symlinked to a different partition. Thus his is missing some text, while I'm missing everything. symlinking fonts to a different partition is quite harmless in my view, and Pango should not treat them any differently. This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK. My current Pango related packages that exhibit such problem: gir1.2-pango-1.0:amd64_1.38.1-1 libcogl-pango20:amd64_1.22.0-2 libpango-1.0-0:amd64_1.38.1-1 libpango-perl_1.227-1 libpango1.0-0:amd64_1.38.1-1 libpangocairo-1.0-0:amd64_1.38.1-1 libpangoft2-1.0-0:amd64_1.38.1-1 libpangomm-1.4-1v5:amd64_2.38.1-1 libpangox-1.0-0:amd64_0.0.2-5 libpangoxft-1.0-0:amd64_1.38.1-1 Please look
[Touch-packages] [Bug 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output
To duplicate the problem: 1. Find the first match of the font used for Pango menu: $ fc-match -s sans-serif | head -1 msyh.ttc: "微软雅黑" "Regular" 2. Copy & symlink that file into a different partition 3. Reboot! That's important, otherwise, I didn't see the problem or fix the problem. 4. Start evince or any gtk/Pango based application from console. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1639513 Title: Pango-WARNING **: shaping failure, expect ugly output Status in pango1.0 package in Ubuntu: New Bug description: Exactly as reported in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048, which was marked as "Invalid" because it is reporting to the wrong package. The problem from that post: Console: $ evince (evince:8959): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'Ubuntu 11' (evince:8959): Pango-WARNING **: font_face status is: out of memory (evince:8959): Pango-WARNING **: scaled_font status is: out of memory (evince:8959): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Ubuntu 11', text='●' As for mine, it is basically the same: (process:13924): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is '微软雅黑 9' (process:13924): Pango-WARNING **: font_face status is: file not found (process:13924): Pango-WARNING **: scaled_font status is: file not found (process:13924): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='微软雅黑 9', text='Ayg' As the result, For the original reported, "some font and only displays squares in menus, text is displayed okay,", but for me, everything are displays as squares in menus, including English texts. However, my rxvt-unicode, which uses the 微软雅黑 font, display correctly without any problem. The cause of the problem, is also exactly as described in the original post: It happens because of symlinks from /usr/share/fonts to a different partition. For the original reporter, some fonts are symlinked, and for me 微软雅黑 is symlinked to a different partition. Thus his is missing some text, while I'm missing everything. symlinking fonts to a different partition is quite harmless in my view, and Pango should not treat them any differently. This only happens since Ubuntu 16.04. In Ubuntu 15.10, it was OK. My current Pango related packages that exhibit such problem: gir1.2-pango-1.0:amd64_1.38.1-1 libcogl-pango20:amd64_1.22.0-2 libpango-1.0-0:amd64_1.38.1-1 libpango-perl_1.227-1 libpango1.0-0:amd64_1.38.1-1 libpangocairo-1.0-0:amd64_1.38.1-1 libpangoft2-1.0-0:amd64_1.38.1-1 libpangomm-1.4-1v5:amd64_2.38.1-1 libpangox-1.0-0:amd64_0.0.2-5 libpangoxft-1.0-0:amd64_1.38.1-1 Please look into it. Thx. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+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@lists.launchpad.net
Public bug reported:
I am experimenting with the new profile stacking feature of AppArmor on
Ubuntu 16.10.
However, when trying the load a profile with stacking ("//&" ), the
apparmor-parser will report the following erros:
AppArmor parser error for /etc/apparmor.d/root.test.shell in
/etc/apparmor.d/root.test.shell at line 8: syntax error, unexpected
TOK_ID, expecting TOK_END_OF_RULE.
The system is Ubuntu 16.10 Server edition. I am trying to confine a
test program at /root/test/shell. The profile looks like the following:
#include
/root/test/shell {
#include
/bin/touch ix,
/root/test/read px -> readtest1 //& readtest2,
/root/test/shell mr,
profile readtest1 {
#include
/root/test/file1 r,
/root/test/read mr,
}
profile readtest2 {
#include
/root/test/file2 r,
/root/test/read mr,
}
}
If the stacking works, when the /root/test/shell execs /root/test/read,
it should not be able to read either file1 or file2.
I am not sure if I am using the stacking in the wrong way, or there is a
bug in userspace support for stacking.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
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/1639660
Title:
apparmor-parse cannot parse profile with stacking //&
Status in apparmor package in Ubuntu:
New
Bug description:
I am experimenting with the new profile stacking feature of AppArmor
on Ubuntu 16.10.
However, when trying the load a profile with stacking ("//&" ), the
apparmor-parser will report the following erros:
AppArmor parser error for /etc/apparmor.d/root.test.shell in
/etc/apparmor.d/root.test.shell at line 8: syntax error, unexpected
TOK_ID, expecting TOK_END_OF_RULE.
The system is Ubuntu 16.10 Server edition. I am trying to confine a
test program at /root/test/shell. The profile looks like the
following:
#include
/root/test/shell {
#include
/bin/touch ix,
/root/test/read px -> readtest1 //& readtest2,
/root/test/shell mr,
profile readtest1 {
#include
/root/test/file1 r,
/root/test/read mr,
}
profile readtest2 {
#include
/root/test/file2 r,
/root/test/read mr,
}
}
If the stacking works, when the /root/test/shell execs
/root/test/read, it should not be able to read either file1 or file2.
I am not sure if I am using the stacking in the wrong way, or there is
a bug in userspace support for stacking.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1639660/+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@lists.launchpad.net
Hi John,
Thanks for the quick reply.
I did what you suggested, but it looks like it is still not working.
After I remove the whitespace, I still have the same error:
AppArmor parser error for root.test.shell in root.test.shell at line 7:
syntax error, unexpected TOK_ID, expecting TOK_END_OF_RULE
Then I tried the quote, the error message changes to the following:
AppArmor parser error for root.test.shell in root.test.shell at line 7:
Found unexpected character: '"'
Thanks.
--
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/1639660
Title:
apparmor-parse cannot parse profile with stacking //&
Status in apparmor package in Ubuntu:
New
Bug description:
I am experimenting with the new profile stacking feature of AppArmor
on Ubuntu 16.10.
However, when trying the load a profile with stacking ("//&" ), the
apparmor-parser will report the following erros:
AppArmor parser error for /etc/apparmor.d/root.test.shell in
/etc/apparmor.d/root.test.shell at line 8: syntax error, unexpected
TOK_ID, expecting TOK_END_OF_RULE.
The system is Ubuntu 16.10 Server edition. I am trying to confine a
test program at /root/test/shell. The profile looks like the
following:
#include
/root/test/shell {
#include
/bin/touch ix,
/root/test/read px -> readtest1 //& readtest2,
/root/test/shell mr,
profile readtest1 {
#include
/root/test/file1 r,
/root/test/read mr,
}
profile readtest2 {
#include
/root/test/file2 r,
/root/test/read mr,
}
}
If the stacking works, when the /root/test/shell execs
/root/test/read, it should not be able to read either file1 or file2.
I am not sure if I am using the stacking in the wrong way, or there is
a bug in userspace support for stacking.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1639660/+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
