Public bug reported:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu
Indeed that's the French translation of "No space left on the device".
As I explained in the comments, I have remastered an ISO (of 20.04) to
connect to my professional workspace (VPN Cisco AnyConnect and Citrix),
because I don't want those 2 closed source things to mess up with my
environment.
I
Public bug reported:
In to the bug reported here:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1664067
indicator-datetime was apparently aware of the locale depending of the
options chosen.
Now it does not at all apply the locale, whatever the option chosen.
Environment:
U
Public bug reported:
VERSION AND CONTEXT
===
$ uname -a; lsb_release -a; dash --version; dpkg -s dash
Linux alain-Desktop 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Descriptio
NOTE: can someone move the status to "Won't Fix" please, it is not
available to "regular users"!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1499473
Title:
dash printf bui
Well, I made some more research: I think this can be closed as
WON'T FIX
This seem to be a feature (not a bug) to comply exactly to POSIX,
**nothing more**.
Here is the related POSIX documentation:
http://www.unix.com/man-page/POSIX/1posix/printf/
It specifies octal escaping, and it also explai
Confirmed also on a clean 20.04, kernel 5.4.0-31-generic
The time difference between gzip and lz4 is not noticeable by the user:
LZ4:
Startup finished in 14.815s (firmware) + 3.483s (loader) + 1.879s (kernel) +
23.176s (userspace) = 43.354s
graphical.target reached after 23.164s in userspace
GZ
Ok, so *I fixed it!*
Sorry guys, the 'patch' process is a bit complicated here, so I'll just
give a diff to what I have done, and explain why:
$ diff aa-status aa-status_orig
137,140c137,140
< for p in open("/proc/mounts","rb").readlines():
< if p.split()[2].decode() == "securityfs"
Thanks Christian for the heavy lifting on the mailinglist and bzr.
I didn't understand, on the FAQ, about yielding permissions to Canonical. Is
that about proposing patches on Launchpad itself, or does it also apply for
projects hosted on launchpad.
Anyway, to whomever, Canonical or "upstream te
[EDIT] Obviously I meant fancy mountpoints having spaces or \n, do *NOT*
break aa-status!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1310598
Title:
AppArmor python to
After some months where it didn't seem to crash -or at least apport
didn't report anything-, now this is crashing again with the same stack
trace about reading my UTF-8/non-ascii mounts.
I'm sending new apports automatic crash reports.
Although, Christian, I would find it normal that it crashes w
11 matches
Mail list logo
