[Desktop-packages] [Bug 2033417] Re: Order of buttons in snap Thunderbird 115 is not following the theme
This affects Ubuntu 22.04 and 23.10 in GNOME. -- 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/2033417 Title: Order of buttons in snap Thunderbird 115 is not following the theme Status in thunderbird package in Ubuntu: Incomplete Bug description: See the screenshot attached for better understanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2033417/+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 2033417] Re: Order of buttons in snap Thunderbird 115 is not following the theme
Hi. New file attached! Thank you. ** Attachment added: "screenshot_snap115.png" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2033417/+attachment/5707170/+files/screenshot_snap115.png -- 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/2033417 Title: Order of buttons in snap Thunderbird 115 is not following the theme Status in thunderbird package in Ubuntu: Incomplete Bug description: See the screenshot attached for better understanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2033417/+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 2033417] [NEW] Order of buttons in snap Thunderbird 115 is not following the theme
Public bug reported: See the screenshot attached for better understanding. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Captura de ecrã de 2023-08-29 17-40-58.png" https://bugs.launchpad.net/bugs/2033417/+attachment/5696145/+files/Captura%20de%20ecr%C3%A3%20de%202023-08-29%2017-40-58.png -- 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/2033417 Title: Order of buttons in snap Thunderbird 115 is not following the theme Status in thunderbird package in Ubuntu: New Bug description: See the screenshot attached for better understanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2033417/+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 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 This bug appeared after an upgrade from 20 to 22 LTS. I've switched back to XOrg as Wayland needed even two clicks to focus. All new windows are affected regardless of whether it is dialogue or not. A bit frustrated. Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: GenuineIntel Model name:Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887/+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 1949433] [NEW] The progress remains inactive and instaling software seems to be doing nothing. Using the cli works.
Public bug reported: When trying to install hexchat there is no progress shown. It seems like installation does nothing. Using the cli works. I was using the flathub (flatpak) to install the aarch64 version of hexchat. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software 40.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 07:46:42 2021 InstallationDate: Installed on 2021-10-26 (6 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) InstalledPlugins: gnome-software-plugin-flatpak 40.4-1build1 gnome-software-plugin-snap40.4-1build1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 impish uec-images wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1949433 Title: The progress remains inactive and instaling software seems to be doing nothing. Using the cli works. Status in gnome-software package in Ubuntu: New Bug description: When trying to install hexchat there is no progress shown. It seems like installation does nothing. Using the cli works. I was using the flathub (flatpak) to install the aarch64 version of hexchat. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software 40.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 07:46:42 2021 InstallationDate: Installed on 2021-10-26 (6 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) InstalledPlugins: gnome-software-plugin-flatpak 40.4-1build1 gnome-software-plugin-snap40.4-1build1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1949433/+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 1849512] [NEW] Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory
Public bug reported: When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user has a home directory mounted on different ZFS dataset like in this case: https://paste.ubuntu.com/p/CSsNtt5j6c/ Afterwards when you're adding new users via the gnome-control-center or with adduser, the new users home directories are created on rpool/USERDATA but they don't have separate ZFS datasets. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 18:12:56 2019 InstallationDate: Installed on 2019-10-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - Creating a new user on top of ZFS filesystem does not create a new datase for his home directory + Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory ** Description changed: - When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user have a home directory mounted on different ZFS dataset like in this case: + When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user has a home directory mounted on different ZFS dataset like in this case: https://paste.ubuntu.com/p/CSsNtt5j6c/ Afterwards when you're adding new users via the gnome-control-center or with adduser, the new users home directories are created on rpool/USERDATA but they don't have separate ZFS datasets. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 18:12:56 2019 InstallationDate: Installed on 2019-10-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1849512 Title: Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory Status in gnome-control-center package in Ubuntu: New Bug description: When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user has a home directory mounted on different ZFS dataset like in this case: https://paste.ubuntu.com/p/CSsNtt5j6c/ Afterwards when you're adding new users via the gnome-control-center or with adduser, the new users home directories are created on rpool/USERDATA but they don't have separate ZFS datasets. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 18:12:56 2019 InstallationDate: Installed on 2019-10-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849512/+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 1846505] [NEW] package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
Public bug reported: Erro ao instalar o pacote. O que fazer? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: desktop-file-utils 0.22-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 3 11:18:46 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2019-06-21 (103 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.26 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1846505 Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar Status in desktop-file-utils package in Ubuntu: New Bug description: Erro ao instalar o pacote. O que fazer? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: desktop-file-utils 0.22-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 3 11:18:46 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2019-06-21 (103 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.26 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1846505/+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 335662] Re: [jaunty] hplip status service cannot find system tray
Installed HPLIP 3.19.3 on Ubuntu 18.04 System Tray problem still there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/335662 Title: [jaunty] hplip status service cannot find system tray Status in HPLIP: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip After login to ubuntu hplip status service cannot find system tray. It shows dialog box: "No system tray detected on this system. Unable to start, exiting". hplip version is 2.8.12-3ubuntu1 on jaunty I found the same bug reported in Debian http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg618714.html Regards To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/335662/+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 1767817] Re: Full text search does not work
Ok guys, how long 'till this drop into updates? Still on proposed... -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Bionic: Fix Committed Status in nautilus source package in Cosmic: Fix Committed Bug description: * Impact The text search feature, which is depending on tracker, is not working even when the service is installed * Test case - install tracker and restart your session - echo 'Nautilus is great' > ~/txt - open nautilus and type 'great' in the search entry -> the file should be listed * Regression potential That's changing the search provider logic, make sure that searching for file without tracker still works (that only look at filenames) and there is no extra logging/cpu usage --- Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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
Re: [Desktop-packages] [Bug 1784173] [NEW] after upgrade to Xubuntu 18.04 Libreoffice crashes during starting
I also removed and re-installed libreoffice.. no luck Vriendelijke groet, Ivo Naninck On 28-07-18 21:58, Ivo Naninck wrote: > Public bug reported: > > It crashes while libreoffice is starting. > I have already tried to remove the user profile from > /home/inaninck/.config/.libreoffice/4.. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libreoffice 1:6.0.3-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 > Uname: Linux 4.15.0-29-generic i686 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: i386 > CurrentDesktop: XFCE > Date: Sat Jul 28 21:53:46 2018 > InstallationDate: Installed on 2014-01-19 (1650 days ago) > InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) > SourcePackage: libreoffice > UpgradeStatus: No upgrade log present (probably fresh install) > > ** Affects: libreoffice (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: apport-bug bionic i386 > -- 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/1784173 Title: after upgrade to Xubuntu 18.04 Libreoffice crashes during starting Status in libreoffice package in Ubuntu: New Bug description: It crashes while libreoffice is starting. I have already tried to remove the user profile from /home/inaninck/.config/.libreoffice/4.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: XFCE Date: Sat Jul 28 21:53:46 2018 InstallationDate: Installed on 2014-01-19 (1650 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1784173/+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 1784173] [NEW] after upgrade to Xubuntu 18.04 Libreoffice crashes during starting
Public bug reported: It crashes while libreoffice is starting. I have already tried to remove the user profile from /home/inaninck/.config/.libreoffice/4.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: XFCE Date: Sat Jul 28 21:53:46 2018 InstallationDate: Installed on 2014-01-19 (1650 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- 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/1784173 Title: after upgrade to Xubuntu 18.04 Libreoffice crashes during starting Status in libreoffice package in Ubuntu: New Bug description: It crashes while libreoffice is starting. I have already tried to remove the user profile from /home/inaninck/.config/.libreoffice/4.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: XFCE Date: Sat Jul 28 21:53:46 2018 InstallationDate: Installed on 2014-01-19 (1650 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1784173/+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 1760294] [NEW] package sysfsutils 2.1.0+repack-4 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug
Public bug reported: I wanted to get my Wireless XBox One Controller to get to work, so I followed this guide: https://askubuntu.com/questions/783587/how-do-i-get-an-xbox-one-controller-to-work-with-16-04-not-steam#798254 But when installing sysfsutilsm I got this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: sysfsutils 2.1.0+repack-4 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libsysfs2:amd64: Install sysfsutils:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Mar 31 14:46:34 2018 Dependencies: gcc-7-base 7.2.0-8ubuntu3.2 libc6 2.26-0ubuntu2.1 libgcc1 1:7.2.0-8ubuntu3.2 libsysfs2 2.1.0+repack-4 multiarch-support 2.26-0ubuntu2.1 ErrorMessage: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug (post-installation script gave back error value 1) InstallationDate: Installed on 2018-02-18 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sysfsutils Title: package sysfsutils 2.1.0+repack-4 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sysfsutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful ** Description changed: I wanted to get my Wireless XBox One Controller to get to work, so I followed this guide: https://askubuntu.com/questions/783587/how-do-i-get-an-xbox-one-controller-to-work-with-16-04-not-steam#798254 But when installing sysfsutilsm I got this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: sysfsutils 2.1.0+repack-4 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: - libsysfs2:amd64: Install - sysfsutils:amd64: Install - NULL: ConfigurePending + libsysfs2:amd64: Install + sysfsutils:amd64: Install + NULL: ConfigurePending Architecture: amd64 Date: Sat Mar 31 14:46:34 2018 Dependencies: - gcc-7-base 7.2.0-8ubuntu3.2 - libc6 2.26-0ubuntu2.1 - libgcc1 1:7.2.0-8ubuntu3.2 - libsysfs2 2.1.0+repack-4 - multiarch-support 2.26-0ubuntu2.1 - ErrorMessage: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug + gcc-7-base 7.2.0-8ubuntu3.2 + libc6 2.26-0ubuntu2.1 + libgcc1 1:7.2.0-8ubuntu3.2 + libsysfs2 2.1.0+repack-4 + multiarch-support 2.26-0ubuntu2.1 + ErrorMessage: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug (post-installation script gave back error value 1) InstallationDate: Installed on 2018-02-18 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: - dpkg 1.18.24ubuntu1 - apt 1.5.1 + dpkg 1.18.24ubuntu1 + apt 1.5.1 SourcePackage: sysfsutils Title: package sysfsutils 2.1.0+repack-4 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1760294 Title: package sysfsutils 2.1.0+repack-4 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug Status in sysfsutils package in Ubuntu: New Bug description: I wanted to get my Wireless XBox One Controller to get to work, so I followed this guide: https://askubuntu.com/questions/783587/how-do-i-get-an-xbox-one-controller-to-work-with-16-04-not-steam#798254 But when installing sysfsutilsm I got this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: sysfsutils 2.1.0+repack-4 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libsysfs2:amd64: Install sysfsutils:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Mar 31 14:46:34 2018 Dependencies: gcc-7-base 7.2.0-8ubuntu3.2 libc6 2.26-0ubuntu2.1 libgcc1 1:7.2.0-8ubuntu3.2 libsysfs2 2.1.0+repack-4 multiarch-support 2.26-0ubuntu2.1 ErrorMess
[Desktop-packages] [Bug 1757280] [NEW] Night Light only on one Monitor
Public bug reported: Hi If I activate the Night Light mode with an external monitor connected, the mode is only on the external monitor activated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompositorRunning: None Date: Tue Mar 20 23:12:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) MachineType: LENOVO 20HF0016MZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF0016MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF0016MZ dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic reproducible ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1757280 Title: Night Light only on one Monitor Status in xorg package in Ubuntu: New Bug description: Hi If I activate the Night Light mode with an external monitor connected, the mode is only on the external monitor activated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompositorRunning: None Date: Tue Mar 20 23:12:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) MachineType: LENOVO 20HF0016MZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF0016MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF0016MZ dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sou
[Desktop-packages] [Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
For reference, a couple of users have been experiencing the same issue on HP ProLiant MicroServer Gen8, which use Matrox MGA G200EH, the original culprit that caused the module mgag200 to be excluded from the kernel years ago. https://community.hpe.com/t5/ProLiant-Servers-Netservers/HP-ProLiant- Gen8-with-Ubuntu-16-and-no-monitor-using-iLO-remote/m-p/6972709 In the linked topic, I put together a step-by-step walkthrough through installing the mgag200 module for Ubuntu or Ubuntu-based distros like Mint. Some users might find it helpful. Unfortunately, only one novice user tried this on HP Gen8 and apparently it did not work. I am not sure whether the mgag200 module just does not work with G200EH yet or whether there was some mistake made in the approach either by me or the user. It would be very helpful for someone to test this with this specific chip and report in more detail. -- 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/1316035 Title: matrox g200eR2 is unclaimed in 14.04 Status in xorg-server package in Ubuntu: Confirmed Bug description: On a certified Dell PowerEdge T620 server (http://www.ubuntu.com/certification/hardware/201207-11426/) The matrox video card is not recognised: lspci | grep VGA 0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 lshw -C display *-display UNCLAIMED description: VGA compatible controller product: G200eR2 vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:0a:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm vga_controller bus_master cap_list configuration: latency=64 maxlatency=32 mingnt=16 resources: memory:d800-d8ff memory:deffc000-deff memory:de00-de7f Thus xserver is not hardver accelerated. Also /dev/dri and /dev/dri/card0 is missing. kernel module mga is not loaded, although if i manually load by modprobe it works fine modprobe mga lsmod | grep mga mga40811 0 drm 302817 1 mga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+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 1453655] Re: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder
same problem with Ubuntu 17.04 (Zesty) : I had two installs : one upgrade from Ubuntu 16.04 and one clean install (next to existing windows 10 partition). The problem was not present with Ubuntu 16.04. In both installations the problem occurs : desktop icons disappear when dropbox folder is opened from system tray -- 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/1453655 Title: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Confirmed Status in nautilus source package in Vivid: Fix Released Status in nautilus source package in Wily: Fix Released Bug description: I've been using both Ubuntu and dropbox for several years. With Ubuntu 15.04 there is a new problem that my desktop icons disappear when I click on the dropbox icon in the status bar and choose Open Dropbox Folder. Then the desktop icons will disappear - but will remain visible in Files -> Desktop. The only way I know to get the desktop icons back is to log out and then log back in again. The bug is 100% reproducible, and it never appeared before 15.04. I also have Copy on my status bar. Clicking on Copy -> Open Copy Folder has no problems. Likewise I can use File with a right click and use Open a New Window and that too is OK. Only dropbox has a problem and only since 15.04 If I can help in any way, please contact me ilan.tal - at - gmail.com [Impact] DE-agnostic programs that invoke nautilus using "nautilus --no-desktop" will make the nautilus-rendered desktop vanish. Dropbox is one such case. [Test Case] 1. Launch nautilus, and make sure it is currently rendering the desktop. 2. Run "nautilus --no-desktop /" 3. See if the desktop vanishes. [Regression Potential] The patch is relatively trivial, only affecting the --no-desktop codepath. As a worst case, --no-desktop would not function correctly in cases where nautilus is not already running (--no-desktop when nautilus is not already running means nautilus should not render the desktop at all). Just to make sure, this additional test case should be used: 1. Kill nautilus, and make sure it doesn't get relaunched. 2. Check to see what the desktop looks like (shouldn't be rendered by nautilus, at least) 3. Launch "nautilus --no-desktop /" 4. Make sure that nautilus really doesn't render a desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1453655/+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 1693779] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: Crash ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri May 26 09:32:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (14 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1693779 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: Crash ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri May 26 09:32:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (14 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1693779/+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 1316035] Re: matrox g200eR2 is unclaimed in 14.04
Short version: kernel module driver "mgag200" did the trick for me. In kernel config, it is represented by CONFIG_DRM_MGAG200. http://cateee.net/lkddb/web-lkddb/DRM_MGAG200.html I found a bug that is relevant to this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642470 It says that the kernel module "mgag200" was blacklisted from kernels due to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 I tried manually compiling the driver as a module, adding it to a kernel and it worked. I had problems with MGA G200e [Pilot] ServerEngines (SEP1) card. I tried Zoltán's X.org regression hack, I also tried using a recompiled up-to- date mga_drv.so, the library in xserver-xorg-video-mga, where the maintainers claim to support G200e chip (https://cgit.freedesktop.org/xorg/driver/xf86-video-mga/, commits from July 2016). Nothing worked. I am, however, just an intermediate user, so I might have made a mistake somewhere. I also do not know the difference between a kernel driver, X.org driver, and how they interact together and how they are used. Therefore I will trust someone more knowledgeable to put this all together, and I am just going to describe what I did to make it work :-) As a reference, I did a fresh install of Linux Mint 18.1 MATE, where the GPU was unclaimed: $ uname -a Linux rack3test 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: MGA G200e [Pilot] ServerEngines (SEP1) vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:02:00.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:c200-c2ff memory:c101-c1013fff memory:c080-c0ff memory:c100-c100 Then I tried two approaches, both worked. 1. the easier way is to compile and install just the module mgag200. I downloaded the sources and headers for the current kernel, compiled and installed the module, and then added it in the initramfs image. Then, after reboot, it worked. Here are the resources I used: http://askubuntu.com/questions/168279/how-do-i-build-a-single-in-tree-kernel-module http://askubuntu.com/questions/676707/how-to-load-a-module-in-initrd In the first one, do not forget to use your kernel version and the path to the module (drivers/gpu/drm/mgag200). Also it is probably more convenient to use "$ make menuconfig" instead of editing the .config file with vi (you need the ncurses package though). In the menu, find Graphics Drivers --> Graphics Support --> Kernel modesetting driver for MGA G200 server engines, and enable it as a module. When updating initramfs, it might be necessary to specify the kernel version, for example $ update-initramfs -u -k 4.4.0-66-generic. If you have multiple kernels, the command will tell you which initramfs it updated. The result after a reboot: $ uname -a Linux rack3test 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -c display *-display description: VGA compatible controller product: MGA G200e [Pilot] ServerEngines (SEP1) vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:02:00.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=mgag200 latency=0 resources: irq:16 memory:c200-c2ff memory:c101-c1013fff memory:c080-c0ff memory:c100-c100 2. Second way is building a new kernel, which is much longer; unfortunately, I tried it first :-) I downloaded the current stable kernel sources from kernel.org, version 4.10.1. Then I used the existing kernel config file for 4.4.0-66-generic, updated it with default choices to 4.10.1 and enabled CONFIG_DRM_MGAG200 as a module. I compiled the whole kernel and installed it, the new driver "mgag200" loads automatically and it works. I used Linux Mint 18.1 for testing, but the installed system is Mint 17.2. I tried compiling the kernel module there for kernel version 3.16.0-38-generic, but after enabling module mgag200 with modprobe, the screen turned black and monitor went into sleep mode. I had to switch to tty1 and reboot. After reboot, the module mgag200 was visible in lsmod, but probably not active and the GPU was still unclaimed with no hardware acceleration. Maybe I did something wrong, but it is possible that the mgag200 module helps only with newer kernels. You can check whether your device is recognized by this driver in the first link in this comment. Numeric ID (vendor, device) can be displayed by running $ sudo lshw -c display -numeric, it will be in square brackets under "product". If anyone
[Desktop-packages] [Bug 1618364] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
Public bug reported: After upgrade from xenial to yakkety ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 09:34:31 2016 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2016-02-15 (196 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618364 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar Status in gconf package in Ubuntu: New Bug description: After upgrade from xenial to yakkety ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 09:34:31 2016 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2016-02-15 (196 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618364/+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 1203276] Re: cups-browsed memory usage unacceptable
Here is an upstream bug with a patch: https://bugs.linuxfoundation.org/show_bug.cgi?id=1365 However, it is for the current revision, so it will probably appear in 1.10.1 and I am not sure how to deliver this patch to the Ubuntu package cups-browsed 1.8.3-2ubuntu3. Basically, I don't know how packaging for Ubuntu works, and I couldn't find the source specific for 1.8.3-2ubuntu3. So, I took the source of 1.8.3, patched it and attached is a diff file. ** Bug watch added: bugs.linuxfoundation.org/ #1365 https://bugs.linuxfoundation.org/show_bug.cgi?id=1365 ** Patch added: "bugfix1203276_1.8.3_launchpad.diff" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1203276/+attachment/4705343/+files/bugfix1203276_1.8.3_launchpad.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1203276 Title: cups-browsed memory usage unacceptable Status in cups-filters package in Ubuntu: Incomplete Status in cups-filters package in Debian: Fix Released Status in cups-filters package in Fedora: Unknown Bug description: cups-browsed uses a lot of memory: % ps u 1886 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1886 0.0 10.9 1433812 851028 ? Ss Jul11 2:05 /usr/sbin/cups-browsed I'm about to uninstall it, but I figured I should report the problem first. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups-browsed 1.0.34-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CupsErrorLog: W [20/Jul/2013:07:55:27 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'C821-Gray..' already exists W [20/Jul/2013:07:55:27 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'C821-RGB..' already exists W [20/Jul/2013:07:55:27 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_LaserJet_3020-Gray..' already exists W [20/Jul/2013:07:55:27 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'MB470-Gray..' already exists Date: Sat Jul 20 12:01:40 2013 InstallationDate: Installed on 2013-06-10 (40 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Lpstat: device for C821: dnssd://OKILondon._pdl-datastream._tcp.local/ device for HP_LaserJet_3020: ipp://olive.local:631/printers/hp_LaserJet_3020 device for MB470: dnssd://OKIMFD._pdl-datastream._tcp.local/ MachineType: LENOVO 34607ZG MarkForUpload: True Papersize: a4 PpdFiles: MB470: OKI MB470(PS) C821: Oki C710 Foomatic/Postscript (recommended) HP_LaserJet_3020: HP LaserJet 3020 3030 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-26-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 34607ZG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET90WW(2.50):bd12/26/2012:svnLENOVO:pn34607ZG:pvrThinkPadX1Carbon:rvnLENOVO:rn34607ZG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34607ZG dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1203276/+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 1490298] Re: Lowercase months in Portuguese language
I think the bug is fixed in: https://sourceware.org/bugzilla/show_bug.cgi?id=19133 -- 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/1490298 Title: Lowercase months in Portuguese language Status in GLibC: Unknown Status in langpack-locales package in Ubuntu: New Bug description: Hi, Due to some modifications made to our mother language back in 2012. The months passed to be written with lowercase. Example: Quarta-feira, 29 de Julho de 2015 (before 2012) quarta-feira, 29 de julho de 2015 (since 2012) Where we can (translator community) fix this? We've been searching, but we can't deal with it. This is one bug we can't fix or solve for the ubuntu touch. Please, gives us some additional information on this subject. Thanks! Ivo Xavier - Ubuntu Portuguese Translators To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1490298/+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 1512520] [NEW] New upstream release wpa 2.5
Public bug reported: Upstream release 2.5 has come out recently, including a number of security bugfixes and additional channel selection and performance improvements to 5GHz networks. Please update to it :) Changelog: 2015-09-27 - v2.5 * fixed P2P validation of SSID element length before copying it [http://w1.fi/security/2015-1/] (CVE-2015-1863) * fixed WPS UPnP vulnerability with HTTP chunked transfer encoding [http://w1.fi/security/2015-2/] (CVE-2015-4141) * fixed WMM Action frame parser (AP mode) [http://w1.fi/security/2015-3/] (CVE-2015-4142) * fixed EAP-pwd peer missing payload length validation [http://w1.fi/security/2015-4/] (CVE-2015-4143, CVE-2015-4144, CVE-2015-4145, CVE-2015-4146) * fixed validation of WPS and P2P NFC NDEF record payload length [http://w1.fi/security/2015-5/] * nl80211: - added VHT configuration for IBSS - fixed vendor command handling to check OUI properly - allow driver-based roaming to change ESS * added AVG_BEACON_RSSI to SIGNAL_POLL output * wpa_cli: added tab completion for number of commands * removed unmaintained and not yet completed SChannel/CryptoAPI support * modified Extended Capabilities element use in Probe Request frames to include all cases if any of the values are non-zero * added support for dynamically creating/removing a virtual interface with interface_add/interface_remove * added support for hashed password (NtHash) in EAP-pwd peer * added support for memory-only PSK/passphrase (mem_only_psk=1 and CTRL-REQ/RSP-PSK_PASSPHRASE) * P2P - optimize scan frequencies list when re-joining a persistent group - fixed number of sequences with nl80211 P2P Device interface - added operating class 125 for P2P use cases (this allows 5 GHz channels 161 and 169 to be used if they are enabled in the current regulatory domain) - number of fixes to P2PS functionality - do not allow 40 MHz co-ex PRI/SEC switch to force MCC - extended support for preferred channel listing * D-Bus: - fixed WPS property of fi.w1.wpa_supplicant1.BSS interface - fixed PresenceRequest to use group interface - added new signals: FindStopped, WPS pbc-overlap, GroupFormationFailure, WPS timeout, InvitationReceived - added new methods: WPS Cancel, P2P Cancel, Reconnect, RemoveClient - added manufacturer info * added EAP-EKE peer support for deriving Session-Id * added wps_priority configuration parameter to set the default priority for all network profiles added by WPS * added support to request a scan with specific SSIDs with the SCAN command (optional "ssid " arguments) * removed support for WEP40/WEP104 as a group cipher with WPA/WPA2 * fixed SAE group selection in an error case * modified SAE routines to be more robust and PWE generation to be stronger against timing attacks * added support for Brainpool Elliptic Curves with SAE * added support for CCMP-256 and GCMP-256 as group ciphers with FT * fixed BSS selection based on estimated throughput * added option to disable TLSv1.0 with OpenSSL (phase1="tls_disable_tlsv1_0=1") * added Fast Session Transfer (FST) module * fixed OpenSSL PKCS#12 extra certificate handling * fixed key derivation for Suite B 192-bit AKM (this breaks compatibility with the earlier version) * added RSN IE to Mesh Peering Open/Confirm frames * number of small fixes ** Affects: wpa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1512520 Title: New upstream release wpa 2.5 Status in wpa package in Ubuntu: New Bug description: Upstream release 2.5 has come out recently, including a number of security bugfixes and additional channel selection and performance improvements to 5GHz networks. Please update to it :) Changelog: 2015-09-27 - v2.5 * fixed P2P validation of SSID element length before copying it [http://w1.fi/security/2015-1/] (CVE-2015-1863) * fixed WPS UPnP vulnerability with HTTP chunked transfer encoding [http://w1.fi/security/2015-2/] (CVE-2015-4141) * fixed WMM Action frame parser (AP mode) [http://w1.fi/security/2015-3/] (CVE-2015-4142) * fixed EAP-pwd peer missing payload length validation [http://w1.fi/security/2015-4/] (CVE-2015-4143, CVE-2015-4144, CVE-2015-4145, CVE-2015-4146) * fixed validation of WPS and P2P NFC NDEF record payload length
[Desktop-packages] [Bug 1475633] Re: New upstream version 2.4 / please merge with Debian 8's wpa 2.3
Thanks for the answer. Upstream has since released wpa 2.5 which includes those patches so I'll open a new request asking for that version instead of the backport. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1475633 Title: New upstream version 2.4 / please merge with Debian 8's wpa 2.3 Status in wpa package in Ubuntu: Fix Released Bug description: There are new wpa_supplicant versions 2.2, 2.3 and 2.4 which bring a horde of improvements to eg WiFi Direct (P2P) and others: http://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog The 2.3 is already part of the stable Debian 8.0 release so it would be useful to sync with at least that for 15.10 (and 16.04 LTS). --- Debian stable changelog --- wpa (2.3-1+deb8u1) jessie-security; urgency=high . * import "P2P: Validate SSID element length before copying it (CVE-2015-1863)" from upstream (Closes: #783148). wpa (2.3-1) unstable; urgency=medium . * New upstream release: - fixed by the new upstream version: + wpa: arbitrary command execution via action scripts (Closes: #765352). wpasupplicant: fixed wpa_cli action script execution to use more robust mechanism (CVE-2014-3686). hostapd: fixed hostapd_cli action script execution to use more robust mechanism (CVE-2014-3686). + wpasupplicant: MAC addressing changing broken after updating to 2.2-1 (Closes: #763775). + drop ap_config_c_fix-typo-for-capabilities, applied upstream. - backport "Include ieee802_11_common.c in wpa_supplicant build unconditionally" from HEAD, to fix a newly introduced FTBS on, at least, kfreebsd. * bump standards version to 3.9.6, no changes necessary. wpa (2.2-1) unstable; urgency=medium . * New upstream release: - import suggested changes from Gerald Turner (see #718651 for details). + disable ACS for hostapd on kfreebsd-any (FTBS). - fixed by the new upstream version: + wpa_supplicant: OpenSSL: tls_connection_handshake - Failed to read (Closes: #561081). + wpasupplicant: new upstream release 2.2 (Closes: #718651). + wpasupplicant: -s option not documented in man page (Closes: #608135). - refresh patches: + drop 13_human_readable_signal.patch, applied upstream. + drop hostapd_fix-WDS-VLAN-bridge-handling.patch, applied upstream. + drop fix-spelling-s-algorith-algorithm.patch, applied upstream. - adapt build configs for hostapd/ wpa_supplicant 2.2: + sync with updated upstream defconfigs. + keep Hotspot 2.0 support disabled for the time being. + hostapd: keep sqlite3 support disabled for the time being. - update debian/copyright manually, the wpa v2 branch was relicensed from (BSD-3-clause || GPL-2) to BSD-3-clause only (for the most part). This doesn't change the licensing state as the BSD-3-clause license is compatible with GPL-2. * drop pre-wheezy /lib/init/rw/sendsigs.omit.d/ migration support, invert the versioned initscripts dependency to a versioned breaks relation. * migrate from /var/run/ to /run/. * adapt get-orig-source for wpa 2.2. * drop version qualifiers for libnl3 build dependencies, as they're fullfilled by wheezy. * drop version qualifiers for the lsb-base build dependency, as they're fullfilled by squeeze. * shorten short description for hostapd. * sort debian/control entries. * make lintian happy (invalid-short-name-in-dep5-copyright bsd) and call it BSD-3-clause. * enable DEBUG_SYSLOG and set DEBUG_SYSLOG_FACILITY=LOG_DAEMON, as requested by Cyril Brulebois to improve logging options for d-i and netcfg (Closes: #761922). * fix various typos around "existence", thanks to A. Costa , (Closes: #683636). * ap_config.c: fix typo for "capabilities". * remove no longer required lintian override (spelling-error-in-binary for the). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1475633/+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 1490298] Re: Lowercase months in Portuguese language
I've already opened it : https://sourceware.org/bugzilla/show_bug.cgi?id=19133 ** Bug watch added: Sourceware.org Bugzilla #19133 http://sourceware.org/bugzilla/show_bug.cgi?id=19133 -- 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/1490298 Title: Lowercase months in Portuguese language Status in langpack-locales package in Ubuntu: New Bug description: Hi, Due to some modifications made to our mother language back in 2012. The months passed to be written with lowercase. Example: Quarta-feira, 29 de Julho de 2015 (before 2012) quarta-feira, 29 de julho de 2015 (since 2012) Where we can (translator community) fix this? We've been searching, but we can't deal with it. This is one bug we can't fix or solve for the ubuntu touch. Please, gives us some additional information on this subject. Thanks! Ivo Xavier - Ubuntu Portuguese Translators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1490298/+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 1475633] Re: New upstream version 2.4 / please merge with Debian 8's wpa 2.3
The current wpa version in debian testing includes the 5GHz band selection improvements patch backports: https://packages.qa.debian.org/w/wpa/news/20150906T154058Z.html Would it be possible to also include these patches? As far as I've checked, they were not included in the ubuntu 2.4 version. (And you would be my best friend forever ;D) Or should I open a separate feature request asking for those patches? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1475633 Title: New upstream version 2.4 / please merge with Debian 8's wpa 2.3 Status in wpa package in Ubuntu: Fix Released Bug description: There are new wpa_supplicant versions 2.2, 2.3 and 2.4 which bring a horde of improvements to eg WiFi Direct (P2P) and others: http://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog The 2.3 is already part of the stable Debian 8.0 release so it would be useful to sync with at least that for 15.10 (and 16.04 LTS). --- Debian stable changelog --- wpa (2.3-1+deb8u1) jessie-security; urgency=high . * import "P2P: Validate SSID element length before copying it (CVE-2015-1863)" from upstream (Closes: #783148). wpa (2.3-1) unstable; urgency=medium . * New upstream release: - fixed by the new upstream version: + wpa: arbitrary command execution via action scripts (Closes: #765352). wpasupplicant: fixed wpa_cli action script execution to use more robust mechanism (CVE-2014-3686). hostapd: fixed hostapd_cli action script execution to use more robust mechanism (CVE-2014-3686). + wpasupplicant: MAC addressing changing broken after updating to 2.2-1 (Closes: #763775). + drop ap_config_c_fix-typo-for-capabilities, applied upstream. - backport "Include ieee802_11_common.c in wpa_supplicant build unconditionally" from HEAD, to fix a newly introduced FTBS on, at least, kfreebsd. * bump standards version to 3.9.6, no changes necessary. wpa (2.2-1) unstable; urgency=medium . * New upstream release: - import suggested changes from Gerald Turner (see #718651 for details). + disable ACS for hostapd on kfreebsd-any (FTBS). - fixed by the new upstream version: + wpa_supplicant: OpenSSL: tls_connection_handshake - Failed to read (Closes: #561081). + wpasupplicant: new upstream release 2.2 (Closes: #718651). + wpasupplicant: -s option not documented in man page (Closes: #608135). - refresh patches: + drop 13_human_readable_signal.patch, applied upstream. + drop hostapd_fix-WDS-VLAN-bridge-handling.patch, applied upstream. + drop fix-spelling-s-algorith-algorithm.patch, applied upstream. - adapt build configs for hostapd/ wpa_supplicant 2.2: + sync with updated upstream defconfigs. + keep Hotspot 2.0 support disabled for the time being. + hostapd: keep sqlite3 support disabled for the time being. - update debian/copyright manually, the wpa v2 branch was relicensed from (BSD-3-clause || GPL-2) to BSD-3-clause only (for the most part). This doesn't change the licensing state as the BSD-3-clause license is compatible with GPL-2. * drop pre-wheezy /lib/init/rw/sendsigs.omit.d/ migration support, invert the versioned initscripts dependency to a versioned breaks relation. * migrate from /var/run/ to /run/. * adapt get-orig-source for wpa 2.2. * drop version qualifiers for libnl3 build dependencies, as they're fullfilled by wheezy. * drop version qualifiers for the lsb-base build dependency, as they're fullfilled by squeeze. * shorten short description for hostapd. * sort debian/control entries. * make lintian happy (invalid-short-name-in-dep5-copyright bsd) and call it BSD-3-clause. * enable DEBUG_SYSLOG and set DEBUG_SYSLOG_FACILITY=LOG_DAEMON, as requested by Cyril Brulebois to improve logging options for d-i and netcfg (Closes: #761922). * fix various typos around "existence", thanks to A. Costa , (Closes: #683636). * ap_config.c: fix typo for "capabilities". * remove no longer required lintian override (spelling-error-in-binary for the). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1475633/+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 1475633] Re: New upstream version 2.4 / please merge with Debian 8's wpa 2.3
It would be awesome to watch closely for the new version including the 5GHz improvements: http://blog.sesse.net/blog/tech/2015-07-14-21-25_wpa_supplicant_5ghz_improvements.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1475633 Title: New upstream version 2.4 / please merge with Debian 8's wpa 2.3 Status in wpa package in Ubuntu: Confirmed Bug description: There are new wpa_supplicant versions 2.2, 2.3 and 2.4 which bring a horde of improvements to eg WiFi Direct (P2P) and others: http://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog The 2.3 is already part of the stable Debian 8.0 release so it would be useful to sync with at least that for 15.10 (and 16.04 LTS). --- Debian stable changelog --- wpa (2.3-1+deb8u1) jessie-security; urgency=high . * import "P2P: Validate SSID element length before copying it (CVE-2015-1863)" from upstream (Closes: #783148). wpa (2.3-1) unstable; urgency=medium . * New upstream release: - fixed by the new upstream version: + wpa: arbitrary command execution via action scripts (Closes: #765352). wpasupplicant: fixed wpa_cli action script execution to use more robust mechanism (CVE-2014-3686). hostapd: fixed hostapd_cli action script execution to use more robust mechanism (CVE-2014-3686). + wpasupplicant: MAC addressing changing broken after updating to 2.2-1 (Closes: #763775). + drop ap_config_c_fix-typo-for-capabilities, applied upstream. - backport "Include ieee802_11_common.c in wpa_supplicant build unconditionally" from HEAD, to fix a newly introduced FTBS on, at least, kfreebsd. * bump standards version to 3.9.6, no changes necessary. wpa (2.2-1) unstable; urgency=medium . * New upstream release: - import suggested changes from Gerald Turner (see #718651 for details). + disable ACS for hostapd on kfreebsd-any (FTBS). - fixed by the new upstream version: + wpa_supplicant: OpenSSL: tls_connection_handshake - Failed to read (Closes: #561081). + wpasupplicant: new upstream release 2.2 (Closes: #718651). + wpasupplicant: -s option not documented in man page (Closes: #608135). - refresh patches: + drop 13_human_readable_signal.patch, applied upstream. + drop hostapd_fix-WDS-VLAN-bridge-handling.patch, applied upstream. + drop fix-spelling-s-algorith-algorithm.patch, applied upstream. - adapt build configs for hostapd/ wpa_supplicant 2.2: + sync with updated upstream defconfigs. + keep Hotspot 2.0 support disabled for the time being. + hostapd: keep sqlite3 support disabled for the time being. - update debian/copyright manually, the wpa v2 branch was relicensed from (BSD-3-clause || GPL-2) to BSD-3-clause only (for the most part). This doesn't change the licensing state as the BSD-3-clause license is compatible with GPL-2. * drop pre-wheezy /lib/init/rw/sendsigs.omit.d/ migration support, invert the versioned initscripts dependency to a versioned breaks relation. * migrate from /var/run/ to /run/. * adapt get-orig-source for wpa 2.2. * drop version qualifiers for libnl3 build dependencies, as they're fullfilled by wheezy. * drop version qualifiers for the lsb-base build dependency, as they're fullfilled by squeeze. * shorten short description for hostapd. * sort debian/control entries. * make lintian happy (invalid-short-name-in-dep5-copyright bsd) and call it BSD-3-clause. * enable DEBUG_SYSLOG and set DEBUG_SYSLOG_FACILITY=LOG_DAEMON, as requested by Cyril Brulebois to improve logging options for d-i and netcfg (Closes: #761922). * fix various typos around "existence", thanks to A. Costa , (Closes: #683636). * ap_config.c: fix typo for "capabilities". * remove no longer required lintian override (spelling-error-in-binary for the). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1475633/+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 998489] Re: Fn+F11 does not control Ambient Light Sensor on HP 8560W
The same on Ubuntu 14.04 with the Elitebook 8440p. Setting /sys/devices/platform/hp-wmi/als to 1 worked for me too. Thank you a lot, no sunshine in my face experience anymore after boot. Only the function key still doesn't work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/998489 Title: Fn+F11 does not control Ambient Light Sensor on HP 8560W Status in xserver-xorg-input-evdev package in Ubuntu: Confirmed Bug description: Ubuntu 12.04 LTS with Gnome Classic tries to disable touchpad (at least it displays that image in top right corner). But actually seems nothing happens at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/998489/+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 1445134] Re: Network manager never scanning for new access points
I'm seeing this as well: after upgrading to 15.04, I sometimes don't get automatically connected to my default network, because it hasn't been found yet. A manual 'sudo iwlist scan' is needed to get it to find the network, upon which it does automatically connect. I installed a fresh copy of 15.04, retaining my home partition. /etc is entirely fresh -- 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/1445134 Title: Network manager never scanning for new access points Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+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 1424372] [NEW] Compiz reset required after downgrading
Public bug reported: After downgrading to nvidia-current-upgrades in 14.10, I was faced with the issue reported e.g. here [1]: no unity, launcher or dash. Fix 5 in this [2] answer to that question solved the problem for me: sudo dconf reset -f /org/compiz/ However, the fact that that was necessary is probably a bug. [1] http://askubuntu.com/questions/449845/problems-after-upgrading-to-14-04-only-background-and-pointer-after-login [2] http://askubuntu.com/a/481620/28943 ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1424372 Title: Compiz reset required after downgrading Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: After downgrading to nvidia-current-upgrades in 14.10, I was faced with the issue reported e.g. here [1]: no unity, launcher or dash. Fix 5 in this [2] answer to that question solved the problem for me: sudo dconf reset -f /org/compiz/ However, the fact that that was necessary is probably a bug. [1] http://askubuntu.com/questions/449845/problems-after-upgrading-to-14-04-only-background-and-pointer-after-login [2] http://askubuntu.com/a/481620/28943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1424372/+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 531208]
+1 thank you Ruslan. I'm guessing that at this point we should be asking for this to be implemented on Wayland, as it seems that X will be deprecated soon enough and its input code is complex and strange enough (no screensaver when a pop-up menu is open, for instance) that this won't make it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/531208 Title: Need way to insert arbitrary unicode characters in Kubuntu Status in X.Org X server: Confirmed Status in xorg package in Ubuntu: Won't Fix Bug description: KDE, Qt, and Xorg are in disagreement about who should implement ISO 14755, which would facilitate the input of arbitrary unicode characters. This is the original KDE bug: https://bugs.kde.org/show_bug.cgi?id=103788 It was pushed upstream to Qt: http://bugreports.qt.nokia.com/browse/QTBUG-8 From there it was pushed further upstream to Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=26747 Xorg pushes the bug downstream, back to either Qt or KDE to implement, just as Gnome implemented the fix themselves. An Xorg developer who does not want to be named says that if KDE won't implement it then my distro should. So here I file that request. Note that in KDE 3 one could use the Kcharselect applet to enter arbitrary unicode characters, however that has been disabled in KDE 4: https://bugs.kde.org/show_bug.cgi?id=190776 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/531208/+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 1402974] Re: Error! Bad return status for module build on kernel: 3.13.0-43-generic
After reboot everything seems normal, despite the dkms error (see build log). The additional drivers screen in Software & Updates shows that nvidia 331.113 from nvidia-331 (proprietary, tested) is in use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1402974 Title: Error! Bad return status for module build on kernel: 3.13.0-43-generic Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: I'm not sure about this bug, I just did a dist-upgrade to upgrade the kernel from 3.13.0-41 to 3.13.0-43 in the terminal window, and the bug-report window popped up. I looked in the terminal to find the error message: Error! Bad return status for module build on kernel: 3.13.0-43-generic Consult /var/lib/dkms/nvidia-331/331.113/build/make.log for more information However, that file does not exist anymore. Since I'm not sure whether nvidia built correctly in the latest kernel, I'll try to reboot to the -43 kernel. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-43-generic Date: Tue Dec 16 09:19:00 2014 InstallationDate: Installed on 2014-01-27 (322 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-06-05 (193 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1402974/+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 1402974] [NEW] Error! Bad return status for module build on kernel: 3.13.0-43-generic
Public bug reported: I'm not sure about this bug, I just did a dist-upgrade to upgrade the kernel from 3.13.0-41 to 3.13.0-43 in the terminal window, and the bug- report window popped up. I looked in the terminal to find the error message: Error! Bad return status for module build on kernel: 3.13.0-43-generic Consult /var/lib/dkms/nvidia-331/331.113/build/make.log for more information However, that file does not exist anymore. Since I'm not sure whether nvidia built correctly in the latest kernel, I'll try to reboot to the -43 kernel. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-43-generic Date: Tue Dec 16 09:19:00 2014 InstallationDate: Installed on 2014-01-27 (322 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-06-05 (193 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1402974 Title: Error! Bad return status for module build on kernel: 3.13.0-43-generic Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: I'm not sure about this bug, I just did a dist-upgrade to upgrade the kernel from 3.13.0-41 to 3.13.0-43 in the terminal window, and the bug-report window popped up. I looked in the terminal to find the error message: Error! Bad return status for module build on kernel: 3.13.0-43-generic Consult /var/lib/dkms/nvidia-331/331.113/build/make.log for more information However, that file does not exist anymore. Since I'm not sure whether nvidia built correctly in the latest kernel, I'll try to reboot to the -43 kernel. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-43-generic Date: Tue Dec 16 09:19:00 2014 InstallationDate: Installed on 2014-01-27 (322 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-06-05 (193 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1402974/+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 1299604] Re: evolution keeps asking for password
Started to have this problem today. Following directions found here, I was able to solve it. It was as simple as opening Seahorse, goin to "Login" section and deleting all entries like "Evolution Data Source ..." - all of this with Evolution closed, of course. Started Evo afterwards and it asked for the passwrod one more time. After that, no more problem. Hope it helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1299604 Title: evolution keeps asking for password Status in “evolution” package in Ubuntu: Confirmed Bug description: Hi, I have connected my evolution to mail server (imap) and it asks EVERY time after login for password to that email account. It do not remember it, even when I tick "remember using keyring". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 23:00:38 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1299604/+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 1365695] Re: No longer able to use GUI after update
OK, I upgraded to ubuntu-drivers-common 0.2.91.7 to reproduce the original problem and then installed xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2~ppa1, which resolves the issue. Great, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Confirmed Status in “ubuntu-drivers-common” source package in Trusty: Triaged Status in “xserver-xorg-video-intel” source package in Trusty: Incomplete Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1365695] Re: No longer able to use GUI after update
I'm not clear on the version of ubuntu-drivers-common that I should test it with. I'm currently up-to-date with 14.04, except for ubuntu-drivers- common, which I've locked at 0.2.91.4. The latest available version is 0.2.91.7. Should I test the xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2~ppa1 from ppa:canonical-x/x-staging against that version? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Confirmed Status in “ubuntu-drivers-common” source package in Trusty: Triaged Status in “xserver-xorg-video-intel” source package in Trusty: Incomplete Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1365695] Re: No longer able to use GUI after update
My experience is slightly different from Fabio's. For me ubuntu-drivers- common 1:0.2.91.4 and 1:0.2.91.5 work, while 1:0.2.91.6 and 1:0.2.91.7 don't. I only changed ubuntu-drivers-common between reboots and never needed to reinstall the nvidia (331-updates) drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Confirmed Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1365695] Re: No longer able to use GUI after update
** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: New Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1101767] Re: Mouse buttons not inverted on initial login
** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Invalid -- 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/1101767 Title: Mouse buttons not inverted on initial login Status in “gnome-settings-daemon” package in Ubuntu: Invalid Bug description: I am experiencing a bug where on first login to an Ubuntu/Unity session (12.04), my mouse buttons are not inverted (left-handed). The configuration does correctly list them as inverted, but they don't behave that way. If I log out and login again, they behave correctly, as per the configuration. It worked correctly for the longest time and only recently (a few weeks ago) started misbehaving. --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True NonfreeKernelModules: nvidia Package: gnome-settings-daemon 3.4.2-0ubuntu0.6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-28 (266 days ago) UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1101767/+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 1365695] [NEW] No longer able to use GUI after update
Public bug reported: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi- monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi- - monitor behavior. Yesterday the set of packages below [1] was updated - and after that I was no longer shown the lightdm login screen: I'm stuck - at the purple screen that precedes it (into which I enter my disk - encryption password). + monitor behavior. Yesterday the set of packages below [1] was updated. I + shut down, booted this morning and found out that I was not shown the + lightdm login screen: I was stuck at the purple screen that precedes it + (into which I enter my disk encryption password). - Now the funny thing is that I hear the lightdm startup sound and can - actually login by typing my password (disk actcivity and started + Now the funny thing is that I could hear the lightdm startup sound and + could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: * .xsession-errors reported 'Xlib: extension "GLX" missing on display
[Desktop-packages] [Bug 1311697] Re: HP Officejet Pro K550 should use hpijs by default
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1311697 Title: HP Officejet Pro K550 should use hpijs by default Status in “hplip” package in Ubuntu: Fix Released Status in “hplip” source package in Trusty: Fix Committed Bug description: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. [Impact] Users of the HP Officejet Pro K550 are not able to print with the automatic printer setup in Ubuntu. [Test Case] Plug an HP Officejet Pro K550 to the USB and wait for a print queue getting auto-generated. If you have an HP Officejet Pro K550 on the network, open system-config-printer, click on "new Printer", and select the HP Officejet Pro K550 under the printers discovered in the network. Follow the steps of the wizard to complete the setup. With the current version of HPLIP you will get a non-working queue with the hpcups driver, due to a bug in the driver which HP does not fix any more as the printer is too old. To get it working with the proposed fix, after installing it, remove your queue(s) for the HP Officejet Pro K550 and create a new queue for it. Now the queue will use the hpijs driver which makes this printer correctly working. [Regression Potential] Very low, as there is nothing more done than removing the hpcups support for the HP Officejet Pro K550. All other printers should work exactly as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1311697/+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 1311697] Re: HP Officejet Pro K550 should use hpijs by default
I successfully tested hplip/3.14.3-0ubuntu3.2 and it fixes my issue. Thanks a lot! --- To test: I removed all printers from my system, and then added the printer again (with the system-config-printer menu) with the old version, and hpcups was selected. I then removed the printer again, upgraded to the new package, and proceeded to add the printer, and now hpijs hpijs was successfully selected. I printed the test page and it worked with no issues. --- Finally, I don't know if there is interested in having this backported to 12.04 LTS, but I still have some machines running it, so I'm willing to test there too, if needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1311697 Title: HP Officejet Pro K550 should use hpijs by default Status in “hplip” package in Ubuntu: Fix Released Status in “hplip” source package in Trusty: Fix Committed Bug description: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. [Impact] Users of the HP Officejet Pro K550 are not able to print with the automatic printer setup in Ubuntu. [Test Case] Plug an HP Officejet Pro K550 to the USB and wait for a print queue getting auto-generated. If you have an HP Officejet Pro K550 on the network, open system-config-printer, click on "new Printer", and select the HP Officejet Pro K550 under the printers discovered in the network. Follow the steps of the wizard to complete the setup. With the current version of HPLIP you will get a non-working queue with the hpcups driver, due to a bug in the driver which HP does not fix any more as the printer is too old. To get it working with the proposed fix, after installing it, remove your queue(s) for the HP Officejet Pro K550 and create a new queue for it. Now the queue will use the hpijs driver which makes this printer correctly working. [Regression Potential] Very low, as there is nothing more done than removing the hpcups support for the HP Officejet Pro K550. All other printers should work exactly as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1311697/+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 1311697] Re: HP Officejet Pro K550 should use hpijs by default
Thanks, I'll test as soon as it is posted! :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1311697 Title: HP Officejet Pro K550 should use hpijs by default Status in “hplip” package in Ubuntu: Fix Released Status in “hplip” source package in Trusty: Fix Committed Bug description: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. [Impact] Users of the HP Officejet Pro K550 are not able to print with the automatic printer setup in Ubuntu. [Test Case] Plug an HP Officejet Pro K550 to the USB and wait for a print queue getting auto-generated. If you have an HP Officejet Pro K550 on the network, open system-config-printer, click on "new Printer", and select the HP Officejet Pro K550 under the printers discovered in the network. Follow the steps of the wizard to complete the setup. With the current version of HPLIP you will get a non-working queue with the hpcups driver, due to a bug in the driver which HP does not fix any more as the printer is too old. To get it working with the proposed fix, after installing it, remove your queue(s) for the HP Officejet Pro K550 and create a new queue for it. Now the queue will use the hpijs driver which makes this printer correctly working. [Regression Potential] Very low, as there is nothing more done than removing the hpcups support for the HP Officejet Pro K550. All other printers should work exactly as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1311697/+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 1311697] Re: HP Officejet Pro K550 should use hpijs by default
Can this please be backported to at least Ubuntu 14.04? Otherwise users will be afected by this issue for years to come. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1311697 Title: HP Officejet Pro K550 should use hpijs by default Status in “hplip” package in Ubuntu: Fix Released Bug description: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1311697/+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 1309535] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so
i've seen this error also, but because i was not able to login with lightdm anymore. i have an encrypted home and changed my password in the shel. so it seems like having different passwords for the system and the encryptedfs does not work. after changing back my system password i was able to log in again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1309535 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so Status in “lightdm” package in Ubuntu: Confirmed Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+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 1311697] [NEW] HP Officejet Pro K550 should use hpijs by default
Public bug reported: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1311697 Title: HP Officejet Pro K550 should use hpijs by default Status in “cups” package in Ubuntu: New Bug description: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1311697/+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 981473] Re: HP Officejet Pro K550 fails to print in Ubuntu
Ok so recently I got surprised by this issue. Unfortunately it is not fixed in 13.10 and I don't believe it will be in 14.04 either. The "changing driver" workaround did work for me. The strange thing was, I installed the latest HP drivers on windows xp and I got the exact same behavior! And also none of HP's troubleshooting tools were able to help. Only by a lot of googling did I have the luck of stumbling onto this bug report. So I'm guessing that since this printer is old it's not really tested anymore, and the technical documentation that is used by both the windows and hplip teams is wrong. I have a normal K550 and a K550dtn and would like to see this fixed. I can setup a machine with remote access to both, and am willing to try debug builds of hplip, so if you're interested please say so. Finally, this Bug #879667 seems to be a dupe of this one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/981473 Title: HP Officejet Pro K550 fails to print in Ubuntu Status in HP Linux Imaging and Printing: Confirmed Status in “hplip” package in Ubuntu: Confirmed Bug description: I am having an issue with an Officejet Pro K550: 1) Issue started under Ubuntu 11.04 2) Under Ubuntu 10.10 on same laptop printer work's fine 3) Currently running latest hplip updates under 12.04 4) And I have HP Device Manager installed and working. When attempting to print or run a test print - job starts and always gets an inch or two down the page and then stops. Error code in HP Device Manager is always 5012 - Device Communication Error. I upgrade to hplip 3.12.4 and same things still happend. I have never logged a bug under Launchpad before but I can follow technical instructions if laid out clearly. Looking forward to a response. Update: Also happens in 12.10 and 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/981473/+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 471457] Re: Shutdown does not have priority over suspend/hibernation
Reported as a logind issue: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1311648 -- 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/471457 Title: Shutdown does not have priority over suspend/hibernation Status in “gnome-power-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: New Status in “upower” package in Ubuntu: New Bug description: When shutting down a laptop, if one closes the lid just after clicking shut down, the laptop may go to suspend/hibernation mode instead of shutting down. This is especially annoying since when recovering from suspend/hibernation, then the laptop continue the shut down process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/471457/+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 1294762] Re: Blur effect on whole screen
Can confirm that turning Anti-Aliasing off fixes the problem, thanks Andrzej! If I can be of help by by giving some log information, please let me now! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1294762 Title: Blur effect on whole screen Status in Compiz: New Status in NVIDIA Drivers Ubuntu: New Status in “compiz” package in Ubuntu: Triaged Bug description: Using Ubuntu 14.04, Compiz seems to apply a blur effect on the whole screen. Fresh updated display areas get transitional blurrier. Behavior applies to the Unity Desktop and all desktop apps like Chrome, the Terminal, Steam Client but not on OpenGL games or Flash content and affects window borders, texts, images and all UI elements except the mouse cursor. -> see attachment Nvidia proprietary drivers are in use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140310-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 19 18:05:00 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed bbswitch, 0.7, 3.13.0-18-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 250M] [10de:0ca9] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-03-16 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316) MachineType: TOSHIBA QOSMIO X500 PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=ba85cdbb-19f2-40d5-85d3-b6f5a031d224 ro nomodeset quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.90 dmi.board.name: QOSMIO X500 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.90:bd12/10/2010:svnTOSHIBA:pnQOSMIOX500:pvrPQX33E-015009GR:rvnTOSHIBA:rnQOSMIOX500:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: QOSMIO X500 dmi.product.version: PQX33E-015009GR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 19 16:49:11 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294762/+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 471457] Re: Shutdown does not have priority over suspend/hibernation
As an update, I never saw this issue again, so indeed it seems it is caused by a race in logind. -- 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/471457 Title: Shutdown does not have priority over suspend/hibernation Status in “gnome-power-manager” package in Ubuntu: Confirmed Status in “upower” package in Ubuntu: New Bug description: When shutting down a laptop, if one closes the lid just after clicking shut down, the laptop may go to suspend/hibernation mode instead of shutting down. This is especially annoying since when recovering from suspend/hibernation, then the laptop continue the shut down process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/471457/+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 471457] Re: Shutdown does not have priority over suspend/hibernation
Just made a clean install of Ubuntu saucy and this started happening to me sometimes. I believe the issue happens due to systemd-logind, which is set to always standby a laptop when you close the lid, and the supposed solution can be found here: http://askubuntu.com/questions/360615 /ubuntu-server-13-10-now-goes-to-sleep-when-closing-laptop-lid (the HandleLidSwitch=ignore option). Because this doesn't happen always I can't be 100% sure; I'm running with that option set for a few days, and if the issue never happens to me again I'll report this as a systemd-logind bug. -- 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/471457 Title: Shutdown does not have priority over suspend/hibernation Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: When shutting down a laptop, if one closes the lid just after clicking shut down, the laptop may go to suspend/hibernation mode instead of shutting down. This is especially annoying since when recovering from suspend/hibernation, then the laptop continue the shut down process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/471457/+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 1217636] [NEW] Tomboy causing logout delay again
Public bug reported: My logout has been slow for months. Finally I decided to look it up, and it seemed that tomboy could cause this, but the bug should be fixed according to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/880299 https://launchpad.net/ubuntu/+source/tomboy/+changelog But unfortunately with Ubuntu 13.04 updated and tomboy 1.12.0-1ubuntu2 I still get delays on logout. I removed tomboy and they went away. A comment in the arch linux bugtracker seems to indicate I'm not the only one still having this issue: https://bugs.archlinux.org/task/26324 . ** Affects: tomboy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tomboy in Ubuntu. https://bugs.launchpad.net/bugs/1217636 Title: Tomboy causing logout delay again Status in “tomboy” package in Ubuntu: New Bug description: My logout has been slow for months. Finally I decided to look it up, and it seemed that tomboy could cause this, but the bug should be fixed according to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/880299 https://launchpad.net/ubuntu/+source/tomboy/+changelog But unfortunately with Ubuntu 13.04 updated and tomboy 1.12.0-1ubuntu2 I still get delays on logout. I removed tomboy and they went away. A comment in the arch linux bugtracker seems to indicate I'm not the only one still having this issue: https://bugs.archlinux.org/task/26324 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/1217636/+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 969489] Re: lightdm tries (and fails) to start too early?
I had this with fglrx, so either both amd and nvidia suffer from the same bug, or it is elsewhere. It's just a pity that this is treated as such low priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 969489] Re: lightdm tries (and fails) to start too early?
Is this both a lightdm bug and a failsafe-x bug? Because I don't get failsafe-x when lightdm fails, I just get a tty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 969489] Re: lightdm tries (and fails) to start too early?
> I have not seen data that proves it has 0 bad effects. I'd suspect that > it would have a minor impact on time between power-on and login for > those users who are not affected, but I also have no data on that either. Sorry... say what!? I will just quote it for you, from canonical's upstart documentation: http://upstart.ubuntu.com/cookbook/#respawn "6.26 respawn Without this stanza, a job that exits quietly transitions into the stop/waiting state, no matter how it exited. With this stanza, whenever the main script/exec exits, without the goal of the job having been changed to stop, the job will be started again." So please don't make up suppositions and compare them to facts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 969489] Re: lightdm tries (and fails) to start too early?
@Clint: But honestly, why not deploy the workaround by default? It has 0 bad effects when you don't have the issue, and is the difference between some strange flickering and most people not being able to get a working system at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 1178006] Re: dvipdfm missing in texmf font map directory.
Not related to texlive-base ** Changed in: texlive-base (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1178006 Title: dvipdfm missing in texmf font map directory. Status in “texlive-base” package in Ubuntu: Invalid Bug description: Precise has files /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm.map /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm_dl14.map /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm_ndl14.map These are missing in quantal and raring but are required for Piscript. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1178006/+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 1178006] [NEW] dvipdfm missing in texmf font map directory.
Public bug reported: Precise has files /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm.map /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm_dl14.map /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm_ndl14.map These are missing in quantal and raring but are required for Piscript. ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1178006 Title: dvipdfm missing in texmf font map directory. Status in “texlive-base” package in Ubuntu: New Bug description: Precise has files /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm.map /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm_dl14.map /usr/share/texmf-texlive/fonts/map/dvipdfm/updmap/dvipdfm_ndl14.map These are missing in quantal and raring but are required for Piscript. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1178006/+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 1169533] [NEW] totem não funciona
Public bug reported: quando tento abrir um arquivo de video ou som, dem uma mensagem dizendo que necessita de um plugin. procuro atualizar, mas nao atuliza. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgstreamer0.10-0 0.10.30-1build2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Tue Apr 16 11:25:42 2013 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.utf8 SHELL=/bin/bash SourcePackage: gstreamer0.10 ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1169533 Title: totem não funciona Status in “gstreamer0.10” package in Ubuntu: New Bug description: quando tento abrir um arquivo de video ou som, dem uma mensagem dizendo que necessita de um plugin. procuro atualizar, mas nao atuliza. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgstreamer0.10-0 0.10.30-1build2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Tue Apr 16 11:25:42 2013 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.utf8 SHELL=/bin/bash SourcePackage: gstreamer0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1169533/+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 1097763]
Ah, my bad! No need to screencast, the issue is exactly what kokoko3k said in comment #28, but it doesn't need to be on a native widget (I see it on gmail). -- 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/1097763 Title: Firefox 18 anti-aliasing does not render correctly some text Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Fix Committed Bug description: Some portion of text are not rendering correctly after upgrading to Firefox 18 in Ubuntu 12.04.1 amd64. I've attached a screenshot, please notice the red text on the right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 18.0+build1-0ubuntu0.12.04.3 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shiba 2252 F pulseaudio /dev/snd/controlC0: shiba 2252 F pulseaudio BuildID: 20130107224849 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe028000 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1028020e,0011' Controls : 39 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia_1'/'HDA NVidia at 0xfbffc000 irq 16' Mixer name : 'Nvidia GPU 15 HDMI/DP' Components : 'HDA:10de0015,10de0101,00100100' Controls : 24 Simple ctrls : 4 Channel: Unavailable Date: Wed Jan 9 14:35:43 2013 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120309) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True PciNetwork: PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=18.0/20130107224849 RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd06/15/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1097763/+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 1097763]
@Comment #33: I'm not sure, I just tried to reproduce your issue and couldn't. Have you tried it on another machine, just to be sure? -- 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/1097763 Title: Firefox 18 anti-aliasing does not render correctly some text Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Fix Committed Bug description: Some portion of text are not rendering correctly after upgrading to Firefox 18 in Ubuntu 12.04.1 amd64. I've attached a screenshot, please notice the red text on the right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 18.0+build1-0ubuntu0.12.04.3 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shiba 2252 F pulseaudio /dev/snd/controlC0: shiba 2252 F pulseaudio BuildID: 20130107224849 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe028000 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1028020e,0011' Controls : 39 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia_1'/'HDA NVidia at 0xfbffc000 irq 16' Mixer name : 'Nvidia GPU 15 HDMI/DP' Components : 'HDA:10de0015,10de0101,00100100' Controls : 24 Simple ctrls : 4 Channel: Unavailable Date: Wed Jan 9 14:35:43 2013 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120309) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True PciNetwork: PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=18.0/20130107224849 RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd06/15/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1097763/+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 1097763]
As peke said in comment #30: It's fixed in Firefox 19 (thanks!) but it can still happen when using hardware acceleration. I turned on layers.acceleration.force-enabled today (Firefox 20 / Ubuntu 12.10 64-bit / nvidia 310.14) and started noticing the issue again. I can see it clearly in gmail, and the strange thing is, that it's temporary: font hinting is strange when scrolling, and after you stop, in 2-3 seconds it jumps to being ok. I'm now attempting to record a screencast to show this. -- 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/1097763 Title: Firefox 18 anti-aliasing does not render correctly some text Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Fix Committed Bug description: Some portion of text are not rendering correctly after upgrading to Firefox 18 in Ubuntu 12.04.1 amd64. I've attached a screenshot, please notice the red text on the right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 18.0+build1-0ubuntu0.12.04.3 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shiba 2252 F pulseaudio /dev/snd/controlC0: shiba 2252 F pulseaudio BuildID: 20130107224849 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe028000 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1028020e,0011' Controls : 39 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia_1'/'HDA NVidia at 0xfbffc000 irq 16' Mixer name : 'Nvidia GPU 15 HDMI/DP' Components : 'HDA:10de0015,10de0101,00100100' Controls : 24 Simple ctrls : 4 Channel: Unavailable Date: Wed Jan 9 14:35:43 2013 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120309) IpRoute: default via 192.168.0.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True PciNetwork: PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=18.0/20130107224849 RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd06/15/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1097763/+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 1115225] Re: after switch to kdm, lightdm starts and stops at boot
Also the case for a fresh 12.10 installation with gnome-shell and gdm as default. /var/log/boot.log shows * Starting LightDM Display ManagerESC[74G[ OK ] * Stopping LightDM Display ManagerESC[74G[ OK ] At the time that happens, gdm has already been started. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1115225 Title: after switch to kdm, lightdm starts and stops at boot Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm was installed on my system, after it came with kubunut release upgrade. I set kdm as standart display manager again, by dpkg-reconfigure kdm. all went fine, and kdm works properly. recently i noticed that lightdm is started at boot, just to become stopped right after that. i searched for, but did not find any sense for this behavior. boot.log: * Starting LightDM Display Manager^[[174G[ OK ] * Stopping LightDM Display Manager^[[174G[ OK ] i think lightdm sould not even be started, after i set an other default display manager. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Mon Feb 4 12:45:42 2013 InstallationDate: Installed on 2011-11-11 (450 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-11-13 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1115225/+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 969489] Re: lightdm tries (and fails) to start too early?
Interesting, I too use btrfs for root and home. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 1101767] Re: Mouse buttons not inverted on initial login
I have not experienced this bug anymore in the past week. It seems some update fixed it. -- 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/1101767 Title: Mouse buttons not inverted on initial login Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: I am experiencing a bug where on first login to an Ubuntu/Unity session (12.04), my mouse buttons are not inverted (left-handed). The configuration does correctly list them as inverted, but they don't behave that way. If I log out and login again, they behave correctly, as per the configuration. It worked correctly for the longest time and only recently (a few weeks ago) started misbehaving. --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True NonfreeKernelModules: nvidia Package: gnome-settings-daemon 3.4.2-0ubuntu0.6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-28 (266 days ago) UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1101767/+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 1101767] Re: Mouse buttons not inverted on initial login
On some occasions, on initial startup, the mouse buttons do no respond at all. Ctrl-alt-del to logout is necessary. -- 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/1101767 Title: Mouse buttons not inverted on initial login Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: I am experiencing a bug where on first login to an Ubuntu/Unity session (12.04), my mouse buttons are not inverted (left-handed). The configuration does correctly list them as inverted, but they don't behave that way. If I log out and login again, they behave correctly, as per the configuration. It worked correctly for the longest time and only recently (a few weeks ago) started misbehaving. --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True NonfreeKernelModules: nvidia Package: gnome-settings-daemon 3.4.2-0ubuntu0.6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-28 (266 days ago) UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1101767/+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 1101767] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1101767/+attachment/3489136/+files/Dependencies.txt -- 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/1101767 Title: Mouse buttons not inverted on initial login Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: I am experiencing a bug where on first login to an Ubuntu/Unity session (12.04), my mouse buttons are not inverted (left-handed). The configuration does correctly list them as inverted, but they don't behave that way. If I log out and login again, they behave correctly, as per the configuration. It worked correctly for the longest time and only recently (a few weeks ago) started misbehaving. --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True NonfreeKernelModules: nvidia Package: gnome-settings-daemon 3.4.2-0ubuntu0.6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-28 (266 days ago) UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1101767/+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 1101767] Re: Mouse buttons not inverted on initial login
It was suggested that the first guess for the package is gnome-settings- daemon. ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) ** Tags added: apport-collected precise running-unity ** Description changed: - I am experiencing a bug where on first login to an Ubuntu/Unity session - (12.04), my mouse buttons are not inverted (left-handed). The - configuration does correctly list them as inverted, but they don't - behave that way. If I log out and login again, they behave correctly, as - per the configuration. It worked correctly for the longest time and only - recently (a few weeks ago) started misbehaving. + I am experiencing a bug where on first login to an Ubuntu/Unity session (12.04), my mouse buttons are not inverted (left-handed). The configuration does correctly list them as inverted, but they don't behave that way. If I log out and login again, they behave correctly, as per the configuration. It worked correctly for the longest time and only recently (a few weeks ago) started misbehaving. + --- + ApportVersion: 2.0.1-0ubuntu17.1 + Architecture: amd64 + DistroRelease: Ubuntu 12.04 + InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) + MarkForUpload: True + NonfreeKernelModules: nvidia + Package: gnome-settings-daemon 3.4.2-0ubuntu0.6 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 + Tags: precise running-unity + Uname: Linux 3.2.0-36-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-04-28 (266 days ago) + UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers -- 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/1101767 Title: Mouse buttons not inverted on initial login Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: I am experiencing a bug where on first login to an Ubuntu/Unity session (12.04), my mouse buttons are not inverted (left-handed). The configuration does correctly list them as inverted, but they don't behave that way. If I log out and login again, they behave correctly, as per the configuration. It worked correctly for the longest time and only recently (a few weeks ago) started misbehaving. --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True NonfreeKernelModules: nvidia Package: gnome-settings-daemon 3.4.2-0ubuntu0.6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-28 (266 days ago) UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1101767/+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 969489] Re: lightdm tries (and fails) to start too early?
Bug 1080082 has been marked as a duplicate of this one, although I'm not sure it is (I use fglrx). Anyway, my workaround for 1.5 months with no issues and no need for arbitrary sleep has been to modify /etc/init/lightdm.conf and adding "respawn" like this: ... stop on runlevel [016] respawn # <-- add this line emits login-session-start emits desktop-session-start emits desktop-shutdown ... If lightdm comes up the first time, it stays. Otherwise, I see a flicker of the first one dying, and then it immediately starts up again and all works good. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 1092777] [NEW] control center crashes when I try to select Logitech BCC950 webcam sound input
Public bug reported: syslog tells me: gnome-control-c[6031]: segfault at 7fffe1112ec8 ip 7fa72cdba9f2 sp 7fffe1112d90 error 6 in libc-2.15.so[7fa72cd72000+1b5000] earlier, I got a crash panel that told me I had a vsprintf error, but now I no longer get the crash panel. (by the way, the bcc950 video input works just fine.) more detailed syslog. Dec 20 19:51:59 iaw-shuttle pulseaudio[5963]: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode! Dec 20 19:51:59 iaw-shuttle pulseaudio[5963]: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time! Dec 20 19:51:59 iaw-shuttle pulseaudio[5965]: [pulseaudio] main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that. Dec 20 19:51:59 iaw-shuttle pulseaudio[5965]: [pulseaudio] main.c: If you do it nonetheless then it's your own fault if things don't work as expected. Dec 20 19:51:59 iaw-shuttle pulseaudio[5965]: [pulseaudio] main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea. Dec 20 19:51:59 iaw-shuttle kernel: [ 745.664603] 4:2:1: cannot get freq at ep 0x1 Dec 20 19:51:59 iaw-shuttle kernel: [ 745.724507] 4:1:1: cannot get freq at ep 0x81 Dec 20 19:52:05 iaw-shuttle pulseaudio[5965]: [pulseaudio] module-always-sink.c: Unable to load module-null-sink Dec 20 19:52:08 iaw-shuttle pulseaudio[5990]: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode! Dec 20 19:52:08 iaw-shuttle pulseaudio[5990]: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time! Dec 20 19:52:08 iaw-shuttle pulseaudio[5992]: [pulseaudio] main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that. Dec 20 19:52:08 iaw-shuttle pulseaudio[5992]: [pulseaudio] main.c: If you do it nonetheless then it's your own fault if things don't work as expected. Dec 20 19:52:08 iaw-shuttle pulseaudio[5992]: [pulseaudio] main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea. Dec 20 19:52:08 iaw-shuttle kernel: [ 754.604317] 4:2:1: cannot get freq at ep 0x1 Dec 20 19:52:08 iaw-shuttle kernel: [ 754.646616] 4:2:1: cannot get freq at ep 0x1 Dec 20 19:52:08 iaw-shuttle kernel: [ 754.674602] 4:2:1: cannot get freq at ep 0x1 Dec 20 19:52:13 iaw-shuttle pulseaudio[1987]: [alsa-source] alsa-source.c: Error opening PCM device front:0: Device or resource busy Dec 20 19:52:22 iaw-shuttle kernel: [ 768.630414] gnome-control-c[6002]: segfault at 7fffabd88e58 ip 7f5a6f0939f2 sp 7fffabd88d20 error 6 in libc-2.15.so[7f5a6f04b000+1b5000] Dec 20 19:52:50 iaw-shuttle kernel: [ 796.482841] gnome-control-c[6013]: segfault at 7fff8a744d68 ip 7f8170cdc9f2 sp 7fff8a744c30 error 6 in libc-2.15.so[7f8170c94000+1b5000] Dec 20 19:54:01 iaw-shuttle kernel: [ 867.223027] gnome-control-c[6031]: segfault at 7fffe1112ec8 ip 7fa72cdba9f2 sp 7fffe1112d90 error 6 in libc-2.15.so[7fa72cd72000+1b5000] ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1092777 Title: control center crashes when I try to select Logitech BCC950 webcam sound input Status in “gnome-control-center” package in Ubuntu: New Bug description: syslog tells me: gnome-control-c[6031]: segfault at 7fffe1112ec8 ip 7fa72cdba9f2 sp 7fffe1112d90 error 6 in libc-2.15.so[7fa72cd72000+1b5000] earlier, I got a crash panel that told me I had a vsprintf error, but now I no longer get the crash panel. (by the way, the bcc950 video input works just fine.) more detailed syslog. Dec 20 19:51:59 iaw-shuttle pulseaudio[5963]: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode! Dec 20 19:51:59 iaw-shuttle pulseaudio[5963]: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time! Dec 20 19:51:59 iaw-shuttle pulseaudio[5965]: [pulseaudio] main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that. Dec 20 19:51:59 iaw-shuttle pulseaudio[5965]: [pulseaudio] main.c: If you do it nonetheless then it's your own fault if things don't work as expected. Dec 20 19:51:59 iaw-shuttle pulseaudio[5965]: [pulseaudio] main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea. Dec 20 19:51:59 iaw-shuttle kernel: [ 745.664603] 4:2:1: cannot get freq at ep 0x1 Dec 20 19:51:59 iaw-shuttle kernel: [ 745.724507] 4:1:1: cannot get freq at ep 0x81 Dec 20 19:52:05 iaw-shuttle pulseaudio[5965]: [pulseaudio] module-always-sink.c: Unable to load module-null-sink Dec 20 19:52:08 iaw-shutt
[Desktop-packages] [Bug 970916] Re: [soundnua]: gnome-control-center crashed with SIGSEGV in vfprintf()
it's not fixed. I am trying it out on a USB mic that is built into a logitech bcc950. whenever I click in the control panel on the input, I get this crash. this happens even after I uncommented the required volume in analog-input.conf and restarted the pulse server. /iaw -- 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/970916 Title: [soundnua]: gnome-control-center crashed with SIGSEGV in vfprintf() Status in “gnome-control-center” package in Ubuntu: Fix Released Bug description: gnome-control-center crashed while I was trying to test the various input/output devices. It is probably not related to this bug, but my soundcard is not 100% properly identified. Here is the lsusb listing : $ lsusb | grep Creative Bus 002 Device 002: ID 041e:3f04 Creative Technology, Ltd E-Mu 0404 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Sun Apr 1 16:20:03 2012 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120401) ProcCmdline: gnome-control-center --overview ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center Title: [soundnua]: gnome-control-center crashed with SIGSEGV in vfprintf() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/970916/+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 1080082] Re: Lightdm killed during boot (kills itself?)
Just to add, I've tried multiple workarounds, and the best one (works every time) and less intrusive is modifying the file /etc/init/lightdm.conf adding "respawn" like this: ... stop on runlevel [016] respawn emits login-session-start emits desktop-session-start emits desktop-shutdown --- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1080082 Title: Lightdm killed during boot (kills itself?) Status in Light Display Manager: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: I'm running 12.10, and since installing the stable release in October I didn't install any upgrades. This week, after installing the latest upgrades, lightdm stopped working: the Xserver starts, and dies immediately, leaving me on a tty7 with remains of log messages. If I log in and manually restart lightdm, it works. I think I am not alone in this, as a user had reported exactly the same back in July in the xubuntu-users mailing list: https://lists.ubuntu.com/archives/xubuntu-users/2012-July/004252.html I've done some tests and: - If I disable plymouth (by removing splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub) the bug goes away - If I press 'esc' to exit plymouth before lightdm triess to start the bug also goes away Looking at the lightdm log, it seems that it decides to kill itself: ... [+1.22s] DEBUG: Starting Light Display Manager 1.4.0, UID=0 PID=1138 (notice the pid) ... [+5.59s] DEBUG: New display ready, switching to it [+5.59s] DEBUG: Activating VT 7 [+6.53s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Started session 1862 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Session 1862: Sending SIGTERM [+6.54s] DEBUG: Started session 1863 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Got signal 15 from process 1138 (signal to die received from itself!!) [+6.54s] DEBUG: Caught Terminated signal, shutting down ... This is what leads me to believe that the bug is in lightdm. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Nov 17 14:06:16 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.5.0-18-generic, x86_64: installed fglrx-updates, 9.000, 3.5.0-19-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397b] InstallationDate: Installed on 2012-10-21 (26 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 10382JG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-19-generic root=UUID=9a791902-1e8f-4073-b59c-de19842fdff8 ro rootflags=subvol=@ crashkernel=384M-2G:64M,2G-:128M quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 4BCN24WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr4BCN24WW:bd08/10/2011:svnLENOVO:pn10382JG:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 10382JG dmi.product.version: Ideapad S205 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notif
[Desktop-packages] [Bug 881819] Re: Pidgin doesn't automatically log in accounts
No, I think the bug was fixed at some point. I haven't experienced the problem in a long time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/881819 Title: Pidgin doesn't automatically log in accounts Status in Pidgin: New Status in “pidgin” package in Ubuntu: Confirmed Bug description: Ever since the upgrade to 11.10, pidgin never recovers from being auto-started before there is a network connection. It remains in "Waiting for network connection" and never logs in its accounts. I need to go to the accounts tab and uncheck and recheck all accounts to get them to sign in. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: pidgin 1:2.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CheckboxSubmission: 5823d95fa64f80a5737523eb4a19225e CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f Date: Wed Oct 26 08:00:47 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin UpgradeStatus: Upgraded to oneiric on 2011-10-13 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/881819/+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 1080082] Re: Lightdm killed during boot (kills itself?)
Might be related to bug #838586 and question #208880 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1080082 Title: Lightdm killed during boot (kills itself?) Status in Light Display Manager: New Status in “fglrx-installer” package in Ubuntu: New Bug description: I'm running 12.10, and since installing the stable release in October I didn't install any upgrades. This week, after installing the latest upgrades, lightdm stopped working: the Xserver starts, and dies immediately, leaving me on a tty7 with remains of log messages. If I log in and manually restart lightdm, it works. I think I am not alone in this, as a user had reported exactly the same back in July in the xubuntu-users mailing list: https://lists.ubuntu.com/archives/xubuntu-users/2012-July/004252.html I've done some tests and: - If I disable plymouth (by removing splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub) the bug goes away - If I press 'esc' to exit plymouth before lightdm triess to start the bug also goes away Looking at the lightdm log, it seems that it decides to kill itself: ... [+1.22s] DEBUG: Starting Light Display Manager 1.4.0, UID=0 PID=1138 (notice the pid) ... [+5.59s] DEBUG: New display ready, switching to it [+5.59s] DEBUG: Activating VT 7 [+6.53s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Started session 1862 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Session 1862: Sending SIGTERM [+6.54s] DEBUG: Started session 1863 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Got signal 15 from process 1138 (signal to die received from itself!!) [+6.54s] DEBUG: Caught Terminated signal, shutting down ... This is what leads me to believe that the bug is in lightdm. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Nov 17 14:06:16 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.5.0-18-generic, x86_64: installed fglrx-updates, 9.000, 3.5.0-19-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397b] InstallationDate: Installed on 2012-10-21 (26 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 10382JG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-19-generic root=UUID=9a791902-1e8f-4073-b59c-de19842fdff8 ro rootflags=subvol=@ crashkernel=384M-2G:64M,2G-:128M quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 4BCN24WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr4BCN24WW:bd08/10/2011:svnLENOVO:pn10382JG:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 10382JG dmi.product.version: Ideapad S205 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1080082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desk
[Desktop-packages] [Bug 1080082] [NEW] Lightdm killed during boot (kills itself?)
Public bug reported: I'm running 12.10, and since installing the stable release in October I didn't install any upgrades. This week, after installing the latest upgrades, lightdm stopped working: the Xserver starts, and dies immediately, leaving me on a tty7 with remains of log messages. If I log in and manually restart lightdm, it works. I think I am not alone in this, as a user had reported exactly the same back in July in the xubuntu-users mailing list: https://lists.ubuntu.com/archives/xubuntu-users/2012-July/004252.html I've done some tests and: - If I disable plymouth (by removing splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub) the bug goes away - If I press 'esc' to exit plymouth before lightdm triess to start the bug also goes away Looking at the lightdm log, it seems that it decides to kill itself: ... [+1.22s] DEBUG: Starting Light Display Manager 1.4.0, UID=0 PID=1138 (notice the pid) ... [+5.59s] DEBUG: New display ready, switching to it [+5.59s] DEBUG: Activating VT 7 [+6.53s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Started session 1862 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Session 1862: Sending SIGTERM [+6.54s] DEBUG: Started session 1863 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Got signal 15 from process 1138 (signal to die received from itself!!) [+6.54s] DEBUG: Caught Terminated signal, shutting down ... This is what leads me to believe that the bug is in lightdm. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Nov 17 14:06:16 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.5.0-18-generic, x86_64: installed fglrx-updates, 9.000, 3.5.0-19-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397b] InstallationDate: Installed on 2012-10-21 (26 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 10382JG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-19-generic root=UUID=9a791902-1e8f-4073-b59c-de19842fdff8 ro rootflags=subvol=@ crashkernel=384M-2G:64M,2G-:128M quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 4BCN24WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr4BCN24WW:bd08/10/2011:svnLENOVO:pn10382JG:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 10382JG dmi.product.version: Ideapad S205 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: lightdm Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 quantal running-unity ubuntu ** Attachment added: "Lightdm log when it dies during boot" https://bugs.launchpad.net/bugs/1080082/+attachment/3436621/+files/lightdm-killed.log ** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1080082 Title: Lightdm killed during boot (kills itself?) Status in Light Display Manager: New Status in “xorg” package in Ubuntu: New Bug description: I'm running 12.10, and since installing the stable r
[Desktop-packages] [Bug 554183] Re: [Upstream] paste special does not work
I have had this problem constantly, for several years, in both OpenOffice and LibreOffice, on multiple consecutive versions of Ubuntu. Paste Special works for a while, and then mysteriously stops working (whether invoked by hotkey or menu). The only workaround is to close all open documents and restart LibreOffice (3.5.4.2 Build ID: 350m1(Build:2) on Ubuntu Precise Pangolin). What causes it to stop working is a mystery. There seems to be no pattern to it. The routine need to restart LibreOffice makes it surprising that this bug has been classified as of low importance. "Won't fix" is not a satisfactory status. -- 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/554183 Title: [Upstream] paste special does not work Status in LibreOffice Productivity Suite: Confirmed Status in The OpenOffice.org Suite: Invalid Status in “libreoffice” package in Ubuntu: Triaged Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.1-1ubuntu1 Candidate: 1:3.5.1-1ubuntu1 Version table: *** 1:3.5.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a blank Calc document: + Cell A1 type: 1 + Copy A1 and paste into A2 + Switch to Firefox and go to https://bugs.freedesktop.org/show_bug.cgi?id=42466 + Copy hyperlink and paste special into A3 and it works. 4) What happens instead is it does not. ***Closed LO, immediately opened new blank Calc file, and then above steps did not recreate bug. Above steps not reproducible in: lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages Original Reporter Comments: OpenOffice 3.2 in Lucid. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openoffice.org-core 1:3.2.0-4ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 2 13:32:27 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/554183/+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 605567] Re: Extremely slow painting of launchpad.net bug details page with nvidia driver
@Robert: This is a firefox+nvidia proprietary linux driver issue. Other browsers and drivers do not have it. -- 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/605567 Title: Extremely slow painting of launchpad.net bug details page with nvidia driver Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Invalid Bug description: Binary package hint: firefox Launchpad.net bug detail pages are painted extremely slowly by Firefox on my machine. I'm running Ubuntu Lucid 64-bit, and I have the proprietary nvidia driver (from the Ubuntu repositories) installed, version "current". The machine has two 8800 GTX GPU's with 768 MB each, so the available graphics power should not be a problem. It takes many seconds (sometimes tens of seconds) to draw the page, during which the entire computer slows to a crawl. Nothing happens on the screen during this time. Whenever I scroll the page up so that more of the page is revealed at the top of the screen, this is painted extremely slowly as well. Scrolling down (once the page is fully painted) does not produce slow-downs, so the problem appears to be with the content at the top of the page. It appears to be an interaction between Firefox, Launchpad.net and the proprietary NVidia driver. I don't notice slowdowns like this on any other web page (including other launchpad.net pages). Other browsers, such as Chrome, draw Launchpad bug detail pages with lighting speed. And when I use the nv or nouveau drivers the problem does not appear either. Since Chrome can paint the pages at fast speeds, Firefox should be able to as well, so I still think this is a Firefox problem. If there is any way I can determine exactly what it is that is taking so much time and slowing down the entire computer, please let me know! Or if there is any other way in which I can help debug this problem. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Jul 14 21:03:25 2010 FirefoxPackages: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1 firefox-gnome-support 3.6.6+nobinonly-0ubuntu0.10.04.1 firefox-branding 3.6.6+nobinonly-0ubuntu0.10.04.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/605567/+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 912702] Re: the window "Wireless Network Authentication Required" keeps popping up until "the end of times" even though the previous one was not closed
It's been six months since this bug was reported, its importance remains undecided, and fixing it remains unassigned. This is a problem. Whenever my machine is disconnected from wi-fi for a few hours, it is faster to reboot than to close the dozens of nm-applet authentication windows trying to connect to alternative wi-fi networks. This drives me nuts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/912702 Title: the window "Wireless Network Authentication Required" keeps popping up until "the end of times" even though the previous one was not closed Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: I left the computer turned on for the night and in the morning I found not less than 65, yes 65!! instances of the same window. my system was responding very slowly. and closing one took more than a minute, so I had to kill it manually. take a look on my screenshots, they look really weird. this is very annoying solution: this window shouldn't pop up when the previous one was not closed! ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager-gnome 0.9.1.90-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Jan 6 11:38:28 2012 ExecutablePath: /usr/bin/nm-applet Gconf: IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) IpRoute: default via 158.195.192.1 dev eth0 proto static 158.195.192.0/19 dev eth0 proto kernel scope link src 158.195.196.69 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/912702/+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 970669] [NEW] Cannot login when shutdown command is overtook by XUbuntu log-out
Public bug reported: XUbuntu 11.10 LightDM 1.0.6-0ubuntu1.6 Steps to reproduce: 1. In standard XUbuntu installation bring up the terminal, type "sudo shutdown -P +80" and press enter. Don't fill in password. 2. Choose Log-Out screen from XUbuntu system menu and turn off computer using this GUI possibility to do it (leaving the terminal with shutdown command opened). 3. Start the computer - the LightDM will not let you log-in as common user, because the system identifies itself as in shutdown mode and the only user that can log-in is root, which can be tricky in Ubuntu as sudoers does not need to set root password. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/970669 Title: Cannot login when shutdown command is overtook by XUbuntu log-out Status in “lightdm” package in Ubuntu: New Bug description: XUbuntu 11.10 LightDM 1.0.6-0ubuntu1.6 Steps to reproduce: 1. In standard XUbuntu installation bring up the terminal, type "sudo shutdown -P +80" and press enter. Don't fill in password. 2. Choose Log-Out screen from XUbuntu system menu and turn off computer using this GUI possibility to do it (leaving the terminal with shutdown command opened). 3. Start the computer - the LightDM will not let you log-in as common user, because the system identifies itself as in shutdown mode and the only user that can log-in is root, which can be tricky in Ubuntu as sudoers does not need to set root password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/970669/+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 912710] Re: Oneiric Thunderbird freezes on receiving mail
Hi Gerd I have TB11 allready for some time (standard for Oneiric now I guess). I am not familiar with strace, I'm a simple user I do think you have a point to stop using several accounts and start switching profiles. I don't think this is the right solution for me and as there is no help available, I'm going to switch to another client asap ! Greetz, and thank for your reaction ! Ivo -- 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/912710 Title: Oneiric Thunderbird freezes on receiving mail Status in “thunderbird” package in Ubuntu: New Bug description: After having switched to Oneiric a couple of days ago, Thunderbird freezes on receiving mail most (all ?) of the time. Running in safe-mode this is very easy to reproduce for me: Having an IMAP mailbox active, I ask someone to drop me a mail to that mailbox. I see the new mail in that mailbox summary, but Thunderbird is frozen completely. The only action I can take is to close (i.e. kill) it via the window manager. This is strace output: lulu:/home/ba> ps -ef | grep thund ba1388 2156 1 11:29 pts/200:00:04 /usr/lib/thunderbird-8.0/thunderbird-bin -safe-mode ba1516 2155 0 11:34 pts/100:00:00 grep thund lulu:/home/ba> sudo strace -p 1388 Process 1388 attached - interrupt to quit write(59, "\17\0)\0?\0S\0c\0q\0\201\0\217\0\233\0\242\0\246\0\243\0\235\0\226\0\214\0\201\0"..., 16560^C Process 1388 detached lulu:/home/ba> So obviously Thunderbird is hanging in a write to fd 59. lsof tells me: thunderbi 1388 ba 59u unix 0xf26e9680 0t0 8554035 socket thunderbi 1388 ba 60u IPv48528771 0t0 TCP lulu:57892->abgze76e.fsc.net:imaps (ESTABLISHED) This happens with different IMAP mailboxes (Google being one of them). With Thunderbird in Natty (very same tb-configuration) I never had such an issue. I really would like to help debugging, if anybody gives me instructions. But I REALLY need advise how to use another Thunderbird version (from the ubuntu repos if possible). Thanks Gerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/912710/+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 912710] Re: Oneiric Thunderbird freezes on receiving mail
I have the same problem: Ubuntu Oneiric Thunderbird hangs continuously (after a few secons, sometimes minutes) Using IMAP The problem started when I changed from POP ==> IMAP-servers (multiple accounts) This is really a pain in the neck and I need to revert to an older version of Thunderbird, or to another mail-client. Any help is appreciated ! Greetings Ivo -- 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/912710 Title: Oneiric Thunderbird freezes on receiving mail Status in “thunderbird” package in Ubuntu: New Bug description: After having switched to Oneiric a couple of days ago, Thunderbird freezes on receiving mail most (all ?) of the time. Running in safe-mode this is very easy to reproduce for me: Having an IMAP mailbox active, I ask someone to drop me a mail to that mailbox. I see the new mail in that mailbox summary, but Thunderbird is frozen completely. The only action I can take is to close (i.e. kill) it via the window manager. This is strace output: lulu:/home/ba> ps -ef | grep thund ba1388 2156 1 11:29 pts/200:00:04 /usr/lib/thunderbird-8.0/thunderbird-bin -safe-mode ba1516 2155 0 11:34 pts/100:00:00 grep thund lulu:/home/ba> sudo strace -p 1388 Process 1388 attached - interrupt to quit write(59, "\17\0)\0?\0S\0c\0q\0\201\0\217\0\233\0\242\0\246\0\243\0\235\0\226\0\214\0\201\0"..., 16560^C Process 1388 detached lulu:/home/ba> So obviously Thunderbird is hanging in a write to fd 59. lsof tells me: thunderbi 1388 ba 59u unix 0xf26e9680 0t0 8554035 socket thunderbi 1388 ba 60u IPv48528771 0t0 TCP lulu:57892->abgze76e.fsc.net:imaps (ESTABLISHED) This happens with different IMAP mailboxes (Google being one of them). With Thunderbird in Natty (very same tb-configuration) I never had such an issue. I really would like to help debugging, if anybody gives me instructions. But I REALLY need advise how to use another Thunderbird version (from the ubuntu repos if possible). Thanks Gerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/912710/+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 963508] Re: lg e900 sync fail.. it could be amazing if there will be a fix
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/963508 Title: lg e900 sync fail.. it could be amazing if there will be a fix Status in “rhythmbox” package in Ubuntu: New Bug description: I report the error message, while i'm trying to sync my ubuntu music library with my Lg Optimus 7 e900 (Windows Phone). I know these 2 are not already workin together, but i noticed that Rhythmbox can see my windows phone, and listed to Device. So i was excited and i tried to sync.. then this error, See what u can do. Thank u!! Unable to send file to MTP device: PTP Layer error 200f: send_file_object_info():Could not send object property list. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Fri Mar 23 23:03:33 2012 ExecutablePath: /usr/bin/rhythmbox ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/963508/+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 963508] [NEW] lg e900 sync fail.. it could be amazing if there will be a fix
Public bug reported: I report the error message, while i'm trying to sync my ubuntu music library with my Lg Optimus 7 e900 (Windows Phone). I know these 2 are not already workin together, but i noticed that Rhythmbox can see my windows phone, and listed to Device. So i was excited and i tried to sync.. then this error, See what u can do. Thank u!! Unable to send file to MTP device: PTP Layer error 200f: send_file_object_info():Could not send object property list. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Fri Mar 23 23:03:33 2012 ExecutablePath: /usr/bin/rhythmbox ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/963508 Title: lg e900 sync fail.. it could be amazing if there will be a fix Status in “rhythmbox” package in Ubuntu: New Bug description: I report the error message, while i'm trying to sync my ubuntu music library with my Lg Optimus 7 e900 (Windows Phone). I know these 2 are not already workin together, but i noticed that Rhythmbox can see my windows phone, and listed to Device. So i was excited and i tried to sync.. then this error, See what u can do. Thank u!! Unable to send file to MTP device: PTP Layer error 200f: send_file_object_info():Could not send object property list. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Fri Mar 23 23:03:33 2012 ExecutablePath: /usr/bin/rhythmbox ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/963508/+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 605567] Re: Extremely slow painting of launchpad.net bug details page with nvidia driver
I think this bug should be attacked in two ways: 1) try to work with firefox and nvidia to fix this and 2) fix launchpad. The bug is elsewhere, but launchpad being broken with the default ubuntu browser with pretty much the default configuration of any nvidia linux user is very bad usability. And yes, I could use nouveau, and have a worse experience everywhere else, as well as wasting more energy, but that's not a very good answer. -- 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/605567 Title: Extremely slow painting of launchpad.net bug details page with nvidia driver Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Invalid Bug description: Binary package hint: firefox Launchpad.net bug detail pages are painted extremely slowly by Firefox on my machine. I'm running Ubuntu Lucid 64-bit, and I have the proprietary nvidia driver (from the Ubuntu repositories) installed, version "current". The machine has two 8800 GTX GPU's with 768 MB each, so the available graphics power should not be a problem. It takes many seconds (sometimes tens of seconds) to draw the page, during which the entire computer slows to a crawl. Nothing happens on the screen during this time. Whenever I scroll the page up so that more of the page is revealed at the top of the screen, this is painted extremely slowly as well. Scrolling down (once the page is fully painted) does not produce slow-downs, so the problem appears to be with the content at the top of the page. It appears to be an interaction between Firefox, Launchpad.net and the proprietary NVidia driver. I don't notice slowdowns like this on any other web page (including other launchpad.net pages). Other browsers, such as Chrome, draw Launchpad bug detail pages with lighting speed. And when I use the nv or nouveau drivers the problem does not appear either. Since Chrome can paint the pages at fast speeds, Firefox should be able to as well, so I still think this is a Firefox problem. If there is any way I can determine exactly what it is that is taking so much time and slowing down the entire computer, please let me know! Or if there is any other way in which I can help debug this problem. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Jul 14 21:03:25 2010 FirefoxPackages: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1 firefox-gnome-support 3.6.6+nobinonly-0ubuntu0.10.04.1 firefox-branding 3.6.6+nobinonly-0ubuntu0.10.04.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/605567/+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 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
@aritchie: could you provide a link to that bug report please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) Status in “libimobiledevice” package in Ubuntu: Fix Released Status in “libimobiledevice” source package in Lucid: Fix Released Status in “libimobiledevice” source package in Maverick: Confirmed Status in “libimobiledevice” source package in Natty: Fix Released Status in “libimobiledevice” source package in Oneiric: Fix Released Status in “libimobiledevice” source package in Precise: Fix Released Bug description: Binary package hint: nautilus TEST CASE: 1. attach an iphone with iOS5 2. see you get the error on mount "Unhandled lockdown error (-4)" 3. now install libimobiledevice from natty-proposed 4. see the iphone successfully makes a USB connection. ==Original Report== Plugged an iphone 4 running beta of iOS 5 into my Ubuntu Natty desktop and got a dialog:- "Unable to mount Alan Pope's iPhone" "Unhandled lockdown error (-4)" ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 10 11:49:15 2011 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+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 855793] Re: Kubuntu 11.10 beta 1: Error upgrading using muon
Kpackagekit also breaks with updates (see my previous comment, its latest version is called Apper) so... yeah. Not the solution also. -- 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/855793 Title: Kubuntu 11.10 beta 1: Error upgrading using muon Status in “gtk+2.0” package in Ubuntu: Confirmed Status in “kde-workspace” package in Ubuntu: Invalid Bug description: After installing Kubuntu 11.10 beta 1 in Virtualbox 4.1.2 (during installation I did not select to get updates) I tried to do a full update using muon package manager. The download of packages completed successfully but the installation process stuck on 20 % on kate package update. After waiting for a long time ( about 1 hour), I killed the update process. Then, I restarted the virtual machine but my system is not functional (e.g no network, no sound, no way to perform updates). System Information -- Description: Ubuntu oneiric (development branch) Release: 11.10 Architecture/Processor/Kernel -- 3.0.0-9-generic i686 i386 GNU/Linux Muon Package Info -- Package: muon Status: install ok installed Priority: optional Section: kde Installed-Size: 328 Maintainer: Ubuntu Developers Architecture: i386 Version: 1.2.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/855793/+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 855793] Re: Kubuntu 11.10 beta 1: Error upgrading using muon
I also saw this. It's a pity that both Apper (Bug# 905415) and Muon are broken for system upgrades. Shouldn't this be attributed to qapt or something like that? It seems that packages do upgrade fine with apt-get, aptitude, synaptic, etc. -- 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/855793 Title: Kubuntu 11.10 beta 1: Error upgrading using muon Status in “gtk+2.0” package in Ubuntu: Confirmed Status in “kde-workspace” package in Ubuntu: Invalid Bug description: After installing Kubuntu 11.10 beta 1 in Virtualbox 4.1.2 (during installation I did not select to get updates) I tried to do a full update using muon package manager. The download of packages completed successfully but the installation process stuck on 20 % on kate package update. After waiting for a long time ( about 1 hour), I killed the update process. Then, I restarted the virtual machine but my system is not functional (e.g no network, no sound, no way to perform updates). System Information -- Description: Ubuntu oneiric (development branch) Release: 11.10 Architecture/Processor/Kernel -- 3.0.0-9-generic i686 i386 GNU/Linux Muon Package Info -- Package: muon Status: install ok installed Priority: optional Section: kde Installed-Size: 328 Maintainer: Ubuntu Developers Architecture: i386 Version: 1.2.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/855793/+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
