[Desktop-packages] [Bug 755342] Re: Samsung Xcover 271 B2710 mass storage does not mount automatically
This bug still exists in Kubuntu 20.04. Samsung Xcover B2710 isn't connected properly. Long ago I fixed it on Ubuntu 12.04 by "DisableSwitching=1" and forgot about it. Now found this bugreport once again and old fix still works. If my help is needed in debugging of this issue, I'm ready. P.S. Does this disabled switching affects other USB devices somehow or only mobile phones? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/755342 Title: Samsung Xcover 271 B2710 mass storage does not mount automatically Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. In the interface of the Samsung Xcover 271 B2710, set it to connect as mass storage. 2. Connect it to the computer via USB cabel. Notice that it does not mount automatically. Also it does mount automatically when instead of step 1 it is set to connect to Samsung Kies or to sync with a media player. Below I provide output from dmesg and lsusb -vv. Output from dmesg as it is connected (step 2): [101332.680133] usb 2-6: new high speed USB device using ehci_hcd and address 6 [101333.630726] Initializing USB Mass Storage driver... [101333.630861] scsi5 : usb-storage 2-6:1.0 [101333.630956] usbcore: registered new interface driver usb-storage [101333.630958] USB Mass Storage support registered. Output from lsusb -vv: Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice2.06 iManufacturer 3 iProduct2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 006 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc01b MX310 Optical Mouse bcdDevice 18.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 64 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength
[Desktop-packages] [Bug 1131072] Re: Test page is printed on available printer if the printer under test is unavailable
In Ubuntu 14.04.5 this issue seems to be fixed. Now the test page is sent to the appropriate printer rather than to the default printer. So this bug can be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1131072 Title: Test page is printed on available printer if the printer under test is unavailable Status in system-config-printer package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 12.04.1 with GNOME Classic. I've got one printer in my system, HP LaserJet 3052, which is connected as network printer. Obviously, it is set as default. Its URI is 'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 Postscript (recommended)'. Later I added second printer using GNOME Printers applet. Second printer model is HP LaserJet 1220, it is connected via SAMBA with URI 'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer. When the setup was finished I sent test page to this printer and nothing happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver and sent another test page, but nothing happened again. My default HP LaserJet 3052 pinter was turned off at this moment, but when I switched it on, both test pages were printed on this printer instead. They got Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were sent from the spool to the default HP LaserJet 3052 printer, not to the printer they were intended for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 1179933] Re: fails to install on a multi-arch on a raring system
This bug still exists in 16.04LTS. flashplugin-installer:i386 cannot be installed in AMD64 system due to unresolved dependency: update-notifier- common. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1179933 Title: fails to install on a multi-arch on a raring system Status in Adobe Flash Plugin Tools: Fix Committed Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: flashplugin-installer fails to install on a raring system in multi- arch mode. To reproduce, start from an x86_64 system and try to install the i386 version of flashplugin-installer: $ sudo apt-get install flashplugin-installer:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: flashplugin-installer:i386 : Depends: update-notifier-common:i386 (>= 0.119ubuntu2) but it is not installable Recommends: libasound2-plugins:i386 (>= 1.0.16) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1179933/+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 1092899] Re: flashplugin-installer not multiarch co-installable
*** This bug is a duplicate of bug 1179933 *** https://bugs.launchpad.net/bugs/1179933 ** This bug has been marked a duplicate of bug 1179933 fails to install on a multi-arch on a raring system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1092899 Title: flashplugin-installer not multiarch co-installable Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: Attempting to install flashplugin-installer:i386 on an amd64 machine running Ubuntu 12.10 causes apt-get to return the following error: The following packages have unmet dependencies. flashplugin-installer:i386 : Depends: update-notifier-common:i386 (>= 0.119ubuntu2) but it is not installable E: Unable to correct problems, you have held broken packages. apt-get is apparently trying to install update-notifier-common:i386, but update-notifier-common is or architecture 'all', which I assume is an error in the packaging of flashplugin-installer. This is an issue with the Steam client which requires the i386 flashplayer library, and this problem forces one to install it by hand. See https://github.com/ValveSoftware/steam-for-linux/issues/36 . ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: flashplugin-installer:i386 (not installed) ProcVersionSignature: Ubuntu 3.5.0-21.19-lowlatency 3.5.7.1 Uname: Linux 3.5.0-21-lowlatency x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Fri Dec 21 13:32:20 2012 InstallationDate: Installed on 2012-09-26 (86 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: flashplugin-nonfree UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1092899/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
Then you are more lucky than I am. My system hangs from time to time with this patched driver - mouse and screen are frozen, only reboot cures that. It happens approximately once a week, and that doesn't suit me because my system should be up 24/7. Nothing can be found in /var/log/syslog, only Xorg log shows some info about "EQ overflowing" [https://nouveau.freedesktop.org/wiki/TroubleShooting/#index5h3]. So it seems that this patch needs proper testing and its stability depends on PC configuration. Good that it helped someone, but that's not my case. -- 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/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few seconds, the second one is "Failed to apply configuration: %s" "GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64" ...and the Displays GUI makes it look like the 4th monitor is enabled but it is still blank. At the time of doing this, /var/log/Xorg.0.log shows: [ 96283.251] resize called 7680 1080 [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96283.299] randr: failed to set shadow slave pixmap [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device I have also tried this with xrandr command line: $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto xrandr: Configure crtc 3 failed ...and the Xorg.0.log at this time is almost the same as above, plus the (I guess) fall back resizing to 3 monitors (5760x1080): [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96645.224] randr: failed to set shadow slave pixmap [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device [ 96645.227] resize called 0 0 [ 96645.227] -22 [ 96645.228] resize called 0 0 [ 96645.228] -22 [ 96645.229] resize called 7680 1080 [ 96645.281] resize called 5760 1080 I have previously tried to get around this with /etc/X11/xorg.conf with various Xinerama or ZaphodHeads settings but at the moment (of starting this "ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no ~/.config/monitors.xml. Obviously monitors.xml has been re-created as I test the Displays GUI to describe the pop-ups above, but it was not there at login. The 2-connector video cards to all four monitors are connected with DVI cables. The monitors are LG E2240TI, the video cards are (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Wed Jun 29 12:21:13 2016 DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller])
[Desktop-packages] [Bug 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
Almost 2 months have passed since I posted the patch. Martin, if you are still tracking this bug, does this patch work stable for you? -- 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/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few seconds, the second one is "Failed to apply configuration: %s" "GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64" ...and the Displays GUI makes it look like the 4th monitor is enabled but it is still blank. At the time of doing this, /var/log/Xorg.0.log shows: [ 96283.251] resize called 7680 1080 [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96283.299] randr: failed to set shadow slave pixmap [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device I have also tried this with xrandr command line: $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto xrandr: Configure crtc 3 failed ...and the Xorg.0.log at this time is almost the same as above, plus the (I guess) fall back resizing to 3 monitors (5760x1080): [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96645.224] randr: failed to set shadow slave pixmap [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device [ 96645.227] resize called 0 0 [ 96645.227] -22 [ 96645.228] resize called 0 0 [ 96645.228] -22 [ 96645.229] resize called 7680 1080 [ 96645.281] resize called 5760 1080 I have previously tried to get around this with /etc/X11/xorg.conf with various Xinerama or ZaphodHeads settings but at the moment (of starting this "ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no ~/.config/monitors.xml. Obviously monitors.xml has been re-created as I test the Displays GUI to describe the pop-ups above, but it was not there at login. The 2-connector video cards to all four monitors are connected with DVI cables. The monitors are LG E2240TI, the video cards are (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Wed Jun 29 12:21:13 2016 DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] [19da:1665] NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] [19da:1665] InstallationDate: Installed on 2015-11-12 (229 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
[Desktop-packages] [Bug 1571806] Re: Backup files are silently ignored when using certain archive types
I met with the same issue in 16.04.1 (amd64). Tested several 'tar' archives (namely tar.7z and tar.gz) - none of them stored backup files. Maybe some problem with generation of the lists of files for archiving? '7z' and 'zip' archives do save backup files, but it seems that they rely on 'p7zip-full' package which provides 7-Zip backend for the File Roller. Until I installed this package 'zip' archives were also losing backup files. In my older system which is 12.04LTS (i386) all the mentioned archive types properly store backup files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1571806 Title: Backup files are silently ignored when using certain archive types Status in file-roller package in Ubuntu: Confirmed Bug description: Depending on the kind of archive you create using file-roller, backup files (files with a `~` on the end of their names) are included or ignored. The user doesn't see any warning at all and will probably only discover this when they try to extract the archive. # How to reproduce the symptom. (I'm assuming you're using Nautilus with file-roller integration.) Create a folder `testFolder` (or any name but I'll use this one to refer to it) and create a file called `testFile~` in it. Then move to the parent folder of `testFolder`. Right-click test folder and choose "Compress". ## Correct behavior. Choose `.7z` as the archive format making it a 7zip archive and click "Create". The archive will contain the folder `testFolder` and in it the file `testFile~`. ## Incorrect behavior. Choose `.tar` as the archive format making it a tarball and click "Create". The tarball will contain the folder `testFolder` but it will be empty. Note that this isn't the fault of `tar`. If you create the tarball from the command line using the command `tar`, `testFile~` will be included. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1571806/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
If debugging symbols weren't disabled during compilation and the resulting file size looks intimidating you can decrease it. Run 'strip -s nouveau_drv.so' and debugging symbols will be purged completely. -- 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/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few seconds, the second one is "Failed to apply configuration: %s" "GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64" ...and the Displays GUI makes it look like the 4th monitor is enabled but it is still blank. At the time of doing this, /var/log/Xorg.0.log shows: [ 96283.251] resize called 7680 1080 [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96283.299] randr: failed to set shadow slave pixmap [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device I have also tried this with xrandr command line: $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto xrandr: Configure crtc 3 failed ...and the Xorg.0.log at this time is almost the same as above, plus the (I guess) fall back resizing to 3 monitors (5760x1080): [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96645.224] randr: failed to set shadow slave pixmap [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device [ 96645.227] resize called 0 0 [ 96645.227] -22 [ 96645.228] resize called 0 0 [ 96645.228] -22 [ 96645.229] resize called 7680 1080 [ 96645.281] resize called 5760 1080 I have previously tried to get around this with /etc/X11/xorg.conf with various Xinerama or ZaphodHeads settings but at the moment (of starting this "ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no ~/.config/monitors.xml. Obviously monitors.xml has been re-created as I test the Displays GUI to describe the pop-ups above, but it was not there at login. The 2-connector video cards to all four monitors are connected with DVI cables. The monitors are LG E2240TI, the video cards are (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Wed Jun 29 12:21:13 2016 DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] [19da:1665] NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] [19da:1665] InstallationDate: Installed on 2015-11-12 (229 days ago) InstallationMedia:
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
This bug affects my system (Ubuntu 16.04.1 amd64, Gnome Flashback session with Compiz). One-key keyboard layout switchers (I tested Right Alt, Right Super, Right Control) don't work, while two-key switchers work (checked several of them). If I run Unity session, these one-key switchers work properly. Is it a bug of g-s-d, or I should open the bug in gnome-flashback section? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in gnome-settings-daemon: Unknown Status in Ubuntu GNOME: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-control-center package in ALT Linux: Unknown Status in gnome-control-center package in Baltix: Confirmed Status in gnome-control-center package in Gentoo Linux: Unknown Status in gnome-control-center package in Mandriva: Unknown Bug description: [Impact] Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift, etc. Shift, Caps Lock keys are just ignored in settings. [Test Case] - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a combination of two modifier keys such as Ctrl+Shift -> the UI should reflect the new keys - add at least two input sources through gnome-control-center's text entry settings - press and release Ctrl+Shift -> the current input source should change [Regression Potential] That UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE=sharing). You can use the tag keyboard-layout-switching-hotkeys to find related bugs. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys For using layout switching hotkeys in Unity Greeter, see bug 1245137. For using layout switching hotkeys in GNOME lockscreen, see bug 1244548. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
Martin, you've done everything well. Indeed, additional packages are needed for the successful compilation. They can be installed by the command 'sudo apt-get build-dep package_name' (there can be hefty pack, that's why I'm usually using virtual machine for the compilation and revert it to the last snapshot afterwards). The size of the resulting library can be decreased by setting specific compiler options. If you examine Makefile which was created after './configure' has finished its work, you'll find CFLAGS string in it containing -g option (the level of debugging information) and -O2 option (optimization level). Disabling debugging information affects size of the resulting file but isn't advised (this may cause undesired results). Increasing optimization level will reduce the compiled file size (higher levels of optimisation also may cause undesired code behavior). Better leave it as it is. Those who perform packaging are better aware how this specific package should be compiled to ensure its minimal size for the distribution. -- 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/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few seconds, the second one is "Failed to apply configuration: %s" "GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64" ...and the Displays GUI makes it look like the 4th monitor is enabled but it is still blank. At the time of doing this, /var/log/Xorg.0.log shows: [ 96283.251] resize called 7680 1080 [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96283.299] randr: failed to set shadow slave pixmap [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device I have also tried this with xrandr command line: $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto xrandr: Configure crtc 3 failed ...and the Xorg.0.log at this time is almost the same as above, plus the (I guess) fall back resizing to 3 monitors (5760x1080): [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96645.224] randr: failed to set shadow slave pixmap [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device [ 96645.227] resize called 0 0 [ 96645.227] -22 [ 96645.228] resize called 0 0 [ 96645.228] -22 [ 96645.229] resize called 7680 1080 [ 96645.281] resize called 5760 1080 I have previously tried to get around this with /etc/X11/xorg.conf with various Xinerama or ZaphodHeads settings but at the moment (of starting this "ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no ~/.config/monitors.xml. Obviously monitors.xml has been re-created as I test the Displays GUI to describe the pop-ups above, but it was not there at login. The 2-connector video cards to all four monitors are connected with DVI cables. The monitors are LG E2240TI, the video cards are (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity
[Desktop-packages] [Bug 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
I met with the same bug in Ubuntu 16.04.1 (amd64): 2 NVIDIA adapters with DVI and HDMI connectors on each of them, 4 identical Samsung monitors, 4th monitor is dead, 3rd is sometimes garbled, sometimes is OK. All the error messages described by Martin are the same. Luckily in #2 he provided the method which cures the bug with ATI cards in Fedora. I decided to try it with Nouveau driver in Ubuntu and it worked! I downloaded the sources using 'apt-get source xserver-xorg-video-nouveau', found the string in drmmode_display.c which checks whether HAS_DIRTYTRACKING2 is defined and fixed it. Then I compiled the driver and replaced '/usr/lib/xorg/modules/drivers/nouveau_drv.so' with the fixed version. After reboot all 4 monitors were working on login screen, '~/.config/monitors.xml' was created properly and all monitors were present when I logged in. I'm attaching the patch. Maybe the developers will notice it and fix the Nouveau driver? (BTW, ATI driver in Ubuntu 16.04 seems already fixed - I checked its sources and the mentioned string is already in place in drmmode_display.c) ** Patch added: "Fixes improper handling of 3rd and 4th monitors" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597437/+attachment/4802770/+files/nouveau_drv.patch ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few seconds, the second one is "Failed to apply configuration: %s" "GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64" ...and the Displays GUI makes it look like the 4th monitor is enabled but it is still blank. At the time of doing this, /var/log/Xorg.0.log shows: [ 96283.251] resize called 7680 1080 [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96283.299] randr: failed to set shadow slave pixmap [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device I have also tried this with xrandr command line: $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto xrandr: Configure crtc 3 failed ...and the Xorg.0.log at this time is almost the same as above, plus the (I guess) fall back resizing to 3 monitors (5760x1080): [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96645.224] randr: failed to set shadow slave pixmap [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device [ 96645.227] resize called 0 0 [ 96645.227] -22 [ 96645.228] resize called 0 0 [ 96645.228] -22 [ 96645.229] resize called 7680 1080 [ 96645.281] resize called 5760 1080 I have previously tried to get around this with /etc/X11/xorg.conf with various Xinerama or ZaphodHeads settings but at the moment (of starting this "ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no ~/.config/monitors.xml. Obviously monitors.xml has been re-created as I test the Displays GUI to describe the pop-ups above, but it was not there at login. The 2-connector video cards to all four monitors are connected with DVI cables. The monitors are LG E2240TI, the video cards are (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
[Desktop-packages] [Bug 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)
I can confirm that upgrading xkb-data package to version 2.5-1ubuntu1.5 in LTS 12.04.4 doesn't resolve the problem. When I disable the mentioned fix in ~/.config/gtk-3.0/gtk.css (F10 is disabled in terminal keyboard combinations), F10 press still opens context menu as if Shift-F10 was pressed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/937822 Title: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update) Status in GTK+ GUI Toolkit: Fix Released Status in central project for keyboard configuration: Fix Released Status in “gtk+2.0” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “gtk+2.0” source package in Precise: Invalid Status in “xkeyboard-config” source package in Precise: Fix Released Status in “gtk+2.0” source package in Quantal: Fix Released Status in “gtk+3.0” source package in Quantal: Fix Released Status in “xkeyboard-config” source package in Quantal: Fix Released Status in “gtk+2.0” package in Debian: Fix Released Status in “gtk+3.0” package in Debian: Fix Released Status in “xkeyboard-config” package in Debian: Fix Released Bug description: [Impact] F10 behaves the same as Shift-F10. This causes menus to pop up incorrectly. [Fix] Upstream patch preserves Shift so that Shift-F10 and F10 act as separate keys. [Test Case] 1. Open a gnome-terminal window 2. Run aptitude 3. Press F10 Expected behavior: Aptitude's menu opens Broken behavior: Menus for both aptitude and gnome-terminal are shown. In different window environments (e.g. unity) other menus can be triggered than should be. [Regression Potential] The patch simply changes a keyboard layout config file, so the severity of any possible regression would be limited to keyboard configuration misbehaviors. This is a well reviewed, tested patch from upstream and not expected to have any regression. [Original Report] Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=661973 Visible in Unity - change keybinding for opening first global menu entry to Alt+F10. Pressing F10 triggers short flash of global menu nevertheless. When you disable the F10 shortcut in gnome-terminal, pressing the key triggers context menu in gnome terminal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgtk-3-0 3.3.14-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.92-0ubuntu1 Architecture: i386 Date: Tue Feb 21 16:29:08 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120119) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937822/+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 1131072] Re: Test page is printed on available printer if the printer under test is unavailable
** Summary changed: - Test page is always printed on default printer + Test page is printed on available printer if the printer under test is unavailable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1131072 Title: Test page is printed on available printer if the printer under test is unavailable Status in “system-config-printer” package in Ubuntu: New Bug description: I'm using Ubuntu 12.04.1 with GNOME Classic. I've got one printer in my system, HP LaserJet 3052, which is connected as network printer. Obviously, it is set as default. Its URI is 'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 Postscript (recommended)'. Later I added second printer using GNOME Printers applet. Second printer model is HP LaserJet 1220, it is connected via SAMBA with URI 'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer. When the setup was finished I sent test page to this printer and nothing happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver and sent another test page, but nothing happened again. My default HP LaserJet 3052 pinter was turned off at this moment, but when I switched it on, both test pages were printed on this printer instead. They got Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were sent from the spool to the default HP LaserJet 3052 printer, not to the printer they were intended for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 1131072] Re: Test page is printed on available printer if the printer under test is unavailable
Actually if printer not available then test page is printed on available printer. It seems to me that more consistent behavior is to send an error rather then redirect printing job to available printer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1131072 Title: Test page is printed on available printer if the printer under test is unavailable Status in “system-config-printer” package in Ubuntu: New Bug description: I'm using Ubuntu 12.04.1 with GNOME Classic. I've got one printer in my system, HP LaserJet 3052, which is connected as network printer. Obviously, it is set as default. Its URI is 'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 Postscript (recommended)'. Later I added second printer using GNOME Printers applet. Second printer model is HP LaserJet 1220, it is connected via SAMBA with URI 'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer. When the setup was finished I sent test page to this printer and nothing happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver and sent another test page, but nothing happened again. My default HP LaserJet 3052 pinter was turned off at this moment, but when I switched it on, both test pages were printed on this printer instead. They got Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were sent from the spool to the default HP LaserJet 3052 printer, not to the printer they were intended for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 836945] Re: Screen always goes blank after 10 minutes
Actually there exist 2 settings, 1st one affects screensaver (blank screen), 2nd affects monitor power saving mode (suspends monitor): 1. Schema: org.gnome.desktop.session, Key: idle-delay 2. Schema: org.gnome.settings-daemon.plugins.power, Key: sleep-display-ac System Settings Brightness and Lock seems to set both of them simultaneously, when you choose the timeout Turn screen off when inactive for:. But you can set them separately with 'dconf' tool or using gsettings. If your screen blanks unexpectedly, check these 2 keys and correct them as needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/836945 Title: Screen always goes blank after 10 minutes Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Even though my screen saver settings say to Turn off after: 1 hour, my screens always go blank after 10 minutes of inactivity. This is entirely reproducible. I am using the free glx driver with my Radeon HD 4670 card, dual-headed. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 BootLog: udevd[362]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev' fsck from util-linux 2.19.1 /dev/sdb2: clean, 142348/90841088 files, 6520516/363354368 blocks CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unitydialog,unityshell] CompositorRunning: None Date: Mon Aug 29 14:52:39 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:2542] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MachineType: Dell Inc. Studio XPS 435MT ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=7ffae0c6-66ea-4bbd-ae3d-f98ddd9603a5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0R849J dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd05/05/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 435MT dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu19 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+7ubuntu6 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.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/836945/+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 1131072] [NEW] Test page is always printed on default printer
Public bug reported: I'm using Ubuntu 12.04.1 with GNOME Classic. I've got one printer in my system, HP LaserJet 3052, which is connected as network printer. Obviously, it is set as default. Its URI is 'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 Postscript (recommended)'. Later I added second printer using GNOME Printers applet. Second printer model is HP LaserJet 1220, it is connected via SAMBA with URI 'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer. When the setup was finished I sent test page to this printer and nothing happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver and sent another test page, but nothing happened again. My default HP LaserJet 3052 pinter was turned off at this moment, but when I switched it on, both test pages were printed on this printer instead. They got Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were sent from the spool to the default HP LaserJet 3052 printer, not to the printer they were intended for. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1131072 Title: Test page is always printed on default printer Status in “system-config-printer” package in Ubuntu: New Bug description: I'm using Ubuntu 12.04.1 with GNOME Classic. I've got one printer in my system, HP LaserJet 3052, which is connected as network printer. Obviously, it is set as default. Its URI is 'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 Postscript (recommended)'. Later I added second printer using GNOME Printers applet. Second printer model is HP LaserJet 1220, it is connected via SAMBA with URI 'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer. When the setup was finished I sent test page to this printer and nothing happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver and sent another test page, but nothing happened again. My default HP LaserJet 3052 pinter was turned off at this moment, but when I switched it on, both test pages were printed on this printer instead. They got Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were sent from the spool to the default HP LaserJet 3052 printer, not to the printer they were intended for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 713860] Re: 1st terminal opens at 80x24, subsequent open at 80x22 [classic desktop]
** This bug is no longer a duplicate of bug 915241 Update menubar patches -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/713860 Title: 1st terminal opens at 80x24, subsequent open at 80x22 [classic desktop] Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-terminal This odd behavior started showing up a few days ago. I'm using the Ubuntu classic desktop (with metacity). I generally have two terminal windows open when I'm coding (I have a 2560x1600 display). When I open the first terminal, it opens at the default size of 80 columns x 24 rows. But subsequent terminals will open at 80x22. If I close all terminal windows, behavior starts over - 1st terminal is 80x24, all subsequent are 80x22. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-terminal 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic x86_64 Architecture: amd64 CheckboxSubmission: fdbdfcded0c0bb479a6b52e9ec5af131 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Sat Feb 5 16:48:12 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/713860/+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 713860] Re: 1st terminal opens at 80x24, subsequent open at 80x22 [classic desktop]
*** This bug is a duplicate of bug 915241 *** https://bugs.launchpad.net/bugs/915241 Actually this bug wasn't fixed in precise. I'm using Ubuntu 12.04.1 with GNOME Classic and Compiz. The behaviour is exactly the same: first opened terminal have the size of 80x24, all subsequent terminal windows are 2 rows less. I've read the description of the bug #915241 which is marked as the duplicate of this bugreport, but I think that this duplicate status is wrong, as I've got versions of libgtk-3-0 = 3.4.2-0ubuntu0.5 and libgtk2.0-0 = 2.24.10-0ubuntu6, both of them are more recent than the ones mentioned as fixed, but the problem persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/713860 Title: 1st terminal opens at 80x24, subsequent open at 80x22 [classic desktop] Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-terminal This odd behavior started showing up a few days ago. I'm using the Ubuntu classic desktop (with metacity). I generally have two terminal windows open when I'm coding (I have a 2560x1600 display). When I open the first terminal, it opens at the default size of 80 columns x 24 rows. But subsequent terminals will open at 80x22. If I close all terminal windows, behavior starts over - 1st terminal is 80x24, all subsequent are 80x22. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-terminal 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic x86_64 Architecture: amd64 CheckboxSubmission: fdbdfcded0c0bb479a6b52e9ec5af131 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Sat Feb 5 16:48:12 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/713860/+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 632412] Re: Windows 2 rows shorter than it should be
*** This bug is a duplicate of bug 915241 *** https://bugs.launchpad.net/bugs/915241 Actually this bug wasn't fixed in precise. I'm using Ubuntu 12.04.1 with GNOME Classic and Compiz. First opened terminal have the size of 80x24, all subsequent terminal windows are 80x22. indicator-applet-appmenu isn't installed in my system. It doesn't seem the duplicate of the bug #915241 - both gtk libraries in my system are newer than mentioned there and the issue is not fixed by them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/632412 Title: Windows 2 rows shorter than it should be Status in GNOME Terminal: Expired Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-terminal I noticed in Maverick when you load up gnome terminal it's not 80x24. Instead it's 80x22. I went into the profile properties and changed it to 80x24 by default, and lo! a new window was 80x22. So I decided to set the default to 80x43, but when I created a new window it was 80x41. In each case, it seems that a new gnome terminal window is 2 rows shorter than it should be. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-terminal 2.31.91-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 7 14:48:41 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/632412/+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 1104877] [NEW] gedit loses cursor when user rolls up its window
Public bug reported: System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz); gedit version: 3.4.1-0ubuntu1 Steps to reproduce the bug: 1. Activate roll up behaviour for the windows using gconf: /apps/gwd/mouse_wheel_action = shade 2. Roll up gedit window into window header scrolling up over window titlebar 3. Unroll gedit window by scrolling down over window titlebar After that gedit window loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor becomes invisible and you cannot determine where it is located. Workaround: If you minimize, then restore back gedit window, then cursor reappears and behaves normally. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1104877 Title: gedit loses cursor when user rolls up its window Status in “gedit” package in Ubuntu: New Bug description: System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz); gedit version: 3.4.1-0ubuntu1 Steps to reproduce the bug: 1. Activate roll up behaviour for the windows using gconf: /apps/gwd/mouse_wheel_action = shade 2. Roll up gedit window into window header scrolling up over window titlebar 3. Unroll gedit window by scrolling down over window titlebar After that gedit window loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor becomes invisible and you cannot determine where it is located. Workaround: If you minimize, then restore back gedit window, then cursor reappears and behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1104877/+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 1104877] Re: gedit loses cursor when user rolls up its window
** Description changed: System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz); gedit version: 3.4.1-0ubuntu1 Steps to reproduce the bug: 1. Activate roll up behaviour for the windows using gconf: /apps/gwd/mouse_wheel_action = shade 2. Roll up gedit window into window header scrolling up over window titlebar 3. Unroll gedit window by scrolling down over window titlebar - After that gedit window loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor becomes invisible and you cannot determine where it is located. + After that document editing field loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor becomes invisible and you cannot determine where it is located. Workaround: If you minimize, then restore back gedit window, then cursor reappears and behaves normally. ** Description changed: System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz); gedit version: 3.4.1-0ubuntu1 Steps to reproduce the bug: 1. Activate roll up behaviour for the windows using gconf: /apps/gwd/mouse_wheel_action = shade 2. Roll up gedit window into window header scrolling up over window titlebar 3. Unroll gedit window by scrolling down over window titlebar - After that document editing field loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor becomes invisible and you cannot determine where it is located. + After that document editing field loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor stays invisible and you cannot determine where it is located. Workaround: If you minimize, then restore back gedit window, then cursor reappears and behaves normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1104877 Title: gedit loses cursor when user rolls up its window Status in “gedit” package in Ubuntu: New Bug description: System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz); gedit version: 3.4.1-0ubuntu1 Steps to reproduce the bug: 1. Activate roll up behaviour for the windows using gconf: /apps/gwd/mouse_wheel_action = shade 2. Roll up gedit window into window header scrolling up over window titlebar 3. Unroll gedit window by scrolling down over window titlebar After that document editing field loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor stays invisible and you cannot determine where it is located. Workaround: If you minimize, then restore back gedit window, then cursor reappears and behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1104877/+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 1103381] [NEW] Menu and launcher spacing on the top panel is incorrect
Public bug reported:
System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz);
light-themes version: 0.1.9.1-0ubuntu1.2
Bug description:
--
Main menu headers (Applications and Places) are placed too tightly in GNOME
Classic session.
If you put some launchers on the top panel, they are also placed without any
spacing (take a look at screenshot, notice separator items which really don't
separate anything).
Proposed fix:
--
Add the padding property to the files:
/usr/share/themes/Ambiance/gtk-3.0/apps/gnome-panel.css
/usr/share/themes/Radiance/gtk-3.0/apps/gnome-panel.css
Code:
--
.gnome-panel-menu-bar.menubar .menuitem,
PanelWidget .button {
padding: 0px 4px;
}
Notes: I used 4 pixel padding for both objects, but this property can be set
separately using different padding settings for each object. Launcher padding
can be increased to 6 pixel to make it even with Indicator Applet icons
padding, but we must bear in mind that bottom panel task buttons also will
become wider, as they are also Panel Widgets.
Also remains unresolved issue with launcher icons size. As you can see on the
applied screenshot they occupy all place from the top to the bottom of the
panel, without any border. They ignore gtk-icon-sizes setting in
/usr/share/themes/Ambiance/gtk-2.0/gtkrc and cannot be resized.
** Affects: light-themes (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: Original menu and launchers placement
https://bugs.launchpad.net/bugs/1103381/+attachment/3496172/+files/Before.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1103381
Title:
Menu and launcher spacing on the top panel is incorrect
Status in “light-themes” package in Ubuntu:
New
Bug description:
System description: Ubuntu 12.04 LTS with GNOME Classic (using
Compiz); light-themes version: 0.1.9.1-0ubuntu1.2
Bug description:
--
Main menu headers (Applications and Places) are placed too tightly in GNOME
Classic session.
If you put some launchers on the top panel, they are also placed without any
spacing (take a look at screenshot, notice separator items which really don't
separate anything).
Proposed fix:
--
Add the padding property to the files:
/usr/share/themes/Ambiance/gtk-3.0/apps/gnome-panel.css
/usr/share/themes/Radiance/gtk-3.0/apps/gnome-panel.css
Code:
--
.gnome-panel-menu-bar.menubar .menuitem,
PanelWidget .button {
padding: 0px 4px;
}
Notes: I used 4 pixel padding for both objects, but this property can be set
separately using different padding settings for each object. Launcher padding
can be increased to 6 pixel to make it even with Indicator Applet icons
padding, but we must bear in mind that bottom panel task buttons also will
become wider, as they are also Panel Widgets.
Also remains unresolved issue with launcher icons size. As you can see on the
applied screenshot they occupy all place from the top to the bottom of the
panel, without any border. They ignore gtk-icon-sizes setting in
/usr/share/themes/Ambiance/gtk-2.0/gtkrc and cannot be resized.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1103381/+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 1103381] Re: Menu and launcher spacing on the top panel is incorrect
The result of the patching can be seen on the screenshot (I also
decreased the size of Ubuntu logo as the buttons become wider using gtk-
icon-sizes = panel-menu-bar=16,16 setting in ~/.config/gtk-3.0
** Attachment added: Menu and launchers placement after patching
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1103381/+attachment/3496175/+files/After.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1103381
Title:
Menu and launcher spacing on the top panel is incorrect
Status in “light-themes” package in Ubuntu:
New
Bug description:
System description: Ubuntu 12.04 LTS with GNOME Classic (using
Compiz); light-themes version: 0.1.9.1-0ubuntu1.2
Bug description:
--
Main menu headers (Applications and Places) are placed too tightly in GNOME
Classic session.
If you put some launchers on the top panel, they are also placed without any
spacing (take a look at screenshot, notice separator items which really don't
separate anything).
Proposed fix:
--
Add the padding property to the files:
/usr/share/themes/Ambiance/gtk-3.0/apps/gnome-panel.css
/usr/share/themes/Radiance/gtk-3.0/apps/gnome-panel.css
Code:
--
.gnome-panel-menu-bar.menubar .menuitem,
PanelWidget .button {
padding: 0px 4px;
}
Notes: I used 4 pixel padding for both objects, but this property can be set
separately using different padding settings for each object. Launcher padding
can be increased to 6 pixel to make it even with Indicator Applet icons
padding, but we must bear in mind that bottom panel task buttons also will
become wider, as they are also Panel Widgets.
Also remains unresolved issue with launcher icons size. As you can see on the
applied screenshot they occupy all place from the top to the bottom of the
panel, without any border. They ignore gtk-icon-sizes setting in
/usr/share/themes/Ambiance/gtk-2.0/gtkrc and cannot be resized.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1103381/+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
