It may also be worth noting that Kerberos/GSSAPI authentication for NFS
works a bit differently from Kerberos/GSSAPI authentication for
applications, because NFS happens in the kernel, and therefore the
kernel needs to get access to the Kerberos tickets (credentials). The
kernel's NFS client does s
Also reported upstream at https://github.com/mate-
desktop/atril/issues/506
** Bug watch added: github.com/mate-desktop/atril/issues #506
https://github.com/mate-desktop/atril/issues/506
** Information type changed from Private to Public
--
You received this bug notification because you are
I should add that at the moment, my first problem is still that NFS
seems not permitted at all:
$ aptitude show snapd
Package: snapd
Version: 2.47.1+20.04
State: installed
# snap install pdftk
2020-10-26T15:12:47Z INFO Waiting for automatic snapd restart...
pdftk 2.02-4 from S
on an NFS filer. Specifically, my environment has the following
characteristics:
$ getent passwd mgk25
mgk25:*:1597:1597:Markus Kuhn:/home/mgk25:/bin/bash
$ echo $HOME
/home/mgk25
$ ls -l /home
lrwxrwxrwx 1 root root 5 Oct 22 23:35 /home -> homes
$ ls -l /homes
lrwxrwxrwx 1 root root 11 Oct 13 20
Dear newcomers to this issue. As explained above in [comment
122](https://bugzilla.mozilla.org/show_bug.cgi?id=505024#c122), this
issue is really a bug (violation of the MIME standard) **in the calendar
function of Microsoft Exchange** that sends these messages. Regarding
Thunderbird, this issue is
Should the capitalization of Adwaita not also be fixed for Ubuntu 18.04
(bionic) in package xubuntu-icon-theme file /usr/share/icons/elementary-
xfce/index.theme which still says
Inherits=adwaita,gnome,hicolor
even though /usr/share/icons/Adwaita has a capital A?
--
You received this bug noti
See also
https://lists.ubuntu.com/archives/apparmor/2018-October/011823.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784499
Title:
AppArmor treats regular NFS file access as network op
To ma
The real bug here is that AppArmor should restrict NFS access only via
the file-path rules, and not via the network rules, since if an
application accesses a file via NFS, all related network traffic is
initiated and controlled by the kernel (or by kernel helper processes
like automount, rpc.gssd a
AppArmor really should restrict NFS access only via the file-path rules,
not via the network rules, since if an application accesses a file via
NFS, all related network traffic is initiated and controlled by the
kernel (or by kernel helper processes like automount, rpc.gssd and
nfsidmap), and not b
Thanks for releasing the fix! I can confirm that the reported problem no
longer appears with the new ghostscript 9.25~dfsg+1-0ubuntu0.18.04.1.
** Changed in: ghostscript (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bu
Related-sounding bug reports:
https://bugs.ghostscript.com/show_bug.cgi?id=699324
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889302
** Bug watch added: Ghostscript (AFPL) Bugzilla #699324
http://bugs.ghostscript.com/show_bug.cgi?id=699324
** Bug watch added: Debian Bug tracker #88
Public bug reported:
Certain PDFs such as
https://www.cl.cam.ac.uk/downloads/ring/ring-2014-05.pdf
render in ghostscript 9.22~dfsg+1-0ubuntu1.1 (as found on a fresh Ubuntu
18.04.1 LTS install) with almost all characters replaced by either
random characters or empty rectangles. Same problem in
LightDM is already able to create the xauthority file locally under
$XDG_RUNTIME_DIR, using configuration option user-authority-in-system-
dir. This option is off by default on Ubuntu 16.04/18.04, but can be
enabled with
# echo -e '[LightDM]\nuser-authority-in-system-dir=true'
>/etc/lightdm/lightd
see also bug 685194
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648107
Title:
$XAUTHORITY should move into $XDG_RUNTIME_DIR
To manage notifications about this bug go to:
https://bugs.launchpad.n
Likewise, I get
$ okular
Icon theme "adwaita" not found.
Icon theme "adwaita" not found.
(on Xubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787989
Title:
adwaita icon them not found
To
Could not perhaps Tor be fixed to follow the advice for developers at
the end of
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#whatdoesthismeanformeadeveloper
such that it can be started up even if the network has not yet been
allocated all addresses?
--
You received this bug
While we are at it, we could probably also set
ICEAUTHORITY=$XDG_RUNTIME_DIR/ICEauthority
in a similar fashion, as this is the equivalent cookie facility for X11
client-client communication.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm the diagnosis in #7 and suggest the attached patch as a
fix.
** Patch added: "patch for /usr/lib/systemd/scripts/nfs-utils_env.sh"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1614261/+attachment/4892651/+files/nfs-utils_env.diff
--
You received this bug notificatio
** Changed in: nfs-utils (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614261
Title:
RPCSVCGSSDOPT is ignored by boot script
To manage notifications ab
As a workaround, install the attached shell script as
/etc/X11/Xsession.d/10local-xauthority
It uses xauth to merge ~/.Xauthority into $XDG_RUNTIME_DIR/xauthority
and then updates XAUTHORITY to point at that location.
(Note that the "xauth merge" command will leave a warning such as
"xauth: f
Public bug reported:
Historically, the X authority file was placed into $HOME/.Xauthority
such that X11 clients on remote servers could access it in environments
in which $HOME is located on a network file system.
Today, this practice has become an anachronism that causes far more
problems than i
Correction: In #9 I should have said "no longer exists in Ubuntu 16.04".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380080
Title:
Cannot make directory '/var/run/screen': Permission denied (conv
If I understood the following correctly, this bug no longer exists in
Ubuntu 14.04, thanks to the switch to systemd:
The file
$ cat /usr/lib/tmpfiles.d/screen-cleanup.conf
d /var/run/screen 0775 root utmp
in package "screen" tells systemd-tmpfiles to create /var/run/screen and
$ systemctl list-
General comment: I would not consider "Use of uninitialized value"
warnings in Perl on their own as evidence of a lack of software quality.
If a Perl programmer deliberately used the fact that undef also works as
an empty string, I would still consider that to be a perfectly
legitimate Perl program
Public bug reported:
In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the
package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is
still included.
How to reproduce:
$ sudo apt-get install ntp
$ dpkg-query -L ntp | grep sntp
/usr/share/man/man1/sntp.1.gz
Expected resul
In Ubuntu 16.04, you could place into /etc/NetworkManager/dispatcher.d
/pre-down.d a script to run something like "killall -s USR1 automount &&
sleep 1". This should help to timeout non-busy automounts before the
network interface goes down.
--
You received this bug notification because you are a
** Also affects: ufw (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ufw (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946322
Title:
Add ICMP/IGMP protocols to c
If I understood correctly, historically there have been two
independently developed alternative user-space mechanisms that can
perform uid <-> user name lookups for the Linux NFSv4 implementation in
the kernel, one from the University of Michigan and one from NetApp:
A) /usr/sbin/rpc.idmapd runs
I can confirm that the problem persists (and possibly even has become
more common) here with the recent kernel update:
$ ls -ld /some-nfsv4-mounted-directory ; cat /proc/key-users ; uname -a
drwxrwsr-x 2 4294967294 4294967294 4096 Dec 20 2007 .
/proc/key-users: 0:60 59/59 53/2000 1226/400
Practically all PostScript interpreters out there either include the 13
standard fonts
- Times (Roman, Italic, Bold, Bold Italic)
- Helvetica (Regular, Oblique, Bold, Bold Oblique)
- Courier (Regular, Oblique, Bold, Bold Oblique)
- Symbol
(listed in Appendix E of the PostScript Language R
These "xhost +si:localuser:..." settings have also caused problems to Tk
users on RedHat/Fedora systems in the past:
https://bugzilla.redhat.com/show_bug.cgi?id=349071
https://partner-bugzilla.redhat.com/show_bug.cgi?id=216236
It all goes back to the Tk changes entry
4/26/93 (new feature)
Since Ubuntu uses several "xhost +..." lines in its default
configuration, one could argue it should have compiled TCL/Tk with the
TK_NO_SECURITY flag set, otherwise Tk's "send" IPC breaks, which is
really what I suspect this bug report is all about.
Even better would be to patch in Tk the "xhost"
Really a Tk problem, nothing to do with openssh, therefore changing
package and reopening.
** Package changed: openssh (Ubuntu) => tk8.5 (Ubuntu)
** Changed in: tk8.5 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The problem may be related to Ubuntu (experienced on 10.4) apparently
executing the commands
xhost +si:localuser:`id -un`
xhost +si:localuser:root
xhost +si:localuser:gdm
or does something equivalent when you log in. Just type "xhost" to see
the list of non-xauth authorizations currently enabled
34 matches
Mail list logo
