[Desktop-packages] [Bug 890061] Re: Nouveau thinks secondary DVI connection is HDMI - monitor blank
I no longer see the problem on Ubuntu 13.10. Both monitors show as DVI connected and both work fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/890061 Title: Nouveau thinks secondary DVI connection is HDMI - monitor blank Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Bug description: Fresh install of 11.10 amd64 on a machine with a dual head nVidia card (shown by lspci as "nVidia Corporation G92 [GeForce GTS 250] rev a2") with twin DVI outputs and a primary 30" monitor and secondary 23" monitor, both connected via DVI. After 11.10 install completed, the right-hand 23" monitor remains blank and in power save, although when I open System Settings / Displays, both monitors appear there with the initial display configuration showing as mirrored displays at 1152x864 resolution. Un-mirroring the displays and setting each display to its native resolution and orientation still has the LH monitor blank. I think the problem is that the 23" monitor is being incorrectly detected as being connected via HDMI, as when I run xrandr in a terminal it shows === nick@ubuntu1110:~$ xrandr Screen 0: minimum 320 x 200, current 3640 x 1920, maximum 8192 x 8192 DVI-I-1 connected 2560x1600+0+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 60.0*+ 1920x1440 60.0 1920x1200 59.9 1600x1200 60.0 1280x1024 75.0 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.1 60.0 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 HDMI-1 connected 1080x1920+2560+0 right (normal left inverted right x axis y axis) 509mm x 286mm 1920x1080 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 === The video card does not have any HDMI output at all, just the two DVI outputs. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,vpswitch,mousepoll,move,wall,place,gnomecompat,imgpng,regex,snap,compiztoolbox,resize,session,animation,expo,workarounds,ezoom,staticswitcher,fade,scale] CompositorRunning: None Date: Mon Nov 14 14:32:07 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: nVidia Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: nVidia Corporation Device [10de:0592] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=94d1d51f-68be-488e-b037-37e7b871a7a7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "n" Driver "nouveau" EndSection dmi.bios.date: 09/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.
[Desktop-packages] [Bug 227808] Re: file permissions destroyed by vim/gvfs/fuse
Also affecting me on Ubuntu 12.04 with emacs editing a file mounted from a remote server via gvfs. Permissions are set to 600. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/227808 Title: file permissions destroyed by vim/gvfs/fuse Status in GVFS: New Status in “gvfs” package in Ubuntu: Confirmed Bug description: This bug is a little difficult to explain, but I will do my best. I'm using Ubuntu Hardy Heron with no third party repositories. Every package is up to date as of this posting. It goes like this. When I edit files with vim or gvim through gvfs/fuse/sftp the file permissions on the real remote file system get destroyed. Here is a procedure you can follow to duplicate this bug. The only non-default package you need installed is vim or gvim. 1 - Open a terminal and ssh to a remote machine. 2 - In this terminal create a text file on the remote machine, and set the permissions to 644. 3 - Go to the Places->Connect to Server... menu item, and create an SSH connection to the remote machine. 4 - Double click the new sftp folder icon that appears on the desktop to open nautilus. 5 - In nautilus browse to the directory containing the text file you just created. 6 - Use the command ls -l in the ssh terminal to verify the permissions of the file are still 644. 7 - In nautilus right-click on the text file, open it with "Text Editor" (gedit) 8 - Make a change to the file in gedit and save it. 9 - Use the ls -l command in the terminal to verify that the permissions of the file are still 644. 10 - Exit gedit. 11 - In nautilus right-click on the text file and select the option to open it with "GVim Text Editor" 12 - Make some changes to the file in GVim, and save those changes. 13 - Use the ls -l command in the terminal, and you will see that the permissions of the file are now 600, not 644. Some interesting things to note about this bug. If you open the text editors from the command line, instead of through nautilus, the same problem happens. So opening gedit like this: gedit ~/.gvfs/sftp\ on\ remote/home/user/test.txt will not damage the permissions. However, opening vim like this: vim ~/.gvfs/sftp\ on\ remote/home/user/test.txt will damage the permissions. Also, I notice that if you do this ls -l ~/.gfvs/sftp\ on\ remote/home/user/ the permissions of test.txt (and every other file) will appear to be 600 (700 for directories), regardless of the file permissions on the "real" remote file system. If you attempt to chmod any files, it will result in a chmod of the actual permissions on the remote file system, but it will not change the permissions of the file in the local ~/.gvfs directory. This has led me to conclude that this bug is a combination of two things. First, using the chmod command on files through gvfs/fuse/sftp does not work in an expected fashion. Secondly, gvim and vim appear to be chmod-ing files when they write to those files. I'm not sure this bug is an actual security risk. It seems it can only result in file permissions becoming more strict, not more permissive. However, I have checked the security box just to be safe. If file permissions involved, there could always be an unseen security issue. I can see a situation where an application losing the ability to read a needed file causes system breakage, if not a security hole. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/227808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
On 13.04, after adding the SIL repository (http://packages.sil.org/ubuntu/) to my sources and installing the Andika font, I'm getting these warnings from fontconfig (version 2.10.2): $ fc-cache Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated. Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 16: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-fonts-sil-andika.conf", line 35: Having multiple in isn't supported and may not work as expected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Fix Released Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “culmus” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” source package in Quantal: Fix Released Status in “fonts-arphic-uming” source package in Quantal: Fix Released Status in “fonts-baekmuk” source package in Quantal: Fix Released Status in “fonts-droid” source package in Quantal: Fix Released Status in “fonts-nanum” source package in Quantal: Fix Released Status in “fonts-nanum-coding” source package in Quantal: Fix Released Status in “fonts-sil-andika” source package in Quantal: Fix Released Status in “fonts-tlwg” source package in Quantal: Fix Released Status in “fonts-unfonts-core” source package in Quantal: Fix Released Status in “fonts-unfonts-extra” source package in Quantal: Fix Released Status in “language-selector” source package in Quantal: Fix Released Status in “libreoffice” source package in Quantal: Confirmed Status in “ttf-wqy-zenhei” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Released Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-ump
