[Bug 1893771] [NEW] gnome fonts too large / detected screen size incorrect
Public bug reported: Hi! after the latest update, I observe problems with the font size used by gdm and the gnome gui. It seems that the font size is now twice as large as before. This affects the login screen as well as elements of the gui (top bar, icon names on the desktop, pop up menus when right-clicking on the desktop). Fonts of standard applications (firefox, libreofffice, etc.) still have the correct size. I'm currently using a 43" 4K monitor. xpdyinfo correctly detects its resolution (3840x2160), but the detected screen size is obviously wrong (602x341 mm2, which would correspond to a 27" monitor). Please see attached screenshot. My NVidia Driver Version is: 440.100 The problem can be temporarily fixed by going to Settings->Displays, and then clicking "Scale 200%" and "Apply". A dialog appears and asks whether I would like to keep the setting. If I click "revert", all font sizes are now ok. Unfortunately the problem reappears after a reboot. Similar reports can be found under: https://askubuntu.com/questions/1268993/ubuntu-20-04-font-and-ui-elements-too-big-on-login Many thanks for your time! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 12:58:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-26 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=6643d18b-001d-4ec7-a81b-e9b6f17236aa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 PRO GAMING/AURA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd05/16/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rn970PROGAMING/AURA:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal fonts ubuntu ** Attachment added: "screen.jpg" https://bugs.launchpad.net/bugs/1893771/+attachment/5406456/+files/screen.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893771 Title: gnome fonts too large / detected screen size incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1883234] Re: unix extensions not working?
I see, it's work in progress. Many thanks! On 12.06.20 15:22, Andreas Hasenack wrote: > It's messy, and I don't think there is a general case that works for > everyone. The good news is that unix extensions for SMB3 are coming, and > there are test implementations out there already. > > There was a talk about it in the recent samba XP 2020 conference, take a > look at https://sambaxp.org/archive/ > > day 3, track 2: "Optimizing Linux Access to Samba: POSIX Protocol > Extensions for SMB3.1.1" > > The slides and video of the talk should be up soon. > > I'll close this bug in the meantime then. > > > ** Changed in: samba (Ubuntu) >Status: Incomplete => Invalid > -- Malte Kleemeier Freudenbergstr. 13 28213 Bremen Telefon: +49 421 3971382 Mobil:+49 1575 3054600 (+49 1575 8868309) (+49 179 1332707) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883234 Title: unix extensions not working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1883234] Re: unix extensions not working?
Hello Andreas,Many thanks for the fast reply!I also had to set "client min
protocol = NT1" and to start smbclient with "-m NT1", but it actually works
exactly the way you said. I would never have found the solution without your
kind help. Again, many thanks!!Maybe the fact that unix extensions are coupled
to the protocol level should be mentioned in the samba documentation (man page
of smb.conf). I did a fair amount of research on the net and could not find any
hint about that.One last question: Is it possible to share files with correct
file permissions under the current SMB3 protocol? I know the SMB protocol comes
from the windows realm, but I think it is not completely unreasonable to use it
to share files between linux boxes.Regards,Malte Kleemeier
Ursprüngliche Nachricht Von: Andreas Hasenack
<1883...@bugs.launchpad.net> Datum: 12.06.20 14:15 (GMT+01:00) An:
malte.kleeme...@googlemail.com Betreff: [Bug 1883234] Re: unix extensions not
working? Unix extensions only work for the SMB1 protocol, which has
beendeprecated and is no longer used by default. Development is ongoing
tosupport them in SMB3.You can re-enable SMB1 by adding this to [global] in the
server'ssmb.conf:server min protocol = NT1Can you please try again with the
above setting and report back?** Changed in: samba (Ubuntu) Status: New
=> Incomplete-- You received this bug notification because you are subscribed
to the bugreport.https://bugs.launchpad.net/bugs/1883234Title: unix extensions
not working?Status in samba package in Ubuntu: IncompleteBug description: I
was trying to share home directories between two linux machines, so I set-up a
samba server (using the default the smb.conf, just uncommenting things in the
[homes] section, see attached smb.conf). That worked nicely, except for one
thing: When mounting the shared home directory all files are marked as
executable. If is obviously due to the fact that unix permissions are not
correctly send from server to client. smbclient reports the following error:
smbclient //server/user Enter WORKGROUP\users's password: Try "help"
to get a list of possible commands. smb: \> stat testparm_v.log Server
doesn't support UNIX CIFS calls. According to the samba docu support for
unix permissions is controlled by "unix extensions" in the [global] section of
smb.conf. If no value is supplied is is turned on by default. As can been been
from the output of "testparm -v" ("unix extensions = Yes") that unix
extensions are indeed enabled for my set-up. So the expected behaviour is
that file permissions are correctly exported from the server when mounting the
homes share. Maybe I misunderstood something (samba configuration is quite
complex), but I think I found an error in the samba package. Any advice is
welcome. Many thanks in advance! Additional Information 1) Description:
Ubuntu 20.04 LTS Release: 20.04 2) samba: Installed:
2:4.11.6+dfsg-0ubuntu1.2To manage notifications about this bug go
to:https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883234/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883234
Title:
unix extensions not working?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883234/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883234] [NEW] unix extensions not working?
Public bug reported:
I was trying to share home directories between two linux machines, so I
set-up a samba server (using the default the smb.conf, just uncommenting
things in the [homes] section, see attached smb.conf).
That worked nicely, except for one thing:
When mounting the shared home directory all files are marked as
executable.
If is obviously due to the fact that unix permissions are not correctly
send from server to client.
smbclient reports the following error:
smbclient //server/user
Enter WORKGROUP\users's password:
Try "help" to get a list of possible commands.
smb: \> stat testparm_v.log
Server doesn't support UNIX CIFS calls.
According to the samba docu support for unix permissions is controlled
by "unix extensions" in the [global] section of smb.conf. If no value is
supplied is is turned on by default. As can been been from the output of
"testparm -v" ("unix extensions = Yes") that unix extensions are indeed
enabled for my set-up.
So the expected behaviour is that file permissions are correctly
exported from the server when mounting the homes share.
Maybe I misunderstood something (samba configuration is quite complex),
but I think I found an error in the samba package. Any advice is
welcome. Many thanks in advance!
Additional Information
1) Description: Ubuntu 20.04 LTS
Release: 20.04
2) samba:
Installed: 2:4.11.6+dfsg-0ubuntu1.2
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "attachment.tgz"
https://bugs.launchpad.net/bugs/1883234/+attachment/5383199/+files/attachment.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883234
Title:
unix extensions not working?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883234/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726064] [NEW] keyboard hanging after activating fcitx pinyin
Public bug reported: Release: Ubuntu 17.10 Package: fcitx 1:4.2.9.1-6 When I tried to activate fcitx pinyin input method after a fresh install of 17.10, keyboard immediately stopped working. After rebooting and logging in again, the system became completely unusable (mouse pointer on an empty black screen). This could be fixed by deleting ".xinputrc" in my home directory, but pinyin input still not working. Has anyone observed the same problem? ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726064 Title: keyboard hanging after activating fcitx pinyin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1726064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210741] Re: no way to read and write files on mounted samba share on hardy
Since I have not seen any new posts on this thread for some months, I would like to confirm the problems mentioned in the earlier bug reports: 1) After the upgrade to Ubuntu 8.04 I cannot access the files on a samba server any longer. When I try to mount the samba share by the following command line smbmount //SERVER/share /mnt/localmountpoint -o rw,username=my_username I get a permission denied error. I have been using this command for several years. I rechecked the permissions of /mnt/localmountpoint and they are ok. The server runs an older version of samba (2.x) with security = user and plaintext authentication. I cannot provide the exact configuration of this server because it is not administered by me. 2) All files on the server are still fully accessible when I use smbclient //SERVER/share. 3) When I tweak the SecurityFlags (as described in the readme file of the cifs kernel module) by echo 0x37 /proc/fs/cifs/SecurityFlags, I can mount the samba share by smbmount. After that I can see the files on the server, but I have no access to them (cannot read/write/create files, although the file permission listed by ls -al are ok). I have setup a minimal samba server on my box and found that the current cifs implementatation in the kernel has great difficulties when connecting to a samba server which requires plain text authentication (that is setting encrypt passwords = no in smb.conf). So far I have not been successful in mounting any share on this test server as long as it runs with the encrypt passwords = no-setting (I always got permission denied errors, tweaking the SecurityFlags had no effect). Everything worked fine when I turned on password encryption. When looking at the kernel source of the cifs module I could not find any code that would send passwords in plaintext to the samba server. There seems to be always some encryption taking place. The same issue is also discussed on http://www.nabble.com/No-connection-using-plain-text-password-td18611280.html where Bart Oldeman suggests a patch, which adds code for handling plain text authentication to the cifs module (http://lists.samba.org/archive/linux-cifs-client/2008-March/002815.html) Applying this patch and recompiling the cifs module resolved the problems (at least for me). I would be glad if the patch could be approved by the developers of cifs kernel module. If possible a corrected version of the kernel should distributed by Ubuntu soon. Not being able to mount samba shares seems to be an annoying problem for quite many users of Ubuntu 8.04. -- no way to read and write files on mounted samba share on hardy https://bugs.launchpad.net/bugs/210741 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 210741] Re: no way to read and write files on mounted samba share on hardy
Since I have not seen any new posts on this thread for some months, I would like to confirm the problems mentioned in the earlier bug reports: 1) After the upgrade to Ubuntu 8.04 I cannot access the files on a samba server any longer. When I try to mount the samba share by the following command line smbmount //SERVER/share /mnt/localmountpoint -o rw,username=my_username I get a permission denied error. I have been using this command for several years. I rechecked the permissions of /mnt/localmountpoint and they are ok. The server runs an older version of samba (2.x) with security = user and plaintext authentication. I cannot provide the exact configuration of this server because it is not administered by me. 2) All files on the server are still fully accessible when I use smbclient //SERVER/share. 3) When I tweak the SecurityFlags (as described in the readme file of the cifs kernel module) by echo 0x37 /proc/fs/cifs/SecurityFlags, I can mount the samba share by smbmount. After that I can see the files on the server, but I have no access to them (cannot read/write/create files, although the file permission listed by ls -al are ok). I have setup a minimal samba server on my box and found that the current cifs implementatation in the kernel has great difficulties when connecting to a samba server which requires plain text authentication (that is setting encrypt passwords = no in smb.conf). So far I have not been successful in mounting any share on this test server as long as it runs with the encrypt passwords = no-setting (I always got permission denied errors, tweaking the SecurityFlags had no effect). Everything worked fine when I turned on password encryption. When looking at the kernel source of the cifs module I could not find any code that would send passwords in plaintext to the samba server. There seems to be always some encryption taking place. The same issue is also discussed on http://www.nabble.com/No-connection-using-plain-text-password-td18611280.html where Bart Oldeman suggests a patch, which adds code for handling plain text authentication to the cifs module (http://lists.samba.org/archive/linux-cifs-client/2008-March/002815.html) Applying this patch and recompiling the cifs module resolved the problems (at least for me). I would be glad if the patch could be approved by the developers of cifs kernel module. If possible a corrected version of the kernel should distributed by Ubuntu soon. Not being able to mount samba shares seems to be an annoying problem for quite many users of Ubuntu 8.04. -- no way to read and write files on mounted samba share on hardy https://bugs.launchpad.net/bugs/210741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
