Package: bash-completion
Version: 1:2.1-4
Severity: minor
Tags: upstream patch
Figuring out how to customize the pre-installed Debian bash completions
is not easy.
This is probably what happens to your average CLI user when they get fed
up with some of bash completion's defaults and decide to try
Package: avahi-autoipd
Version: 0.6.31-4+b2
Severity: normal
Dear Maintainer,
The avahi-autoipd package places a script in /etc/network/if-up.d.
When the avahi-autoipd package is removed, but not purged, this script
still alters the state of the system, because it performs no checks to
ensure t
Package: gnome-shell
Version: 3.14.2-3+b1
Severity: normal
When GNOME desktop is configured to raise and focus windows on click,
and one clicks on a window title bar to raise it, sometimes the window
remains "grabbed" for moving. This appears to be due to failure to
handle mouse-up events, becau
Package: reportbug
Version: 6.6.3
Severity: normal
Dear Maintainer,
To file a previous bug report I invoked:
reportbug --email 'bju...@clarku.edu' -o cust/sensible.bug.txt
The -o option was supposed to prevent the use of email by the
reportbug tool and instead generate the file that I could em
Specifically gpm does not install a gpm.service file, and even as
such, things are configured for systemd to hijack /etc/init.d/gpm
so the daemon fails to start.
Related bugs in other tracking systems, with suggested fixes:
https://bugs.archlinux.org/task/30053
https://bugzilla.novell.com/show_b
Attached is a patch that fixes this issue and probably other related ones
that have not been reported.
--- vte-0.28.2/src/vte.c 2014-12-10 20:58:07.0 -0500
+++ vte-0.28.2-fix-termcap-restoration/src/vte.c 2014-12-10 20:52:42.833753783 -0500
@@ -8130,4 +8130,29 @@
#endif /* GTK 2.x */
+
Removing the old udev rules did indeed resolve the precipitating error and allow
a smooth boot.
I kept the files so I could recreate the boot dependency failure, so if anyone
has an idea as to what output would be useful for me to collect to diagnose the
strange emergency shell behavior, I can ta
It took a while to grep the vol_id culprit. It's probably this:
/usr/share/initramfs-tools/scripts/functions: elif [ "$FSTYPE" = "unknown" ]
&& [ -x /lib/udev/vol_id ]; then
/usr/share/initramfs-tools/scripts/functions:
FSTYPE=$(/lib/udev/vol_id -t "${FS}" 2> /dev/null)
--
To UNS
Michael Biebl wrote:
> You have a broken/outdated 60-persistent-storage.rules in
> /etc/udev/rules.d. Why?
I don't know why. I pasted my package history for udev|systemd at the end of
the email.
> You have a device listed in /etc/fstab which doesn't exist during boot,
> Please double check if
Michael Biebl wrote:
>Am 26.07.2014 20:10, schrieb Brian Julin:
>> 3) If you enable "quiet" and run the recovery mode, you will get login
>> prompts
>> within a minute or two. You will get two login prompts running
>> simultaneously.
>> Once you hav
I just went through this ordeal myself. Here are some observations.
1) The problem causing the OP to enter emergency mode in the first place
is likely because systemd does not seem to (with current packages) want
to do anything with swap or non-root partitions that are referenced by
UUID in /etc
Package: libvte9
Version: 1:0.28.2-3
Severity: normal
Terminals based on libvte do not reset the auto-wrap mode (DECAWM)
when they are sent a DECSTR (soft reset) sequence.
This causes strange line wrapping behavior after interfacing with
a new (and broken) curses-like stack that is starting to a
Sigh, well what can you do if upstream just
doesn't care... thanks.
.oO(We've had centralized privilaged daemons
providing multi-user access to video hardware
for how many years now? You'd think the model
for securely sharing DMA and memory apertures
would be textbook enough for devels to be co
13 matches
Mail list logo
