I can confirm the issue on 23.10 with no printers configured
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2021956
Title:
crash cups-proxyd
Status in cups package in Ubuntu
@mantas
Thanks for letting me know about the bug/fix.
Looks like my version was not affected due to slightly different systemd config.
Nevertheless, I've added the fix (just in case) and pushed it to
lp:~eugenesan/+git/zram-config
PPA was updated as well.
--
You received this bug notification be
Confirming the bug in Xenial.
** Tags removed: amd64
** Tags added: xenial
** Description changed:
After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
suspend DNS resolution stops working.
+
+ * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack
+ was upgr
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
I have merged in another bug(s) and updated the name of the bug to be a
bit more "user friendly".
** Summary changed:
- dnsmasq fails to send queries out after suspend disconnects the interface
+ name resolution (dnsmasq) fails to send queries out after suspend/resume
reconnects the interface
-
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out after suspend disconnects the interface
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
The reason for the failure seems to be in default configuration of PAM
for SSH.
If I understand correctly, PAM is configured to enforce session keys revocation
upon termination of parent SSHD process:
--- /etc/pam.d/sshd ---
...
# Create a new session keyring.
sessionoptional pam_keyinit.
** Also affects: indicator-bluetooth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1554878
Title:
fix up
** Also affects: python-xdgapp
Importance: Undecided
Status: New
** Also affects: pyxdg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: syncthing-gtk (Ubuntu)
Importance: Undecided
Status: New
** Also affects: dropbox (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
** This bug is no longer a duplicate of bug 1522922
Screen flickering in Intel i915 driver
** This bug has been marked a duplicate of bug 1554613
screen flickering on XPS13 9350/9550
--
You received
Public bug reported:
Dialog "Authentication is required to change your own user data" appears
when changing keyboard language inside non-physical session.
This is reincarnation of
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512002.
I am experiencing the bug on 16.04 with gnom
Public bug reported:
initramfs-tools calls dpkg with obsolete parameter:
...
Processing triggers for initramfs-tools (0.103ubuntu16) ...
dpkg: warning: --compare-versions used with obsolete relation operator '>'
...
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status
** No longer affects: apparmor
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags added: ssh x2go
--
You received this bug notification because you are a member of Ubuntu
Touch see
While I agree that moving systemd-cryptsetup to 'recommended' (or even
'depends') is the solution, it doesn't solve the issue with installs
using LiveCDs.
Install ISOs must be updated to make systems with separate encrypted
/home bootable and systems with 2+ encrypted volumes usable.
Which projec
@vorlon
Currently when installing using Calamares (Kubuntu, Lubuntu etc) and probably
Ubiquity (Mate etc), manual partitioning allows arbitrary number of luks
volumes including one them being /home.
Configurations with /home on luks which is not the first one, are "unbootable".
Configurations wi
I can confirm.
Not mounting luks volumes is not the only issue.
Among the issues are: very long boo times, inability to login using
graphical login managers and random hangs all over the place. Systems
with /home on separate encrypted location are completely broken even
with fresh installs.
The i
23 matches
Mail list logo
