[Desktop-packages] [Bug 10910]
in print-to-file I first have to select a different paper size (any different paper size), then re-select A4, then I get A4 paper size in the .pdf. Otherwise I get letter. printer_Print_to_File.print_paper_name=iso_a4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/10910 Title: Default page size for printing is letter Status in The Mozilla Firefox Browser: In Progress Status in “firefox” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “firefox” package in Baltix: Confirmed Bug description: (Default warty install, dist-upgraded to hoary, language chosen is Norwegian) about:config reports that print.postscript.paper_size is letter, which is wrong for Norway, it should be A4. It should probably look at LC_PAPER or /etc/papersize To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/10910/+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 10910]
In firefox 20.0, print to file defaults to letter. If I change this to A4, the PDF file on disk is still marked as size Letter. So various PDF readers assume it's Letter. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/10910 Title: Default page size for printing is letter Status in The Mozilla Firefox Browser: In Progress Status in “firefox” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “firefox” package in Baltix: Confirmed Bug description: (Default warty install, dist-upgraded to hoary, language chosen is Norwegian) about:config reports that print.postscript.paper_size is letter, which is wrong for Norway, it should be A4. It should probably look at LC_PAPER or /etc/papersize To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/10910/+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 1076315] [NEW] Chromium print to file puts the pdf in the wrong directory
Public bug reported: When printing, and choosing print to file, the .pdf is always generated in the home directory, and not in the chosen directory. Print to file lets one choose a directory, however, this is ignored. This used to work correctly as recently as October. I think this might have been broken by chromium-browser 22.0.1229.94~r1 61065-0ubuntu1 which came as an update on 17 October. That matches the timestamps of the .pdf files in my home directory. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1076315 Title: Chromium print to file puts the pdf in the wrong directory Status in “chromium-browser” package in Ubuntu: New Bug description: When printing, and choosing print to file, the .pdf is always generated in the home directory, and not in the chosen directory. Print to file lets one choose a directory, however, this is ignored. This used to work correctly as recently as October. I think this might have been broken by chromium-browser 22.0.1229.94~r1 61065-0ubuntu1 which came as an update on 17 October. That matches the timestamps of the .pdf files in my home directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1076315/+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 1071288] Re: No multiple monitors
I've found a probable cause. xrandr won't enable LVDS1 unless VGA1 is off. So I have to plug in VGA1, and then run: xrandr --output VGA1 --off xrandr --output LVDS1 --mode 1366x768 xrandr --output VGA1 --auto xrandr --output VGA1 --primary I have to turn VGA1 off, then I can turn LVDS1 on, and then VGA1 on. The xrandr error message is cannot find crtc for output LVDS1 A bit of googling shows that this happens to more people, with different video cards, on all sorts of versions, with all sorts of Linux distributions. Possibly related, possibly off-topic: I make VGA1 the primary display, because if I don't I can't resize beyond a certain size even though VGA1 is 1920x1080. This may be because VGA1's resolution is higher, and windows are stuck on LVDS1's size. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1071288 Title: No multiple monitors Status in “gnome-control-center” package in Ubuntu: New Bug description: Gnome-shell usually doesn't run on multiple monitors, even though it's configured in SystemSettings - Displays usually because once in a blue moon it does. So the hardware supports it. xrandr lists: LVDS1 connected (normal left inverted right x axis y axis) 1366x768 59.9 + VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm 1920x1080 60.0*+ (other resolutions cut from the output) gdm starts on both monitors. As soon as I log in, LVDS1 goes off. I can enable the second monitor in SystemSettings-Displays, and even click on keep configuration but it doesn't activate. It's disabled in software somewhere. I say that because the message tray at the bottom is in a different location when both monitors are active. So there is a software detect-monitor-size that moves the message tray, and it's almost always where it would be for single monitors. Worked fine in Gnome-Shell 3.0.0. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-shell 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CheckboxSubmission: 4c35a9d722052b5a55114f98690e7808 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Thu Oct 25 13:47:41 2012 DisplayManager: gdm InstallationDate: Installed on 2010-02-06 (992 days ago) InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 (20091028.4) MarkForUpload: True SourcePackage: gnome-shell UpgradeStatus: Upgraded to quantal on 2012-10-10 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1071288/+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 1070284] [NEW] Locale is set wrong
Public bug reported: As of today, my locale changed for some unknown reason. I assume a apt upgrade, but I actually don't know. It used to be English South Africa (en_ZA), now it's Afrikaans South Africa (af_ZA) While I understand Afrikaans, and I have 29 locales installed, I don't understand why it was changed. I also don't know where to change it back. I've tried to dpkg reconfigure locales, and checked /etc/default/locale. /etc/default/locale is set to en_ZA.UTF-8 $LANG is af_ZA.UTF-8 on login $LC_* is en_US.UTF-8 (which is wrong for en_ZA) /etc/environment contains no LANG, LC_, etc. locale: LANG=af_ZA.UTF-8 LANGUAGE=af:en_US:en LC_CTYPE=af_ZA.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=af_ZA.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=af_ZA.UTF-8 LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_ALL= I expect the environment variables of new logins to match /etc/default/locale. That file is owned by root, readable by everyone, and unmodified in almost 3 years. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: locales 2.13+git20120306-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 CheckboxSubmission: 4c35a9d722052b5a55114f98690e7808 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Tue Oct 23 12:22:39 2012 InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 (20091028.4) PackageArchitecture: all SourcePackage: langpack-locales UpgradeStatus: Upgraded to quantal on 2012-10-10 (13 days ago) ** Affects: langpack-locales (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to langpack-locales in Ubuntu. https://bugs.launchpad.net/bugs/1070284 Title: Locale is set wrong Status in “langpack-locales” package in Ubuntu: New Bug description: As of today, my locale changed for some unknown reason. I assume a apt upgrade, but I actually don't know. It used to be English South Africa (en_ZA), now it's Afrikaans South Africa (af_ZA) While I understand Afrikaans, and I have 29 locales installed, I don't understand why it was changed. I also don't know where to change it back. I've tried to dpkg reconfigure locales, and checked /etc/default/locale. /etc/default/locale is set to en_ZA.UTF-8 $LANG is af_ZA.UTF-8 on login $LC_* is en_US.UTF-8 (which is wrong for en_ZA) /etc/environment contains no LANG, LC_, etc. locale: LANG=af_ZA.UTF-8 LANGUAGE=af:en_US:en LC_CTYPE=af_ZA.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=af_ZA.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=af_ZA.UTF-8 LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_ALL= I expect the environment variables of new logins to match /etc/default/locale. That file is owned by root, readable by everyone, and unmodified in almost 3 years. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: locales 2.13+git20120306-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 CheckboxSubmission: 4c35a9d722052b5a55114f98690e7808 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Tue Oct 23 12:22:39 2012 InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 (20091028.4) PackageArchitecture: all SourcePackage: langpack-locales UpgradeStatus: Upgraded to quantal on 2012-10-10 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1070284/+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 989921] Re: package colord 0.1.16-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Still happens with 12.04 - 12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/989921 Title: package colord 0.1.16-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “colord” package in Ubuntu: Triaged Status in “colord” source package in Precise: Triaged Bug description: [Impact] Upgrades from 11.10 to 12.04 fail indicating exit status 1 from installing/upgrading colord. [Discussion] /var/lib/dpkg/info/colord.postinst does not produce helpful error messages even if run manually. But the script is trying to run this command: addgroup --quiet --system scanner Running it without the --quiet option reveals the error: sudo addgroup --system scanner addgroup: The group `scanner' already exists and is not a system group. Exiting. So there's the problem: the group is already there but is not a system group. Taking a look at the group I see: $ grep scanner /etc/group scanner:x:1001:colord Indeed it is not a system group, and it only seems to be used by colord. [Test Case] 1. Install Ubuntu 11.10 2. ??? 3. Upgrade to Ubuntu 12.04 Expected: Successful upgrade with no errors Actual: Upgrade hits this error - package colord 0.1.16-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 [Workaround] sudo delgroup scanner sudo apt-get install -f [Original Report] No idea. The installation was going on and suddenly this message appears. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: colord 0.1.16-2 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu6 Architecture: i386 Date: Fri Apr 27 18:46:43 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: colord Title: package colord 0.1.16-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/989921/+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 879384] [NEW] Toggle wireless off makes it impossible to toggle back on
Public bug reported: Toggling wireless off (to disconnect) makes it impossible to later toggle back on. I have to run rfkill unblock all before I can toggle wireless back on. Then it comes back. This is for Gnome3.2, which doesn't allow you to disconnect from a wireless network: you have to toggle the entire wireless stack off to disconnect. $ sudo rfkill list all 0: sony-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: sony-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no Toggling it back on should soft-unblock if toggling it off soft-blocks. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/879384 Title: Toggle wireless off makes it impossible to toggle back on Status in “network-manager” package in Ubuntu: New Bug description: Toggling wireless off (to disconnect) makes it impossible to later toggle back on. I have to run rfkill unblock all before I can toggle wireless back on. Then it comes back. This is for Gnome3.2, which doesn't allow you to disconnect from a wireless network: you have to toggle the entire wireless stack off to disconnect. $ sudo rfkill list all 0: sony-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: sony-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no Toggling it back on should soft-unblock if toggling it off soft- blocks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/879384/+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 879384] Re: Toggle wireless off makes it impossible to toggle back on
I've found a bunch of other bugs that say that the wireless is blocked on reboot. That's not the problem here. Wireless works on reboot. It just stops working (from the GUI) if you ever disconnect from a wireless network; and you can't get it working again afterwards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/879384 Title: Toggle wireless off makes it impossible to toggle back on Status in “network-manager” package in Ubuntu: New Bug description: Toggling wireless off (to disconnect) makes it impossible to later toggle back on. I have to run rfkill unblock all before I can toggle wireless back on. Then it comes back. This is for Gnome3.2, which doesn't allow you to disconnect from a wireless network: you have to toggle the entire wireless stack off to disconnect. $ sudo rfkill list all 0: sony-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: sony-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no Toggling it back on should soft-unblock if toggling it off soft- blocks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/879384/+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 879384] Re: Toggle wireless off makes it impossible to toggle back on
Has a known workaround: rfkill unblock all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/879384 Title: Toggle wireless off makes it impossible to toggle back on Status in “network-manager” package in Ubuntu: New Bug description: Toggling wireless off (to disconnect) makes it impossible to later toggle back on. I have to run rfkill unblock all before I can toggle wireless back on. Then it comes back. This is for Gnome3.2, which doesn't allow you to disconnect from a wireless network: you have to toggle the entire wireless stack off to disconnect. $ sudo rfkill list all 0: sony-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: sony-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no Toggling it back on should soft-unblock if toggling it off soft- blocks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/879384/+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
