[Desktop-packages] [Bug 1918422] [NEW] At startup cryptsetup passwords are sometimes forgotten
Public bug reported: At startup of the Ubuntu system, encrypted disks are unlocked. The saved passwords are forgotten in a very reproducible way. This happens if you have three or more disks to be unlocked and mounted. 1) At first startup you enter the password and saves it for future use. The disk is unlocked and mounted. 2) The second startup the disk is only unlocked, but not mounted. Clicking on it in the file browser mounts it. 3) The third startup you need to enter the password again, starting over again at step one. The password is still in the keyring and every time you enter the password a new entry is added. Looking in "gnome-disks" it seems as while other disks are being unlocked, a disk can't be mounted at the same time. My unlock time it set for 60 seconds. $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1918422 Title: At startup cryptsetup passwords are sometimes forgotten Status in gnome-disk-utility package in Ubuntu: New Bug description: At startup of the Ubuntu system, encrypted disks are unlocked. The saved passwords are forgotten in a very reproducible way. This happens if you have three or more disks to be unlocked and mounted. 1) At first startup you enter the password and saves it for future use. The disk is unlocked and mounted. 2) The second startup the disk is only unlocked, but not mounted. Clicking on it in the file browser mounts it. 3) The third startup you need to enter the password again, starting over again at step one. The password is still in the keyring and every time you enter the password a new entry is added. Looking in "gnome-disks" it seems as while other disks are being unlocked, a disk can't be mounted at the same time. My unlock time it set for 60 seconds. $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1918422/+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 1124282] Re: screen lock by timeout does not affect vm
*** This bug is a duplicate of bug 49579 *** https://bugs.launchpad.net/bugs/49579 Fails with Virtualbox in focus: user@ubuntu:~$ sleep 20s; gnome-screensaver-command --lock Works with Virtualbox in focus: user@ubuntu:~$ sleep 20s; wmctrl -k on; gnome-screensaver-command --lock Works with Virtualbox in focus: user@ubuntu:~$ sleep 20s; wmctrl -k on; gnome-screensaver-command --lock; wmctrl -k off Works with Virtualbox in focus: user@ubuntu:~$ sleep 20s; wmctrl -k on; gnome-screensaver-command --lock; sleep 1s; wmctrl -k off Works with Virtualbox in focus: user@ubuntu:~$ sleep 20s; wmctrl -k on; gnome-screensaver-command --lock; wmctrl -k off I can't understand why it couldn't be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1124282 Title: screen lock by timeout does not affect vm Status in gnome-screensaver package in Ubuntu: Opinion Bug description: I have a virtualbox running a Windows 7 64 bit on my Ubuntu 12.04 64 bit. If the Windows window is on focus and i am inactive, then my screen is locked after a certain amount of time and should normally ask for my password. But it only does so if a change the focus to a window other than my virtual machine. Worse than that, if I hurry after my screen should be locked, I perform some actions on my Ubuntu host before the password prompt locks the screen. So the presence of my virtualbox allows people to open a terminal on the host and type any command in the worst case. This is a security issue. Ubuntu: 12.04 64 bit Window Manager: gnome-shell VM: Oracle VM VirtualBox Manager 4.1.12_Ubuntu Screen saver: gnome-screensaver 3.4.1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screensaver 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Feb 13 17:19:45 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) WindowManager: No value set for `/desktop/gnome/session/required_components/windowmanager' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1124282/+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 1276659] Re: suspending on shutdown when lid is closed
** Package changed: xorg-server (Ubuntu) => systemd (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/1276659 Title: suspending on shutdown when lid is closed Status in systemd package in Ubuntu: New Bug description: Description of the problem: When power-settings are set to do nothing when lid is closed, my computer most of the times suspends on shutdown, only shutdown. When lid is opened the shutdown is continued. Result 9 cases out of 10: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. Wait for suspend. 6. Open the lid. (You will find the computer in suspended mode. It always displays its final logo before shutdown when opened. So actually the shutdown is triggered and in progress, but is then interrupted by a suspend instruction.) 7. The computer continues to shutdown, when lid is opened. Expected result: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. The computer is off. When I don't close the lid everything goes as expected. I actually have a backup script running when I shutdown the computer and the last thing it does is to shutdown the computer. I have run Debian with gtk 2 successfully. I have run Ubuntu successfully before Unity. Now I run UbuntuGnome. I think there is a change in option, set to the kernel during shutdown, which triggers the suspend. A page (https://wiki.ubuntu.com/Bugs/FindRightPackage) suggests gnome- power-manager, pm-utils, or the kernel to be the failure. patrik@Ubuntu:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1276659/+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 1276659] Re: suspending on shutdown when lid is closed
It is also present in Ubuntu 14.10. -- 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/1276659 Title: suspending on shutdown when lid is closed Status in xorg-server package in Ubuntu: New Bug description: Description of the problem: When power-settings are set to do nothing when lid is closed, my computer most of the times suspends on shutdown, only shutdown. When lid is opened the shutdown is continued. Result 9 cases out of 10: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. Wait for suspend. 6. Open the lid. (You will find the computer in suspended mode. It always displays its final logo before shutdown when opened. So actually the shutdown is triggered and in progress, but is then interrupted by a suspend instruction.) 7. The computer continues to shutdown, when lid is opened. Expected result: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. The computer is off. When I don't close the lid everything goes as expected. I actually have a backup script running when I shutdown the computer and the last thing it does is to shutdown the computer. I have run Debian with gtk 2 successfully. I have run Ubuntu successfully before Unity. Now I run UbuntuGnome. I think there is a change in option, set to the kernel during shutdown, which triggers the suspend. A page (https://wiki.ubuntu.com/Bugs/FindRightPackage) suggests gnome- power-manager, pm-utils, or the kernel to be the failure. patrik@Ubuntu:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276659/+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 1276659] Re: suspending on shutdown when lid is closed
This bug is also in effect when shutting down in the normal way: 1) Select shutdown from the menu 2) Select restart or shutdown 3) Close the lid The computer suspends, when x-org exit. -- 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/1276659 Title: suspending on shutdown when lid is closed Status in xorg-server package in Ubuntu: New Bug description: Description of the problem: When power-settings are set to do nothing when lid is closed, my computer most of the times suspends on shutdown, only shutdown. When lid is opened the shutdown is continued. Result 9 cases out of 10: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. Wait for suspend. 6. Open the lid. (You will find the computer in suspended mode. It always displays its final logo before shutdown when opened. So actually the shutdown is triggered and in progress, but is then interrupted by a suspend instruction.) 7. The computer continues to shutdown, when lid is opened. Expected result: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. The computer is off. When I don't close the lid everything goes as expected. I actually have a backup script running when I shutdown the computer and the last thing it does is to shutdown the computer. I have run Debian with gtk 2 successfully. I have run Ubuntu successfully before Unity. Now I run UbuntuGnome. I think there is a change in option, set to the kernel during shutdown, which triggers the suspend. A page (https://wiki.ubuntu.com/Bugs/FindRightPackage) suggests gnome- power-manager, pm-utils, or the kernel to be the failure. patrik@Ubuntu:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276659/+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 885593] Re: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows
At the moment I don't use Windows, but at the time of filing this bug all worked with Acrobat Reader for Windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/885593 Title: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows Status in evince package in Ubuntu: Invalid Bug description: The attached pdf-file can be read with Acrobat Reader on Windows, but is said to be damaged by document viewer. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Thu Nov 3 10:21:55 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-12.51-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/885593/+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 885593] Re: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows
It opens in Adobe Windows and displays correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/885593 Title: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows Status in evince package in Ubuntu: Invalid Bug description: The attached pdf-file can be read with Acrobat Reader on Windows, but is said to be damaged by document viewer. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Thu Nov 3 10:21:55 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-12.51-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/885593/+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 1276659] Re: suspending on shutdown when lid is closed
This bug is from Xorg: Log of Acpid: acpid: received input layer event "button/lid LID close" acpid: rule from 1606[0:0] matched acpid: notifying client 1606[0:0] acpid: 1 total rule matched acpid: completed input layer event "button/lid LID close" acpid: received input layer event "button/lid LID open" acpid: rule from 1606[0:0] matched acpid: notifying client 1606[0:0] acpid: 1 total rule matched acpid: completed input layer event "button/lid LID open" Process 1606 is notified: ps -Al | grep 1606 4 S 0 1606 1262 1 80 0 - 90365 poll_s tty7 00:00:18 Xorg patrik@ubuntu:/home/files$ dpkg -S Xorg xserver-xorg-core: /usr/share/man/man1/Xorg.1.gz xserver-xorg-core: /usr/bin/Xorg => xorg-server ** Package changed: gnome-power-manager (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1276659 Title: suspending on shutdown when lid is closed Status in “xorg-server” package in Ubuntu: New Bug description: Description of the problem: When power-settings are set to do nothing when lid is closed, my computer most of the times suspends on shutdown, only shutdown. When lid is opened the shutdown is continued. Result 9 cases out of 10: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. Wait for suspend. 6. Open the lid. (You will find the computer in suspended mode. It always displays its final logo before shutdown when opened. So actually the shutdown is triggered and in progress, but is then interrupted by a suspend instruction.) 7. The computer continues to shutdown, when lid is opened. Expected result: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. The computer is off. When I don't close the lid everything goes as expected. I actually have a backup script running when I shutdown the computer and the last thing it does is to shutdown the computer. I have run Debian with gtk 2 successfully. I have run Ubuntu successfully before Unity. Now I run UbuntuGnome. I think there is a change in option, set to the kernel during shutdown, which triggers the suspend. A page (https://wiki.ubuntu.com/Bugs/FindRightPackage) suggests gnome- power-manager, pm-utils, or the kernel to be the failure. patrik@Ubuntu:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276659/+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 1276659] Re: suspending on shutdown when lid is closed
This bug is still present in Ubuntu 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1276659 Title: suspending on shutdown when lid is closed Status in “gnome-power-manager” package in Ubuntu: New Bug description: Description of the problem: When power-settings are set to do nothing when lid is closed, my computer most of the times suspends on shutdown, only shutdown. When lid is opened the shutdown is continued. Result 9 cases out of 10: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. Wait for suspend. 6. Open the lid. (You will find the computer in suspended mode. It always displays its final logo before shutdown when opened. So actually the shutdown is triggered and in progress, but is then interrupted by a suspend instruction.) 7. The computer continues to shutdown, when lid is opened. Expected result: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. The computer is off. When I don't close the lid everything goes as expected. I actually have a backup script running when I shutdown the computer and the last thing it does is to shutdown the computer. I have run Debian with gtk 2 successfully. I have run Ubuntu successfully before Unity. Now I run UbuntuGnome. I think there is a change in option, set to the kernel during shutdown, which triggers the suspend. A page (https://wiki.ubuntu.com/Bugs/FindRightPackage) suggests gnome- power-manager, pm-utils, or the kernel to be the failure. patrik@Ubuntu:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1276659/+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 1285543] [NEW] apt-get remove simple-scan will remove ubuntu-gnome-desktop
Public bug reported: When uninstalling simple-scan ubuntu-gnome-desktop will also be uninstalled: $ sudo apt-get remove simple-scan [sudo] password for patrik: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: simple-scan ubuntu-gnome-desktop 0 upgraded, 0 newly installed, 2 to remove and 15 not upgraded. 4 not fully installed or removed. After this operation, 671 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: simple-scan 3.11.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: GNOME Date: Thu Feb 27 08:50:03 2014 DriverPackageVersions: libsane 1.0.23-3ubuntu3 libsane-extras N/A hplip 3.14.1-1 hpoj N/A InstallationDate: Installed on 2014-02-26 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140226) MachineType: ASUSTeK Computer INC. 1215N ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic root=UUID=ad95ee31-a262-4713-911b-944bb6afe9bc ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1215N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd05/05/2011:svnASUSTeKComputerINC.:pn1215N:pvrx.x:rvnASUSTeKComputerINC.:rn1215N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1215N dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1285543 Title: apt-get remove simple-scan will remove ubuntu-gnome-desktop Status in “simple-scan” package in Ubuntu: New Bug description: When uninstalling simple-scan ubuntu-gnome-desktop will also be uninstalled: $ sudo apt-get remove simple-scan [sudo] password for patrik: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: simple-scan ubuntu-gnome-desktop 0 upgraded, 0 newly installed, 2 to remove and 15 not upgraded. 4 not fully installed or removed. After this operation, 671 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: simple-scan 3.11.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: GNOME Date: Thu Feb 27 08:50:03 2014 DriverPackageVersions: libsane 1.0.23-3ubuntu3 libsane-extras N/A hplip 3.14.1-1 hpoj N/A InstallationDate: Installed on 2014-02-26 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140226) MachineType: ASUSTeK Computer INC. 1215N ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic root=UUID=ad95ee31-a262-4713-911b-944bb6afe9bc ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1215N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd05/05/2011:svnASUSTeKComputerINC.:pn1215N:pvrx.x:rvnASUSTeKComputerINC.:rn1215N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1215N dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1285543/+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 1283991] Re: screen lock fail unlock with gnome
I managed to report this bug with "ubuntu-bug" instead. This is bug 1285258. ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1283991 Title: screen lock fail unlock with gnome Status in “gnome-screensaver” package in Ubuntu: Invalid Bug description: Gnome screen saver fails to unlock and the rotating pause indicator rotates. If I press cancel, I can try again and most of the times it works on the second attempt. When it works the inputed characters are erased immediately when pressing enter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1283991/+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 1285258] [NEW] failing to unlock screensaver
Public bug reported: There seem to be two distinct errors when unlocking gnome-screensaver. Both prevents you from logging in. The first is the most serious. 1) When I move the mouse, the lock screen appears. Whatever I type it only activates the top right menu. I'm completely unable to login. I used power button to restart the computer. 2) Most common is that you can type your password, but the rotating- pause-animation never stops. You can cancel this with the button and usually you can get passed the screensave on the second attempt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 Date: Wed Feb 26 17:54:36 2014 InstallationDate: Installed on 2014-02-26 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140226) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1285258 Title: failing to unlock screensaver Status in “gnome-screensaver” package in Ubuntu: New Bug description: There seem to be two distinct errors when unlocking gnome-screensaver. Both prevents you from logging in. The first is the most serious. 1) When I move the mouse, the lock screen appears. Whatever I type it only activates the top right menu. I'm completely unable to login. I used power button to restart the computer. 2) Most common is that you can type your password, but the rotating- pause-animation never stops. You can cancel this with the button and usually you can get passed the screensave on the second attempt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 Date: Wed Feb 26 17:54:36 2014 InstallationDate: Installed on 2014-02-26 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140226) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1285258/+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 1283991] Re: screen lock fail unlock with gnome
I'm unable to apport-collect: patrik@patrik-1215N:/media/patrik/458257a4-e4bf-4632-b4c2-6d098f3b4a0b$ apport-collect 1283991 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=SBw6stK5BZxV8RVR1b0c&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press any key to continue or wait (5) seconds... Waiting to hear from Launchpad about your decision... (process:5643): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1283991 Title: screen lock fail unlock with gnome Status in “gnome-screensaver” package in Ubuntu: Incomplete Bug description: Gnome screen saver fails to unlock and the rotating pause indicator rotates. If I press cancel, I can try again and most of the times it works on the second attempt. When it works the inputed characters are erased immediately when pressing enter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1283991/+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 1283991] Re: screen lock fail unlock with gnome
This is tested with Ubuntu Gnome 14.04 prerelease. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1283991 Title: screen lock fail unlock with gnome Status in “gnome-screensaver” package in Ubuntu: New Bug description: Gnome screen saver fails to unlock and the rotating pause indicator rotates. If I press cancel, I can try again and most of the times it works on the second attempt. When it works the inputed characters are erased immediately when pressing enter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1283991/+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 1283991] [NEW] screen lock fail unlock with gnome
Public bug reported: Gnome screen saver fails to unlock and the rotating pause indicator rotates. If I press cancel, I can try again and most of the times it works on the second attempt. When it works the inputed characters are erased immediately when pressing enter ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1283991 Title: screen lock fail unlock with gnome Status in “gnome-screensaver” package in Ubuntu: New Bug description: Gnome screen saver fails to unlock and the rotating pause indicator rotates. If I press cancel, I can try again and most of the times it works on the second attempt. When it works the inputed characters are erased immediately when pressing enter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1283991/+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 1276659] Re: suspending on shutdown when lid is closed
The message that appears when lid is opened is something about "acpi". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1276659 Title: suspending on shutdown when lid is closed Status in “gnome-power-manager” package in Ubuntu: New Bug description: Description of the problem: When power-settings are set to do nothing when lid is closed, my computer most of the times suspends on shutdown, only shutdown. When lid is opened the shutdown is continued. Result 9 cases out of 10: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. Wait for suspend. 6. Open the lid. (You will find the computer in suspended mode. It always displays its final logo before shutdown when opened. So actually the shutdown is triggered and in progress, but is then interrupted by a suspend instruction.) 7. The computer continues to shutdown, when lid is opened. Expected result: 1. Setting options to do nothing (not suspending) on closing lid on my laptop. 2. Open terminal and type "sudo shutdown -P 5 min" 3. Close Lid. 4. Wait for shutdown. 5. The computer is off. When I don't close the lid everything goes as expected. I actually have a backup script running when I shutdown the computer and the last thing it does is to shutdown the computer. I have run Debian with gtk 2 successfully. I have run Ubuntu successfully before Unity. Now I run UbuntuGnome. I think there is a change in option, set to the kernel during shutdown, which triggers the suspend. A page (https://wiki.ubuntu.com/Bugs/FindRightPackage) suggests gnome- power-manager, pm-utils, or the kernel to be the failure. patrik@Ubuntu:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1276659/+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 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
Anton Veretenenko (anton.veretenenko): You can buy me a new laptop every time my internal right button on my computer needs to be switched! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/410636 Title: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. Status in GTK+ GUI Toolkit: Confirmed Status in One Hundred Paper Cuts: In Progress Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: When I right click in nautilus, the context menu appear. If I right click on a menu item, the function of that menu item is performed. This is very annoying, because when the context menu appears, the mouse is at the first menu item, so if you accidentally right click two times, you will surely perform the function of the first menu item! Everytime I right click in desktop, i probably create a new Folder! I think there maybe 2 solutions to this: - To perform the function of a menu item, only left click is allowed. - When the user right click, the context menu will appear at a bit lower position, so the mouse will not be at the first menu item. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/410636/+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 774312] Re: making link from Nautilus doesn't use the correct working directory
The bug is still there when you use LibreOffice Writer and tested with the live cd. 1) Create a Writer document. Write "test" into it and save it into "Documents" 2) Quit Writer. 3) Make a link to your document. 4) Writer accepts to open both the original file and the link-file and start to edit them both. I'm not able to use any software to check the original reported error with the live cd. ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/774312 Title: making link from Nautilus doesn't use the correct working directory Status in “nautilus” package in Ubuntu: New Bug description: Binary package hint: nautilus When making a link from nautilus and using it from another folder doesn't set the correct working folder. Example steps to reproduce: 1) Find a file and make a link to it by right clicking in nautilus. 2) Move the link-file to desktop. 3) Double clicking runs the action, but it is not the correct working folder The working folder should be where the file is, not, as in this example, on desktop. Always reproducible. I use some programs that depend on being started in the folder where data is. This is not a problem if there is only one data file, but it is, when there are several files necessary such as an IDE. Ubuntu 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/774312/+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 885593] Re: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows
The about dialog says: evince. http://www.gnome.org/projects/evince ** Changed in: evince (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/885593 Title: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows Status in “evince” package in Ubuntu: New Bug description: The attached pdf-file can be read with Acrobat Reader on Windows, but is said to be damaged by document viewer. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Thu Nov 3 10:21:55 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-12.51-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/885593/+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 898531] [NEW] thunderbird doesn't quit when using IMAP and empty trash on exit
Public bug reported: When using an IMAP server and set Thunderbird to empty trash on exit, Thunderbird doesn't quit. When you press the cross button on the title list, Thunderbird closes all its windows, but the process always stays in memory. You can't start Thunderbird again with this option, it says it is still running. You need to kill the process first. Unchecking "empty on exit" when using IMAP and you can start Thunderbird repeatedly. (When using POP it always works as expected.) Ubuntu 10.04 Thunderbird 3.1.15+build1+nobinonly-0ubuntu0.11.04.1 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Description changed: When using an IMAP server and set Thunderbird to empty trash on exit, Thunderbird doesn't quit. When you press the cross button on the title list, Thunderbird closes all its windows, but the process always stays - always memory. + in memory. You can't start Thunderbird again with this option, it says it is still running. You need to kill the process first. Unchecking "empty on exit" when using IMAP and you can start Thunderbird repeatedly. (When using POP it always works as expected.) Ubuntu 10.04 Thunderbird 3.1.15+build1+nobinonly-0ubuntu0.11.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/898531 Title: thunderbird doesn't quit when using IMAP and empty trash on exit Status in “thunderbird” package in Ubuntu: New Bug description: When using an IMAP server and set Thunderbird to empty trash on exit, Thunderbird doesn't quit. When you press the cross button on the title list, Thunderbird closes all its windows, but the process always stays in memory. You can't start Thunderbird again with this option, it says it is still running. You need to kill the process first. Unchecking "empty on exit" when using IMAP and you can start Thunderbird repeatedly. (When using POP it always works as expected.) Ubuntu 10.04 Thunderbird 3.1.15+build1+nobinonly-0ubuntu0.11.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/898531/+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 892589] Re: attaching an external monitor to a laptop makes the image bad
I read the information on https://wiki.ubuntu.com/Bugs/FindRightPackage and took a package that could be involved in this issue. One thing to note: If you start Ubuntu with the external monitor everything goes really fine. This bug happens when you attach the monitor while Ubuntu is running. ** Package changed: ubuntu => metacity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/892589 Title: attaching an external monitor to a laptop makes the image bad Status in “metacity” package in Ubuntu: New Bug description: If you attach an external monitor to a laptop while Ubuntu is running, always makes the image of the screen look bad on both the internal and the external monitor. I have two command attached to keyboard shortcuts which sometimes can make the computer usable again, if you switch back and forth between the internal and external monitor with: xrandr --output LVDS1 --off --output VGA1 --auto #switch on the internal monitor, external off xrandr --output LVDS1 --auto --output VGA1 --off #external on, internal off The success seem to depend on what programs are running at the moment of running those commands. If you only have a terminal opened it goes fine, but with Libreoffice and Firefox you need to restart Ubuntu. Attached are three screenshots which all show the screen looks like when the external monitor is attached. Ubuntu 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/892589/+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 322387] Re: network monitor doesnt retry connection after waiting for password for too long
This bug is still there. Here is a test case, but can also happen if low signal strength or some radio noise. Take a modern cellular phone and connect the wireless radio (wlan) from the computer to the phone. When connected walk away from the computer and put the phone where it is unreachable. NetworkManager puts up a requester asking for the password and it won't dismiss itself. Sometimes you accidentally enter some letters and press connect and you can't connect to your wireless network to much you try. This has happened several times for me. It is very annoying. Better would be if there is a notification (right top of screen) telling that the password is incorrect and that there is a menu in "system/preferences/network connections" giving the option to set a password. It will retry the same connection if it becomes available. -- 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/322387 Title: network monitor doesnt retry connection after waiting for password for too long Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I have set ubuntu (8.10) to automatically log in to gnome on startup - this results in the keyring manager asking for my password anyway, since it needs it in order to unlock the keyring so that it can connect to any of my wireless networks that i'm near. Trouble is if i turn the laptop on and walk off when i come back gnome is logged in and the keyring thing is asking for my password, but by the time i type it in the WPA authentication request that network manager initiated has timed out. Once i put my password into keyring manager, it just goes away, and network manager does not try to reinitiate the WPA logon. So I have to click the network manager tray icon and manually choose my wireless connection. What i'd like to happen is i turn my laptop, come back minutes later and gnome is up, and i'm connected to the nearest wireless network. What happens currently is i turn the laptop on, walk off, gnome logs in, network manager asks the keyring manager for one of my WPA keys, but keyring manager needs me to have sudo'd recently or something which i assume is usually accomplished by typing in your password to log in to gnome, so sits there waiting for a password to be put in while network manager times out and gives up. Then once i give the keyring manager my password it takes it but has no one to give my WPA keys to. Then i manually tell network manager which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/322387/+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 322387] Re: network monitor doesnt retry connection after waiting for password for too long
** Changed in: network-manager (Ubuntu) Status: Invalid => 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/322387 Title: network monitor doesnt retry connection after waiting for password for too long Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I have set ubuntu (8.10) to automatically log in to gnome on startup - this results in the keyring manager asking for my password anyway, since it needs it in order to unlock the keyring so that it can connect to any of my wireless networks that i'm near. Trouble is if i turn the laptop on and walk off when i come back gnome is logged in and the keyring thing is asking for my password, but by the time i type it in the WPA authentication request that network manager initiated has timed out. Once i put my password into keyring manager, it just goes away, and network manager does not try to reinitiate the WPA logon. So I have to click the network manager tray icon and manually choose my wireless connection. What i'd like to happen is i turn my laptop, come back minutes later and gnome is up, and i'm connected to the nearest wireless network. What happens currently is i turn the laptop on, walk off, gnome logs in, network manager asks the keyring manager for one of my WPA keys, but keyring manager needs me to have sudo'd recently or something which i assume is usually accomplished by typing in your password to log in to gnome, so sits there waiting for a password to be put in while network manager times out and gives up. Then once i give the keyring manager my password it takes it but has no one to give my WPA keys to. Then i manually tell network manager which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/322387/+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 885593] Re: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows
** Attachment added: "Damaged pdf-file according to document viewer" https://bugs.launchpad.net/bugs/885593/+attachment/2583919/+files/2_2010_Kompetensutveckling.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/885593 Title: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows Status in “evince” package in Ubuntu: New Bug description: The attached pdf-file can be read with Acrobat Reader on Windows, but is said to be damaged by document viewer. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Thu Nov 3 10:21:55 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-12.51-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/885593/+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 885593] [NEW] pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows
Public bug reported: The attached pdf-file can be read with Acrobat Reader on Windows, but is said to be damaged by document viewer. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Thu Nov 3 10:21:55 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-12.51-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 natty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/885593 Title: pdf is damaged says Document Viewer, but can be open with Acrobat Reader on windows Status in “evince” package in Ubuntu: New Bug description: The attached pdf-file can be read with Acrobat Reader on Windows, but is said to be damaged by document viewer. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 Architecture: i386 Date: Thu Nov 3 10:21:55 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-12.51-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/885593/+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 842939] Re: libreoffice calc read error during opening
I had a backup copy of the file. Libreoffice opened this file without error. Some changes lost. ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/842939 Title: libreoffice calc read error during opening Status in “libreoffice” package in Ubuntu: Invalid Bug description: I can't open a speadsheet that I could open with previous version of Libreoffice-calc. The error I get: "Read error: Format error discovered in the file sub-document content.xml at 2, 2210775 (row, col)." patrik@ubuntu:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 patrik@ubuntu:~$ apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages patrik@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/842939/+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 842939] Re: libreoffice calc read error during opening
** Description changed: - I can open a speadsheet that I could open with previous version of + I can't open a speadsheet that I could open with previous version of Libreoffice-calc. The error I get: "Read error: Format error discovered in the file sub-document content.xml at 2, 2210775 (row, col)." patrik@ubuntu:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 patrik@ubuntu:~$ apt-cache policy libreoffice-calc libreoffice-calc: - Installed: 1:3.3.3-1ubuntu2 - Candidate: 1:3.3.3-1ubuntu2 - Version table: - *** 1:3.3.3-1ubuntu2 0 - 500 http://archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages - 100 /var/lib/dpkg/status - 1:3.3.2-1ubuntu4 0 - 500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages + Installed: 1:3.3.3-1ubuntu2 + Candidate: 1:3.3.3-1ubuntu2 + Version table: + *** 1:3.3.3-1ubuntu2 0 + 500 http://archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages + 100 /var/lib/dpkg/status + 1:3.3.2-1ubuntu4 0 + 500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages patrik@ubuntu:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/842939 Title: libreoffice calc read error during opening Status in “libreoffice” package in Ubuntu: New Bug description: I can't open a speadsheet that I could open with previous version of Libreoffice-calc. The error I get: "Read error: Format error discovered in the file sub-document content.xml at 2, 2210775 (row, col)." patrik@ubuntu:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 patrik@ubuntu:~$ apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages patrik@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/842939/+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 842939] [NEW] libreoffice calc read error during opening
Public bug reported: I can open a speadsheet that I could open with previous version of Libreoffice-calc. The error I get: "Read error: Format error discovered in the file sub-document content.xml at 2, 2210775 (row, col)." patrik@ubuntu:~$ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 patrik@ubuntu:~$ apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages patrik@ubuntu:~$ ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/842939 Title: libreoffice calc read error during opening Status in “libreoffice” package in Ubuntu: New Bug description: I can open a speadsheet that I could open with previous version of Libreoffice-calc. The error I get: "Read error: Format error discovered in the file sub-document content.xml at 2, 2210775 (row, col)." patrik@ubuntu:~$ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 patrik@ubuntu:~$ apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages patrik@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/842939/+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 657022] Re: screen-saver does not lock after movie/music played
I think this is a serious security issue. You should know that you can leave the computer and no one is able to get into your work, once the time-out of the screensaver is elapsed. The outline to reproduce this bug is described above and I answer requests of to assist Ubuntu being better. Does a post of a video dump of the screen make any difference? ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/657022 Title: screen-saver does not lock after movie/music played Status in “gnome-screensaver” package in Ubuntu: New Bug description: Binary package hint: gnome-screensaver After a movie/music (Movieplayer) has been played and the screensaver times out, the screensaver does not lock the screen. It goes blank if you have set it to do it, but you can touch any key to activate the screen and you can start using it. After one touch and the screensaver times out, everything works again. The screensaver should lock after timing out, after music/movie played. gnome-screensaver: 2.30.0-0ubuntu2 Ubuntu 10.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/657022/+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
