[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
I can confirm that on an up-to-date Ubuntu 22.04 use-dns doesn't work
with the NetworkManager renderer. It does work with networkd.
network:
ethernets:
enp2s0:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
addresses: [9.9.9.9, 149.112.112.112]
search: []
renderer: NetworkManager
version: 2
$ resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
DNS Servers: 9.9.9.9
Link 2 (enp2s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 9.9.9.9 149.112.112.112 192.168.0.1
DNS Domain: Home
(With option "use-dns: false" 192.168.0.1 shouldn't be added to the list of DNS
servers.)
With "renderer: networkd" it looks alright:
$ resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
DNS Servers: 9.9.9.9
Link 2 (enp2s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 9.9.9.9 149.112.112.112
DNS Domain: Home
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
Status in Default settings and artwork for Baltix OS:
New
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Fix Released
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1759014/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Hi!
I just found this bug report.
I use a clean installed 22.04 (not upgraded from 20.04) and a clean setup of
Evolution (no config was copied from an earlier release) and I do experience
this issue, it's pretty straightforward to reproduce, i.e. every time a
composed email is saved into an autosave file and I send the email, the
autosave file remains and upon restarting Evolution I get asked whether I want
to recover. If I say yes, all emails open up that I've sent since the last
restart (and "recovery").
I've tested the 0.30-10ubuntu1.22.04.1 version of the libcanberra-
gtk3-module package (from the jammy-proposed repo) and I can confirm
that it fixes the issue. I also hear sounds from Evolution, when a new
mail arrives. I'm not sure whether this qualifies as a "libcanberra-
gtk3-module still works as intended" test or not. I'm happy to do more
testing if somebody gives me a testcase description.
Since I've just upgraded libcanberra-gtk3-module to
0.30-10ubuntu1.22.04.1 a few minutes ago, I've no long-term experience
whether anything else got accidentally broken.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1945202] [NEW] Tar changes folder ownership when run under root
Public bug reported: I got locked out of my server via SSH, simply by extracting a tar file. No matter how crazy it sounds, it is reproducible. 1. login as root 2. wget https://github.com/aristocratos/btop/releases/download/v1.0.9/btop-1.0.9-linux-x86_64.tbz` 3. tar -xjvf btop-1.0.9-linux-x86_64.tbz` At this point the /root folder has ownership of user:user (1000:1000) and the root is locked out from SSH login. I had to fix the server via KVM. auth.log contained the following: "Authentication refused: bad ownership or modes for directory /root" This seems to be a bug in tar, as the above behaviour doesn't happen when logged in under any non-root user. With non-root users the directory does not change ownership. With root user, no matter where I extract the tar file, the directory changes ownership. --- lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 apt-cache policy tar tar: Installed: 1.29b-2ubuntu0.2 Candidate: 1.29b-2ubuntu0.2 ** Affects: tar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1945202 Title: Tar changes folder ownership when run under root Status in tar package in Ubuntu: New Bug description: I got locked out of my server via SSH, simply by extracting a tar file. No matter how crazy it sounds, it is reproducible. 1. login as root 2. wget https://github.com/aristocratos/btop/releases/download/v1.0.9/btop-1.0.9-linux-x86_64.tbz` 3. tar -xjvf btop-1.0.9-linux-x86_64.tbz` At this point the /root folder has ownership of user:user (1000:1000) and the root is locked out from SSH login. I had to fix the server via KVM. auth.log contained the following: "Authentication refused: bad ownership or modes for directory /root" This seems to be a bug in tar, as the above behaviour doesn't happen when logged in under any non-root user. With non-root users the directory does not change ownership. With root user, no matter where I extract the tar file, the directory changes ownership. --- lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 apt-cache policy tar tar: Installed: 1.29b-2ubuntu0.2 Candidate: 1.29b-2ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1945202/+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 50093] Re: Some sysctls are ignored on boot
Actually, the line which works without specifying a PATH in a cron.d file is the following: @reboot root /bin/sleep 5 && /sbin/sysctl --system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 50093] Re: Some sysctls are ignored on boot
I feel it's important to add that the very last comment (Stanley Sisneros (stanley-sisneros) wrote on 2018-05-30) is wrong, and the right workaround is by Tomasz Konefal (twkonefal-j) wrote on 2018-05-07. That is, add this to crontab: @reboot root sleep 5 && sysctl --system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I have installed Ubuntu 18.04 because I thought it must already be stable. Then I had to find out that it is impossible to run node js 11 and mongodb 4 on the same system, just because node js 11 depends on libcurl4 and mongodb-org 4 depends on libcurl3, and they cannot coexist. Come on, this bug has been here for more than 6 months now! I don't have a choice but to select a different distribution. :-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645002] [NEW] ssh sessions are not cleanly terminated on shutdown/restart with systemd
Public bug reported: In Ubuntu 16.04, a "reboot" command does not terminate the ssh session. This results in clients hanging, until timing out (sometimes as much as 120 seconds). This also introduces bugs to all orchestration / automation tools which work over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 hosts. For example, have a look at this issue for Fabric: https://github.com/fabric/fabric/issues/1488 The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. There is a very detailed discussion in their bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1645002 Title: ssh sessions are not cleanly terminated on shutdown/restart with systemd Status in openssh package in Ubuntu: New Bug description: In Ubuntu 16.04, a "reboot" command does not terminate the ssh session. This results in clients hanging, until timing out (sometimes as much as 120 seconds). This also introduces bugs to all orchestration / automation tools which work over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 hosts. For example, have a look at this issue for Fabric: https://github.com/fabric/fabric/issues/1488 The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. There is a very detailed discussion in their bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1645002/+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 1644996] [NEW] logrotate config uses syslog group
Public bug reported: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1618764] [NEW] package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, a
Public bug reported: It is conflict with kde-config-telepathy-accounts package. Kibontás: account-plugin-google (0.13+16.04.20160719-0ubuntu1) e helyett: 0.12+16.04.20160126-0ubuntu1 ... dpkg: hiba az archívum feldolgozásakor: /var/cache/apt/archives/account-plugin-google_0.13+16.04.20160719-0ubuntu1_all.deb (--unpack): a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 31 10:23:48 2016 ErrorMessage: a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel InstallationDate: Installed on 2016-03-29 (155 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: account-plugins Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel UpgradeStatus: Upgraded to xenial on 2016-04-01 (152 days ago) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package gnome3-ppa third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1618764 Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel Status in account-plugins package in Ubuntu: New Bug description: It is conflict with kde-config-telepathy-accounts package. Kibontás: account-plugin-google (0.13+16.04.20160719-0ubuntu1) e helyett: 0.12+16.04.20160126-0ubuntu1 ... dpkg: hiba az archívum feldolgozásakor: /var/cache/apt/archives/account-plugin-google_0.13+16.04.20160719-0ubuntu1_all.deb (--unpack): a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 31 10:23:48 2016 ErrorMessage: a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel InstallationDate: Installed on 2016-03-29 (155 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: account-plugins Title: package account-plugin-google 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: a(z) „/usr/share/accounts/services/google-im.service” felülírási kísérlete, amely a(z) kde-config-telepathy-accounts 4:15.12.3-0ubuntu1 csomagban is szerepel UpgradeStatus: Upgraded to xenial on 2016-04-01 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1618764/+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 1559416] [NEW] package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Package failed to install. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CustomUdevRuleFiles: 99_smfpautoconf_samsung.rules 98_smfpautoconf_samsung.rules 60-vboxdrv.rules Date: Sat Mar 19 08:49:08 2016 DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (42 days ago) InstallationMedia: Ubuntu "Wily" - Build amd64 LIVE Binary 20151022-22:44 MachineType: LENOVO 80QQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=b90b210d-00e1-49c5-adb1-fdb79e306e2b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: systemd Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: E0CN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Nano 5B6 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 100-15IBD dmi.modalias: dmi:bvnLENOVO:bvrE0CN16WW:bd08/04/2015:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD: dmi.product.name: 80QQ dmi.product.version: Lenovo ideapad 100-15IBD dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check wily -- 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/1559416 Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Package failed to install. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CustomUdevRuleFiles: 99_smfpautoconf_samsung.rules 98_smfpautoconf_samsung.rules 60-vboxdrv.rules Date: Sat Mar 19 08:49:08 2016 DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-02-05 (42 days ago) InstallationMedia: Ubuntu "Wily" - Build amd64 LIVE Binary 20151022-22:44 MachineType: LENOVO 80QQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=b90b210d-00e1-49c5-adb1-fdb79e306e2b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: systemd Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: E0CN16WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Nano 5B6 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 100-15IBD dmi.modalias: dmi:bvnLENOVO:bvrE0CN16WW:bd08/04/2015:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD: dmi.product.name: 80QQ dmi.product.version: Lenovo ideapad 100-15IBD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1559416/+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 860003] Re: running LightDM in test mode doesn't work
Got exactly the same. L ~ : lightdm --test-mode Running inside an X server requires Xephyr to be installed but it cannot be found. Please install it or update your PATH environment variable. L ~ : cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu 15.10" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/860003 Title: running LightDM in test mode doesn't work Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: As described on https://wiki.ubuntu.com/LightDM, I should be able to run lightdm --test-mode in a console. However, when I try that, I first get this error: matthijs@Simba:~$ lightdm --test-mode Running inside an X server requires Xephyr to be installed but it cannot be found. Please install it or update your PATH environment variable. When I then install the xserver-xephyr package and try again, a small window opens for less than a second and then closes again. No errors, no testing environment. Nothing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Mon Sep 26 22:01:52 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/860003/+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
