[Desktop-packages] [Bug 1966580] Re: Erroneously huge mouse pointer with snap-packaged firefox in jammy
Laptop: HP Spectre x360 Convertible 14-ea0xxx Graphics: Intel TigerLake-LP GT2 [Iris Xe Graphics] Resolution: 3000x2000 Mostly uncustomized out-of-the-box Ubuntu, the one notable choice being to use the gnome-xorg session type (declining to use the Ubuntu customisations to gnome-session, declining to use Wayland) More than that, I can't give you, as I've long since uninstalled snapd, and am unwilling to reinstall it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy Status in firefox package in Ubuntu: Incomplete Bug description: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+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 1966580] Re: Erroneously huge mouse pointer with snap-packaged firefox in jammy
Sorry, I am opposed to Canonical forcing snap on Ubuntu users and do not wish to spend my personal time on supporting that. I'll just use a non-snap distribution mechanism instead. -- 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/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy Status in firefox package in Ubuntu: New Bug description: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+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 1966580] [NEW] Erroneously huge mouse pointer with snap-packaged firefox in jammy
Public bug reported: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy Status in firefox package in Ubuntu: New Bug description: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+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 1765911] Re: Major performance regression from Ubuntu 17.10 with i915
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765911 Title: Major performance regression from Ubuntu 17.10 with i915 Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765911/+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 1765911] Re: Major performance regression from Ubuntu 17.10 with i915
Similar/same issue observed on HP Spectre 13 (2017 model) which has exactly the same Intel HD 520 graphics. Bad enough that I had to reinstall 17.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765911 Title: Major performance regression from Ubuntu 17.10 with i915 Status in xorg package in Ubuntu: Confirmed Bug description: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765911/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source package, rebuilt it locally, and installed it. It seems to have fixed the problem for me. So perhaps the problem really is in the Ubuntu delta? -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
I'm not sure if this helps, but I see pulseaudio logging an "Operation Not Authorized" message when things do not work: Apr 26 01:46:52 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c: Acquiring transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd0 Apr 26 01:46:52 zenbook pulseaudio[3346]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd0 (Operation Not Authorized) Whereas after doing the switch-to-HSP, disconnect, reconnect, switch-to- A2DP dance to make it work, the equivalent logging is: Apr 26 01:52:40 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c: Acquiring transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd2 Apr 26 01:52:40 zenbook bluetoothd[808]: /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd2: fd(23) ready Apr 26 01:52:40 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c: Transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd2 acquired: fd 46 -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+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 1289180] [NEW] Zoom dropdown is broken
Public bug reported: Recently, within trusty, evince has broken so that the zoom selector in the top right of the window is inoperable. Clicking its dropdown arrow does not cause any UI to open. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 7 07:30:30 2014 EcryptfsInUse: Yes SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-02-28 (7 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1289180 Title: Zoom dropdown is broken Status in “evince” package in Ubuntu: New Bug description: Recently, within trusty, evince has broken so that the zoom selector in the top right of the window is inoperable. Clicking its dropdown arrow does not cause any UI to open. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 7 07:30:30 2014 EcryptfsInUse: Yes SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-02-28 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1289180/+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 1282203] Re: gnome-terminal not respecting Enable menu access keys setting, inside the Unity desktop environment.
I observe that the menu access keys are correctly disabled if UBUNTU_MENUPROXY=0 is set in the environment, disabling the global menu to revert to menu bar drawn within the gnome-terminal window. Therefore, I've marked the bug as also affecting unity, as it seems highly likely that at least some of the fix will need to be in Unity rather than gnome-terminal. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1282203 Title: gnome-terminal not respecting Enable menu access keys setting, inside the Unity desktop environment. Status in “gnome-terminal” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: New Bug description: Under Edit -- Keyboard Shortcuts.. there is a checkbox for Enable menu access keys (such as Alt+F to open the File menu). That checkbox appear to have no affect what so ever. No matter whatever I have it checked or not I still get the same behavior, that menu access keys are enabled. This being a problem since I'd much rather not have the menu get in the way of my readline/emacs bindings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 19 19:15:57 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2013-09-06 (166 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130906) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to trusty on 2013-10-23 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1282203/+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 1167934] [NEW] gnome-disks crashed with SIGSEGV in udisks_drive_ata_get_smart_updated()
Public bug reported: I am seeing a repeatable crash in gnome-disks when unplugging a SATA HD whilst the SMART Data window for the HD in question is open. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-disk-utility 3.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: nfsv3 nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc arc4 md4 nls_utf8 cifs fscache btrfs zlib_deflate ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c reiserfs ext2 nfnetlink_log nfnetlink dm_crypt bnep rfcomm bluetooth binfmt_misc snd_hda_codec_analog dell_wmi coretemp kvm_intel kvm psmouse sparse_keymap gpio_ich snd_hda_intel tpm_tis ppdev dcdbas snd_hda_codec snd_hwdep snd_pcm snd_page_alloc lpc_ich snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer i7core_edac edac_core snd dm_multipath scsi_dh serio_raw soundcore microcode parport_pc mac_hid lp parport hid_generic usbhid hid usb_storage radeon i2c_algo_bit tg3 ttm ptp drm_kms_helper ahci libahci pps_core drm wmi ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Thu Apr 11 14:25:58 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-disks MarkForUpload: True ProcCmdline: gnome-disks ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f54884a7dd7 udisks_drive_ata_get_smart_updated+23: mov0xf0(%rax),%rax PC (0x7f54884a7dd7) ok source 0xf0(%rax) (0x00f0) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-disk-utility StacktraceTop: udisks_drive_ata_get_smart_updated () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0 ?? () ?? () g_timeout_dispatch (source=source@entry=0xc9c370, callback=optimised out, user_data=optimised out) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:4413 g_main_dispatch (context=0xb5d5b0) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3054 Title: gnome-disks crashed with SIGSEGV in udisks_drive_ata_get_smart_updated() UpgradeStatus: Upgraded to raring on 2013-03-16 (25 days ago) UserGroups: adm admin arpwatch cdrom dialout libvirtd lpadmin plugdev sambashare sbuild sudo wireshark ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace raring ** Information type changed from Private to Public -- 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/1167934 Title: gnome-disks crashed with SIGSEGV in udisks_drive_ata_get_smart_updated() Status in “gnome-disk-utility” package in Ubuntu: New Bug description: I am seeing a repeatable crash in gnome-disks when unplugging a SATA HD whilst the SMART Data window for the HD in question is open. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-disk-utility 3.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: nfsv3 nfsv4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc arc4 md4 nls_utf8 cifs fscache btrfs zlib_deflate ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c reiserfs ext2 nfnetlink_log nfnetlink dm_crypt bnep rfcomm bluetooth binfmt_misc snd_hda_codec_analog dell_wmi coretemp kvm_intel kvm psmouse sparse_keymap gpio_ich snd_hda_intel tpm_tis ppdev dcdbas snd_hda_codec snd_hwdep snd_pcm snd_page_alloc lpc_ich snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer i7core_edac edac_core snd dm_multipath scsi_dh serio_raw soundcore microcode parport_pc mac_hid lp parport hid_generic usbhid hid usb_storage radeon i2c_algo_bit tg3 ttm ptp drm_kms_helper ahci libahci pps_core drm wmi ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Thu Apr 11 14:25:58 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-disks MarkForUpload: True ProcCmdline: gnome-disks ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f54884a7dd7 udisks_drive_ata_get_smart_updated+23:mov0xf0(%rax),%rax PC (0x7f54884a7dd7) ok source 0xf0(%rax) (0x00f0) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-disk-utility StacktraceTop: udisks_drive_ata_get_smart_updated () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0 ?? () ?? () g_timeout_dispatch (source=source@entry=0xc9c370, callback=optimised out, user_data=optimised out) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:4413 g_main_dispatch (context=0xb5d5b0) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3054 Title: gnome-disks crashed with SIGSEGV in
[Desktop-packages] [Bug 1165789] [NEW] Wifi indicator shows disconnected in between connecting and connected (raring regression)
Public bug reported: In quantal, the network-manager indicator progressed straight from connecting (pulsing/rippling wifi symbol) to connected (static wifi signal level indicator) when successfully connected. In raring, it shows the disconnected (outlined empty lack of wifi symbol) symbol for a half-second or so between connecting and connected, provoking a moment's concern of What? My wifi connection failed? until the user learns to tolerate this quirk. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Apr 7 16:45:16 2013 EcryptfsInUse: Yes IpRoute: default via 192.168.42.129 dev usb0 proto static 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.195 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-03-16 (21 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH usb0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled disabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1165789 Title: Wifi indicator shows disconnected in between connecting and connected (raring regression) Status in “network-manager” package in Ubuntu: New Bug description: In quantal, the network-manager indicator progressed straight from connecting (pulsing/rippling wifi symbol) to connected (static wifi signal level indicator) when successfully connected. In raring, it shows the disconnected (outlined empty lack of wifi symbol) symbol for a half-second or so between connecting and connected, provoking a moment's concern of What? My wifi connection failed? until the user learns to tolerate this quirk. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Apr 7 16:45:16 2013 EcryptfsInUse: Yes IpRoute: default via 192.168.42.129 dev usb0 proto static 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.195 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-03-16 (21 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH usb0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1165789/+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 689593] Re: 2x100% CPU and memory usage growth when performing partition modifications via udisks
** Summary changed: - 2x100% CPU and memory usage growth when setting bootable flag in palimpsest + 2x100% CPU and memory usage growth when performing partition modifications via udisks -- 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/689593 Title: 2x100% CPU and memory usage growth when performing partition modifications via udisks Status in abstraction for enumerating and managing block devices: New Status in “gnome-disk-utility” package in Ubuntu: Confirmed Status in “usb-creator” package in Ubuntu: Confirmed Bug description: When unsetting the bootable flag on a partition using palimpsest, the following things happen: - udisks-helper-modify-partition and udisks-daemon processes use 100% CPU each - udisks-daemon chews about 18MiB of memory each second This problem exists regardless of whether the partition is mounted or not. natty gnome-disk-utility 2.32.1-0ubuntu3 udisks 1.0.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/689593/+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 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal
The other option for people on Quantal is to upgrade to Raring. There's still no fglrx, but the open source radeon driver has improved a *lot*. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Won't Fix Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards for the legacy 12.6 driver as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy-radeon_linux.aspx , fglrx-installer installs non-working drivers for users of the cards: AMD Radeon HD 4000 Series AMD Radeon HD 3000 Series AMD Radeon HD 2000 Series AMD Radeon HD Series AGP AMD Mobility Radeon HD 4000 Series AMD Mobility Radeon HD 3000 Series AMD Mobility Radeon HD 2000 Series I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. One of the outstanding issues for addressing this bug is AMD currently does not plan to support XServer 1.13 (for Ubuntu the package is xserver-xorg-core) for the legacy 12.6 driver, which Quantal uses: apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.0-0ubuntu6 Candidate: 2:1.13.0-0ubuntu6 Version table: *** 2:1.13.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 1162389] [NEW] Preferences inaccessible
Public bug reported: The menu option to open the Totem Preferences UI appears to have gone missing. There's evidence in the source code that there's supposed to be a preferences UI, and the online help states there should be an Edit Preferences menu item, but it does not appear. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 00:46:48 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-03-16 (14 days ago) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1162389 Title: Preferences inaccessible Status in “totem” package in Ubuntu: New Bug description: The menu option to open the Totem Preferences UI appears to have gone missing. There's evidence in the source code that there's supposed to be a preferences UI, and the online help states there should be an Edit Preferences menu item, but it does not appear. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 00:46:48 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1162389/+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 1162389] Re: Preferences inaccessible
Actually, on digging around in the glade file totem.ui, it would appear that the whole menu with id 'appmenu' is missing from the UI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1162389 Title: Preferences inaccessible Status in “totem” package in Ubuntu: New Bug description: The menu option to open the Totem Preferences UI appears to have gone missing. There's evidence in the source code that there's supposed to be a preferences UI, and the online help states there should be an Edit Preferences menu item, but it does not appear. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 00:46:48 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1162389/+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 1158594] Re: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)
I think I've discovered mostly what had gone wrong - somehow in the process of going quantal-raring, either the various colour balance settings in totem got changed, or it changed how it interpreted the numerical values in dconf. When I dug around in dconf-editor, I found various colour-related settings under org.gnome.Totem, which, once reset to defaults, caused my display issue to go away. The problem was exacerbated by bug 1162389 - the totem preferences dialog has become inaccessible - hence why I had to resort to dconf- editor to change them. Thus, this bug becomes a question of how a visually sensible colour configuration on quantal ended up looking wrong after upgrading to raring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1158594 Title: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression) Status in “totem” package in Ubuntu: New Bug description: Some video files play in totem in raring appearing far too bright and yellowish - the appearance is similar to an excessively strong application of a gamma transform. To reproduce: 1) Download this video from youtube (~15MB): youtube-dl -f 18 http://www.youtube.com/watch?v=rUgAgfO-16s 2) Open the downloaded file in totem, and the youtube page in a browser, and play them side by side simultaneously. The difference should be readily apparent, especially in the flaring on the Game of Thrones text in the title sequence and in the desert scenery. Other media players such as vlc, xine-ui render the video correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1158594/+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 1162389] Re: Preferences inaccessible
*** This bug is a duplicate of bug 1131754 *** https://bugs.launchpad.net/bugs/1131754 ** This bug has been marked a duplicate of bug 1131754 [raring] Totem is missing the GNOME AppMenu functions: Open, Preferences, etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1162389 Title: Preferences inaccessible Status in “totem” package in Ubuntu: New Bug description: The menu option to open the Totem Preferences UI appears to have gone missing. There's evidence in the source code that there's supposed to be a preferences UI, and the online help states there should be an Edit Preferences menu item, but it does not appear. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 00:46:48 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1162389/+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 1158594] [NEW] Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)
Public bug reported: Some video files play in totem in raring appearing far too bright and yellowish - the appearance is similar to an excessively strong application of a gamma transform. To reproduce: 1) Download this video from youtube (~15MB): youtube-dl -f 18 http://www.youtube.com/watch?v=rUgAgfO-16s 2) Open the downloaded file in totem, and the youtube page in a browser, and play them side by side simultaneously. The difference should be readily apparent, especially in the flaring on the Game of Thrones text in the title sequence and in the desert scenery. Other media players such as vlc, xine-ui render the video correctly. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1158594 Title: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression) Status in “totem” package in Ubuntu: New Bug description: Some video files play in totem in raring appearing far too bright and yellowish - the appearance is similar to an excessively strong application of a gamma transform. To reproduce: 1) Download this video from youtube (~15MB): youtube-dl -f 18 http://www.youtube.com/watch?v=rUgAgfO-16s 2) Open the downloaded file in totem, and the youtube page in a browser, and play them side by side simultaneously. The difference should be readily apparent, especially in the flaring on the Game of Thrones text in the title sequence and in the desert scenery. Other media players such as vlc, xine-ui render the video correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1158594/+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 1158594] Re: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)
It looks like this may be a totem bug specifically, as if I launch the same file playing simultaneously through totem, gst-launch-0.10 and gst- launch-1.0 by executing the following in a terminal: totem rUgAgfO-16s.mp4 gst-launch-1.0 playbin uri=file:///home/maxb /rUgAgfO-16s.mp4 gst-launch-0.10 playbin uri=file:///home/maxb /rUgAgfO-16s.mp4 it is easy to see that only the totem playback displays the abnormal colouring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1158594 Title: Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression) Status in “totem” package in Ubuntu: New Bug description: Some video files play in totem in raring appearing far too bright and yellowish - the appearance is similar to an excessively strong application of a gamma transform. To reproduce: 1) Download this video from youtube (~15MB): youtube-dl -f 18 http://www.youtube.com/watch?v=rUgAgfO-16s 2) Open the downloaded file in totem, and the youtube page in a browser, and play them side by side simultaneously. The difference should be readily apparent, especially in the flaring on the Game of Thrones text in the title sequence and in the desert scenery. Other media players such as vlc, xine-ui render the video correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1158594/+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 1067876] Re: Missing Safely Remove Drive option from Quicklists. Only have Eject.
I have Quantal on USB-flash for testing. There are 70+ users of Quantal, which are affected by this bug. As far I know Quantal is supported until 2014 April. I hope you can fix this bug in Quantal using another method in near future. It doesn't sound like a very effective use of developers' time to craft a separate temporary solution for an older release, when the problem is so easily worked around (just choose Unmount, then manually unplug the device). Personally, I'd rather people spent time on making Raring the best release it can be - it's under 8 weeks to release, even. -- 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/1067876 Title: Missing Safely Remove Drive option from Quicklists. Only have Eject. Status in GVFS: Invalid Status in abstraction for enumerating and managing block devices: Won't Fix Status in Unity: Invalid Status in “gvfs” package in Ubuntu: Fix Released Status in “udisks2” package in Ubuntu: Fix Released Bug description: In Ubuntu 12.04, I could right-click on my usb-external-harddrive's Unity-Task-Bar icon (launcher icon) and select Safely Remove. Upon doing this, the icon would disappear and I would proceed in unplugging my external hard drive. However, since upgrading to Ubuntu 12.10, this option is no longer available in the context menus (Quicklists) for external drives. Instead, all I see is Unmount, and after clicking Unmount the icon remains on the task-bar (launcher) and no indication is given that would imply that the unmount occurred successfully. The intent of this report is to bring back the Safely Remove option which (by making the icon disappear after selected) indicates that you may now safely removal your USB external hard drive (by unplugging its usb connector). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed Oct 17 14:55:17 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-04 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1067876/+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 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal
My FirePro V5700 ceased to work with the fglrx driver with the exact same update, in the exact same way, as described here, and has the same underlying chip as Radeon HDs known to be affected. The AMD website is hardly a shining example of consistency - there's an 8.982 Linux driver offered for the FirePro V5700 at http://support.amd.com/us/Pages/AMDSupportHub.aspx if you select Workstation Graphics and FirePro Performance Pre-WHQL Driver. The weight of evidence is certainly sufficient to convince me that it's all one issue. If AMD ever come up with a driver that supports the Radeon HD [234]xxx on X server 1.13 but does not support my FirePro, I'll reconsider. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Triaged Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards for the legacy 12.6 driver as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy-radeon_linux.aspx , fglrx-installer installs non-working drivers for users of the cards: AMD Radeon HD 4000 Series AMD Radeon HD 3000 Series AMD Radeon HD 2000 Series AMD Radeon HD Series AGP AMD Mobility Radeon HD 4000 Series AMD Mobility Radeon HD 3000 Series AMD Mobility Radeon HD 2000 Series I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. One of the outstanding issues for addressing this bug is AMD currently does not plan to support XServer 1.13 (for Ubuntu the package is xserver-xorg-core) for the legacy 12.6 driver, which Quantal uses: apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.0-0ubuntu6 Candidate: 2:1.13.0-0ubuntu6 Version table: *** 2:1.13.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 1058040] Re: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal
lspci has this to say about it: 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV730 [FirePro V5700] The balance of evidence regarding the FirePro V5700 seems to be support was dropped in 8.982, and the AMD website is just getting it wrong when it offers 8.982.x for the FirePro V5700 in some combinations of clicking through the driver selector forms. The balance of evidence regarding the FireStream cards seems confused. The PDF release notes linked from individual driver versions at http://support.amd.com/us/gpudownload/fire/previous/Pages/fire_linux.aspx suggest support dropped, whilst http://support.amd.com/us/kbarticles/Pages/AMDCatalystSoftwareSuiteVersion1211BetaReleaseNotes.aspx is contradictory to this, suggesting support continues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Triaged Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards for the legacy 12.6 driver as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy-radeon_linux.aspx , fglrx-installer installs non-working drivers for users of the cards: AMD Radeon HD 4000 Series AMD Radeon HD 3000 Series AMD Radeon HD 2000 Series AMD Radeon HD Series AGP AMD Mobility Radeon HD 4000 Series AMD Mobility Radeon HD 3000 Series AMD Mobility Radeon HD 2000 Series I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. One of the outstanding issues for addressing this bug is AMD currently does not plan to support XServer 1.13 (for Ubuntu the package is xserver-xorg-core) for the legacy 12.6 driver, which Quantal uses: apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.0-0ubuntu6 Candidate: 2:1.13.0-0ubuntu6 Version table: *** 2:1.13.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal
@Christopher Penalver: Your comment-less removal of a useful part of the bug description after the confrontations already occurred in this bug is frankly rude. I shall add it back with additional notes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with HD2000-4000 legacy cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy- radeon_linux.aspx , fglrx-installer installs non-working drivers. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal
** Description changed: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy- radeon_linux.aspx , fglrx-installer installs non-working drivers. + + NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 chips are affected - if your board's chip is a member of these families, you should consider this bug report to most likely apply to you. This includes some FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility parts which are rebadged Radeon HD4x00 parts. If unsure, please consult + http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. However there seems to be some question surrounding some FireStream parts containing R7xx chips, which may still be supported by the main Catalyst driver releases. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with HD2000-4000 legacy cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy- radeon_linux.aspx , fglrx-installer installs non-working drivers. NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 chips are affected - if your board's chip is a member of these families, you should consider this bug report to most likely apply to you. This includes some FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility parts which are rebadged Radeon HD4x00 parts. If unsure, please consult http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. However there seems to be some question surrounding some FireStream parts containing R7xx chips, which may still be supported by the main Catalyst driver releases. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or
[Desktop-packages] [Bug 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal
** Description changed: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy- radeon_linux.aspx , fglrx-installer installs non-working drivers. NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 chips are affected - if your board's chip is a member of these families, you should consider this bug report to most likely apply to you. This includes some FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility parts which are rebadged Radeon HD4x00 parts. If unsure, please consult - http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. However there seems to be some question surrounding some FireStream parts containing R7xx chips, which may still be supported by the main Catalyst driver releases. + http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. However there seems to be some question surrounding some FireStream parts containing R7xx chips, which may still be supported by the main Catalyst driver releases according to AMD's website, though bug 1075035 contains as yet inconclusive evidence counter to this. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with HD2000-4000 legacy cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards as per http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy- radeon_linux.aspx , fglrx-installer installs non-working drivers. NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 chips are affected - if your board's chip is a member of these families, you should consider this bug report to most likely apply to you. This includes some FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility parts which are rebadged Radeon HD4x00 parts. If unsure, please consult http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. However there seems to be some question surrounding some FireStream parts containing R7xx chips, which may still be supported by the main Catalyst driver releases according to AMD's website, though bug 1075035 contains as yet inconclusive evidence counter to this. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx
[Desktop-packages] [Bug 1058040] Re: fglrx-installer not working with HD2000-4000 legacy cards in Quantal
@ Christopher Penalver: Why are you so very determined to make this bug's description LESS useful for users? I have a FirePro V5700 [RV730] which is affected by this. The nomenclature HD2000-4000 doesn't identify this card at all. The chip information is vastly more useful in identifying whether a given card is likely to be affected, yet you insist on deleting it even after I expanded the wording to document the interesting ambiguity of the FireStreams. I'll put my revised wording in my comment here, since you deleted it from the description: -- NOTE: It is mostly agreed that all AMD cards based on R(V)6x0 and R(V)7x0 chips are affected - if your board's chip is a member of these families, you should consider this bug report to most likely apply to you. This includes some FirePro/FireGL/FireStream products as well as certain Radeon HD5x00 mobility parts which are rebadged Radeon HD4x00 parts. If unsure, please consult http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units. However there seems to be some question surrounding some FireStream parts containing R7xx chips, which may still be supported by the main Catalyst driver releases according to AMD's website, though bug 1075035 contains as yet inconclusive evidence counter to this. -- As for your reluctance to refer to Wikipedia: if AMD actually provided an official source thsat would be great. Since they don't bother, Wikipedia is a good second best. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer not working with HD2000-4000 legacy cards in Quantal Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Triaged Bug description: Following the AMD decision to change to a new driver support model for Radeon™ HD 4000, HD 3000 and HD 2000 series cards for the legacy 12.6 driver as per http://support.amd.com/us/gpudownload/linux/legacy/Pages /legacy-radeon_linux.aspx , fglrx-installer installs non-working drivers for users of these cards. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards or patch the current code base for use with these cards. One of the outstanding issues for addressing this bug is AMD currently does not plan to support XServer 1.13 (for Ubuntu the package is xserver-xorg-core) for the legacy 12.6 driver, which Quantal uses: apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.0-0ubuntu6 Candidate: 2:1.13.0-0ubuntu6 Version table: *** 2:1.13.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 WARNING !!! The following workaround has produced mixed results and left some users with temporarily broken systems. It is not recommended for production systems or novice users that are not comfortable with basic console/non-GUI recovery. USE AT OWN RISK. WORKAROUND: sudo add-apt-repository ppa:makson96/fglrx sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install fglrx-legacy This workaround will downgrade X to 1.12 and install the AMD legacy fglrx 8.97 (Catalyst 12.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 945450] Re: Responsiveness: LightDM in ubuntu 12.04 very slow
** Tags removed: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/945450 Title: Responsiveness: LightDM in ubuntu 12.04 very slow Status in GNOME Shell: Fix Released Status in GNOME Themes Standard: Fix Released Status in GTK+ GUI Toolkit: Fix Released Status in Light Themes: Fix Released Status in Light Display Manager: Confirmed Status in Unity Greeter: Fix Released Status in xserver-xorg-driver-radeonhd: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: ubuntu 12.04 (last update today, 3/3/2012) lightdm 1.1.3 1.) Boot = LightDM is shown 2.) Move mouse cursor to session selector button = Mouse moves slow = The button is highlighted after more that 3 seconds 3.) Click button = It takes to long for the list to show Note: -- This only happend after dist-upgrade to 12.04 (beta), before everything worked fine. $ lspci -v | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Xorg.0.log ... [30.658] ABI class: X.Org Video Driver, version 11.0 [30.658] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, [30.659] (II) VESA: driver for VESA chipsets: vesa [30.659] (II) FBDEV: driver for framebuffer: fbdev [30.661] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [30.703] ABI class: X.Org Video Driver, version 11.0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/945450/+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 1005642] Re: Garbage written to state file, causing slow UI
This bug does not appear to related to light-themes, marking bugtask Invalid. ** Tags removed: patch ** Changed in: light-themes Status: Confirmed = Invalid ** Changed in: gtk Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1005642 Title: Garbage written to state file, causing slow UI Status in GTK+ GUI Toolkit: Invalid Status in Light Themes: Invalid Status in Unity Greeter: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Released Bug description: Impact: A software bug causes garbage data to be written to the unity greeter state file which makes file large to open causing a slow down. Test Case: 1. Stop lightdm $ sudo stop lightdm 2. Remove greeter state file $ sudo rm ~lightdm/.cache/unity-greeter/state 3. Start lightdm $ sudo start lightdm 4. Pick user and log in normally Expected result: ~lightdm/.cache/unity-greeter/state exists and contains the key last-user which is set to the user that just logged in Observed result: File exists but has garbage after last-user key Regression Potential: Chance of causing the last logged in user to be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1005642/+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 1073369] [NEW] Ubuntu patch unconditionally breaks three-finger tap
Public bug reported: The Ubuntu gnome-settings-daemon package contains a patch disable_three_touch_tap.patch which unconditionally disables three- finger tap. This is annoying. I want to tap with three fingers to paste. There's a comment mentioning some kind of gestures, but whatever they are, nothing seems to happen on my system. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Oct 30 23:26:28 2012 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1073369 Title: Ubuntu patch unconditionally breaks three-finger tap Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: The Ubuntu gnome-settings-daemon package contains a patch disable_three_touch_tap.patch which unconditionally disables three- finger tap. This is annoying. I want to tap with three fingers to paste. There's a comment mentioning some kind of gestures, but whatever they are, nothing seems to happen on my system. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Oct 30 23:26:28 2012 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1073369/+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 877438] Re: [8xxx] Unity/compiz has sluggish performance on dual-head with nvidia driver
This bug is very much still present on Quantal. Environment: Quantal, at time of release. nvidia-current driver package. Quadro NVS 290/PCIe/SSE2 Guest session (no significant customizations) Simply maximizing a gnome-terminal takes more than 2 full seconds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/877438 Title: [8xxx] Unity/compiz has sluggish performance on dual-head with nvidia driver Status in “compiz” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Incomplete Bug description: When Unity/Compiz is running with the -nvidia driver and two monitors are connected, compiz and/or Xorg will consume CPU time (50-90% typ.) with window activity (opening large numbers of windows, resizing, moving, etc.) Disabling Sync to VBlank appears not to help. Duplicate bug #737454 suggests it may be an issue specific to the NVIDIA 8xxx series cards with large resolution sizes. [Workarounds] The issue can be reliably worked around by either disabling one of the displays, or disabling the Unity Plugin in CompizConfig Settings Manager The nouveau driver on the same hardware typically does not have the performance issue (but may have other issues such as stability, rendering it not a valid workaround). Some have reported that upgrading to -nvidia 290.03 solves the problem; others report it has no effect. See http://www.nvnews.net/vbulletin/showthread.php?p=2493300 Some have reported that lowering the external monitor resolution to match the laptop LVDS resolution brings performance to acceptable levels. Description: Ubuntu 11.10 Release: 11.10 -- xorg: Installed: 1:7.6+7ubuntu7 Candidate: 1:7.6+7ubuntu7 Version table: *** 1:7.6+7ubuntu7 0 500 http://se.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,imgpng,gnomecompat,vpswitch,regex,resize,grid,mousepoll,scale,move,session,animation,unitymtgrabhandles,workarounds,wall,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Oct 18 11:08:19 2011 DistUpgraded: Log time: 2011-10-14 08:32:51.288330 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 285.05.09, 3.0.0-12-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. nvidia-current-updates, 280.13, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: nVidia Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: nVidia Corporation Device [10de:0492] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) MachineType: Hewlett-Packard HP Compaq dc7800p Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=f5c340d9-f04b-4bcd-b714-909faceebfda ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to oneiric on 2011-10-14 (4 days ago) dmi.bios.date: 07/18/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F1 v01.04 dmi.board.asset.tag: CZC8378X1V dmi.board.name: 0AA8h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8378X1V dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800pSmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7800p Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu26 version.libdrm2: libdrm2 2.4.26-1ubuntu1
[Desktop-packages] [Bug 1058040] Re: fglrx-installer does not support HD2000-4000 legacy cards
I have added an ubuntu-release-notes bugtask to this bug, because I think it is appropriate to release-note a warning to users of older ATI hardware that due to AMD/ATI's failure to continue to support their hardware, they will not have the option of using fglrx after updating to Quantal. ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer does not support HD2000-4000 legacy cards Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: Following the AMD decision to drop support for older hardware fglrx- installer will install non-working drivers for some users. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 1058040] Re: fglrx-installer does not support HD2000-4000 legacy cards
Additionally, I'd suggest that the release notes mention the design names i.e. R600 and R700 series as well as the marketing names, as my hardware, which is affected, doesn't include any HD2000-4000 style indication in its lspci output: 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV730 [FirePro V5700] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1058040 Title: fglrx-installer does not support HD2000-4000 legacy cards Status in Release Notes for Ubuntu: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: Following the AMD decision to drop support for older hardware fglrx- installer will install non-working drivers for some users. I suggest the addition of an fglrx-legacy package to install the AMD legacy drivers for users with older cards. Output for fglrx 9.00 [1]: # lspci|grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780L [Radeon HD 3000] # modprobe fglrx FATAL: Error inserting fglrx (/lib/modules/3.5.0-15-generic/updates/dkms/fglrx.ko): No such device # dmesg|tail -n3 [ 6785.693869] [fglrx] Maximum main memory to use for locked dma buffers: 7132 MBytes. [ 6785.694089] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 6785.694091] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed # dpkg --list|grep fglrx ii fglrx 2:9.000-0ubuntu1 amd64 Video driver for the AMD graphics accelerators ii fglrx-amdcccle 2:9.000-0ubuntu1 amd64 Catalyst Control Center for the AMD graphics accelerators [1] https://bugs.launchpad.net/ubuntu/+source/fglrx-installer- updates/+bug/1032672/comments/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1058040/+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 977048] Re: Totem fails to play mp4 files originating from youtube
Another way to obtain a video file to reproduce this: $ sudo apt-get install youtube-dl $ youtube-dl -f 18 lk5_OSsawz4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/977048 Title: Totem fails to play mp4 files originating from youtube Status in “gstreamer0.10” package in Ubuntu: Confirmed Bug description: In precise beta 2, Totem fails to plays mp4 files downloaded from youtube via Minitube or the Firefox DownloaHhelper plugin. Totem does not crash, but displays a black screen. As a result, totem-video-thumbnailer fails to create a proper snapshot to be used as a thumbnail for those videos in Nautilus (it aborts with a totem-video-thumbnailer couldn't process file: 'video.mp4' Reason: Took too much time to process. error message) This is a regression as everything was fine in 11.10 using the same videos. Moreover, other media players such as VLC or SMPlayer have no trouble playing the video. Steps to reproduce - Download a video from youtube using minitube or the DownloadHelper Firefox plugin - check that Nautilus does not display a snapshot of the video as a thumbnail - check that Totem fails to properly plays the video, although it does not crash - check that it is not the case in 11.10 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgstreamer0.10-0 0.10.36-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Mon Apr 9 10:11:47 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to precise on 2012-03-29 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/977048/+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 982585] [NEW] Fails to play a video which VLC can play, and that totem/gstreamer in previous Ubuntu versions could play
Public bug reported: totem/gstreamer in precise fails to play a video file which VLC in precise plays fine, and I believe I've played the same file in totem/gstreamer in older Ubuntu releases fine too. The symptoms of the failure are the totem properties declaring the video size to be 0x0 and neither audio nor video appearing. The file in question may be downloaded with: youtube-dl -f 18 lk5_OSsawz4 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 21:32:01 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm LC_COLLATE=C PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to precise on 2012-03-31 (15 days ago) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/982585 Title: Fails to play a video which VLC can play, and that totem/gstreamer in previous Ubuntu versions could play Status in “gstreamer0.10” package in Ubuntu: New Bug description: totem/gstreamer in precise fails to play a video file which VLC in precise plays fine, and I believe I've played the same file in totem/gstreamer in older Ubuntu releases fine too. The symptoms of the failure are the totem properties declaring the video size to be 0x0 and neither audio nor video appearing. The file in question may be downloaded with: youtube-dl -f 18 lk5_OSsawz4 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 21:32:01 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm LC_COLLATE=C PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to precise on 2012-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/982585/+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 982585] Re: Fails to play a video which VLC can play, and that totem/gstreamer in previous Ubuntu versions could play
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/982585 Title: Fails to play a video which VLC can play, and that totem/gstreamer in previous Ubuntu versions could play Status in “gstreamer0.10” package in Ubuntu: New Bug description: totem/gstreamer in precise fails to play a video file which VLC in precise plays fine, and I believe I've played the same file in totem/gstreamer in older Ubuntu releases fine too. The symptoms of the failure are the totem properties declaring the video size to be 0x0 and neither audio nor video appearing. The file in question may be downloaded with: youtube-dl -f 18 lk5_OSsawz4 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 21:32:01 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: TERM=xterm LC_COLLATE=C PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to precise on 2012-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/982585/+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 869311] Re: searchplugins installation damaged after natty-oneiric upgrade
What would constitute adequate testing? Undoing manual fixing of the symlink back to being a directory, then upgrading, on an affected oneiric system? I can do that, though it might take a while, as I'm stuck on a ridiculously poor DSL line until Tuesday. -- 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/869311 Title: searchplugins installation damaged after natty-oneiric upgrade Status in Release Notes for Ubuntu: New Status in “firefox” package in Ubuntu: Fix Committed Status in “firefox” source package in Oneiric: Fix Committed Bug description: I did a natty-oneiric distribution upgrade today, and was left with Ask.com as the only option in the Firefox search box. The upgrade was from/to the following versions of the firefox package: 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 7.0.1+build1+nobinonly-0ubuntu1 After the upgrade /usr/lib/firefox-7.0.1/distribution was an empty directory, not a symlink as it is supposed to be. From /var/log/dpkg.log, I can see that the last upgrade to firefox from natty-updates was a full week ago, so I'm certain that I still had Google showing in the search box before the dist-upgrade. (Additionally, the mtime of the spurious /usr/lib/firefox-7.0.1/distribution directory matches timestamps in /var/log/dpkg.log for the unpack of the oneiric package) I also upgraded a second system natty-oneiric simultaneously - that one did *not* manifest the problem. The only pertinent difference that I can see on that system is that it had not been upgraded with SRUs for several weeks, and as such still had firefox 6.0.2+build2 +nobinonly-0ubuntu0.11.04.1 installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/869311/+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 869311] Re: searchplugins installation damaged after natty-oneiric upgrade
Tested OK - successfully changes a distribution directory to a symlink. -- 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/869311 Title: searchplugins installation damaged after natty-oneiric upgrade Status in Release Notes for Ubuntu: New Status in “firefox” package in Ubuntu: Fix Committed Status in “firefox” source package in Oneiric: Fix Committed Bug description: I did a natty-oneiric distribution upgrade today, and was left with Ask.com as the only option in the Firefox search box. The upgrade was from/to the following versions of the firefox package: 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 7.0.1+build1+nobinonly-0ubuntu1 After the upgrade /usr/lib/firefox-7.0.1/distribution was an empty directory, not a symlink as it is supposed to be. From /var/log/dpkg.log, I can see that the last upgrade to firefox from natty-updates was a full week ago, so I'm certain that I still had Google showing in the search box before the dist-upgrade. (Additionally, the mtime of the spurious /usr/lib/firefox-7.0.1/distribution directory matches timestamps in /var/log/dpkg.log for the unpack of the oneiric package) I also upgraded a second system natty-oneiric simultaneously - that one did *not* manifest the problem. The only pertinent difference that I can see on that system is that it had not been upgraded with SRUs for several weeks, and as such still had firefox 6.0.2+build2 +nobinonly-0ubuntu0.11.04.1 installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/869311/+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 869311] [NEW] searchplugins installation damaged after natty-oneiric upgrade
Public bug reported: I did a natty-oneiric distribution upgrade today, and was left with Ask.com as the only option in the Firefox search box. The upgrade was from/to the following versions of the firefox package: 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 7.0.1+build1+nobinonly-0ubuntu1 After the upgrade /usr/lib/firefox-7.0.1/distribution was an empty directory, not a symlink as it is supposed to be. From /var/log/dpkg.log, I can see that the last upgrade to firefox from natty-updates was a full week ago, so I'm certain that I still had Google showing in the search box before the dist-upgrade. (Additionally, the mtime of the spurious /usr/lib/firefox-7.0.1/distribution directory matches timestamps in /var/log/dpkg.log for the unpack of the oneiric package) I also upgraded a second system natty-oneiric simultaneously - that one did *not* manifest the problem. The only pertinent difference that I can see on that system is that it had not been upgraded with SRUs for several weeks, and as such still had firefox 6.0.2+build2+nobinonly- 0ubuntu0.11.04.1 installed. ** Affects: firefox (Ubuntu) Importance: Critical Assignee: Micah Gersten (micahg) Status: In Progress ** Affects: firefox (Ubuntu Oneiric) Importance: Critical Assignee: Micah Gersten (micahg) Status: In Progress ** Tags: oneiric regression-release -- 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/869311 Title: searchplugins installation damaged after natty-oneiric upgrade Status in “firefox” package in Ubuntu: In Progress Status in “firefox” source package in Oneiric: In Progress Bug description: I did a natty-oneiric distribution upgrade today, and was left with Ask.com as the only option in the Firefox search box. The upgrade was from/to the following versions of the firefox package: 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 7.0.1+build1+nobinonly-0ubuntu1 After the upgrade /usr/lib/firefox-7.0.1/distribution was an empty directory, not a symlink as it is supposed to be. From /var/log/dpkg.log, I can see that the last upgrade to firefox from natty-updates was a full week ago, so I'm certain that I still had Google showing in the search box before the dist-upgrade. (Additionally, the mtime of the spurious /usr/lib/firefox-7.0.1/distribution directory matches timestamps in /var/log/dpkg.log for the unpack of the oneiric package) I also upgraded a second system natty-oneiric simultaneously - that one did *not* manifest the problem. The only pertinent difference that I can see on that system is that it had not been upgraded with SRUs for several weeks, and as such still had firefox 6.0.2+build2 +nobinonly-0ubuntu0.11.04.1 installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/869311/+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 869562] [NEW] totem CPU usage playing DVD is excessive - oneiric regression
Public bug reported: After an upgrade to oneiric, I noticed totem is using an excessive amount of CPU to play a DVD - top shows between 20% - 26% on an Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz I don't have figures for natty trivially available, but I feel based on perceptions of fan speeds and how hot the laptop becomes to the touch, that this must be excessive, and a regression compared to natty. I'll be reinstalling natty on the system in question to get a better comparison. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/869562 Title: totem CPU usage playing DVD is excessive - oneiric regression Status in “totem” package in Ubuntu: New Bug description: After an upgrade to oneiric, I noticed totem is using an excessive amount of CPU to play a DVD - top shows between 20% - 26% on an Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz I don't have figures for natty trivially available, but I feel based on perceptions of fan speeds and how hot the laptop becomes to the touch, that this must be excessive, and a regression compared to natty. I'll be reinstalling natty on the system in question to get a better comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/869562/+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 869562] Re: totem CPU usage playing DVD is excessive - oneiric regression
Well, now I feel silly. Turns out CPU usage under natty was comparably high, I just never noticed until looking at things with a post-release critical eye for regressions. ** Changed in: totem (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/869562 Title: totem CPU usage playing DVD is excessive - oneiric regression Status in “totem” package in Ubuntu: Invalid Bug description: After an upgrade to oneiric, I noticed totem is using an excessive amount of CPU to play a DVD - top shows between 20% - 26% on an Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz I don't have figures for natty trivially available, but I feel based on perceptions of fan speeds and how hot the laptop becomes to the touch, that this must be excessive, and a regression compared to natty. I'll be reinstalling natty on the system in question to get a better comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/869562/+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
