In the latest man pages I recently found:
Since util-linux 2.35, mount does not exit when user permissions are
inadequate according to libmount’s internal security rules. Instead, it
drops suid permissions and continues as regular non-root user. This
behavior supports use-cases where root
Both options and a third exist.
Extract from man mount in section FILESYSTEM-INDEPENDENT MOUNT OPTIONS:
user
Allow an ordinary user to mount the filesystem. The name of the
mounting user is written to the mtab file (or to the private
libmount file in
This applies to all versions up to 22.10.
** Changed in: nemo (Ubuntu)
Status: Invalid => New
** Changed in: glib2.0 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in
Yes, but this bug is about focal (+ impish), and I'm missing 21.2.x (or
21.3.x) on focal updates.
--
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/1956915
Title:
New bugfix
Hi, since 4 weeks the state is "fix released".
But I do not see this with:
sudo apt dist-upgrade
Why?
--
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/1956915
Title:
New
Here is a similar problem on 20.04 (Focal):
https://forum.winehq.org/viewtopic.php?f=8=36119=135865#p135852
The following packages have unmet dependencies:
perl-base : Conflicts: perl-base:i386 but 5.30.0-9ubuntu0.2 is to be installed
perl-base:i386 : Conflicts: perl-base but 5.30.0-9ubuntu0.2
I have installed version 21.2.6 by:
sudo add-apt-repository ppa:savoury1/display && sudo apt upgrade
since some time.
I never had noticed problems and bug 1950044 was fixed by that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #3969
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
Hi,
I was running into this problem:
https://bugs.winehq.org/show_bug.cgi?id=50864
The current workaround is:
sudo add-apt-repository ppa:savoury1/display && sudo apt upgrade
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags:
** Changed in: tracker (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1946561
Title:
tracker causes 0 bytes free in /home
current boot log ...
** Attachment added: "boot_2021-10-11_20-50-34.log.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1946561/+attachment/5531987/+files/boot_2021-10-11_20-50-34.log.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Now I intentionally forced the problem again to provide:
$ du -a .cache/tracker/
4 .cache/tracker/last-crawl.txt
4 .cache/tracker/db-locale.txt
1406936 .cache/tracker/meta.db-wal
356 .cache/tracker/ontologies.gvdb
4 .cache/tracker/first-index.txt
4
These are some boot logs, hoping you find, what you look for.
** Attachment removed: "boot_2021-10-07_18-25-11.log"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1946561/+attachment/5531978/+files/boot_2021-10-07_18-25-11.log
** Attachment removed: "boot_2021-10-07_01-56-33.log"
These are some boot logs, hoping you find, what you look for.
** Attachment added: "boot_2021-10-07_01-56-33.log"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1946561/+attachment/5531976/+files/boot_2021-10-07_01-56-33.log
--
You received this bug notification because you are a
** Attachment added: "boot_2021-10-07_18-25-11.log"
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1946561/+attachment/5531978/+files/boot_2021-10-07_18-25-11.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1946561
Title:
tracker causes 0 bytes free in /home
Status in tracker package in Ubuntu:
Incomplete
Bug description:
Public bug reported:
This is what I have:
Partition Ubuntu mounted in / : 20 GiB, 12 GiB in use
Partition home mounted in /home : 8 GiB, 3.1 GiB in use
Partition Data mounted in /mnt/Data : 120 GiB, 35 GiB in use
Symlink /home/me/Download -> /mnt/Data/Users/me/Download
Symlink
Public bug reported:
Ubuntu 16.04 32-bit
In fstab I have:
UUID=38e6603c-6b17-488a-9613-7341e8e89274 none swapsw 0
0
But I have 2 swap partitions on my hard drive, the other for a 64-bit instance.
With this setting, suspend-to-disk (STD) was functional in ~ 50 % of the
Hi,
I experience this bug again with Ubuntu 14.10.
I need to do:
sudo alsa force-reload
To make it work permanently, I need to edit /etc/pulse/default.pa :
load-module module-alsa-sink device=hw:0
load-module module-alsa-source device=hw:0
--
You received this bug notification because you are a
Added tag dataloss.
If user had some open documents and is not able to login after automatic
screen-lock/standby, his data is lost forever, when user without administrator
knowledge only is able to shut down his PC.
** Tags added: dataloss
--
You received this bug notification because you are
20 matches
Mail list logo
