The current Firefox AppArmor profile includes the "openssl" abstraction,
which allows access to /etc/ssl/openssl.cnf. This bug should no longer
be present in Ubuntu.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
Does this issue still occur with Firefox 60 or later? I am unable to
reproduce it on 18.04/bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885211
Title:
firefox generates apparmor violations
I think we could really use some kind of conditional construct (IF ...
THEN ...) in AppArmor syntax. Everything being talking about here
should, ideally, be adjustable using tunables. With a debconf
configuration option, even.
Between users who want strict access control to user files, and users
For the record, Firefox 61 very much does continue to make use of
/proc//smaps (and /proc//statm) when using the about:memory
page.
I confirmed this by experimentally commenting out the AppArmor rules for
those two /proc files (motivated by comment #3 above), and subsequently
observed
Public bug reported:
This concerns shim 13-0ubuntu2 in Ubuntu 18.04/bionic.
(Note: I am not entirely clear on whether this issue belongs to shim, or
to grub2; please redirect as appropriate.)
I am installing Ubuntu with EFI support with the following two
prerequisites:
1. No changes are made
I should point out that on the Debian side, the same conditional exists
in the postinst script, so this same issue occurs there as well. (Only
with the /boot/efi/EFI/debian/ directory, of course.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
This concerns grub-efi-amd64 2.02-2ubuntu8.1 in Ubuntu 18.04/bionic.
When the grub-efi-amd64 package is initially installed on a system that
has not previously booted via the Ubuntu EFI bootloader (so /boot/efi/
is either empty, or at least does not have a
Hello everyone,
There is a bug report similar to this one on the Debian side:
https://bugs.debian.org/902928
There, Colin Watson made an interesting comment:
> When I last looked into this, this wasn't possible with UEFI: the
> firmware doesn't tell us about held modifier keys. You'll
Public bug reported:
This concerns xfce4-pulseaudio-plugin 0.4.1-0ubuntu1 in Ubuntu
18.04/bionic.
In an Xfce desktop session, when this package is installed, and
Pulseaudio is not active, I see a steady procession of these messages in
~/.xsession-errors:
(wrapper-2.0:2036):
Dimitri, thank you for laying out the rationale behind the package name.
Since there is good reason for things to be the way they are here, I've
opened a bug on the Debian side for them to address the naming
inconsistency:
https://bugs.debian.org/904152
** Bug watch added: Debian Bug
This issue can be addressed with a manual action, but first you have to
dig into the scripts to diagnose the problem, and really if resolvconf
is installed then it should just work.
Part of this setup involves disabling systemd-resolved, in favor of a
"direct" /etc/resolv.conf, to match the
Public bug reported:
The package that Ubuntu calls "ubuntu-keyring" is present in Debian as
"ubuntu-archive-keyring".
Debian has separate "debian-keyring" and "debian-archive-keyring"
packages, described as follows:
d-k: GnuPG keys of Debian Developers and Maintainers
d-a-k: GnuPG
Public bug reported:
I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead of
netplan, as the latter does not meet my needs. I am using resolvconf to
update /etc/resolv.conf from DHCP, as in earlier releases.
Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to
Public bug reported:
When I install resolvconf on a minimal install of Ubuntu 18.04 (bionic),
I see this:
# apt-get install resolvconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
resolvconf
0
Philip Susi: Confirmed with the Bionic live CD:
root@xubuntu:~# cat /proc/cmdline
BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper
iso-scan/filename=/linux/xubuntu-18.04-desktop-amd64.iso toram
root@xubuntu:~# umount /isodevice
umount: /isodevice: target is busy.
root@xubuntu:~# losetup -d
This bug appears to have been fixed in 8.32.0-1ubuntu4. Looks like this
was an issue with the Apparmor profile.
rsyslog (8.32.0-1ubuntu4) bionic; urgency=medium
[ Jamie Strandboge ]
* debian/usr.sbin.rsyslogd: updates for bionic (LP: #1766600)
- allow rsyslog modules in multiarch
Hi Brian,
This is actually the same issue.
I am seeing the same error message quoted by the original reporter, but
that message is filtered through systemd---it is not direct output from
rsyslogd. What I provided was the direct output, that actually shows
what's going on.
I think this needs to
I am seeing this same error in Bionic. Some further telemetry:
# /usr/sbin/rsyslogd -n
rsyslog internal message (3,-2066): could not load module
'/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so', dlopen:
/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so: failed to map segment from shared
object
[v8.32.0
Thanks Dimitri, greatly appreciated. I haven't found many problems in my
testing of Bionic, but this is the juiciest one so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731522
Title:
Steve, Bionic still has the default (commented-out)
#DNSStubListener=udp
in /etc/systemd/resolved.conf .
I've noticed that this breaks Kerberos KDC lookup at a large site,
because the reply is quite large:
# host -t SRV _kerberos._udp.xxx.example.com
;; Connection to
Public bug reported:
This concerns linux-base 4.0ubuntu1 in Ubuntu Xenial.
Removing Linux kernel packages from the system leads to initrd
generation and causes /var/run/reboot-required to appear. Neither of
these side effects should occur if only kernel packages older than the
running one are
Confirmed that this fixes the segfault for me when applied to version
3.20.0. Thanks :)
(Figured this would be easy to reproduce...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468
Title:
Er...
$ klist -v
klist: invalid option -- 'v'
Usage: klist [-e] [-V] [[-c] [-l] [-A] [-d] [-f] [-s] [-a [-n]]] [-k [-t]
[-K]] [name]
[...]
Remember, the segfault occurs with a user that is local-only. Kerberos
infrastructure is installed on the system, but the user has no
Hi Guido, I think you mean "klist -V" (uppercase) :-)
On the system in question, that returns
$ klist -V
Kerberos 5 version 1.13.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468
Attached is a Valgrind log file produced from a debug build of k-a-d
version 3.20.0.
All the errors appear to be accesses within freed memory...
** Attachment added: "kad-valgrind-log.txt"
Hunh. How odd... I can't imagine that there would be something
particular to this system that is causing the crash. As you requested:
skunk@darkstar:/tmp/krb5-auth-dialog-3.20.0/_build/src$ G_MESSAGES_DEBUG=all
./krb5-auth-dialog -a
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG:
Thank you Dimitry, that is a helpful link.
I've removed the key-file attachment from comment #5, but am unable to
otherwise edit/remove the text.
** Attachment removed: "dbgsym-release-key.asc"
I'm afraid I see the same failure mode with 3.20. The GDB session is
below.
(You're not able to reproduce this? This is a system with all the
Kerberos infrastructure, but a local-only user---no KRB* envvars set)
$ gdb --args /tmp/krb5-auth-dialog-3.20.0/_build/src/krb5-auth-dialog --auto
GNU
Public bug reported:
This concerns krb5-auth-dialog 3.12.0-2 in Ubuntu Xenial.
When the program is invoked with the --auto option, it briefly maps the
systray icon, and then segfaults.
Here is a GDB session running on a debug build of the original package
source:
$ gdb --args
I agree on this key needing to be available in the/an official Ubuntu
keyring package.
For now, because the original key file is not even accessible via HTTPS,
I am attaching a copy of it here. The file is dated 2016-07-04 16:10,
and has the following SHA{256,512} hashes:
Hi Luigi,
This StackExchange posting should answer your question:
https://unix.stackexchange.com/questions/3586/what-do-the-numbers-in-a
-man-page-mean
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Benjamin, what you're seeing appears to be bug #1607535. (That bug
report doesn't quote the "/the fonts/" URL directly, but it links to a
comment that does.
I have a bug report (bug #1575408) against ttf-mscorefonts-installer due
to the "Can't drop privileges" warning, but am assuming that that
*** This bug is a duplicate of bug 1522675 ***
https://bugs.launchpad.net/bugs/1522675
This appears to be a duplicate of bug #1522675, which more broadly
addresses the "_apt" user permissions issue.
** This bug has been marked a duplicate of bug 1522675
Can't drop privileges for
Hi Alex, the failure to download is actually bug #1607535. This bug is
about the "Can't drop privileges" warnings, which are ultimately
harmless to package installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update: This bug is NOT a duplicate of
https://bugs.launchpad.net/bugs/1607535
(Bug #1607535 is about unreliable SourceForge servers; this is about
warnings from the package scripts)
** This bug is no longer a duplicate of bug 1607535
ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install
Public bug reported:
I'm filing this against dkms 2.2.0.3-2ubuntu11.2 in Ubuntu Xenial,
although the issue may come down to a different package.
I issued an "apt-get --purge autoremove" command to clear out some old
kernel packages, and the command took several minutes to complete due to
kernel
I should point out, the update-initramfs invocations should also not be
happening for kernel packages being removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636701
Title:
Removing kernel
Maybe make display-manager.service into an actual service file (rather
than a symlink), and have that start whatever /etc/X11/default-display-
manager points to?
What I want is to be able to disable and then re-enable the display
manager starting on boot using similar administrative commands,
Public bug reported:
This concerns unattended-upgrades 0.90 in Xenial.
Here is an excerpt from an e-mail report sent out by u-u after the
upgrade process is completed:
Package installation log:
Log started: 2016-07-06 17:24:21
Preconfiguring packages ...
This whole systemd thing is new to me, and I can't say I'm terribly
enamored of it, so I'm not the best person to ask. But by way of
example, I'll point out what a couple other .service files do:
/lib/systemd/system/rsyslog.service:
[Install]
WantedBy=multi-user.target
Public bug reported:
This concerns lightdm 1.18.1-0ubuntu1 in Xenial.
The /lib/systemd/system/lightdm.service file lacks an [Install] clause.
Meaning, that if you do
# systemctl disable display-manager
to prevent LightDM from starting, running
# systemctl enable lightdm
does not
Generalized the title to include terminal devices (e.g. Linux virtual
terminals) as well.
I'd like to see a better way to set this up. Yes, you can add the syslog
user to the dialout and/or tty groups, but that grants access to *all*
serial/terminal devices respectively. This can have security
Thanks to systemd, I've had to update my setterm invocation in
/etc/rc.local to the following:
setterm --term linux --blank 0 --powerdown 0 >/dev/console
("--powersave off" fails with an "Inappropriate ioctl" error because
rc.local no longer runs directly on the Linux virtual console.)
--
On a minimal install:
# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.4.0-22-generic
W: plymouth: The plugin label.so is missing, the selected theme might not work
as expected.
W: plymouth: You might want to install the plymouth-themes and plymouth-label
package to fix
Public bug reported:
I am seeing this on a Xenial minimal install with plymouth
0.9.2-3ubuntu13 (as well as 0.9.2-3ubuntu13.1).
After the text-mode boot logo ("Ubuntu 16.04" with the four dots) is
shown on start-up, the text-mode tty1 login prompt is sometimes printed
in brown/orange text
Thank you Seth :-) Next rev in each release should have this, right?
No copyright line is needed; this was trivial to derive from the nscd
profile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seth, it seems you're absolutely right.
Denying dgram while the system is up is no big deal, because DNS lookups
go through nscd (or other similar infrastructure) instead of being sent
out directly.
But when the system is starting up, and nscd et al. aren't running yet,
the queries do need to go
Public bug reported:
I installed a minimal Xenial system. Whenever the initramfs is
regenerated, I see
W: plymouth: The plugin label.so is missing, the selected theme might not
work as expected.
W: plymouth: You might want to install the plymouth-themes and
plymouth-label package to
This issue is no longer observable in a standard console X11 login on
Xenial.
There is still an issue with GVFS daemons hanging around after an XFCE
session that was launched from a terminal (as in a remote X11 session),
but that is actually due to dbus-launch not being killed at the end of
the
Hello,
I, too, am seeing this issue of gpg-agent persisting after an XFCE
session ends. However, I think the problem may be outside of
xfce4-session proper.
In my investigation into https://bugs.launchpad.net/bugs/1577562 , I
found two places where gpg-agent may be started at the beginning of
Public bug reported:
I am using xfce4-session 4.12.1-3ubuntu1 on Xenial.
I am logging into a remote system via SSH with X11 forwarding, starting
the XFCE desktop with "startxfce4", and then exiting the session.
After logout, several processes remain visible, most notably dbus-launch
(which
Spurious dialog observed in remote X session on Xenial install with
accountservice 0.6.40-2ubuntu10.
Enabled xenial-proposed, installed accountservice 0.6.40-2ubuntu11, and
the dialog no longer appears.
I wasn't seeing this problem as badly as some other folks here, but for
my use case, the
Public bug reported:
I have a Xenial system; gnupg-agent 2.1.11-6ubuntu2 is part of the
install.
In /etc/X11/Xsession.d/90gpg-agent , gpg-agent is started if either
~/.gnupg/gpg.conf or ~/.gnupg/options contains a "use-agent" directive.
This part is working fine, as far as I'm aware.
Now, the
Public bug reported:
I am using thunar version 1.6.10-2ubuntu1 in Xenial.
Thunar connects to SMB/CIFS shares just fine, even using current
Kerberos credentials to avoid any password prompt. That part's working
great.
However, if I enter a UNC path into the location bar like
Also, for those interested, here is the GraphViz source for the "visual
aid." The graphic can be regenerated with the command
$ dot -Tpng ldap-deps.dot >ldap-deps.png
(The dot(1) command is in the "graphviz" package.)
** Attachment added: "ldap-deps.dot"
Hi everyone. I've been setting up LDAP in Ubuntu lately, and have run
headlong into this issue again.
Arguably, the situation has gotten worse in the past three years, as the
dependency rat's nest has become more convoluted.
I've put together a new visual aid to illustrate the current situation;
Minor addendum: It's conceivable that the new line should go into
rather than just the nscd profile. I do see
that the nscd socket is already mentioned there.
I don't know if/why anything else would need access to the nslcd socket,
but that may be a valid use case for other folks.
--
You
For my part, I'm not seeing DNS issues, and I've got a hostname in my
LDAP server URI.
I'm not sure what goes on under the hood for normal DNS resolution these
days (maybe DNS over TCP is favored now?), but if there's any doubt in
your mind, feel free to drop those lines.
--
You received this
Chromium continues to fail on Xenial with the title error message when
the currently-shipped AppArmor profile is enforced.
I've updated my profile adjustments to address some new issues that have
cropped up in recent builds of Chromium.
Everyone who wants to get things working again, please add
> I don't think Heimdal supports including krb5.conf snippets, which
means we can't use the include functionality in kerberos-configs.
And even if it did, it would still be awkward (you have to add the
#include at any rate). It needs to be a standard expectation these days
that configs in /etc
Public bug reported:
nslcd is a good program to be covered by an AppArmor profile, as it
communicates with an LDAP server and services queries from arbitrary
local applications.
This new profile used the existing usr.sbin.nscd profile as a starting
point.
** Affects: apparmor (Ubuntu)
Public bug reported:
I am usinc nscd with nslcd (LDAP lookup daemon) for NSS services via
LDAP.
It is typical to configure nslcd to connect to the actual LDAP server,
and then set up /etc/ldap.conf (which is what NSS/nscd uses for "ldap"
type lookups in /etc/nsswitch.conf) with a server URI of
I've been working on a Kerberos system config lately, and have once more
run into the title question.
It's been six years. Debian bugs #330882 (no real shells for system
users) and #429692 (support include directives in krb5.conf) are done
and laid to rest.
Can we move minimum_uid= out from the
Public bug reported:
Installing ttf-mscorefonts-installer 3.4+nmu1ubuntu2 on Xenial, I see
the following in the output of apt-get(8):
[...]
ttf-mscorefonts-installer: downloading
http://downloads.sourceforge.net/corefonts/andale32.exe
Get:1
Public bug reported:
I am using apparmor-profiles in Xenial.
The AppArmor profiles, by default, are set to "complain" mode by way of
"flag=(complain)" directives written into the profiles themselves.
If I want these profiles to be enforced, then I have to edit each one
and manually delete the
** Changed in: apparmor (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471645
Title:
[trusty] [regression] chromium-browser crashed with SIGABRT in
Chad, what is the intended purpose of that command? Because it's
mistranscribed:
$ dpkg -S $(grep -l /etc/apparmor.d/*)
grep: /etc/apparmor.d/apache2.d: Is a directory
grep: /etc/apparmor.d/cache: Is a directory
grep: /etc/apparmor.d/disable: Is a directory
grep:
Hi Stuart,
Note that Anacron is not a daemon; it needs to be executed at boot time
and intermittently thereafter (via that cron.d script).
It doesn't work to have Anacron run only at boot time and Cron
thereafter, because Anacron maintains state in /var/spool/anacron/ that
needs to be updated
The crash is due to AppArmor. Adding the following to the profile for
/usr/lib/chromium-browser/chromium-browser gets things working again:
capability sys_admin,
capability sys_chroot,
owner @{PROC}/[0-9]*/setgroups w,
owner @{PROC}/[0-9]*/gid_map w,
owner
*** This bug is a duplicate of bug 1471645 ***
https://bugs.launchpad.net/bugs/1471645
I have configured apport to submit crash traces to Launchpad and have
filed a new report that way.
** This bug has been marked a duplicate of private bug 1471645
--
You received this bug notification
Public bug reported:
This bug report concerns chromium-browser version
43.0.2357.81-0ubuntu0.14.04.1.1089 in Ubuntu Trusty.
Previously, this system had 41.0.2272.76-0ubuntu0.14.04.1.1076
installed, and it worked correctly. Now, after an update, the browser
crashes immediately upon startup with a
Correction: I have a .crash file, but cannot find what invocation of
apport-{bug,cli} will attach it to an existing bug report.
The crash in question may be found in the Ubuntu Error Tracker at
https://errors.ubuntu.com/problem/70617e44460c73fcc19361b37a0b38c02af9090e
--
You received this bug
I think this bug is pretty serious from a usability perspective, given
that an unplanned reboot can result in lost data and pissed-off users. I
use Trusty, and would go for the SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Brian,
This issue also manifests via accidental clicking (you're about to click
in a regular application window, then the dialog pops up, with the
Restart Now button right under the pointer). Changing the default
focus only addresses accidental rebooting via keyboard---and even then,
will
I will point out that the postgresql package is part of Ubuntu main,
whereas xscreensaver is in Ubuntu universe. The distinctions between
these components of the repository are described at
https://help.ubuntu.com/community/Repositories/Ubuntu
Universe is Community maintained software, i.e.
Public bug reported:
A fresh, up-to-date, minimal (no GUI) install of Ubuntu Utopic (14.10)
results in a blank (completely black) console.
No kernel messages flash on the screen, no text-mode start-up screen
(with the Ubuntu text in the middle of the screen) appears, nothing---
just black.
The
I've observed this CreateFont error as well. If I compile and install
the DirectFB packages from Debian unstable (currently at 1.2.10.0-5.1),
the problem goes away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That bug is about not using the system-configured HTTP proxy; this one
is about not handling network errors in general well (Python stack
traces are not supposed to be seen by end users). The two are related,
but still address distinct issues.
--
You received this bug notification because you
I would add that if the Restart Now action is selected, it should do
the usual thirty-second countdown, to allow the user a chance to cancel
if needed. Even if the default action is not to restart, an errant mouse
click in the wrong spot can still lead to the same problem.
(The dialog should not
Steve,
If anacron sending out e-mail under such circumstances is a desired
behavior, could you at least make the message more intelligible, with a
mention of the likelihood that a previously-started cron job has hung?
Even nicer would be some shell magic that greps the process table for
children
Steve,
Anacron sending out a cryptic e-mail due to a hung cron job is a primary
bug in and of itself. Either don't send out an e-mail at all, or send
an e-mail that doesn't confuse people while leaving them no avenue for
follow-up. You have enough deep knowledge of the system to intuit the
It's not clear that the chromium-browser package maintainers are
willing/interested in taking on the profile. As it is, this has been
almost entirely Jamie Strandboge's show, and he's a security guy, not a
Chromium dev.
That said, i do wonder why the profile doesn't exist in Ubuntu's
apparmor
Jorge: Check in the upstream bugzilla to see if someone's already filed
a bug, but if not, then go for it. Very few Ubuntu package maintainers
take the initiative to file upstream bugs themselves.
If you do file a bug upstream, or a report already exists, please link
it here!
(As a possible
Marcelo: You could make /sbin/fsck a shell script that wraps the real
fsck binary, and logs the output as desired. Doing this with a dpkg
diversion might even keep things from breaking when the util-linux
package is upgraded
--
You received this bug notification because you are a member of
Public bug reported:
Saw this while installing TeX on Ubuntu Saucy:
Setting up texlive-base (2013.20130722-1) ...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr:
Codeslinger, Windows is not known to trash hard drives when booting
for no other reason than seeing an out-of-order partition table. I don't
know what happened in your scenario, but it was likely some errant tool
like a defragmenter or partitioner that was not able to handle such a
table. If
Tristan, I agree with you, but unfortunately would have to recommend
using Debian instead of Ubuntu for server applications. Not only was
this bug the result of an oversight in switching to mountall, mountall
itself made the system less admin-friendly by doing away with several
boot-time shell
Bryan: Are you saying 256MB was needed in order for the crash kernel to
boot, that 128MB was not enough?
(I'm not sure that there is any advantage to reserving more memory than
needed, aside from the kernel one day growing to need 129MB)
--
You received this bug notification because you are a
Ah, okay, that's an issue. Not only do we not have an easy way of
measuring how much memory a kernel needs to boot, we don't know how that
requirement varies depending on the system configuration...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Walter Garcia-Fontes, please do not mark this bug as a duplicate of bug
1037662. This bug occurred due to a proxy issue, but it specifically
addresses p-d-d's inability to handle network errors in general in a
robust way.
** This bug is no longer a duplicate of bug 1037662
Walter,
adobe-flashplugin is only available in the Canonical partner
repository, which is not enabled per default, and should not be required
to install Adobe Flash. The flashplugin-installer package is still very
much needed as a solution that can reside within the regular Ubuntu
repositories.
Christopher,
This wishlist item is properly implemented in a system script
(/etc/X11/Xsession.d/90x11-common_ssh-agent) authored and provided by
Debian/Ubuntu, not by Xorg upstream. The file path in the source tree is
xorg-7.6+12ubuntu2/debian/local/Xsession.d/90x11-common_ssh-agent
(as
Christopher,
Let me rephrase what I said: This wishlist item properly belongs in
90x11-common_ssh-agent; it has yet to be implemented.
That GNOME discussion from six years ago is not relevant here. Fedora
may be doing something like what is described in that thread, but
Debian/Ubuntu are not.
Christopher: thanks.
Upstream patching isn't really applicable here, because the script in
question is distribution-specific session-setup code.
As for demo code, here's a tidbit to get the ball rolling:
if [ -n $XDG_RUNTIME_DIR -a -d $XDG_RUNTIME_DIR ]; then
SSHAGENTARGS+=-a
Agreed. It's not clear that there is *any* standard Ubuntu kernel
configuration that can boot in 64MB. And having that as a default is
worse than useless, because the crash-kernel's OOM prevents the system
from recovering automatically after a kernel crash.
--
You received this bug notification
Bryan: Could you elaborate on how this issue appears to be fixed in
13.04? Was the memory reservation increased to 128MB, or is the kernel
now capable of booting in 64MB? Given the lack of any updates here, I'm
doubtful that any progress has been made at all.
Dave: Have you tried crash-booting a
The prompt does look better in the Ubuntu theme, at least as far as
error messages are concerned. Still need a better way of displaying the
long disk UUID.
** Attachment added: ubuntu-prompt.png
Would it be possible to reformat the prompt for a better fit? E.g. use
UUID= instead of /dev/disk/by-uuid/, and maybe break it out across
multiple lines, like
Unlocking disk
Device: UUID=12345678-1234-1234-1234-12345678abcd
Target: sda2_crypt
Enter passphrase: []
The error message remains in place even as you type in the passphrase
again.
** Attachment added: crypt-prompt-2b.png
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1205054/+attachment/3749097/+files/crypt-prompt-2b.png
--
You received this bug notification because you are a member
Unfortunately, things get worse from there. If the passphrase entered is
incorrect, the error message partially obscures the passphrase-entry
field (see attached).
** Attachment added: crypt-prompt-2.png
101 - 200 of 872 matches
Mail list logo
