I think I'm using 4, but I am set up using autofs and haven't touched
NFS directly:
# /etc/auto.home
* -fstype=nfs,rw,async servername:/nfshome/&
`nfsstat -c` tells me: "Client nfs v4"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
If this is the same problem I'm having
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1901279)
Then a workaround that works for me is to set the display with
`xsetwacom` using coords or HEAD-1 (VGA-1 and DP-3 type identifiers
aren't working)
$ xsetwacom --set "Wacom Intuos
** Summary changed:
- map wacom drawing tablet to single monitor doesn't work
+ wacom tablet map to single monitor doesn't work with nvidia drivers
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Upon further investigation, this appears to be a problem with the
display output names names no longer being recognized when using some
nvidia drivers. e.g VGA-1 HMDI-0 etc as provided by xrandr
For example:
$ xsetwacom --set "Wacom Intuos Pro S Pen stylus" MapToOutput DP-3
Unable to find an
https://www.reddit.com/r/gnome/comments/frncmc/tablet_monitor_mapping_not_working_on_ubuntu_2004/
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1901279
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
When I try to map my wacom tablet to a single monitor, it doesn't do
anything. The tablet appears fine with the proper name in the tablet
setting app, and it appears if I run xsetwacom --list
Tried:
Wacom Graphire3 4x5 (CTE-430)
Wacom Intuos Pro S (PTH-460)
Also same
** Description changed:
My physical computer lab uses nfs home drives. If any user tries to
run chromium browser, it fails.
- I assume it is related to this:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
+ I assume it is related to these:
+
Public bug reported:
My physical computer lab uses nfs home drives. If any user tries to
run chromium browser, it fails.
I assume it is related to this:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
But that says a fix was released.
$ chromium -v
cannot create user data
*** This bug is a duplicate of bug 1857191 ***
https://bugs.launchpad.net/bugs/1857191
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
2) The version of the package you are
Public bug reported:
Description:Ubuntu 20.04 LTS
with ubuntu-desktop and libnss-ldapd
Trying to log in to the desktop environment when the username (e.g
9912345) begins with a number results in a black screen, and then quits
back to the log in screen.
Here is the error:
Confirmed for:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
$ uname -a
Linux tbl-hackerspace-01-e 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
11 matches
Mail list logo
