Schools have started installing/upgrading to 22.04.1 and we're just now
seeing this.
This change takes away the ability of the users to share some of their data
WITHOUT involving the administrator.
It's not "privacy by default", it's "mandatory privacy".
Privacy by default could be done with umas
Public bug reported:
Hi, recently netplan added support for a yaml NM backend:
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-
settings/32420
The rationale is that "the descriptive YAML layer is especially useful
in cloud environments":
https://gitlab.freedesktop.org/Networ
Public bug reported:
I updated my Kubuntu 23.04 to 23.10 using do-release-upgrade. It
finished 100% successfully. But after rebooting into 23.10, I noticed
that network-manager was kept back to the 23.04 version due to phased
updates. Specifically:
# apt policy network-manager
network-manager:
Thank you; if I understood correctly, that method would render all the
NM GUI/console tools unusable; it's not a viable workaround, as I would
like to be able to use these tools as well... E.g.:
- Create a new bond => GUI, nmtui, nmcli
- Did I forget any setting while creating that bond? Let's com
My problem is a bit different: everything works fine, but the dialog
appears when we ACTIVATE a VPN connection, even if we don't want to
modify it.
1) I've prepared a VPN connection for my non-admin users and put it in
/etc/NetworkManager/system-connections/vpn.nmconnection.
2) When they click to
I also see it on Ubuntu MATE Jammy.
Will the fix come from Xorg,
or should we add LightDM to the affected projects list?
--
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/1922414
While working on a remote server, it took me 2-3 hours to locate this
bug report and apply its workarounds. It's certainly not a good default
behavior.
In case someone has already removed netplan, the recommended steps to
get network-manager to manage the interfaces, as I understood them, are:
``
The issue is still there in today's Ubuntu MATE 22.04 daily built.
Greeks cannot even type their names in the installer (ubiquity)...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launch
** Changed in: ltsp (Ubuntu)
Status: New => Invalid
--
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/2019940
Title:
Directly manipulating NetworkManager keyfi
Public bug reported:
The Debian packaging contains these lines:
https://salsa.debian.org/debian/rsyslog/-/blob/debian/master/debian/rules#L43
--enable-pmnormalize \
--enable-mmnormalize \
AFAIK these were removed because liblognorm was in universe:
- Drop [mm
> I will point out that Firefox, regardless of how it's launched, seems
to not be affected anymore.
If you're testing firefox.snap, that might be the cause, i.e. maybe snap does
the parenting.
While e.g. firefox.deb from the mozillateam PPA (or firefox in Debian) could
still have the issue.
Tha
Reproduced in Ubuntu 22.04 and 20.04.
Could NOT reproduce in Ubuntu 18.04.
I think the problem is in `agetty` though, not in `login`.
Added `util-linux` to affected packages.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification b
Public bug reported:
Please do not add "universe" in "deb cdrom:" lines of
/etc/apt/sources.list.
To reproduce the issue, boot Ubuntu GNOME 22.04, and at the live
session, run:
sudo add-apt-repository universe
After that, `apt update` will keep complaining:
W: Skipping acquire of configured fi
Since this was fixed upstream and it doesn't affect any LTS Ubuntu
releases, I don't think it's important enough to do SRUs. Thank you!
(For LTSP users, that are affected by this: once a fixed rsync version
lands in Ubuntu, I'll copy it to the LTSP PPA for Groovy, so LTSP will
work there too)
--
** No longer affects: ltsp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/206924
Title:
Make it possible to create a guest account
Status in accountsservice:
Co
I too got affected by this regression.
On servers with network-manager, without netplan (01-network-manager-all.yaml),
systemd-networkd-wait-online.service started failing after the latest updates
and leaves systemd in a degraded state.
Example:
root@gldap:/var/log/apt# ip a
1: lo: mtu 65536 q
A workaround to avoid rebuilding the initramfs is to use TWO
initramfs's. The second one contains just a symlink from scripts/casper-
bottom/25disable_cdrom.mount to /bin/true. I.e.:
cd $(mktemp -d)
mkdir -p scripts/casper-bottom/
ln -s /bin/true scripts/casper-bottom/25disable_cdrom.mount
find .
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment
#12 above; and unfortunately I don't have an affected school nearby,
where I could test 18.2.8 in cosmic, and installing cosmic in a remote
school would be hard.
Thanks a lot Timo!
--
You received this bug notification beca
Hi Timo,
if I remember correctly, there were some schools that were affected by this
issue, but I wasn't able to reproduce it in the office due to lack of similar
hardware.
Unfortunately it's not easy to check which were those schools; but I can keep
an eye on this issue, in case I hear about b
** No longer affects: ltsp (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/183303
Title:
Can't create new wireless network using mac80211 based drivers
St
** No longer affects: epoptes (Ubuntu)
--
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/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/netw
Public bug reported:
While netbooting, in initramfs-tools/scripts/functions, netplan for some
reason tries to overwrite /run/net-enp0s3.conf that is initially and
correctly generated by ipconfig.
There, it writes unquoted values like the following, which are a shell syntax
error:
IPV4DNS0=1.2.3.
Using Ubuntu live CDs, I verified that this did not happen in 18.04 and
happens in both 18.10 and 19.04.
--
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/1840965
Title
The code that generates the invalid /run/net-enp0s3.conf belongs in the
Ubuntu isc-dhcp package, and specifically in debian/initramfs-
tools/lib/etc/dhcp/dhclient-enter-hooks.d/config.
It got in effect in 18.10 when initramfs-tools in Ubuntu switched to
calling dhclient instead of ipconfig.
Addit
I'm attaching a patch for dhclient-enter-hooks.d/config.
I thought to imitate ipconfig and write all values even if they're empty.
For the debian/dhclient-script.* scripts which use chmod/chown parameters that
aren't available in busybox, it might be best to just omit them, or use `cp/rm`
instea
I just noticed that the original script used tabs instead of spaces;
I'm attaching a new .diff that respects that.
** Patch removed: "isc-dhcp.diff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1840965/+attachment/5284861/+files/isc-dhcp.diff
** Patch added: "isc-dhcp.diff"
htt
I uploaded my patch as a merge proposal instead.
--
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/1840965
Title:
dhclient initramfs code writes invalid net-eth0.conf
** No longer affects: initramfs-tools (Ubuntu)
** No longer affects: initramfs-tools (Ubuntu Eoan)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1840965
Title:
dhclient
Public bug reported:
Several schools reported black screens after normally updating their
Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.
Downgrading mesa fixes the problem.
lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
Graphics 530 [8086:1912] (rev
I verify that the bionic-proposed package addresses the issue.
Tested in:
# lspci -nn -k | grep -A 2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630
[8086:5912] (rev 04)
Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
Kernel driv
I just tried with 4.18.0-14-generic, the same issue happens there as
well.
And, another school reported the issue on HD Graphics 630:
root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible
controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev
04) Subsystem: ASRoc
Hello Sergii,
I tried with 4.20.7 and it appears to work fine! Thanks!
Output of the commands:
# uname -a
Linux srv-6gym-chalk 4.20.7-042007-generic #201902061234 SMP Wed Feb 6 17:49:39
UTC 2019 i686 i686 i686 GNU/Linux
# file /usr/bin/glxinfo
/usr/bin/glxinfo: ELF 32-bit LSB shared object, In
I don't know the software stacks involved:
If I understood it correctly,
mesa 18.3.3 doesn't work with older kernels while 18.0 did work,
and so I'll do a bisection to see which kernel commit fixes the issue,
and then distro kernel maintainers may cherrypick it for older kernels.
If there's no ne
I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-041902=fails,
4.19.3-041903=works
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1815172
Title:
Blac
Just correcting a wrong comment (#2) I made:
> It happens on both 32bit and 64bit installations.
I asked the school that reported the issue on 64bit to check again, and
they said they have a 32bit installation after all.
So the problem has only been reported in 32bit installations; I don't
know i
The following workaround doesn't remove anything and allows the wrapper
to survive updates:
sudo -i
printf '#!/bin/sh\n\n/usr/share/gdebi/gdebi-gtk "$@"\n' >
/usr/local/bin/gdebi-gtk
chmod +x /usr/local/bin/gdebi-gtk
exit
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hi, I'm upstream and Debian/Ubuntu maintainer for LTSP.
In the past, LTSP required some patches in isc-dhcp-server and tftpd-hpa.
Since Bullseye and Focal these are no longer needed and they should be dropped.
Specifically, LTSP now defaults to dnsmasq, and in the case where
Are you still using lightdm there? Ubuntu 19.10 uses GDM; only some
other flavors like MATE, Xubuntu and Lubuntu use lightdm.
--
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/1
Another use case is in LTSP, where we debootstrap an armhf chroot to netboot
raspberrypi clients.
This currently fails in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/
For the maintainers of the affected packages to be able to help in this issue,
addressing the main question already stated above would be most helpful:
To support netplan, do we have to implement netlink events listeners ourselves?
I'm not sure all maintainers are willing to do that.
Or is there a
I'm the bug reporter, and I have a problem in doing the verification.
a) The initial testcase that I reported happens in both 4.4 unpatched
and 4.10. I.e. the bug that I reported is not yet fixed.
b) Some Ubuntu developer wrote a new testcase as part of doing the SRU.
I cannot reproduce that test
Public bug reported:
The following function is defined in /etc/init.d/dnsmasq:
start_resolvconf()
{
# If interface "lo" is explicitly disabled in /etc/default/dnsmasq
# Then dnsmasq won't be providing local DNS, so don't add it to
# the resolvconf server set.
for interface in $DNSMASQ_EXC
Better regex to avoid a possibly commented #port=0:
grep -qr "^[[:space:]]*port=0" /etc/dnsmasq.d/ /etc/dnsmasq.conf && return
--
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/b
** Also affects: im-config (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ibus (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:
Gunnar, one of the 3 problems here is that im-config starts ibus while it
shouldn't.
We Greeks have no need for ibus, and
IM_CONFIG_DEFAULT_MODE=auto
should understand that and act accordingly like im-switch did in the past.
In the past I've exchanged some emails with Osamu, the im-config Debi
> How can you tell that im-config shouldn't start IBus?
Isn't that why system settings vs user settings exist?
For example, my /etc/default/keyboard reads:
XKBLAYOUT="us,gr"
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
Then for example Gnome puts those as the default layouts for my session.
Hi Gunnar,
that patch works lovely for me, I tried it in Wily beta 2 + updates in:
gnome-flashback-metacity (running ibus)
mate-desktop (running fcitx)
lubuntu (running fcitx)
...and it prohibited ibus and fcitx from running, solving the keyboard layout
switching problems that they were causing (
Thanks a lot Martin, works fine for me.
/me reverts the LTSP workaround...
--
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/1492546
Title:
Systemd runs ifdown on shutdown ev
Hi Robie,
while this also happens in Debian, the use case is more common in Ubuntu,
because NetworkManager is patched to use a spawned dnsmasq instance as a local
resolver, and mixing the two DNS servers is problematic (neither bind-dynamic
nor bind-interfaces work very well).
In Debian they mo
Public bug reported:
Ubuntu 14.04, upstart 1.12.1-0ubuntu4.2.
man Xsession:
"Xsession may optionally be passed a single argument indicating the type of X
session to be started."
"default produces the same behavior as if no session type argument had been
given at all."
In /etc/X11/Xsession.d/
To work around the issue from the LTSP side, I pushed the following changes:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1577
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2646
Anyone interested in getting Unity to work with LTSP in Ubuntu 14.04 should
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ltsp (Ubuntu)
Importance: Undecided => High
** Changed in: ltsp (Ubuntu)
Status: New => Fix Committed
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) => Alkis Georgopoulo
The "no tray" issue was fix-committed in
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1457730
The "no lock screen" issue was fix-committed with LDM_PASSWORD_HASH.
** Changed in: ltsp
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of
Public bug reported:
The unit /lib/systemd/system/ifup@.service is Debian and Ubuntu specific, it's
not part of upstream systemd.
On shutdown, it unconditionally ifdowns all interfaces:
ExecStop=/sbin/ifdown %I
This is a regression from previous init systems (sysvinit and upstart)
which cared
This also affects LTSP, e.g. Wily clients can't shutdown because
/sbin/poweroff is no longer accessible once ifup@.service unmounts
/dev/nbd0.
If systemd is fixed in Ubuntu before 15.10 is released, problem solved,
otherwise we'll need to commit the following in upstream LTSP.
Script /usr/share/l
Public bug reported:
Ubuntu 14.04.3, software-properties-gtk 0.92.37.3
If I have this in my sources.list.d/some-source.list:
deb http://ppa.launchpad.net/ts.sch.gr/ppa/ubuntu trusty main #My repository
Then "main" does not appear in the list box in the software-properties-gtk
dialog → Other Sof
Hi, this fix caused a regression in ubiquity: LP: #1892014
Ubiquity doesn't put alt_shift_toggle in XKBOPTIONS anymore, so we
cannot switch to e.g. Greek using Alt+Shift, after going through a
normal installation (or even in the live session).
Are users expected to manually run `dpkg-reconfigure
The problem is not in firefox or mate, it's in gdebi-gtk, and
specifically in GDebiGtk.py, line 619:
os.execv(pkexec_cmd, pkexec_args+gdebi_args)
This replaces the current process with a pkexec call. This is not a
valid usage of pkexec, as pkexec requires the parent process to not be
init (ppid!=
Hi Gunnar, thank you for the feedback,
> Possibly console-setup could be modified again, so the default
shortcut depends on XDG_CURRENT_DESKTOP ("No toggling" for GNOME and
"Alt+Shift" for others). That way there wouldn't be a need to involve
ubiquity or other desktops.
When launching a console,
*** This bug is a duplicate of bug 1829401 ***
https://bugs.launchpad.net/bugs/1829401
** This bug has been marked a duplicate of bug 1829401
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support
--
You received this bug notification becaus
Same problem here when telling software-properties-gtk to refresh the
cache, in Ubuntu MATE 20.04.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.re
Public bug reported:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a
Hi Robie, thank you for the feedback,
I located an upstream bug report in glibc for this:
https://sourceware.org/bugzilla/show_bug.cgi?id=26401
** Bug watch added: Sourceware.org Bugzilla #26401
https://sourceware.org/bugzilla/show_bug.cgi?id=26401
** Also affects: rsync via
https://source
Hi, this update makes slick-greeter segfault, so Ubuntu MATE 18.04 users
doing normal updates now get a black screen with a flicking cursor.
A temporary workaround is to enable autologin in
/etc/lightdm/lightdm.conf:
[Seat:*]
autologin-guest=false
autologin-user=administrator
autologin-user-timeo
Hi, a recent systemd update in 18.04 makes slick-greeter segfault.
So all Ubuntu MATE 18.04 users now get black screens instead of lightdm.
It's related to memory limits so I'm cross-referencing it here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746
This didn't help:
[LightDM]
l
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:
* soft memlock 262144
* hard memlock 262144
Should all lightdm users manually put that in limits.conf, or should we
expect some update?
--
You received this bug notifica
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:
* soft memlock 262144
* hard memlock 262144
Should all lightdm users manually put that in limits.conf, or should we
expect some update?
--
You received this bug notifica
Thank you Łukasz, I filed it in LP: #1902879.
--
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/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bion
Hi all,
final freeze is approaching, and I don't see anyone syncing Andrej's new
version from Debian...
Maybe it would be easier to just accept my patch, to have this solved
for 20.04, and do the syncing for 20.10?
--
You received this bug notification because you are a member of Ubuntu
Touch s
Anydesk too. Thanks for the fix! :)
--
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/1869716
Title:
Removing libpango1.0-0 broke Minecraft Launcher
Status in pango1.0 pa
Thank you seb128! :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1867908
Title:
Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
Status in wpa package in Ubu
Public bug reported:
Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE
and Xubuntu), if a user selects a language in syslinux other than those
with an included langpack, the session is then untranslated.
For example, if one boots Ubuntu MATE 20.04 and selects Greek in
syslin
Gunnar, yes, the live sessions are properly translated up to and including
19.04 (and of course 18.04 too).
Starting from 19.10, all child processes of lightdm have LANGUAGE=en, so the
session is untranslated. But this only happens for languages that don't have
the langpack installed.
Running /
In Ubuntu 20.04 live CD, in .xsession-errors, I see this line:
dbus-update-activation-environment: setting LANGUAGE=en
Maybe that's to blame here; looking more...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservi
No, sorry, that's not it, I removed it and restarted lightdm and I still
had LANGUAGE=en in the live session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1861481
Hi Gunnar, here are the results:
Output of Ubuntu MATE 20.04 today's daily build:
$ env | grep LANG
LANGUAGE=en
GDM_LANG=en
LANG=el_GR.UTF-8
$ locale -a
C
C.UTF-8
de_AT.utf8
de_BE.utf8
de_CH.utf8
de_DE.utf8
de_IT.utf8
de_LI.utf8
de_LU.utf8
el_GR.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.
I.e. from what I can see, the basic difference is that since 19.10,
something sets LANGUAGE=en.
While in the Italian session that has a langpack in the live iso,
LANGUAGE=it.
It's not /etc/default/locale, in all the cases only LANG is there and
not LANGUAGE.
--
You received this bug notificatio
On a focal live cd, I tried to downgrade lightdm and accountsservice to
their bionic versions and restart their services without rebooting, yet
again the session was not translated. So I'm at a loss on which package
was the one that caused the change in 19.10, maybe even glibc itself.
Nevertheless
The reason that this regression doesn't affect ubuntu-desktop, might be
that unlike LightDM, GDM doesn't have that Ubuntu-specific patch to use
/usr/share/language-tools/language-options.
So, I subscribed "lightdm (Ubuntu)" to the affected packages, in case we
just want to drop the Ubuntu-specific
Gunnar, so if a MATE user doesn't have the langpack installed, he shouldn't
have a translated session?
Why do we want to fix this only for Live CDs?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://b
I mean that if, on a normal 20.04 installation, I uninstall the el langpack,
then
1) If I'm using GDM, universe apps show Greek,
2) If I'm using LightDM, universe apps show English (this one regressed in
19.10).
If we're modifying LightDM, I suggest to modify LightDM to not set LANGUAGE at
all,
Btw, lightdm doesn't set LANGUAGE at all in Debian; it only sets LANG,
like GDM, and everything works fine.
Gunnar, do you see any issues with just completely dropping your
04_language_handling.patch?
Or at least this line there:
+session_set_env (session, "LANGUAGE", language);
--
You
I commented before I saw the previous reply; I'll reply to that now.
The "grep cow" approach breaks the LTSP package and other software that uses a
COW root.
To check for casper, please `grep -w boot=casper /proc/cmdline` or something
casper-specific.
In schools, we sometimes have students of v
I checked with 20.04 and it appears that recent Ubuntu live CDs don't
have boot=casper anymore; they do still have initrd=/casper/initrd; but
anyway, ^/cow should be fine (sorry I hadn't noticed the ^ there
before).
Thank you for your work in this.
--
You received this bug notification because y
Public bug reported:
Running for example `pam-auth-update` results in
/var/cache/debconf/templates.{dat,dat-old} getting regenerated with no diff.
In focal live CD this file is 17 MB, so that wastes 34 MB of cow/tmpfs/RAM.
This also affects ltsp.org which too uses a live session.
And of course it
I've had success with:
Ubuntu 14.04.2 64bit
Lexmark S305
lexmark-inkjet-legacy 1.0-1
I played a lot before I got it to work, but I think that in the end only 2
changes were needed,
...a mode change in:
-rwxr-xr-x 1 root root 144K Aug 16 2012 /usr/local/lexmark/v3/bin/printfilter
...and in th
It also worked fine in Ubuntu 12.04 32bit, and the printfilter mode
changing wasn't needed, it's possibly not used at all with the lxusb
backend.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.lau
Public bug reported:
In Ubuntu 16.04, I've configured dnsmasq to reply on subnet=10.160.37.0/24, yet
it replies even when it gets an IP on subnet=10.161.254.0/24.
I've only seen this after clean system restart. If I restart dnsmasq later on,
it works as expected.
Maybe when dnsmasq starts, the n
I did another test:
* I unplugged the network cable so that the ltsp-server didn't have an ip.
* I ran `service dnsmasq restart`.
* I plugged the network cable back in.
* ...and the problem came back again, i.e. dnsmasq replied on invalid range.
This again suggests that it's some kind of wrong
Hi Christian,
Simon, the dnsmasq developer and Debian maintainer, frequently answers here in
launchpad as well (and there's no upstream bug tracker).
In any case, I did forward the report to the dnsmasq mailing list:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q4/011010.html
Tha
I'm closing the LTSP task as LTSP 5.5.6 got released and was published
in Xenial without the fix being included, and the newer ifupdown makes
the fix not necessary anymore.
** Changed in: ltsp (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a me
> Sebastien Bacher (seb128) wrote on 2016-04-29:#43
> @Alkis, right, the line changed was what you suggested in the upstream report
> and in comment #33,
> if that's incorrect/incomplete could you update the upstream report?
I'm sorry guys for some reason I wasn't getting notifications
Hi Gunnar,
the issue was that in some cases, typing the Greek key for accent (tonos, the
key is ";"), and then after releasing it, typing "α", resulted in two separate
characters, i.e.
;+α=´α
instead of the correct
;+α=ά
At first I thought this was because of ibus, because I was seeing the issu
The network-manager package still ships /etc/dnsmasq.d/network-manager
with "bind-interfaces" in it
and that breaks the TFTP server of dnsmasq
and sometimes even the DNS server of dnsmasq.
"bind-dynamic" is a little better, but too unreliable to be used in
production.
So this bug is still not res
With the switch to configure UTC from /etc/adjtime instead of
/etc/default/rcS, I'm having the following regression:
I've installed Xenial some months ago and it's fully updated.
Without customizing it, my /etc/adjtime reads:
0.0 0 0
0
The regression is this:
# timedatectl set-local-rtc 1
Failed
Hi Martin,
I reported it here: https://github.com/systemd/systemd/issues/2638
We also need to fix this in the systemd packaging in Debian/Ubuntu:
# grep printf /var/lib/dpkg/info/systemd.postinst
printf "0.0 0 0.0\n0\nLOCAL" > /etc/adjtime
This is similar to https://bugs.debian.org/cgi-
This is still an issue in Ubuntu 16.04, now initramfs-tools
unconditionally calls `wait-for-root /dev/nbd0 10` without even using
ROOTDELAY.
I also reported this bug to https://github.com/yoe/nbd/issues/36.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
I was able to reproduce the issue in Debian Stretch after applying an
Ubuntu specific patch to it. So I'm suspecting that Ubuntu's etwork-
manager might be involved in this, I've put it to the affects list.
Specifically, by editing Debian's /lib/systemd/system/NetworkManager.service
like this:
-A
mterry, charlesk, I took the liberty of subscribing you because I think it
involves this commit:
https://code.launchpad.net/~mterry/indicator-messages/tell-accounts-services/+merge/93290
The issue is happening to me as well, on Ubuntu 16.04 gnome-flashback, in 2
cases:
1) sometimes when I try to
Here is one method to see the dialog without working remotely:
sudo sed 's/yes/auth_self/' -i
/usr/share/polkit-1/actions/org.freedesktop.accounts.policy
Then press Alt+Ctrl+F2 to switch to vt2, and Alt+Ctrl+F7 to switch back to vt7.
After testing, to revert the change, run:
sudo sed 's/auth_sel
1 - 100 of 121 matches
Mail list logo
