[Desktop-packages] [Bug 1373815] Re: unable to start simple-scan when added 66 remote HP_LaserJet_Professional_M1212nf_MFP printer
Hi Temo, Thank you for providing us the gdb and strace output. We are looking into the issue. We will revert back on this soon. Thanks, goutam -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1373815 Title: unable to start simple-scan when added 66 remote HP_LaserJet_Professional_M1212nf_MFP printer Status in “simple-scan” package in Ubuntu: New Bug description: I have some problem related to scanning on all-in-one HP_LaserJet_Professional_M1212nf_MFP. I had installed ubuntu 14.04 i386 with hplip 3.14.6 I have added 65 remote all-in-one printer (HP_LaserJet_Professional_M1212nf_MFP) and used scanner of local M1212nf_MFP printer everything worked well, but when I added one more HP_LaserJet_Professional_M1212nf_MFP printer simple-scan program crashes on local machine with error code [user@localhost ~]$ export SANE_DEBUG_DLL=255 [user@localhost ~]$ simple-scan -d [+0.00s] DEBUG: simple-scan.vala:593: Starting Simple Scan 3.10.3, PID=2166 [+0.00s] DEBUG: Connecting to session manager [+0.04s] WARNING: g_object_set_valist: invalid object type 'GtkAdjustment' for value type 'GtkWidget' [+0.05s] DEBUG: ui.vala:1524: Restoring window to 600x400 pixels [+0.05s] DEBUG: autosave-manager.vala:64: Loading autosave information [+0.05s] DEBUG: autosave-manager.vala:258: Waiting to autosave... [sanei_debug] Setting debug level of dll to 255. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.24 [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/hpaio [dll] sane_init/read_config: reading dll.d/hpaio [dll] add_backend: adding backend `hpaio' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [+0.17s] DEBUG: scanner.vala:1443: sane_init () - SANE_STATUS_GOOD [+0.17s] DEBUG: scanner.vala:1449: SANE version 1.0.24 [+0.17s] DEBUG: scanner.vala:1510: Requesting redetection of scan devices [+0.17s] DEBUG: autosave-manager.vala:280: Autosaving book information [+0.17s] DEBUG: scanner.vala:802: Processing request [dll] sane_get_devices [dll] load: searching backend `hpaio' in `/usr/lib64/sane' [dll] load: trying to load `/usr/lib64/sane/libsane-hpaio.so.1' [dll] load: dlopen()ing `/usr/lib64/sane/libsane-hpaio.so.1' [dll] init: initializing backend `hpaio' [dll] init: backend `hpaio' is version 1.0.0 Segmentation fault (core dumped) syslog entry [user@localhost ~]$ dmesg [ .834761] scan-thread[2044]: segfault at 0 ip 7fab765aebca sp 7fab5de001a8 error 4 in libc-2.18.so[7fab7652a000+1b4000] when I lunch hp-scan all scanner listed but simple-scan cannot lunch [user@localhost ~]$ hp-scan HP Linux Imaging and Printing System (ver. 3.14.6) Scan Utility ver. 2.2 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. - | SELECT DEVICE | - Num Scan device URI - 0 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.28.76 1 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.33.124 2 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.32.236 3 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.33.108 4 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.33.204 5 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.32.188 6 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.34.44 7 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.29.76 8 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.29.12 9 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.32.172 10 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.34.28 11 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.32.156 12 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.32.252 13 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.37.44 14 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.29.156 15 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.31.44 16 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.34.188 17 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.29.172 18 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.33.220 19 hpaio:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.33.188 20
[Desktop-packages] [Bug 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
Should I move to the latest alsa driver? If so, how do I do this? Just follow the instructions here: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS Try that first. If it does not help, here's another workaround you can try: Edit the file /etc/modprobe.d/alsa-base.conf and add: options snd-hda-intel jackpoll_ms=400 Reboot and test, and see if this helps. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1365769 Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The problem is that the microphone is not detected after a reboot. As a result, some applications cannot get sound from the microphone. The Input tab of the Sound window lists no device. I have a workround which is to disconnect and then connect the microphone after I have logged in. Interestingly, the audacity application can access the microphone when the system says that the device does not exist ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 00:12:39 2014 InstallationDate: Installed on 2011-07-29 (1133 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio Symptom_Jack: Pink Mic, Rear Symptom_Type: No sound at all Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
Also, you seem to have some strange stuff in ~/.asoundrc and /etc/asound.conf. Before doing anything else, could you remove these files (or move them somewhere for backup purposes). It probably won't solve this issue, but it's just good to have one cause of error removed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1365769 Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The problem is that the microphone is not detected after a reboot. As a result, some applications cannot get sound from the microphone. The Input tab of the Sound window lists no device. I have a workround which is to disconnect and then connect the microphone after I have logged in. Interestingly, the audacity application can access the microphone when the system says that the device does not exist ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 00:12:39 2014 InstallationDate: Installed on 2011-07-29 (1133 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio Symptom_Jack: Pink Mic, Rear Symptom_Type: No sound at all Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1375571] [NEW] libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d
Public bug reported: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: ppa -- 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/1375571 Title: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d Status in “libreoffice” package in Ubuntu: New Bug description: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1375571/+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 1375577] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Public bug reported: not sure ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.16.0-18-generic Date: Tue Sep 30 00:30:54 2014 InstallationDate: Installed on 2013-11-27 (306 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-09-26 (3 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- 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/1375577 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: not sure ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.16.0-18-generic Date: Tue Sep 30 00:30:54 2014 InstallationDate: Installed on 2013-11-27 (306 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-09-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1375577/+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 1029289] Re: Need to authorize my google account each time I boot the computer
** No longer affects: signon-plugin-oauth2 ** Changed in: account-plugins Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Status in “account-plugins” source package in Trusty: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Released Status in “signon-plugin-oauth2” source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1375571] Re: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d
Those are generated dependencies coming from nss and nspr. So there is nothing libreoffice will do about that. -- 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/1375571 Title: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d Status in “libreoffice” package in Ubuntu: New Bug description: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1375571/+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 1365490] Re: ubuntu 12.04.5 broken on VMware
** Tags added: trusty ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: New Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: New Status in “mesa” source package in Trusty: New Bug description: Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+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 1370859] Re: Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)
Latest upgrade error met: Setting up linux-image-extra-3.16.0-18-generic (3.16.0-18.25) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-3.16.0-18-generic ) points to /boot/initrd.img-3.16.0-18-generic (/boot/initrd.img-3.16.0-18-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-extra-3.16.0-18-generic.postinst line 491. vmlinuz(/boot/vmlinuz-3.16.0-18-generic ) points to /boot/vmlinuz-3.16.0-18-generic (/boot/vmlinuz-3.16.0-18-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-extra-3.16.0-18-generic.postinst line 491. -- 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/1370859 Title: Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64) Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: Installing a new kernel 3.16.0.16 from a running gnome-shell session using the kernel 3.16.014, i'm getting: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64) Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information. * As apport also fails to report that issue (it simply does nothing, it even does not start and does not warns either), i'm joining the crash file and make.log for details. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 18 07:13:23 2014 SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1370859/+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 1371919] Re: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371919 Title: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I have a gigabyte f2a88xn motherboard with built-in audio. In pavucontrol, under Configuration - Built-in audio (the first), there is Digital Stereo (HDMI) Output. When I disable it, the kern.log continuously reports HDMI ATI/AMD: no speaker allocation for ELD. This happens almost every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:08:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371919/+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 1254369] Re: Incorrect Icon on Input Language Change, on Korean (hangul) input method
** Changed in: ibus (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1254369 Title: Incorrect Icon on Input Language Change, on Korean (hangul) input method Status in “ibus” package in Ubuntu: Invalid Bug description: In new Ubuntu version (Saucy), the ibus has changed to integrate more to the Ubuntu itself. So, when you change the input method, you can see the input method changing by the icon of the methods. However, in Korean input (hangul), the icon at the indicator doesn't reflect the input method settings. Also, intermittenly, the icon, shown when pressing keyboard shortcut of changing input method, is reversed between korean and english, showing the korean traditional shape above 'English'. I presume this to happen as hangul is not on the menu list when you go to ubuntu settings (text entry settings), but rather is added automatically if you choose Korean locale. Ubuntu Saucy Salamander (13.10) at i386. ibus 1.5.3-6ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sun Nov 24 10:42:35 2013 InstallationDate: Installed on 2013-11-23 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ko_KR.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1254369/+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 1365490] Re: ubuntu 12.04.5 broken on VMware
This has been fixed in utopic by moving to mesa 10.3. mesa-lts-trusty and mesa in trusty are still affected, I'll prepare a fix for them. I don't think the images can be redone. The trusty 14.04.2 dvd will have the utopic stack which will be fixed, but precise will no longer have new iso's. Could you update the bug description with the template linked below? https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Changed in: mesa (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa-lts-trusty (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Also affects: mesa (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: mesa-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mesa-lts-trusty (Ubuntu Trusty) Importance: Undecided Status: New ** No longer affects: mesa (Ubuntu Precise) ** No longer affects: mesa-lts-trusty (Ubuntu Trusty) ** Changed in: mesa-lts-trusty (Ubuntu) Status: New = Invalid ** Changed in: mesa-lts-trusty (Ubuntu Precise) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Trusty) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Trusty) Importance: Undecided = High ** Changed in: mesa-lts-trusty (Ubuntu Precise) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Status: New = Fix Released ** Changed in: mesa (Ubuntu Trusty) Status: New = Incomplete ** Changed in: mesa-lts-trusty (Ubuntu Precise) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+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 1375571] Re: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d
From the description and the resolution of this bug https://bugs.launchpad.net/bugs/1262775 , it looks like your reply just incorrect... -- 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/1375571 Title: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d Status in “libreoffice” package in Ubuntu: New Bug description: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1375571/+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 1310174] Re: cryptsetup should be included and installed by default in ubuntu 14.04
The same issue also arrises when you add a new disk to your system and wish to encrypt it. The disks utility offers you the encryption option, but then returns the none obvious error as stated before, instead of telling you that cryptsetup is not installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1310174 Title: cryptsetup should be included and installed by default in ubuntu 14.04 Status in “cryptsetup” package in Ubuntu: Incomplete Status in “gnome-disk-utility” package in Ubuntu: Confirmed Bug description: After upgrade from ubuntu 13.10 to 14.04 lts, I am unable to ulock my luks device. It gives the following error message: Error unlocking /dev/sda6: Error spawning command-line `cryptsetup luksOpen /dev/sda6 luks-9082ff43-d991-4bf1-8bb6-ef8452e3e11a ': Failed to execute child process cryptsetup (No such file or directory) (g-exec-error-quark, 8) Then I noticed that the package cryptsetup was not installed in my system. cryptsetup should be included and installed as default in ubuntu 14.04 lts, as it was in the previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cryptsetup (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 20 13:21:55 2014 InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1310174/+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 1375601] [NEW] Wifi gets disconnected on random
Public bug reported: Wifi gets disconnected randomly on xubuntu 14.10 beta 2. Not experienced this problem while running windows.Laptop is HP DV5 pavilion. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue Sep 30 10:03:51 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-09-26 (3 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.4 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 17b2f3d58-b9ed-4cda-802d-53c3f96d25e7 802-3-ethernet1412028845 Tue 30 Sep 2014 01:14:05 AM ASTyes no /org/freedesktop/NetworkManager/Settings/1 Zain Broadband 4G 1f3af6ec-07d7-4539-a1ca-8dc6f6ad0f45 802-11-wireless 1412060346 Tue 30 Sep 2014 09:59:06 AM ASTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- 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/1375601 Title: Wifi gets disconnected on random Status in “network-manager” package in Ubuntu: New Bug description: Wifi gets disconnected randomly on xubuntu 14.10 beta 2. Not experienced this problem while running windows.Laptop is HP DV5 pavilion. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue Sep 30 10:03:51 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-09-26 (3 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.4 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 17b2f3d58-b9ed-4cda-802d-53c3f96d25e7 802-3-ethernet1412028845 Tue 30 Sep 2014 01:14:05 AM ASTyes no /org/freedesktop/NetworkManager/Settings/1 Zain Broadband 4G 1f3af6ec-07d7-4539-a1ca-8dc6f6ad0f45 802-11-wireless 1412060346 Tue 30 Sep 2014 09:59:06 AM ASTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1375601/+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 1375571] Re: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d
Libreoffice *doesn't* hardcode shlibs in its control file like the flash package does. So this is not comparable. Also libreoffice-core depends on libnss3 (= 2:3.13.4-2~) | libnss3-1d (= 3.12.0~1.9b1) which is what nss defines and causes with libnss3.so libnss3 (= 2:3.13.4-2~) | libnss3-1d #MINVER#! -- 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/1375571 Title: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d Status in “libreoffice” package in Ubuntu: New Bug description: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1375571/+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 1076458] Re: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()
I reproduced this crash on my local Precise machine: gnome-control-center (gnome-control-center:501): Gtk-WARNING **: Overriding tab label for notebook (gnome-control-center:501): Gtk-WARNING **: Overriding tab label for notebook ** (gnome-control-center:501): CRITICAL **: nm_device_get_udi: assertion `NM_IS_DEVICE (device)' failed Segmentation fault -- 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/1076458 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Status in “network-manager” source package in Trusty: Invalid Status in “network-manager” package in Debian: Fix Released Bug description: [Impact] * gnome-control-center will crash when you get into network panel. [Test Case] * open gnome-control-center * click network --2 * go back to main panel --3 * repeat step 2 and 3 [Regression Potential] * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696143 it has been accepted by upstream for a very long time. And our qe has verified it. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1076458/+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 1076458] Re: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()
More details about crash: Program received signal SIGSEGV, Segmentation fault. 0x7fffd582323e in nm_device_get_udi () from /usr/lib/libnm-glib.so.4 (gdb) bt #0 0x7fffd582323e in nm_device_get_udi () from /usr/lib/libnm-glib.so.4 #1 0x7fffd5ed5e10 in ?? () from /usr/lib/control-center-1/panels/libnetwork.so #2 0x761f7ca2 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x76208d71 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x76211069 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x76211212 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x761fc957 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x761fe233 in g_object_notify () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7fffd581c08b in ?? () from /usr/lib/libnm-glib.so.4 #9 0x75f3ad13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x75f3b060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x75f3b124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x764cedd4 in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0xb7aa in main () -- 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/1076458 Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi() Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Status in “network-manager” source package in Trusty: Invalid Status in “network-manager” package in Debian: Fix Released Bug description: [Impact] * gnome-control-center will crash when you get into network panel. [Test Case] * open gnome-control-center * click network --2 * go back to main panel --3 * repeat step 2 and 3 [Regression Potential] * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696143 it has been accepted by upstream for a very long time. And our qe has verified it. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1076458/+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 1375571] Re: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d
Rico, thanks for the explanation. -- 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/1375571 Title: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d Status in “libreoffice” package in Ubuntu: New Bug description: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1375571/+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 1365490] Re: ubuntu 12.04.5 broken on VMware
[Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+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 1303567]
Created attachment 107084 Fills with transparency fail to show up in presentation This slide has a faux timeline at the bottom that is basically two rectangles with gradient fills and transparency. I have been using this slide with earlier versions of Impress for about 2 years, with no problems. Now that I've moved to 4.3.1.2 it suddenly doesn't display properly. I have about 500 slides for a workshop I am giving, and I have had the same problem with about a dozen other slides as well. -- 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/1303567 Title: [Upstream] Impress changes background color in Slide Show Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:4.2.3~rc2-0ubuntu1 Candidate: 1:4.2.3~rc2-0ubuntu1 Version table: *** 1:4.2.3~rc2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen via a terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1303567/+attachment/4072202/+files/test_impress_vintage_14.04.odp loimpress --nologo test_impress_vintage_14.04.odp is the slide look exactly the same in editing mode, as it does when in Slide Show (F5). 4) What happens instead is in Slide Show it looks like the background color changes to white, and the red ribbon in the top right changes color to black. The background doesn't change color if one converts the file to PPT and opens in Microsoft Office PowerPoint 2003 (11.5529.8179) via WINE. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1303567/+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 1296487] Re: Initial zoom level is slightly under 100%
** Also affects: eog via https://bugzilla.gnome.org/show_bug.cgi?id=733290 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: Unknown Status in “eog” package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+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 1373318] Re: Udisks2 prevents HDDs from going to standby because of polling SMART information
** Description changed: 1) Ubuntu Version: Description: Ubuntu 14.04.1 LTS Release: 14.04 2) Package Version udisks2: Installiert: 2.1.3-1 Installationskandidat: 2.1.3-1 Versionstabelle: *** 2.1.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status 3) What I expected to happen: My two Seagate drives go to sleep after 10 minutes of inactivity. 4) What happened instead: The drives stay on all the time. The full story: The problem is that the minimum time for the drives to go to sleep is 10 minutes, but they are kept awake by the udisks2 daemon which polls them every 10 minutes for SMART data, resetting the idle timer by doing so. Also this might not happen to all drives, there should be a workaround. Would be great if the patch proposed here [1] would also be integrated into udisks2. A more universal approach might be to make the polling interval configurable with 0=polling disabled. Disabling SMART for the disks works partially: a) The following UDEV flags don't have any effect: E: ID_ATA_FEATURE_SET_SMART=0 E: ID_ATA_FEATURE_SET_SMART_ENABLED=0 E: UDISKS_DISABLE_POLLING=1 E: UDISKS_IGNORE=1 b) The following works: (Note: without killing the daemon, according to udisksctl monitor it keeps polling. By polling, the SMART support is reactivated, which seems to be some unexpected behaviour from libatasmart [2]) - sudo killall udiskd + sudo killall udisksd sudo smartctl --smart=off /dev/sdb # verify sudo smartctl --all /dev/sdb | grep SMART support I think it is quite a bad workaround to kill the deamon after every reboot to be able to diable SMART. And disabling SMART is not good either, but it would be fine for me as workaround. [1] https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 [2] can be verified with sudo smartctl --smart=off /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support sudo skdump --overall /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support PS: This is mainly about the old udisks1, but may provide some additional information: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 This is about gnome-disk-utility, but the underlying problem seems udisks2 https://bugzilla.redhat.com/show_bug.cgi?id=1047339 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1373318 Title: Udisks2 prevents HDDs from going to standby because of polling SMART information Status in “udisks2” package in Ubuntu: New Bug description: 1) Ubuntu Version: Description: Ubuntu 14.04.1 LTS Release: 14.04 2) Package Version udisks2: Installiert: 2.1.3-1 Installationskandidat: 2.1.3-1 Versionstabelle: *** 2.1.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status 3) What I expected to happen: My two Seagate drives go to sleep after 10 minutes of inactivity. 4) What happened instead: The drives stay on all the time. The full story: The problem is that the minimum time for the drives to go to sleep is 10 minutes, but they are kept awake by the udisks2 daemon which polls them every 10 minutes for SMART data, resetting the idle timer by doing so. Also this might not happen to all drives, there should be a workaround. Would be great if the patch proposed here [1] would also be integrated into udisks2. A more universal approach might be to make the polling interval configurable with 0=polling disabled. Disabling SMART for the disks works partially: a) The following UDEV flags don't have any effect: E: ID_ATA_FEATURE_SET_SMART=0 E: ID_ATA_FEATURE_SET_SMART_ENABLED=0 E: UDISKS_DISABLE_POLLING=1 E: UDISKS_IGNORE=1 b) The following works: (Note: without killing the daemon, according to udisksctl monitor it keeps polling. By polling, the SMART support is reactivated, which seems to be some unexpected behaviour from libatasmart [2]) sudo killall udisksd sudo smartctl --smart=off /dev/sdb # verify sudo smartctl --all /dev/sdb | grep SMART support I think it is quite a bad workaround to kill the deamon after every reboot to be able to diable SMART. And disabling SMART is not good either, but it would be fine for me as workaround. [1] https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 [2] can be verified with sudo smartctl --smart=off /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support sudo skdump --overall /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support PS: This is mainly about the old udisks1, but may provide some additional information: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 This is about gnome-disk-utility, but the underlying problem seems udisks2
[Desktop-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%
I can't reproduce the issue with High Contrast theme. Adding light- themes task here. ** Also affects: light-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: Unknown Status in “eog” package in Ubuntu: Confirmed Status in “light-themes” package in Ubuntu: New Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+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 1375637] [NEW] Premature end of data in tag file line 247651 will libxml2
Public bug reported: Hello, I'm getting the following behaviour of createrepo on Ubuntu 14.04.1 LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main). createrepo -g /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml \ -o /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ I/O error : No such file or directory (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag package line 246828 (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag filelists line 2 Spawning worker 0 with 54 pkgs Spawning worker 1 with 54 pkgs Spawning worker 2 with 54 pkgs Spawning worker 3 with 54 pkgs Spawning worker 4 with 54 pkgs Spawning worker 5 with 54 pkgs Spawning worker 6 with 54 pkgs Spawning worker 7 with 54 pkgs Spawning worker 8 with 54 pkgs Spawning worker 9 with 54 pkgs Spawning worker 10 with 53 pkgs Spawning worker 11 with 53 pkgs Spawning worker 12 with 53 pkgs Spawning worker 13 with 53 pkgs Spawning worker 14 with 53 pkgs Spawning worker 15 with 53 pkgs Spawning worker 16 with 53 pkgs Spawning worker 17 with 53 pkgs Spawning worker 18 with 53 pkgs Spawning worker 19 with 53 pkgs Spawning worker 20 with 53 pkgs Spawning worker 21 with 53 pkgs Spawning worker 22 with 53 pkgs Spawning worker 23 with 53 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Traceback (most recent call last): File /usr/share/createrepo/genpkgmetadata.py, line 308, in module main(sys.argv[1:]) File /usr/share/createrepo/genpkgmetadata.py, line 280, in main mdgen.doRepoMetadata() File /usr/lib/python2.7/dist-packages/createrepo/__init__.py, line 999, in doRepoMetadata rp.getFilelists(complete_path, csum) File /usr/lib/python2.7/dist-packages/sqlitecachec.py, line 55, in getFilelists self.repoid)) TypeError: Parsing filelists.xml error: Premature end of data in tag file line 247651 Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid. Comparing patchsets in debian package sources between 2.9.1+dfsg1 and 2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one of them helps in my problem: 2.9.1+dfsg1-3ubuntu4.3: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-Fix-an-error-in-xmlCleanupParser.patch 0003-Fix-missing-break-on-last-function-for-attributes.patch 0004-xmllint-memory-should-fail-on-empty-files.patch 0005-properly-quote-the-namespace-uris-written-out-during.patch 0006-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0006-fix-python-multiarch-includes.patch 0007-Fix-XPath-optimization-with-predicates.patch CVE-2014-0191.patch lp1321869.patch xmllint_pretty.patch 2.9.1+dfsg1: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-fix-python-multiarch-includes.patch 0003-Fix-an-error-in-xmlCleanupParser.patch 0004-Fix-missing-break-on-last-function-for-attributes.patch 0005-xmllint-memory-should-fail-on-empty-files.patch 0006-properly-quote-the-namespace-uris-written-out-during.patch 0007-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0008-missing-else-in-xlink.c.patch 0009-Catch-malloc-error-and-exit-accordingly.patch 0010-Fix-handling-of-mmap-errors.patch 0011-Avoid-crash-if-allocation-fails.patch 0012-Fix-a-possible-NULL-dereference.patch 0013-Clear-up-a-potential-NULL-dereference.patch 0014-Fix-XPath-optimization-with-predicates.patch 0015-xmllint-pretty-crashed-without-following-numeric-arg.patch 0016-Fix-potential-NULL-pointer-dereferences-in-regexp-co.patch 0017-Fix-a-potential-NULL-dereference-in-tree-code.patch 0018-Fix-pointer-dereferenced-before-null-check.patch 0019-Fix-a-bug-loading-some-compressed-files.patch 0020-Avoid-a-possibility-of-dangling-encoding-handler.patch 0021-Fix-a-couple-of-missing-NULL-checks.patch 0022-adding-init-calls-to-xml-and-html-Read-parsing-entry.patch 0023-Handling-of-XPath-function-arguments-in-error-case.patch 0024-Missing-initialization-for-the-catalog-module.patch 0025-Fix-an-fd-leak-in-an-error-case.patch 0026-fixing-a-ptotential-uninitialized-access.patch 0027-Fix-xmlTextWriterWriteElement-when-a-null-content-is.patch 0028-Avoid-a-possible-NULL-pointer-dereference.patch 0029-Do-not-fetch-external-parameter-entities.patch 0030-Avoid-Possible-null-pointer-dereference-in-memory-de.patch 0031-xmllint-was-not-parsing-the-c14n11-flag.patch
[Desktop-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2
** Summary changed: - Premature end of data in tag file line 247651 will libxml2 + Premature end of data in tag file line 247651 with libxml2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1375637 Title: Premature end of data in tag file line 247651 with libxml2 Status in “libxml2” package in Ubuntu: New Bug description: Hello, I'm getting the following behaviour of createrepo on Ubuntu 14.04.1 LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main). createrepo -g /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml \ -o /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ I/O error : No such file or directory (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag package line 246828 (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag filelists line 2 Spawning worker 0 with 54 pkgs Spawning worker 1 with 54 pkgs Spawning worker 2 with 54 pkgs Spawning worker 3 with 54 pkgs Spawning worker 4 with 54 pkgs Spawning worker 5 with 54 pkgs Spawning worker 6 with 54 pkgs Spawning worker 7 with 54 pkgs Spawning worker 8 with 54 pkgs Spawning worker 9 with 54 pkgs Spawning worker 10 with 53 pkgs Spawning worker 11 with 53 pkgs Spawning worker 12 with 53 pkgs Spawning worker 13 with 53 pkgs Spawning worker 14 with 53 pkgs Spawning worker 15 with 53 pkgs Spawning worker 16 with 53 pkgs Spawning worker 17 with 53 pkgs Spawning worker 18 with 53 pkgs Spawning worker 19 with 53 pkgs Spawning worker 20 with 53 pkgs Spawning worker 21 with 53 pkgs Spawning worker 22 with 53 pkgs Spawning worker 23 with 53 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Traceback (most recent call last): File /usr/share/createrepo/genpkgmetadata.py, line 308, in module main(sys.argv[1:]) File /usr/share/createrepo/genpkgmetadata.py, line 280, in main mdgen.doRepoMetadata() File /usr/lib/python2.7/dist-packages/createrepo/__init__.py, line 999, in doRepoMetadata rp.getFilelists(complete_path, csum) File /usr/lib/python2.7/dist-packages/sqlitecachec.py, line 55, in getFilelists self.repoid)) TypeError: Parsing filelists.xml error: Premature end of data in tag file line 247651 Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid. Comparing patchsets in debian package sources between 2.9.1+dfsg1 and 2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one of them helps in my problem: 2.9.1+dfsg1-3ubuntu4.3: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-Fix-an-error-in-xmlCleanupParser.patch 0003-Fix-missing-break-on-last-function-for-attributes.patch 0004-xmllint-memory-should-fail-on-empty-files.patch 0005-properly-quote-the-namespace-uris-written-out-during.patch 0006-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0006-fix-python-multiarch-includes.patch 0007-Fix-XPath-optimization-with-predicates.patch CVE-2014-0191.patch lp1321869.patch xmllint_pretty.patch 2.9.1+dfsg1: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-fix-python-multiarch-includes.patch 0003-Fix-an-error-in-xmlCleanupParser.patch 0004-Fix-missing-break-on-last-function-for-attributes.patch 0005-xmllint-memory-should-fail-on-empty-files.patch 0006-properly-quote-the-namespace-uris-written-out-during.patch 0007-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0008-missing-else-in-xlink.c.patch 0009-Catch-malloc-error-and-exit-accordingly.patch 0010-Fix-handling-of-mmap-errors.patch 0011-Avoid-crash-if-allocation-fails.patch 0012-Fix-a-possible-NULL-dereference.patch 0013-Clear-up-a-potential-NULL-dereference.patch 0014-Fix-XPath-optimization-with-predicates.patch 0015-xmllint-pretty-crashed-without-following-numeric-arg.patch 0016-Fix-potential-NULL-pointer-dereferences-in-regexp-co.patch 0017-Fix-a-potential-NULL-dereference-in-tree-code.patch 0018-Fix-pointer-dereferenced-before-null-check.patch 0019-Fix-a-bug-loading-some-compressed-files.patch 0020-Avoid-a-possibility-of-dangling-encoding-handler.patch
[Desktop-packages] [Bug 1375571] Re: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d
** Changed in: libreoffice (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1375571 Title: libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d Status in “libreoffice” package in Ubuntu: Invalid Bug description: The last version of LibreOffice for Trusty (14.04 LTS) in libreoffice-4-3 PPA, 4.3.1~rc2-0ubuntu1~trusty1, depends on libnspr4-0d and libnss3-1d. libreoffice-core should depend on libnspr4 and libnss3 instead of libnspr4-0d and libnss3-1d, because the latter are transitional packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1375571/+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 1341550] Re: Numpad doesn't work in launcher
** Changed in: unity Status: New = Fix Released ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1341550 Title: Numpad doesn't work in launcher Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: On Ubuntu 14.04, with all updates installed: 1. Start the launcher by hitting super. 2. Type something on the numpad (incl. Enter). 3. Nothing happens. I don't think that this behavior is intended, is it? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1341550/+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 1375577] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: New = Confirmed -- 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/1375577 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: not sure ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.16.0-18-generic Date: Tue Sep 30 00:30:54 2014 InstallationDate: Installed on 2013-11-27 (306 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-09-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1375577/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Branch linked: lp:ubuntu/utopic-proposed/gnome-desktop3 -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese * eog * epiphany-browser * evince * gnome-clocks * gnome-contacts * gnome-control-center * gnome-documents * gnome-font-viewer * gnome-panel * gnome-photos * gnome-screensaver * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter * nautilus * unity * unity-control-center * unity-settings-daemon I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 800064] Re: touchpad rotation when monitor rotated
** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/800064 Title: touchpad rotation when monitor rotated Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: when the monitor is rotated to a portrait orientation using gnome- display-properties (changing the rotation dropdown), and then i physically rotate my laptop, any connected usb mice then move correctly across the portrait screen- there are no issues with rotation for external mice. however, ubuntu (maverick at least) does not account for the fact that if you physically rotate your monitor, then you're obviously going to need to physically rotate a laptop's touchpad as well and thus the internal touchpad does not properly work when the laptop's monitor is in a portrait mode- up on the rotated touchpad = left, etc not sure of what package the bug is in - probably x.org ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ubuntu-desktop 1.207 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Tue Jun 21 08:52:53 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/800064/+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 1371919] Re: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD
does your amd r6xx hdmi support multi channel LPCM? the speaket allocation of your hdmi tv is not really needed if you hdmi codec only support stereo ode 0x02 [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=0, channel=0 Digital: Enabled Digital category: 0x0 IEC Coding Type: 0x0 Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital Control: name=HDMI/DP,pcm=3 Jack, index=0, device=0 Control: name=IEC958 Playback Con Mask, index=0, device=0 Control: name=IEC958 Playback Pro Mask, index=0, device=0 Control: name=IEC958 Playback Default, index=0, device=0 Control: name=IEC958 Playback Switch, index=0, device=0 Control: name=ELD, index=0, device=3 Pincap 0x0094: OUT Detect HDMI Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=01, enabled=1 Connection: 1 0x02 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371919 Title: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I have a gigabyte f2a88xn motherboard with built-in audio. In pavucontrol, under Configuration - Built-in audio (the first), there is Digital Stereo (HDMI) Output. When I disable it, the kern.log continuously reports HDMI ATI/AMD: no speaker allocation for ELD. This happens almost every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:08:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371919/+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 1371919] Re: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD
post output of xrandr --verbose -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371919 Title: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I have a gigabyte f2a88xn motherboard with built-in audio. In pavucontrol, under Configuration - Built-in audio (the first), there is Digital Stereo (HDMI) Output. When I disable it, the kern.log continuously reports HDMI ATI/AMD: no speaker allocation for ELD. This happens almost every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:08:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371919/+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 1375652] [NEW] [Utopic] nouveau flush timeout lockups
Public bug reported: Needs more investigation but the system feels sluggish (video operations not always smooth). This morning I had a crash in firefox (may not be related) and it does not always seem to be reproducible. Yesterday I was able to run glxgears and play a video stream through firefox for quite some time without issues. So HW failure from old age might be a reason, too. With the initial install the lockups always seemed to happen when opening a selection dropbox (like the timeout for blanking the screen in the settings). Yesterday (after getting console to be a serial one) the lockup happened on the youtube front-page. After a reboot it did not happen again and today (after dist-upgrading) it just happened again (on some youtube page). For yesterday and today, mouse still moved but gui was not responding. Also would not allow to switch to any vt. Serial console was still working and showed: nouveau [W_PCIEGART] [:01:00.0] flush timeout, 0x0002 Today also (after a while): nouveau E[Xorg[1500]] failed to idle channel 0x [Xorg[1500]] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 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: Tue Sep 30 10:40:50 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41 [GeForce 6800] [10de:00c1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:2a0c] InstallationDate: Installed on 2014-09-25 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) Lsusb: Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller Bus 002 Device 002: ID 8054:0001 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic root=/dev/mapper/username--vg-root ro priority=low hpet=force console=ttyS0,115200n8 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1006 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1006:bd03/03/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System name dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Sep 30 10:39:42 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 04d9:1400KEYBOARD, id 8 inputHID 04d9:1400KEYBOARD, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: nouveau ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1375652 Title: [Utopic] nouveau flush timeout lockups Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Needs more investigation but
[Desktop-packages] [Bug 1370852] Re: Scans all user accounts when not required
** Branch linked: lp:ubuntu/utopic-proposed/lightdm -- 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/1370852 Title: Scans all user accounts when not required Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Trusty: Triaged Status in “lightdm” source package in Utopic: Triaged Bug description: On startup LightDM gets the list of users in the shared data code. This causes all the user properties to be loaded, in the case of not using accounts service all the .dmrc files are accessed. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370852/+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 1305006] Re: Crashes running display server scripts for non X servers
** Branch linked: lp:ubuntu/utopic-proposed/lightdm -- 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/1305006 Title: Crashes running display server scripts for non X servers Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Trusty: Triaged Status in “lightdm” source package in Utopic: Triaged Bug description: switched from Unity 8 preview session to Unity 7. I am using Nouveau graphics drivers. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 9 06:53:22 2014 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2014-04-07 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x41d419: mov0x30(%rax),%rax PC (0x0041d419) ok source 0x30(%rax) (0x0030) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () ?? () ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: lightdm crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1305006/+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 1332721] Re: Add patch to allow toolbar dragging
On Mon, Sep 29, 2014 at 07:33:39PM -, Adam Smith wrote: Hi Iain, I use it with the Mate desktop, so try something like caja..but I can compile it myself, I'm not sure if the versions in the Ubuntu repo uses GTK2 or 3I'm guessing it will still be 2. It is, and I'm afraid I can't get the patch as attached to this bug to work with caja. Could you prepare a debdiff on top of the gtk+2.0 package in Utopic? I think that'd be easier at this point. If you need help you can come to #ubuntu-desktop on Freenode IRC where we hang out. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1332721 Title: Add patch to allow toolbar dragging Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: Ubuntu already has a patch - 062_dnd_menubar.patch - that allows the window to be dragged by clicking on empty space in the menubar. The attached patch builds on this and allows empty space in the toolbar to be also dragged. It is essentially commit 7491e9e97aa6b0f9950897c4f1282b470c79d451 that went into gtk+3.0 way back in 2010. This would make GTK2 themes behave much more like GTK3 themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1332721/+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 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
Still does not work on 14.04. My solution is to disable socket in audio.conf, then I can connect, but not with the default GUI thing. Using the bluetooth icon in the titlebar, I connect, and it shows up as connected. However, using any other tool (blueman-manager, pactl list, pavucontrol) it is obvious it fails to connect, a sink is not established, and the module is not loaded. Sometimes it successfully connects using headset service only, but fails on the A2DP, and still shows up as successful. So it seems it tries to connect, but does not perform any check if it actually succeded or not. This is a problem in Unity i think. Using blueman-manager, I can connect, but get this error from bluetoothd: bluetoothd[14256]: Unable to select SEP This is mentioned here and is a separate bug: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059 The fix for that seems to be to manually load module-bluetooth-discover, and things work. Still, it would be nice to get some checks in the default applet if it actually connects or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in “pulseaudio” package in Ubuntu: Confirmed Status in “pulseaudio” package in Debian: Fix Released Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will show in the PulseAudio mixer * After connecting the external speaker to the audio sink, I can also see the device in the Play sound through listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose Audio Profile from the context menu and try to select High Fidelity Playback (A2DP) as the new profile, I get an error message stating failed to change profile to a2dp I've already added Enable=Socket in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty) Status: New = Confirmed -- 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty) Status: New = Confirmed -- 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Trusty) Status: New = Confirmed -- 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 956618]
I don't think I have to say anything now about this. Thanks. -- 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/956618 Title: Nickname not over-riding names in email address Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: New Bug description: From what I have read in the support forum the nickname should take priority in the search for an email address in the to: field. It does not appear to work any more. Example: One friend's address is Markm...@.com. The other is Jamesjames.m...@.com. Both are in my address book with Mark entered as the nickname of m...@.com and James as nickname for james.m...@.com. If I type james in the To: field I get james.mark as a first entry in the list of available addresses. If I type mark I get the same address again, when I would prefer the first optional address to be m...@.com Reason it is needed: I am trying to avoid sending emails meant for m...@.com to James.mark because I do not notice in time that I have defaulted to the first entry in the list of available addresses. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 10.0.2+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20 Uname: Linux 3.0.0-16-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 BuildID: 20120216123548 Date: Fri Mar 16 00:31:06 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/956618/+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 1375672] [NEW] gftp-gtk crashes on host connect with SSH
Public bug reported: GFTP crashes when connecting to any host using protocol SSH2. Error messages on console: (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Attempt to unlock mutex that was not locked zsh: abort (core dumped) gftp ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gftp-gtk 2.0.19-4ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 11:48:34 2014 InstallationDate: Installed on 2011-04-05 (1273 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gftp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gftp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Bug watch added: Debian Bug tracker #763371 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763371 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gftp in Ubuntu. https://bugs.launchpad.net/bugs/1375672 Title: gftp-gtk crashes on host connect with SSH Status in “gftp” package in Ubuntu: New Bug description: GFTP crashes when connecting to any host using protocol SSH2. Error messages on console: (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Attempt to unlock mutex that was not locked zsh: abort (core dumped) gftp ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gftp-gtk 2.0.19-4ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 11:48:34 2014 InstallationDate: Installed on 2011-04-05 (1273 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gftp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gftp/+bug/1375672/+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 1375672] Re: gftp-gtk crashes on host connect with SSH
See also: Debian Bug report #763371 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763371 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gftp in Ubuntu. https://bugs.launchpad.net/bugs/1375672 Title: gftp-gtk crashes on host connect with SSH Status in “gftp” package in Ubuntu: New Bug description: GFTP crashes when connecting to any host using protocol SSH2. Error messages on console: (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (gftp-gtk:19977): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Attempt to unlock mutex that was not locked zsh: abort (core dumped) gftp ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gftp-gtk 2.0.19-4ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 11:48:34 2014 InstallationDate: Installed on 2011-04-05 (1273 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gftp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gftp/+bug/1375672/+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 951585] Re: gvfsd-afp consumes 100% of processor cycles
Same problem on ubuntu 14.04 64b connect to Synologie NAS = 100% CPU activity because of gvfs-afp and gvfs-browse. Some time I've diffulcty to unmount and have the message unable to unmount because of the broken pipe error. I've to kill or reboot... Same issu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680389 https://bugzilla.redhat.com/show_bug.cgi?id=1001320 https://bugzilla.gnome.org/show_bug.cgi?id=710490 ** Bug watch added: Debian Bug tracker #680389 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680389 ** Bug watch added: Red Hat Bugzilla #1001320 https://bugzilla.redhat.com/show_bug.cgi?id=1001320 ** Bug watch added: GNOME Bug Tracker #710490 https://bugzilla.gnome.org/show_bug.cgi?id=710490 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/951585 Title: gvfsd-afp consumes 100% of processor cycles Status in “gvfs” package in Ubuntu: Confirmed Bug description: Happens on an irregular basis on 12.04 and I think I've experienced it on 11.10. For no reason gvfsd-afp starts up. Cooling fan kicks in, system becomes laggy. Easily cured using system monitor and killing the process. Someone on the Ubuntu Forum asked if I have a Mac on the network and the answer is yes, an iMac and there are shares on that machine I can access. Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+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 1371032] Re: Cannot send MMS from Yoigo
Victor provided the log so setting this to confirmed. If you have all
the information you need then set it to Triaged
** Changed in: ofono (Ubuntu)
Status: Incomplete = Confirmed
--
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/1371032
Title:
Cannot send MMS from Yoigo
Status in “network-manager” package in Ubuntu:
New
Status in “ofono” package in Ubuntu:
Confirmed
Bug description:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
AccessPointName = internet
Name = Yoigo Internet
Password =
Protocol = ip
IPv6.Settings = { }
Type = internet
Active = 1
Username =
Settings = { DomainNameServers=217.168.13.34,46.6.113.2,
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31
Interface=ccmni0 }
[ /ril_0/context2 ]
AccessPointName = mms
MessageCenter = http://mmss/
Name = Yoigo MMS
Password =
Protocol = ip
MessageProxy = 193.209.134.141:80
IPv6.Settings = { }
Type = mms
Active = 0
Username =
Settings = { }
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not
attached
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
/ril_0 1
Additional info:
- I didn't see any error in the messaging app.
- Couldn't send nor receive MMS.
- 3G connection is activated, but usually after a reboot. After a while, it
looses it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1371032/+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 1372164] Re: evince crashed with SIGSEGV in ev_window_title_sanitize_title()
*** This bug is a duplicate of bug 1369894 *** https://bugs.launchpad.net/bugs/1369894 ** Attachment removed: Project used to create the error https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1372164/+attachment/4210790/+files/presentation.tgz ** This bug has been marked a duplicate of bug 1369894 evince crashed with SIGSEGV in ev_window_title_sanitize_title() ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1372164 Title: evince crashed with SIGSEGV in ev_window_title_sanitize_title() Status in “evince” package in Ubuntu: New Bug description: I am working on an presentation with beamer latex. This means I compile my presentation and view the resulting PDF in evince. Until today, evince was able to auto refresh the content after compilation, but this time it crashed. In the process of creating a complete presentation the generation script runs pdflatex three times (if necessary) so all table of contents and references are in perfect order. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: evince 3.13.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-16.22-lowlatency 3.16.2 Uname: Linux 3.16.0-16-lowlatency i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Sep 21 20:23:36 2014 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-04-18 (521 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-lowlatency root=UUID=fa400436-f6bc-4f1e-9e78-5284a6e9f17c ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x8079654: pushl (%eax) PC (0x08079654) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination (%esp) (0xbf85dfd4) ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () ?? () g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: evince crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1372164/+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 1370702] Re: evince crashed with SIGSEGV in ev_window_title_sanitize_title()
*** This bug is a duplicate of bug 1369894 *** https://bugs.launchpad.net/bugs/1369894 ** This bug has been marked a duplicate of bug 1369894 evince crashed with SIGSEGV in ev_window_title_sanitize_title() ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1370702 Title: evince crashed with SIGSEGV in ev_window_title_sanitize_title() Status in “evince” package in Ubuntu: New Bug description: el pc despues de hibernar o volver de la suspencion, presenta error interno ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: evince 3.13.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Sep 17 14:49:26 2014 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2014-08-07 (41 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=eed2d282-9ad4-4f95-9f39-5be8ee000cc0 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x8079654: pushl (%eax) PC (0x08079654) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination (%esp) (0xbfdf3d64) ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () ?? () g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: evince crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM() 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/evince/+bug/1370702/+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 1369894] Re: evince crashed with SIGSEGV in ev_window_title_sanitize_title()
That has been fixed with https://git.gnome.org/browse/evince/commit/?id=0aafd8809a5464aef05e73c33e501cea0b413059 ** Changed in: evince (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1369894 Title: evince crashed with SIGSEGV in ev_window_title_sanitize_title() Status in Evince document viewer: Fix Released Status in “evince” package in Ubuntu: Fix Committed Bug description: Evince just crashed while it was open and idle. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: evince 3.13.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 16 09:24:16 2014 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2010-10-25 (1421 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash SegvAnalysis: Segfault happened at: 0x43984b: mov(%rax),%rdi PC (0x0043984b) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () ?? () g_closure_invoke (closure=0x1f56320, return_value=0x0, n_param_values=2, param_values=0x7fff82bc6540, invocation_hint=0x7fff82bc64e0) at /build/buildd/glib2.0-2.41.4/./gobject/gclosure.c:768 signal_emit_unlocked_R (node=node@entry=0x1b12f30, detail=detail@entry=1242, instance=instance@entry=0x1c93aa0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff82bc6540) at /build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3553 g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fff82bc66d0) at /build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3309 Title: evince crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-15 (0 days ago) UserGroups: adm admin audio cdrom dialout kismet lp lpadmin plugdev sambashare video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1369894/+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 1373225] Re: Unity Control Center icons in the dash don't point to the right section in the Control Center
Ok, thanks, then it all makes sense, and we can just await your upload. -- 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/1373225 Title: Unity Control Center icons in the dash don't point to the right section in the Control Center Status in One Hundred Papercuts: Triaged Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE - In the dash, open one of these applications: Notifications, Online Accounts, Privacy, Security, Sharing. ** EXPECTED BEHAVIOUR ** - Going to the right section in the Control Center. ** REAL BEHAVIOUR ** - You go to the main page in the Control Center. RELEVANT DETAILS - Old icons are still there, and should be removed too. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 24 06:43:11 2014 InstallationDate: Installed on 2013-05-21 (490 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu15 deja-dup 32.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1373225/+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 1375703] Re: chromium-browser crashed with SIGSEGV
*** This bug is a duplicate of bug 1368217 *** https://bugs.launchpad.net/bugs/1368217 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1368217, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1375703/+attachment/4220101/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1375703/+attachment/4220103/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1375703/+attachment/4220106/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1375703/+attachment/4220107/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1375703/+attachment/4220108/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1375703/+attachment/4220112/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1375703/+attachment/4220113/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1368217 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1375703 Title: chromium-browser crashed with SIGSEGV Status in “chromium-browser” package in Ubuntu: New Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Sep 30 12:27:35 2014 ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2013-12-22 (282 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) ProcCmdline: /proc/self/exe --type=gpu-process --channel=13244.0.44323626 --supports-dual-gpus=false --gpu-driver-bug-workarounds=1,11,15 --disable-accelerated-video-decode --gpu-vendor-id=0x8086 --gpu-device-id=0x0126 --gpu-driver-vendor --gpu-driver-version Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 Title: chromium-browser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-14T18:16:36.315577 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1375703/+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 1374927] Re: After changing cell borders in Calc, Metacity stops drawing gnome-panel
Mate has fix for this - https://github.com/mate- desktop/marco/commit/064f1ff4d56da2d0fc6b9cce674c667c5d3c7ec4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1374927 Title: After changing cell borders in Calc, Metacity stops drawing gnome- panel Status in Ubuntu GNOME Flashback: New Status in “metacity” package in Ubuntu: New Bug description: This is a very strange bug, but I can reliably reproduce it on Ubuntu 14.10 amd64 with latest updates. Steps to reproduce: * Log in into GNOME Flashback (Metacity) session. * Open Libreoffice Calc. * Click on the Borders item on the toolbar and select the first option. After that, gnome-panel will be invisible. However, it is still there, and restarting Metacity makes it show again. This does not happen when using Compiz. See the screencast attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1374927/+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 1209008] Re: X fails to detect certain video cards on non-seat0 seats
** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Trusty) Status: New = In Progress ** Changed in: xorg-server (Ubuntu Trusty) Assignee: (unassigned) = Laércio de Sousa (lbssousa) -- 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/1209008 Title: X fails to detect certain video cards on non-seat0 seats Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Trusty: In Progress Status in Fedora: Unknown Bug description: From https://bugs.freedesktop.org/show_bug.cgi?id=66851: I have a multiseat setup with a primary on-board Intel graphics device and a secondary Silicon Motion SM501 graphics card. My SM501 is configured via custom xorg.conf with siliconmotion ddx driver, so it exposes no framebuffer devices to e.g. systemd-logind. The same situation is seen e.g. for a NVIDIA graphics card with proprietary drivers. Every time I configure my system to assign my SM501 card with a secondary seat, i.e. not seat0, my X server fails to start, returning a No devices detected error. Nevertheless, when I assign my SM501 card with seat0 and attach my Intel graphics device to secondary seat (via loginctl), both seats load successfully. Investigating the Xorg-server sources, I've found something related to platform bus. I don't know what is it at all, but whatever it means, my Intel graphics card with its open-source drivers implement it, but my siliconmotion driver doesn't. In its current form, Xorg-server probes for platform bus devices as well as legacy PCI bus ones only for seat0. For other seats, it only probes for platform bus devices, hence it never reaches my SM501 card, returning that No devices found error. I don't know if there's a good reason for probing only platform bus devices on non-seat0 seats, but this brings a problem for multiseat setups like mine. This same problem was encoutered by a user with two NVIDIA cards; see bug #976124. A patch was supplied to the upstream bug report, and this patch seems to fix the problem. Note that this bug only affects detection of cards when X is passed the '-seat' argument with a seat name OTHER than seat0. Thus, this only happens in multiseat setups. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1363721] Re: Duplicate Security Privacy icons in Unity dash
** Changed in: activity-log-manager (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1363721 Title: Duplicate Security Privacy icons in Unity dash Status in Privacy Manager for Zeitgeist: New Status in “activity-log-manager” package in Ubuntu: Fix Committed Bug description: Ubuntu 14.04, activity-log-manager 0.9.7-0ubuntu14. My Unity dash contains two entries for Security Privacy. In /usr/share/applications, there are two .desktop files which this string in them: gnome-activity-log-manager-panel.desktop and unity- activity-log-manager-panel.desktop. Both of these files can be tracked to the 'activity-log-manager' package. I'm thinking gnome-activity-log-manager-panel.desktop should be excluded from Unity, by changing OnlyShowIn=Unity; to NotShowIn=Unity;? To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1363721/+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 1360241] Re: [Regression] LLVM ERROR: Do not know how to split the result of this operator! in executing Ubuntu UI Toolkit tests on x86
Happened now on ubuntu-system-settings-online-accounts autopkgtests, preventing qtbase from moving from -proposed to -release: https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic- adt-ubuntu-system-settings-online- accounts/lastBuild/ARCH=i386,label=adt/console -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1360241 Title: [Regression] LLVM ERROR: Do not know how to split the result of this operator! in executing Ubuntu UI Toolkit tests on x86 Status in “llvm-toolchain-3.5” package in Ubuntu: Confirmed Status in “mesa” package in Ubuntu: Fix Released Bug description: With upgrade to LLVM 3.5, UITK tests start failing with LLVM error. This was reported earlier and the change to 3.5 reverted, but now 3.5 landed again. So we're seeing errors like this: https://launchpadlibrarian.net/182951835/buildlog_ubuntu-utopic-i386.ubuntu-ui-toolkit_1.1.1206%2B14.10.20140822-0ubuntu1_FAILEDTOBUILD.txt.gz To reproduce, simply bzr branch lp:ubuntu-ui-toolkit and run bzr bd which also executes the unit tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1360241/+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 1369894] Re: evince crashed with SIGSEGV in ev_window_title_sanitize_title()
** Branch linked: lp:~ubuntu-desktop/evince/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1369894 Title: evince crashed with SIGSEGV in ev_window_title_sanitize_title() Status in Evince document viewer: Fix Released Status in “evince” package in Ubuntu: Fix Committed Bug description: Evince just crashed while it was open and idle. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: evince 3.13.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 16 09:24:16 2014 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2010-10-25 (1421 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash SegvAnalysis: Segfault happened at: 0x43984b: mov(%rax),%rdi PC (0x0043984b) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () ?? () g_closure_invoke (closure=0x1f56320, return_value=0x0, n_param_values=2, param_values=0x7fff82bc6540, invocation_hint=0x7fff82bc64e0) at /build/buildd/glib2.0-2.41.4/./gobject/gclosure.c:768 signal_emit_unlocked_R (node=node@entry=0x1b12f30, detail=detail@entry=1242, instance=instance@entry=0x1c93aa0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff82bc6540) at /build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3553 g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fff82bc66d0) at /build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3309 Title: evince crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-15 (0 days ago) UserGroups: adm admin audio cdrom dialout kismet lp lpadmin plugdev sambashare video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1369894/+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 1365490] Re: ubuntu 12.04.5 broken on VMware
** Description changed: + [Impact] + + A user might find Ubuntu 12.04.5 unusable on vmware because he would + face a black screen after logging in. Although there is a workaround + (disabling 3D) a user may have given up at that point. + + Backporting will help the user run the distro after upgrading, so I + believe it's highly justified. + + [Test Case] + + On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. + Boot the VM, log in. You'll see a black screen only. + + [Regression Potential] + + The bug affects a function that impots a shared buffer to the 3D driver. + The function is completely broken by the bug. Even if the patch should + introduce another type of breakage, the problem couldn't be much worse + than it already is, and should be confined to the specific function in + question. + + [Other info] + + Due to different stack ordering of automatic variables, the bug may or + may not be visible depending on the C compiler and the level of + optimization used. For example, if -O0 -g is used the bug is not visible + on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. + + [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+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 1375742] [NEW] ibus-daemon uses 100% CPU after a modifier key is pressed
Public bug reported: 1. Open a gtk app like gnome-calculator or gedit 2. Press a modifier key (shift, ctrl...) 3. Watch ibus-daemon and ibus-x11 use 100% cpu 4. Can be stopped by right clicking, or switching windows ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 21:26:06 2014 InstallationDate: Installed on 2014-09-03 (27 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1375742 Title: ibus-daemon uses 100% CPU after a modifier key is pressed Status in “ibus” package in Ubuntu: New Bug description: 1. Open a gtk app like gnome-calculator or gedit 2. Press a modifier key (shift, ctrl...) 3. Watch ibus-daemon and ibus-x11 use 100% cpu 4. Can be stopped by right clicking, or switching windows ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 21:26:06 2014 InstallationDate: Installed on 2014-09-03 (27 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1375742/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Description changed: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome-desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese * eog - * epiphany-browser + * epiphany-browser [x] * evince * gnome-clocks * gnome-contacts * gnome-control-center - * gnome-documents + * gnome-documents [x] * gnome-font-viewer - * gnome-panel - * gnome-photos + * gnome-panel [x] + * gnome-photos [x] * gnome-screensaver * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution - * mutter + * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon + packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese * eog * epiphany-browser [x] * evince * gnome-clocks * gnome-contacts * gnome-control-center * gnome-documents [x] * gnome-font-viewer * gnome-panel [x] * gnome-photos [x] * gnome-screensaver * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1371651] Re: Daily does not boot into graphical interface after installation
zynced to today's daily installed and rebooted still have to service lightdm start still have service lightdm status =stop/waiting doesn't look like it's fixed to me here unfortunately -- 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/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Isn't this really a workaround, rather than a proper fix? Presumably when bi-directional comms are used there is useful info being returned by the printer, so now that it's prevented that will cause the printer to run slower or other problems will be ignored? Will this be taken up with Canon's engineers, or were they not the people who wrote the driver? -- 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/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Triaged Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Description changed: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome-desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese * eog * epiphany-browser [x] * evince - * gnome-clocks + * gnome-clocks [x] * gnome-contacts * gnome-control-center * gnome-documents [x] * gnome-font-viewer * gnome-panel [x] * gnome-photos [x] * gnome-screensaver * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese * eog * epiphany-browser [x] * evince * gnome-clocks [x] * gnome-contacts * gnome-control-center * gnome-documents [x] * gnome-font-viewer * gnome-panel [x] * gnome-photos [x] * gnome-screensaver * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Description changed: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome-desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === - * cheese - * eog - * epiphany-browser [x] - * evince + * cheese [x] + * eog [x] + * epiphany-browser [x] + * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts * gnome-control-center * gnome-documents [x] * gnome-font-viewer * gnome-panel [x] * gnome-photos [x] * gnome-screensaver * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts [x] * gnome-control-center * gnome-documents [x] * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] * gnome-screensaver [x] * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
I ran sudo hda-jack-sense-test -c 0 -d 2 but I got an error ValueError: wrong proc file format ( In-driver Connection: 6) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1365769 Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The problem is that the microphone is not detected after a reboot. As a result, some applications cannot get sound from the microphone. The Input tab of the Sound window lists no device. I have a workround which is to disconnect and then connect the microphone after I have logged in. Interestingly, the audacity application can access the microphone when the system says that the device does not exist ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 00:12:39 2014 InstallationDate: Installed on 2011-07-29 (1133 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio Symptom_Jack: Pink Mic, Rear Symptom_Type: No sound at all Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1375753] [NEW] nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build
Public bug reported: The package was previously all okay but a kernel upgrade broke it somehow. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 DKMSKernelVersion: 3.13.0-36-generic Date: Fri Sep 26 21:18:46 2014 InstallationDate: Installed on 2014-07-27 (65 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (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-updates in Ubuntu. https://bugs.launchpad.net/bugs/1375753 Title: nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: The package was previously all okay but a kernel upgrade broke it somehow. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 DKMSKernelVersion: 3.13.0-36-generic Date: Fri Sep 26 21:18:46 2014 InstallationDate: Installed on 2014-07-27 (65 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu7.1: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1375753/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Description changed: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome-desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] - * epiphany-browser [x] + * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] - * gnome-contacts + * gnome-contacts [x] * gnome-control-center * gnome-documents [x] - * gnome-font-viewer + * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] - * gnome-screensaver + * gnome-screensaver [x] * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts [x] * gnome-control-center * gnome-documents [x] * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] * gnome-screensaver [x] * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1371651] Re: Daily does not boot into graphical interface after installation
@elfy - is plymouth is still crashing for you? $ sudo grep SEGV /var/log/syslog -- 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/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
To be clear, it was always intended that this transition would allow the corresponding update of gnome-control-center and gnome-settings-daemon to 3.12 so FFe ACK for those (they're ~Ubuntu GNOME only - actually also on Edubuntu but they aren't releasing for Utopic) -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts [x] * gnome-control-center * gnome-documents [x] * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] * gnome-screensaver [x] * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1302098] Re: Windows cascading mode cause segfault
** Changed in: compiz Status: Fix Committed = In Progress -- 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/1302098 Title: Windows cascading mode cause segfault Status in Compiz: In Progress Status in “compiz” package in Ubuntu: Confirmed Bug description: I found a critical bug in compiz, the x-window-manager. Ubuntu version : 12.04.4 LTS compiz version : 1:0.9.7.12-0ubuntu3 The test case is as below. 1) Set the window placement option to cascade mode. - run gnome-terminal and then type sudo gconftool-2 --type int --set /apps/compiz-1/plugins/place/screen0/options/mode 0 OR - run gconf-editor(At first, install gconf-editor from software center) and then go through /apps/compiz-1/plugins/place/screen0/options/ and the set modevalue to 0 2) Run gnome-terminal and then repeat opening new windows about 30 times.(using shortcut key Ctrl+Alt+T) (OR run nautilus file manager and then repeat opening new windows about 30 times (using shortcut key Ctrl+N)) It is Note for you: Although you reproduce this bug, your Ubuntu will not break. System restore is very simple. Please try log out and log in again. And then try resetting as following. run gnome-terminal and then type sudo gconftool-2 --type int --set /apps/compiz-1/plugins/place/screen0/options/mode 2 (OR - run gconf-editor(At first, install gconf-editor from software center) and then go through /apps/compiz-1/plugins/place/screen0/options/ and the set modevalue to 2) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1302098/+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 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
Okay, moving to the latest driver did not help. The change to alsa-base.conf did work. I now see the microphone in Sound Settings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1365769 Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The problem is that the microphone is not detected after a reboot. As a result, some applications cannot get sound from the microphone. The Input tab of the Sound window lists no device. I have a workround which is to disconnect and then connect the microphone after I have logged in. Interestingly, the audacity application can access the microphone when the system says that the device does not exist ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 00:12:39 2014 InstallationDate: Installed on 2011-07-29 (1133 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio Symptom_Jack: Pink Mic, Rear Symptom_Type: No sound at all Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1178271] Re: Translation template of signon-ui is not updated
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon-ui (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1178271 Title: Translation template of signon-ui is not updated Status in Ubuntu Translations: New Status in “signon-ui” package in Ubuntu: Confirmed Bug description: The translation template of signon-ui in Raring/Saucy is not updated since early last year. Building the code does not run the po/update- pot.sh script, this needs to be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1178271/+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 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
you have to post output of alsa -info.sh the polling is implemented for vt1708 which does not support unsolicited event, this may mean unsolicited event is broken and you need to fire an upstream bug report -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1365769 Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The problem is that the microphone is not detected after a reboot. As a result, some applications cannot get sound from the microphone. The Input tab of the Sound window lists no device. I have a workround which is to disconnect and then connect the microphone after I have logged in. Interestingly, the audacity application can access the microphone when the system says that the device does not exist ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 00:12:39 2014 InstallationDate: Installed on 2011-07-29 (1133 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio Symptom_Jack: Pink Mic, Rear Symptom_Type: No sound at all Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1330385] Re: Intel GPU crash corrupts fonts
Just had the same error. Here is the requested file. ** Attachment added: card0_error https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1330385/+attachment/4220309/+files/card0_error ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1330385 Title: Intel GPU crash corrupts fonts Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: The bug occurs regularly, without any special action. I'm just working in gnome-terminal und using Firefox. Symptoms: * While working, the system suddenly freezes for a few seconds (like a typical crash in the X system) * Then I can continue work, but with corrupted fonts and views * New windows are sometimes readable again Don't know if the package is correct. Dmesg shows: [ 3647.214489] [drm] stuck on render ring [ 3647.214499] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 3647.214500] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 3647.214501] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel [ 3647.214502] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 3647.214502] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Mon Jun 16 10:22:11 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2014-05-12 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 2356LQG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356LQG 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:bvrG7ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2356LQG:pvrThinkPadT430s:rvnLENOVO:rn2356LQG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356LQG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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.1 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: Mon Jun 16 09:15:09 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8510 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1330385/+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 1375782] [NEW] Unable to perform search error when syncing Evolution with Google Contacts
Public bug reported: Hello, When trying to synchronise Google Contacts with Evolution, I am getting the error message: The backend for this address book was unable to parse this query. GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code16: Invalid request URI or header, or unsupported nonstandard parameter: ?xml version=1.0 encoding=UTF-8? errors xmlns=http://schemas.google.com/g/2005; error domainGData/domain codeinvalid/code internalReasonBad updated-min timestamp format: 2014-09-30T12:48:18.01 00:00/internalReason /error /errors My system is Ubunru 14.10, Evolution 3.12.6. Before updating to Ubuntu 14.10 (in 14.04) it worked without an error. Ruben ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- 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/1375782 Title: Unable to perform search error when syncing Evolution with Google Contacts Status in “evolution” package in Ubuntu: New Bug description: Hello, When trying to synchronise Google Contacts with Evolution, I am getting the error message: The backend for this address book was unable to parse this query. GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code16: Invalid request URI or header, or unsupported nonstandard parameter: ?xml version=1.0 encoding=UTF-8? errors xmlns=http://schemas.google.com/g/2005; error domainGData/domain codeinvalid/code internalReasonBad updated-min timestamp format: 2014-09-30T12:48:18.01 00:00/internalReason /error /errors My system is Ubunru 14.10, Evolution 3.12.6. Before updating to Ubuntu 14.10 (in 14.04) it worked without an error. Ruben To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1375782/+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 1323006] Re: touchpad too sensitive. focus jumps all over document on text input
Well, on trusty XRecord was not working, so -R was a noop. I've uploaded a fix for trusty to ppa:canonical-x/x-staging . Could you try that package and see if you get the same issues as utopic? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1323006 Title: touchpad too sensitive. focus jumps all over document on text input Status in “xserver-xorg-input-synaptics” package in Ubuntu: Fix Released Status in “xserver-xorg-input-synaptics” source package in Trusty: New Bug description: I am a very fast typist. When I type into emacs, gedit, and libreoffice, the focus jumps around when I am typing. I look up and find I have just entered text in a different area. This happens all the time. I have set the touchpad to disable during text input and this doesn't seem to work. Perhaps this command is broken. I have a lenovo x230 tablet computer, with touchpad. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-input-synaptics 1.7.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-2.6-lowlatency 3.15.0-rc6 Uname: Linux 3.15.0-2-lowlatency x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 25 09:27:11 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu InstallationDate: Installed on 2014-04-22 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) LightdmGreeterLog: ** (lightdm-gtk-greeter:1171): WARNING **: Failed to load user image: Failed to open file '/home/susan/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1161): WARNING **: Failed to load user image: Failed to open file '/home/susan/.face': No such file or directory MachineType: LENOVO 3434CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-2-lowlatency root=UUID=7a4f9c50-a2d1-43cb-865b-dbc9949a4cf7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GCET21WW (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 3434CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET21WW(1.10):bd07/25/2012:svnLENOVO:pn3434CTO:pvrThinkPadX230Tablet:rvnLENOVO:rn3434CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3434CTO dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 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-1ubuntu4 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: Sun May 25 09:20:59 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.15.1-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1323006/+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 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch
I guess this is something that would affect also other VP implementations (such as cube), so I think it's better to do this at core level (if applicable). I'm ok with the setting, so we could even enable it by default, eventually. ** Also affects: compiz Importance: Undecided Status: New ** Changed in: unity Status: Triaged = Won't Fix ** Changed in: unity (Ubuntu) Status: Confirmed = Won't Fix ** Changed in: compiz Status: New = Triaged ** Changed in: unity (Ubuntu Precise) Status: Confirmed = Won't Fix ** Changed in: compiz Assignee: (unassigned) = Dariusz Gadomski (dgadomski) ** Changed in: compiz Importance: Undecided = Low ** No longer affects: unity (Ubuntu Precise) ** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1125442 Title: Always Visible and On Top Windows Steal Focus on Workspace Switch Status in Ayatana Design: New Status in Compiz: Triaged Status in Unity: Won't Fix Status in Xubuntu: New Bug description: 1. Open any application (e.g. TextEditor) 2. Right click the title bar 2a. Select Always on Visible Workspace 3. Right click the title bar 3a. Select Always on Top 4. Open a different application (e.g. Terminal) 5. Ensure that window has focus 6. Switch workspaces (Notice: the first application now has focus) 7. Return to first workspace (Notice: the second application does not regain focus) Expected: The initial application should not have ever regained focus, and certainly the second application should have it when returning to that workspace. antarus@mach ~ $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 antarus@mach ~ $ apt-cache policy unity unity: Installed: 5.18.0-0ubuntu2 Candidate: 5.18.0-0ubuntu2 Version table: To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1125442/+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 1371651] Re: Daily does not boot into graphical interface after installation
Deleted exisiting zsynced image and redownloaded todays daily. Reinstalled. Boot fails - same symptoms - lightdm is stop/waiting. Plymouth is 0.9.0-0ubuntu6 sudo grep SEGV /var/log/syslog echoes nothing -- 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/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1373318] Re: Udisks2 prevents HDDs from going to standby because of polling SMART information
So, I did some debugging and I can confirm that changing the houskeeping from 10 minutes to at least 11 minutes fixes the problem for me. I attached a patch that changes the housekeeping to 15 minutes. btw: I cloned from here http://anonscm.debian.org/cgit/pkg-utopia/udisks2.git/ (git://anonscm.debian.org/pkg-utopia/udisks2.git) I hope that's the right repository. ** Attachment added: Changes the housekeeping to 15 minutes https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1373318/+attachment/4220313/+files/seagate15minPatch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1373318 Title: Udisks2 prevents HDDs from going to standby because of polling SMART information Status in “udisks2” package in Ubuntu: New Bug description: 1) Ubuntu Version: Description: Ubuntu 14.04.1 LTS Release: 14.04 2) Package Version udisks2: Installiert: 2.1.3-1 Installationskandidat: 2.1.3-1 Versionstabelle: *** 2.1.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status 3) What I expected to happen: My two Seagate drives go to sleep after 10 minutes of inactivity. 4) What happened instead: The drives stay on all the time. The full story: The problem is that the minimum time for the drives to go to sleep is 10 minutes, but they are kept awake by the udisks2 daemon which polls them every 10 minutes for SMART data, resetting the idle timer by doing so. Also this might not happen to all drives, there should be a workaround. Would be great if the patch proposed here [1] would also be integrated into udisks2. A more universal approach might be to make the polling interval configurable with 0=polling disabled. Disabling SMART for the disks works partially: a) The following UDEV flags don't have any effect: E: ID_ATA_FEATURE_SET_SMART=0 E: ID_ATA_FEATURE_SET_SMART_ENABLED=0 E: UDISKS_DISABLE_POLLING=1 E: UDISKS_IGNORE=1 b) The following works: (Note: without killing the daemon, according to udisksctl monitor it keeps polling. By polling, the SMART support is reactivated, which seems to be some unexpected behaviour from libatasmart [2]) sudo killall udisksd sudo smartctl --smart=off /dev/sdb # verify sudo smartctl --all /dev/sdb | grep SMART support I think it is quite a bad workaround to kill the deamon after every reboot to be able to diable SMART. And disabling SMART is not good either, but it would be fine for me as workaround. [1] https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 [2] can be verified with sudo smartctl --smart=off /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support sudo skdump --overall /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support PS: This is mainly about the old udisks1, but may provide some additional information: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 This is about gnome-disk-utility, but the underlying problem seems udisks2 https://bugzilla.redhat.com/show_bug.cgi?id=1047339 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1373318/+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 1371651] Re: Daily does not boot into graphical interface after installation
@Elf -- if there is no SEGV then this is likely different. A quick test here for me with todays image gets to lightdm ok. So in the short term we should file a new bug for your issue. You may want to put the bug number here for anyone following along. -- 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/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1375805] [NEW] Lightdm fails to start in VirtualBox
Public bug reported: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug iso-testing utopic ** Description changed: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting - once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA + once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same + result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) SourcePackage: lightdm 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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1375805 Title: Lightdm fails to start in VirtualBox Status in “lightdm” package in Ubuntu: New Bug description: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) 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/1375805/+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 1375805] Re: Lightdm fails to start in VirtualBox
** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1375805/+attachment/4220339/+files/dmesg -- 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/1375805 Title: Lightdm fails to start in VirtualBox Status in “lightdm” package in Ubuntu: New Bug description: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) 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/1375805/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Changed in: gnome-control-center (Ubuntu) Status: New = Fix Committed ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Fix Committed -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts [x] * gnome-control-center * gnome-documents [x] * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] * gnome-screensaver [x] * gnome-session-bin * gnome-settings-daemon * indicator-keyboard * evolution * mutter [x] * nautilus * unity * unity-control-center * unity-settings-daemon packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1375805] Re: Lightdm fails to start in VirtualBox
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1375805 ** Tags added: iso-testing -- 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/1375805 Title: Lightdm fails to start in VirtualBox Status in “lightdm” package in Ubuntu: New Bug description: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) 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/1375805/+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 1375784] [NEW] Disk space messages need ordered placeholders
Public bug reported: While translating: https://translations.launchpad.net/ubuntu/utopic/+source/unity-settings- daemon/+pots/unity-settings-daemon I have run into problems with fixed word order: The volume %s has only %s disk space remaining. You may free up some space by emptying the trash. Located in ../plugins/housekeeping/gsd-disk-space.c:590 The volume %s has only %s disk space remaining. Located in ../plugins/housekeeping/gsd-disk-space.c:594 ../plugins/housekeeping/gsd-ldsm-dialog.c:81 Is is possible to have %1$s and %2$s here, so I can reverse the order? The current translation that I'm forced to do is very artificial. ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1375784 Title: Disk space messages need ordered placeholders Status in “unity-settings-daemon” package in Ubuntu: New Bug description: While translating: https://translations.launchpad.net/ubuntu/utopic/+source/unity- settings-daemon/+pots/unity-settings-daemon I have run into problems with fixed word order: The volume %s has only %s disk space remaining. You may free up some space by emptying the trash. Located in ../plugins/housekeeping/gsd-disk-space.c:590 The volume %s has only %s disk space remaining. Located in ../plugins/housekeeping/gsd-disk-space.c:594 ../plugins/housekeeping/gsd-ldsm-dialog.c:81 Is is possible to have %1$s and %2$s here, so I can reverse the order? The current translation that I'm forced to do is very artificial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1375784/+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 1373318] Re: Udisks2 prevents HDDs from going to standby because of polling SMART information
In addition to the above patch, I made the housekeeping more configurable. It adds the commandline parameter housekeeping which can be used to set the amount of minutes of the interval (0=disable housekeeping). Might not be a clean implementation, but at least it's pretty straight forward to get the idea. To apply the changes in the system add --housekeeping=15 to the command lines in /usr/share/dbus-1/system-services/org.freedesktop.UDisks2.service and /lib/systemd/system/udisks2.service ** Patch added: AdjustableHousekeeping.patch https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1373318/+attachment/4220338/+files/AdjustableHousekeeping.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1373318 Title: Udisks2 prevents HDDs from going to standby because of polling SMART information Status in “udisks2” package in Ubuntu: New Bug description: 1) Ubuntu Version: Description: Ubuntu 14.04.1 LTS Release: 14.04 2) Package Version udisks2: Installiert: 2.1.3-1 Installationskandidat: 2.1.3-1 Versionstabelle: *** 2.1.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status 3) What I expected to happen: My two Seagate drives go to sleep after 10 minutes of inactivity. 4) What happened instead: The drives stay on all the time. The full story: The problem is that the minimum time for the drives to go to sleep is 10 minutes, but they are kept awake by the udisks2 daemon which polls them every 10 minutes for SMART data, resetting the idle timer by doing so. Also this might not happen to all drives, there should be a workaround. Would be great if the patch proposed here [1] would also be integrated into udisks2. A more universal approach might be to make the polling interval configurable with 0=polling disabled. Disabling SMART for the disks works partially: a) The following UDEV flags don't have any effect: E: ID_ATA_FEATURE_SET_SMART=0 E: ID_ATA_FEATURE_SET_SMART_ENABLED=0 E: UDISKS_DISABLE_POLLING=1 E: UDISKS_IGNORE=1 b) The following works: (Note: without killing the daemon, according to udisksctl monitor it keeps polling. By polling, the SMART support is reactivated, which seems to be some unexpected behaviour from libatasmart [2]) sudo killall udisksd sudo smartctl --smart=off /dev/sdb # verify sudo smartctl --all /dev/sdb | grep SMART support I think it is quite a bad workaround to kill the deamon after every reboot to be able to diable SMART. And disabling SMART is not good either, but it would be fine for me as workaround. [1] https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 [2] can be verified with sudo smartctl --smart=off /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support sudo skdump --overall /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support PS: This is mainly about the old udisks1, but may provide some additional information: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 This is about gnome-disk-utility, but the underlying problem seems udisks2 https://bugzilla.redhat.com/show_bug.cgi?id=1047339 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1373318/+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 1373318] Re: Udisks2 prevents HDDs from going to standby because of polling SMART information
Another hint: If you want to compile udisks, use ./configure --prefix=/usr if you want to replace udisksd on your system otherwise the new version will be in /usr/local/lib/udisks2/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1373318 Title: Udisks2 prevents HDDs from going to standby because of polling SMART information Status in “udisks2” package in Ubuntu: New Bug description: 1) Ubuntu Version: Description: Ubuntu 14.04.1 LTS Release: 14.04 2) Package Version udisks2: Installiert: 2.1.3-1 Installationskandidat: 2.1.3-1 Versionstabelle: *** 2.1.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status 3) What I expected to happen: My two Seagate drives go to sleep after 10 minutes of inactivity. 4) What happened instead: The drives stay on all the time. The full story: The problem is that the minimum time for the drives to go to sleep is 10 minutes, but they are kept awake by the udisks2 daemon which polls them every 10 minutes for SMART data, resetting the idle timer by doing so. Also this might not happen to all drives, there should be a workaround. Would be great if the patch proposed here [1] would also be integrated into udisks2. A more universal approach might be to make the polling interval configurable with 0=polling disabled. Disabling SMART for the disks works partially: a) The following UDEV flags don't have any effect: E: ID_ATA_FEATURE_SET_SMART=0 E: ID_ATA_FEATURE_SET_SMART_ENABLED=0 E: UDISKS_DISABLE_POLLING=1 E: UDISKS_IGNORE=1 b) The following works: (Note: without killing the daemon, according to udisksctl monitor it keeps polling. By polling, the SMART support is reactivated, which seems to be some unexpected behaviour from libatasmart [2]) sudo killall udisksd sudo smartctl --smart=off /dev/sdb # verify sudo smartctl --all /dev/sdb | grep SMART support I think it is quite a bad workaround to kill the deamon after every reboot to be able to diable SMART. And disabling SMART is not good either, but it would be fine for me as workaround. [1] https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 [2] can be verified with sudo smartctl --smart=off /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support sudo skdump --overall /dev/sdb sudo smartctl --all /dev/sdb | grep SMART support PS: This is mainly about the old udisks1, but may provide some additional information: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=26508 This is about gnome-disk-utility, but the underlying problem seems udisks2 https://bugzilla.redhat.com/show_bug.cgi?id=1047339 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1373318/+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 1375805] Re: Lightdm fails to start in VirtualBox
** Attachment added: syslogverbose https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1375805/+attachment/4220365/+files/syslogverbose -- 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/1375805 Title: Lightdm fails to start in VirtualBox Status in “lightdm” package in Ubuntu: New Bug description: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) 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/1375805/+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 1373904] Re: Backport libgdata error saving Google Contacts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution (Ubuntu) Status: New = Confirmed -- 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/1373904 Title: Backport libgdata error saving Google Contacts Status in “evolution” package in Ubuntu: Confirmed Bug description: See issue in https://bugzilla.gnome.org/show_bug.cgi?id=732809 When saving a Google contact in Evolution 3.10 (default in Ubuntu 14.04), the following error appears: ?xml version=1.0 encoding=UTF-8? errors xmlns=http://schemas.google.com/g/2005; error domainGData/domain codeinvalid/code internalReasonInvalid value for: Invalid format: 2010-06-03T10:01:08Z is malformed at Z/internalReason /error /errors Is it possible to backport the fix to Ubuntu 14.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1373904/+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 1290535] Re: [FFE] Webapps support for the new Oxide container
** Changed in: oxide-qt (Ubuntu) Status: New = Invalid ** Changed in: webbrowser-app (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1290535 Title: [FFE] Webapps support for the new Oxide container Status in WebApps: libunity: Fix Released Status in Unity WebApps QML component: Fix Released Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “oxide-qt” package in Ubuntu: Invalid Status in “unity-webapps-qml” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: This is a feature freeze exception request to integrate the following feature in the upcoming Ubuntu 14.04 release. The overall web application support in Ubuntu currently relies on various components and a web container(s) in particular. So far we have been using Firefox and Chromium, by way of browser extensions, to detect, host and integrate web applications in Ubuntu. On mobile devices however, we have already switched to using our own webapp container, based on webbrowser-app. The integration itself has been present as an option since 13.10. However we have been using the QtWebkit engine so far. This request is to also enable and use our webapp-container by defaullt, with the Oxide engine, on the desktop edition. The change impacts a set of packages linked to this bug report. NOTE: This request is not complete and serves to let the release team know of the impact and scope of changes, while the individual MPs with fixes are being consolidated. It will be updated at the beginning of next week when the landing silo is ready for a potential landing. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1290535/+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 1342031] Re: Rename QML modules to follow qml-module-foo naming
** Changed in: webbrowser-app (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to qtlocation-opensource-src in Ubuntu.
https://bugs.launchpad.net/bugs/1342031
Title:
Rename QML modules to follow qml-module-foo naming
Status in “accounts-qml-module” package in Ubuntu:
New
Status in “address-book-app” package in Ubuntu:
New
Status in “bacon2d” package in Ubuntu:
Triaged
Status in “clickmanager-plugin” package in Ubuntu:
New
Status in “content-hub” package in Ubuntu:
New
Status in “cordova-ubuntu” package in Ubuntu:
New
Status in “dee-qt” package in Ubuntu:
New
Status in “gsettings-qt” package in Ubuntu:
New
Status in “history-service” package in Ubuntu:
New
Status in “libhud-qt” package in Ubuntu:
Won't Fix
Status in “libqofono” package in Ubuntu:
New
Status in “libusermetrics” package in Ubuntu:
New
Status in “mediascanner2” package in Ubuntu:
New
Status in “poppler-qml-plugin” package in Ubuntu:
New
Status in “qml-box2d” package in Ubuntu:
New
Status in “qml-friends” package in Ubuntu:
New
Status in “qt3d-opensource-src” package in Ubuntu:
New
Status in “qtconnectivity-opensource-src” package in Ubuntu:
Fix Released
Status in “qtdeclarative-opensource-src” package in Ubuntu:
Fix Released
Status in “qtgrilo” package in Ubuntu:
New
Status in “qtlocation-opensource-src” package in Ubuntu:
New
Status in “qtmultimedia-opensource-src” package in Ubuntu:
Fix Released
Status in “qtpim-opensource-src” package in Ubuntu:
Fix Released
Status in “qtquickcontrols-opensource-src” package in Ubuntu:
Fix Released
Status in “qtsensors-opensource-src” package in Ubuntu:
Fix Released
Status in “qtsystems-opensource-src” package in Ubuntu:
Fix Released
Status in “reminders-app” package in Ubuntu:
New
Status in “solid” package in Ubuntu:
New
Status in “sync-monitor” package in Ubuntu:
New
Status in “telephony-service” package in Ubuntu:
Triaged
Status in “thumbnailer” package in Ubuntu:
New
Status in “u1db-qt” package in Ubuntu:
New
Status in “ubuntu-download-manager” package in Ubuntu:
New
Status in “ubuntu-keyboard” package in Ubuntu:
New
Status in “ubuntu-settings-components” package in Ubuntu:
New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
New
Status in “ubuntu-ui-extras” package in Ubuntu:
New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
New
Status in “ubuntuone-credentials” package in Ubuntu:
New
Status in “unity-action-api” package in Ubuntu:
Triaged
Status in “unity-notifications” package in Ubuntu:
New
Status in “webbrowser-app” package in Ubuntu:
Confirmed
Bug description:
The package names of QML modules should be of the format qml-
module-{$modulename}[version], a transition that was started during Qt
5.3 preparation in Ubuntu. For example this could be qml-module-
qtquick-localstorage or qml-module-qtsysteminfo for non versioned
modules, and qml-module-ubuntu-webthing0.3 for versioned/co-
installable modules.
Further details in Debian e-mail:
http://lists.alioth.debian.org/pipermail/pkg-kde-
talk/2014-March/001889.html
For Ubuntu, transitional packages should be put in place for smooth
distribution upgrades, since we're shipping with the old names in previous
Ubuntus. An example of that is at
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
- in other words:
- Make the old package a transitional oldlibs package that depends on the new
package
- Add Breaks/Replaces to the new package for the old non-transitional
packages (be careful about the version number specification)
- Keep Multi-Arch: same and Architecture: any for the transitional package
- Write QML module instead of QML plugin
- Rename also the *.install files
---
One more example on naming:
For example, the test (qtdeclarative5-test-plugin) in the old
qtdeclarative5-style package naming became qttest (qml-module-
qttest) in the new naming since the path is actually under
/usr/lib/*/qt5/qml/QtTest/
qml-module-qtquick-xmllistmodel has path
/usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have
more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be
qml-module-ubuntu-connectivity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+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 1375805] Re: Lightdm fails to start in VirtualBox
** Attachment added: initctl https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1375805/+attachment/4220351/+files/initctl -- 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/1375805 Title: Lightdm fails to start in VirtualBox Status in “lightdm” package in Ubuntu: New Bug description: Current daily - install and boot. Fails to boot. service lightdm status is stop/waiting once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same result prior to lightdm start ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Tue Sep 30 14:40:39 2014 InstallationDate: Installed on 2014-09-30 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) 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/1375805/+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 1375819] [NEW] gnome-font-viewer freezes up itself or the X session
Public bug reported: 4) What happened instead When I open gnome-font-viewer by clicking on font file (tried on TTF and PFB) it sometimes locks up. Then nothing can be done within the window, but the rest of X session works. However sometimes the whole X session freezes, only mouse cursor moves. It can be worked around by switching to tty1 and killall'ing gnome-font-viewer. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-font-viewer 3.12.0-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 30 16:46:07 2014 InstallationDate: Installed on 2013-07-21 (436 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) SourcePackage: gnome-font-viewer UpgradeStatus: Upgraded to utopic on 2014-09-25 (4 days ago) ** Affects: gnome-font-viewer (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-font-viewer (Fedora) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug utopic ** Bug watch added: Red Hat Bugzilla #1055649 https://bugzilla.redhat.com/show_bug.cgi?id=1055649 ** Also affects: gnome-font-viewer (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1055649 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1375819 Title: gnome-font-viewer freezes up itself or the X session Status in “gnome-font-viewer” package in Ubuntu: New Status in “gnome-font-viewer” package in Fedora: Unknown Bug description: 4) What happened instead When I open gnome-font-viewer by clicking on font file (tried on TTF and PFB) it sometimes locks up. Then nothing can be done within the window, but the rest of X session works. However sometimes the whole X session freezes, only mouse cursor moves. It can be worked around by switching to tty1 and killall'ing gnome-font-viewer. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-font-viewer 3.12.0-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 30 16:46:07 2014 InstallationDate: Installed on 2013-07-21 (436 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) SourcePackage: gnome-font-viewer UpgradeStatus: Upgraded to utopic on 2014-09-25 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819/+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 1371651] Re: Daily does not boot into graphical interface after installation
@jamesodhunt - nothing found -- 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/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 510059] Re: Gvfs keeps asking for password when trying to mount Samba share
Addendum: I have now discovered something interesting enlightening this problem. When I try Linux Mint 17 XFCE from usb (without installing to computer) I am able to mount smb inside Thunar (smb://XXX.XXX.XX/XXX). I just have to write username, domain and password once. When I install the same system to the same computer the username-domain-password prompt keeps reappering without mounting the folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/510059 Title: Gvfs keeps asking for password when trying to mount Samba share Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus My Ubuntu Desktop (9.10, 64-bit) VM can't connect to my Windows 7 (64-bit, Ultimate) File Share using Nautilus. I enter smb://comuterName in the address bar and then it comes up with a password dialog (see screenshot) and then after entering the correct login info, the dialog disappears for a second or two but then reappears again. The dialog always comes back up and the share is never mounted. * Connecting from an XP box on the network to the windows 7 share works just fine. * Connecting from the Ubuntu machine to the windows 7 share using the appropriate 'smbmount' command works just fine. * Connecting from the Ubuntu machine (using the nautilus GUI) to the XP box (password protected) works just fine. * Then I turned off password protection in Win7, rebooted the win7 machine, and still all of the above tests turned out the same. And the Ubuntu machine still doesn't connect to the windows share using the nautilus GUI, and still displays the password dialog even though no password is required anymore. * I tried using smbclient to view the shares, here is the output (not sure if I should be trying something else using the smbclient program): o eddie@eddie-ubuntu:~$ smbclient -L eddie-win7 Enter eddie's password: session setup failed: SUCCESS - 0 ProblemType: Bug Architecture: amd64 Date: Sun Jan 17 15:41:28 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Package: nautilus 1:2.28.1-0ubuntu3 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-server SourcePackage: nautilus Uname: Linux 2.6.31-17-server x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/510059/+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 434476]
On Ubuntu 14.04 I have org.gnome.SessionManager but the screensaver still enters. Based on previous comments it appears that the fix is working for gnome-screensaver 2.30 but that version of gnome-screensaver is pretty old( from September 2010). It appears that the fix is not working for Gnome 3. I found a post that discusses the changes suffered by Gnome lock-screen with the 3.0 release, not sure how relevant is to this bug but I'm going to post it nevertheless. http://www.lucidelectricdreams.com/2011/06/disabling-screensaverlock-screen-on.html Our testing machines are running only newer versions of Ubuntu and no other Linux based operating systems so our verification of this bug options are limited. We can only confirm that the fix is not working on the newer Ubuntu releases. -- 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/434476 Title: screensaver starts while playing HTML5 videos Status in The Mozilla Firefox Browser: Fix Released Status in “firefox” package in Ubuntu: Confirmed Status in “firefox-3.5” package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.5 karmic alpha6 + updates - click on a .ogv video link - after watching some time, screensaver starts. ProblemType: Bug Architecture: amd64 Date: Tue Sep 22 08:45:53 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: firefox 3.5.3+build1+nobinonly-0ubuntu2 PackageArchitecture: all ProcEnviron: LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: firefox-3.5 Uname: Linux 2.6.31-10-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/434476/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition
** Description changed: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome-desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts [x] - * gnome-control-center + * gnome-control-center [x] * gnome-documents [x] * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] * gnome-screensaver [x] - * gnome-session-bin - * gnome-settings-daemon - * indicator-keyboard - * evolution + * gnome-session [x] + * gnome-settings-daemon [x] + * indicator-keyboard [x] + * evolution [x] * mutter [x] - * nautilus - * unity - * unity-control-center - * unity-settings-daemon + * nautilus [x] + * unity [x] + * unity-control-center [x] + * unity-settings-daemon [x] packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. -- 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/1372346 Title: [FFe] gnome-desktop 3.12 transition Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-desktop3” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Bug description: We have been trying to land this transition for about 9 months now (well previously was 3.10, but that was largely the same). The big blocker was the removal of xrandr and idlemonitor code out of gnome- desktop. Robert Ancell has solved that issue see Bug 1372240 There is a SONAME bump, however that only affects g-s-d/g-c-c. Mostly apps are using things like the thumbnailer etc, and these are not affected by api changes, so they just need to be rebuilt. gnome-session could be updated to the latest 3.10 stable release, however this is not strictly required and will require reverting removal of fallback dialogs. A rebuild would be fine for now. Full lost of r-depends: Reverse-Depends === * cheese [x] * eog [x] * epiphany-browser [x] * evince (separately uploaded, no need to rebuild) * gnome-clocks [x] * gnome-contacts [x] * gnome-control-center [x] * gnome-documents [x] * gnome-font-viewer [x] * gnome-panel [x] * gnome-photos [x] * gnome-screensaver [x] * gnome-session [x] * gnome-settings-daemon [x] * indicator-keyboard [x] * evolution [x] * mutter [x] * nautilus [x] * unity [x] * unity-control-center [x] * unity-settings-daemon [x] packages marked [x] are uploaded I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c 3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99). gnome-control-center update will also require a UIFe, Ubuntu GNOME slideshow has not yet been updated for utopic, so this shouldnt be a problem from our side. No other flavours use the UI part of gnome- control-center anymore, the shared-data (faces) are unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 1371651] Re: Daily does not boot into graphical interface after installation
reported at Bug 1375805 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1375805 -- 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/1371651 Title: Daily does not boot into graphical interface after installation Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Fix Released Bug description: used the daily iso 2015-09-19 i386 ran installation on virtualbox 4.3.16 after installation, the system won't boot into the graphical interface. instead, switching to vt1 and back to vt7 reveals the attached errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic i686 ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 Date: Fri Sep 19 17:09:17 2014 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de keyboard-configuration/layoutcode?=de InstallationDate: Installed on 2014-09-19 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371651/+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 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
here is the output ** Attachment added: alsa.txt https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+attachment/4220358/+files/alsa.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1365769 Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: The problem is that the microphone is not detected after a reboot. As a result, some applications cannot get sound from the microphone. The Input tab of the Sound window lists no device. I have a workround which is to disconnect and then connect the microphone after I have logged in. Interestingly, the audacity application can access the microphone when the system says that the device does not exist ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 5 00:12:39 2014 InstallationDate: Installed on 2011-07-29 (1133 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim2060 F pulseaudio Symptom_Jack: Pink Mic, Rear Symptom_Type: No sound at all Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago) dmi.bios.date: 12/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: G41MT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
Marketing wise, as the Ubuntu Touch phones are about to go to market, it would be embarrassing that OSs such as Windows and Mac can transfer files via Bluetooth with the new phones, but not Ubuntu itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Bogus another operation in progress error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gnome-vfs-obexftp” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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
