[Desktop-packages] [Bug 1199571]
(In reply to Behdad Esfahbod from comment #4) Looks like copying thread-local storage macros from pixman-compiler.h and using them to use per-thread FT_Library might easily get most of this resolved. I can take a look if no one else steps in. Hi Behdad, had you time to look at this already? Regards Marek -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1199571 Title: Huge multi-threading violations in cairo Status in libcairo - cairo vector graphics library: Confirmed Status in “cairo” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/1199571/+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 1395443] [NEW] package libgbm1:amd64 10.1.3-0ubuntu0.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovam
Public bug reported: This error appeared on login. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgbm1:amd64 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Nov 20 09:12:55 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgbm1:amd64:10.1.3-0ubuntu0.2:il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0511] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-09-06 (77 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20140417-06:05 MachineType: Packard Bell EasyNote TS11HR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=6fe06780-614a-4a70-b544-ab9a85e90b87 ro quiet splash acpi_backlight=vendor intel_pstate=enable SourcePackage: mesa Title: package libgbm1:amd64 10.1.3-0ubuntu0.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJV50_HR dmi.board.vendor: Packard Bell dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnPackardBell:bvrV1.07:bd03/02/2011:svnPackardBell:pnEasyNoteTS11HR:pvrV1.07:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.07: dmi.product.name: EasyNote TS11HR dmi.product.version: V1.07 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20140915.d470f0f5-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 23 10:32:02 2014 xserver.configfile: default xserver.errors: intel: Failed to load module dri3 (module does not exist, 0) intel: Failed to load module present (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9964 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 need-duplicate-check trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1395443 Title: package libgbm1:amd64 10.1.3-0ubuntu0.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in “mesa” package in Ubuntu: New Bug description: This error appeared on login. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgbm1:amd64 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Nov 20 09:12:55 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgbm1:amd64:10.1.3-0ubuntu0.2:il pacchetto si trova in uno
[Desktop-packages] [Bug 1395443] Re: package libgbm1:amd64 10.1.3-0ubuntu0.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamen
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1395443 Title: package libgbm1:amd64 10.1.3-0ubuntu0.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in “mesa” package in Ubuntu: New Bug description: This error appeared on login. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgbm1:amd64 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Nov 20 09:12:55 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgbm1:amd64:10.1.3-0ubuntu0.2:il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0511] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-09-06 (77 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20140417-06:05 MachineType: Packard Bell EasyNote TS11HR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=6fe06780-614a-4a70-b544-ab9a85e90b87 ro quiet splash acpi_backlight=vendor intel_pstate=enable SourcePackage: mesa Title: package libgbm1:amd64 10.1.3-0ubuntu0.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJV50_HR dmi.board.vendor: Packard Bell dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnPackardBell:bvrV1.07:bd03/02/2011:svnPackardBell:pnEasyNoteTS11HR:pvrV1.07:rvnPackardBell:rnSJV50_HR:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.07: dmi.product.name: EasyNote TS11HR dmi.product.version: V1.07 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20140915.d470f0f5-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 23 10:32:02 2014 xserver.configfile: default xserver.errors: intel: Failed to load module dri3 (module does not exist, 0) intel: Failed to load module present (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9964 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1395443/+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 1166125] Re: Broken fonts for Gtk based applications
** Tags added: utopic ** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1166125 Title: Broken fonts for Gtk based applications Status in GTK+ GUI Toolkit: Unknown Status in Pango - Layout and Text Rendering LIbrary: Unknown Status in “gtk+2.0” package in Ubuntu: Invalid Status in “gtk+3.0” package in Ubuntu: Invalid Status in “pango-graphite” package in Ubuntu: Triaged Bug description: After upgrade from 12.10 to 13.04 beta of Ubuntu (Xubuntu), I am experiencing some issues. Like without me actually changing anything, my fonts are broken for some applications (most of them) and not for other (rxvt). See this http://i.imgur.com/ubVvr53.png As you can see, rxvt there is the only application with normal fonts. The Terminal application from Xfce suite is for some inexplicable reason using some kind of proportional font. See that the font in the Terminal Preferences is set to Liberation Mono. Also, please notice how in the Choose Terminal Font dialog the Courier New font Preview is not Courier New. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1166125/+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 1395450] [NEW] cannot adjust sound
Public bug reported: tried to purge and reinstall pulseaudio. When I try to start pulseaudio I get the following message: Connection to PulseAudio failed. Automatic retry in 5 s In this case this is likely because PULSE_SERVER in the Environment/X11 Root Window Properties or default-server in client.conf is misconigured. This situation can also arrise [sic] when PulseAudio crashed and left stale details in the X11 Root Window. If this is the case, then PulseAudio should autospawn again, of if this is not configured you should run start-pulseaudio-x11 manually I have no idea what this means and what I should do. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Nov 23 19:24:12 2014 InstallationDate: Installed on 2014-06-08 (168 days ago) InstallationMedia: It PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0200Y3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0200Y3:bd08/27/2009:svnSonyCorporation:pnVGN-NS50B_W:pvrC6U0MVY9:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-NS50B_W dmi.product.version: C6U0MVY9 dmi.sys.vendor: Sony Corporation ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1395450 Title: cannot adjust sound Status in “pulseaudio” package in Ubuntu: New Bug description: tried to purge and reinstall pulseaudio. When I try to start pulseaudio I get the following message: Connection to PulseAudio failed. Automatic retry in 5 s In this case this is likely because PULSE_SERVER in the Environment/X11 Root Window Properties or default-server in client.conf is misconigured. This situation can also arrise [sic] when PulseAudio crashed and left stale details in the X11 Root Window. If this is the case, then PulseAudio should autospawn again, of if this is not configured you should run start-pulseaudio-x11 manually I have no idea what this means and what I should do. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Nov 23 19:24:12 2014 InstallationDate: Installed on 2014-06-08 (168 days ago) InstallationMedia: It PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0200Y3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0200Y3:bd08/27/2009:svnSonyCorporation:pnVGN-NS50B_W:pvrC6U0MVY9:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-NS50B_W dmi.product.version: C6U0MVY9 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1395450/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
I take my previous comment back. Debian unstable also does this. -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in “network-manager” package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1250196] Re: sane plustek backend not working on USB 3 root hub
It looks like the patch had some shortcomings and I can't find a revised version anywhere. I tried applying it to Debian Jessie's 3.16 kernel and it had (what appeared to be) only minor conflicts which I resolved. Unfortunately the patched kernel doesn't compile due to incompatible upstream changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub Status in “sane-backends” package in Ubuntu: Confirmed Status in “sane-backends” package in Fedora: New Status in “sane-backends” package in Gentoo Linux: Unknown Bug description: I have a HP Scanject 2100c and a Canoscan LIDE-25 both of which use the Sane plustek backend for comms. My PC only has a USB 3 root hub, when either of these devices are connected, either directly or via an external USB 2 hub, they do not work. In general (although not always), 'scanimage -L' will detect the scanner ok: device `plustek:libusb:001:012' is a Hewlett-Packard Scanjet 2100c flatbed scanner however there is always about a 30s delay before the shell prompt is returned. Scanning always fails however, using the suggested method on the sane HOW-TO page: scanimage -vvv -format pnm outfile.pnm Calling sane_exit is the usual response. By enabling debug on the plustek backend, the response I normally get results in the following: [plustek] Vendor ID=0x03F0, Product ID=0x0505 [plustek] usbio_DetectLM983x [plustek] * could not read version register! [plustek] open failed: -1 [plustek] sane_get_devices (0x7fff0686dbc8, 0) In an effort to try and diagnose this, I've build the latest SANE backends from scratch and tried out the latest libusb none of which has resolved the issue. My original kernel was a 3.5.x, I pushed it up to 3.8.0-30 this also made no difference. My guess based on what I've seen is that this is related to the USB 3 hub. The HP Scanjet worked ok on my old Linux box (a 2.6.27 kernel with USB 2 hub) and I've had the Canon one working (albeit not that reliably) on a Raspberry Pi with a 3.6.11 kernel. The key difference (aside from this being a 64 bit flavour of Linux) is the USB. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libsane 1.0.22-7ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Mon Nov 11 19:41:08 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+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 1310551] Re: NVIDIA proprietary driver 331.38 from package nvidia-331 on Xubuntu 14.04 causes display to hang
Same problem as described for me as well Display freezes, often within 1 minute of start up. (using menus seems most dangerous) Only when using 331.38 ( +update) works fine with Intel power savings mode (still using Nvidia drivers - settings within Nvidia X server settings) ubuntu 14.4 Nvidia Gforce GT750M -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1310551 Title: NVIDIA proprietary driver 331.38 from package nvidia-331 on Xubuntu 14.04 causes display to hang Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: On 14.04 I am getting an issue on my Thinkpad T520 where running the proprietary,tested 331.38 driver causes my display to hang. It seems to stay that way until I switch to tty6 with ctrl+alt+f6 and then back to tty7 which has the display, this causes it to un-hang. This then happens back and forth. I am not sure but it might be triggered by clicking things, opening windows and such. The problem disappears when switching back to the open source driver. Should I try an even newer driver from nvidia, or is there any more information you need for troubleshooting? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 21 12:29:36 2014 InstallationDate: Installed on 2014-03-18 (33 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140318) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1310551/+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 1383737] Re: Bad version of python-clang in file cindex.py
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: llvm-toolchain-3.4 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1383737 Title: Bad version of python-clang in file cindex.py Status in “llvm-toolchain-3.4” package in Ubuntu: Confirmed Bug description: I have error: LibclangError: libclang-3.3.so: cannot open shared object file: No such file or directory. To provide a path to libclang use Config.set_library_path() or Config.set_library_file(). In file: /usr/lib/python2.7/dist-packages/clang/cindex.py In class Config we have function get_filename(self) , in this function in the last else is: file = 'libclang-3.3.so' I must improved version of libclang from 3.3 to 3.4. The line where is this error - 3361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1383737/+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 1383737] Re: Bad version of python-clang in file cindex.py
Repeat with: $ python import clang.cindex index = clang.cindex.Index.create() Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.7/dist-packages/clang/cindex.py, line 2047, in create return Index(conf.lib.clang_createIndex(excludeDecls, 0)) File /usr/lib/python2.7/dist-packages/clang/cindex.py, line 141, in __get__ value = self.wrapped(instance) File /usr/lib/python2.7/dist-packages/clang/cindex.py, line 3344, in lib lib = self.get_cindex_library() File /usr/lib/python2.7/dist-packages/clang/cindex.py, line 3375, in get_cindex_library raise LibclangError(msg) clang.cindex.LibclangError: libclang-3.3.so: cannot open shared object file: No such file or directory. To provide a path to libclang use Config.set_library_path() or Config.set_library_file(). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1383737 Title: Bad version of python-clang in file cindex.py Status in “llvm-toolchain-3.4” package in Ubuntu: Confirmed Bug description: I have error: LibclangError: libclang-3.3.so: cannot open shared object file: No such file or directory. To provide a path to libclang use Config.set_library_path() or Config.set_library_file(). In file: /usr/lib/python2.7/dist-packages/clang/cindex.py In class Config we have function get_filename(self) , in this function in the last else is: file = 'libclang-3.3.so' I must improved version of libclang from 3.3 to 3.4. The line where is this error - 3361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1383737/+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 1342175] Re: [upstream] Poor performance with find replace with empty value on large data set
Pushed for cherry-pick and review for (still upstream alive) libreoffice-4-3 branch (for LibreOffice 4.3.5, ETA Week 51 , Dec 15, 2014 - Dec 21, 2014), so we will have this on Utopic and later: https://gerrit.libreoffice.org/#/c/13041/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1342175 Title: [upstream] Poor performance with find replace with empty value on large data set Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: In Progress Bug description: [SRU justification] [Impact] Hang or Very slow performance after replaceall or searchall massive data Regression in Find and Replace with LO Calc 4.2 (last worked in 4.1). It now takes a long time to Find and Replace if the to be replaced is to nothing. See comment #5/#6 of upstream for reproducer. See commend #8 for bibisect. [Test Case] fill A column to 0 select A column Replace All 0 to ( null space ) [Regression Potential] [Other Info] upstream patch http://cgit.freedesktop.org/libreoffice/core/commit/?id=1cf19ea84794ca065749667b480dfed2d27d47b7 http://cgit.freedesktop.org/libreoffice/core/commit/?id=1e721077b43de84edab2a3ed2f316ddcbec6e3ec http://cgit.freedesktop.org/libreoffice/core/commit/?id=91502a72c12c559442e8bf77c27a516b49c2a68d To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1342175/+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 1311403] Re: Can't type password after resume.
*** This bug is a duplicate of bug 1311316 *** https://bugs.launchpad.net/bugs/1311316 ** This bug has been marked a duplicate of bug 1311316 After locking screen there is no input field to type password for unlock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+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 1377177] Re: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing
First of all I'm just a longtime Ubuntu user trying to contribute a bit to Ubuntu... The pxlcolor driver is an free generic PCL6 driver provided by ghostscript. Your printer supports hardware resolution of 600x600 dpi (according to its specifications), the higher resolution 2400x600 dpi support uses Brother Color Advanced Photoscale Technology (CAPT) especially for images, this probably requires some extra PJL initialization specific for this printer (probably something like @PJL SET APT = ON but the exact command is only known by Brother). For this one would have to look at the output sent to the printer by the Windows PCL driver (reserve engineering), since I don't have this printer that will be difficult to test. Limiting the pxlcolor driver for your printer to 600x600 dpi is the easiest and is sufficient for text printing. And if you want the higher resolution you can use the free Brother BR3 Script driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1377177 Title: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing Status in “foomatic-db” package in Ubuntu: Confirmed Bug description: printer driver: Brother MFC9840CDW Foomatic/pxlcolor (color, 2-sided printing) Result when trying to print sth. with it: PCL XL error Subsystem: TEXT Error: IllegalBitmapResolutionSegment Position: 9 reproducible: always ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 3 16:08:17 2014 Lpstat: device for MFC9840CDW: socket://10.0.0.20:9100 device for MFC9840CDW_pxlcolor: socket://10.0.0.20:9100 MachineType: Packard Bell DOTS E2 Papersize: a4 PpdFiles: MFC9840CDW: Brother MFC9840CDW Foomatic/Postscript MFC9840CDW_pxlcolor: Brother MFC9840CDW Foomatic/pxlcolor ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-36-generic root=UUID=16250f8e-725d-430c-8ccc-95387d8f9ba7 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V3.16(DDR3) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE02_PT_E dmi.board.vendor: Packard Bell dmi.board.version: V3.16(DDR3) dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V3.16(DDR3) dmi.modalias: dmi:bvnPackardBell:bvrV3.16(DDR3):bd04/22/2011:svnPackardBell:pnDOTSE2:pvrV3.16(DDR3):rvnPackardBell:rnSJE02_PT_E:rvrV3.16(DDR3):cvnPackardBell:ct10:cvrV3.16(DDR3): dmi.product.name: DOTS E2 dmi.product.version: V3.16(DDR3) dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1377177/+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 383495] Re: E-mails cannot be moved to different IMAP folder by dragging
does this ever occur in trusty or later? ** Changed in: thunderbird (Ubuntu) Status: New = Incomplete ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) = Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/383495 Title: E-mails cannot be moved to different IMAP folder by dragging Status in “thunderbird” package in Ubuntu: Incomplete Bug description: When I am trying to move a read mail into my archive folder on my IMAP mail account nothing happens. I have attached a screen cast showing what happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/383495/+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 1389781] Re: A2DP works randomly
Bryan Paradis : I'm sorry but using pulseaudio instead of the system configuration menu doesn't change anything for me (but I'm using KDE, so maybe there isn't the bug that affects Unity ?). But my problem is still here, even with Disable=Headset in my /etc/bluetooth/audio.conf sometimes I need a full reboot to make my bluetooth headset working (sudo services bluetooth restart isn't always enough). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1389781 Title: A2DP works randomly Status in “bluez” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: New Bug description: Hello, There is a problem with the bluetooth mode A2DP. When I connect my bluetooth headphone, sometimes I can activate the A2DP mode (which gives a good sound quality) and sometimes I can't (nothing happened when I change it in the configuration window), and I need to switch to HFS/HFP (bad sound quality). Note that some logs are attached. I found on the internet a work around which is to put in /etc/bluetooth/audio.conf a line Disable=Socket It seems to work (well it's hard to say for the moment because I didn't have the time to do much tests), but I would like to know what Socket is supposed to do. Would it be possible to solve this bug when Socket is activated too ? Thank you, Tobias. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1389781/+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 1289202] Re: archive function does not always work - regression
this still affects me, but now a folder #mbox/Sent/Archives is created while all my folders are either local or in IMAP maildir. I cannot remember if back in March nothing happened or it was also creating that folder. It's pretty annoying in any case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1289202 Title: archive function does not always work - regression Status in “thunderbird” package in Ubuntu: New Bug description: == Regression details == Discovered in version: 1:24.3.0+build2-0ubuntu0.12.04.1 Last known good version: 1:24.2.0+build1-0ubuntu0.12.04.1 I am running an up-to-date precise installation. Since about two weeks, pressing 'a' or choosing Archive from the context menu stops to work about 50% of the times. I have run thunderbird in safe-mode and it still occurs. This used to work for a long time, so it's a regression. /var/log/dpkg.log.1:2014-02-22 07:53:19 upgrade thunderbird 1:24.2.0+build1-0ubuntu0.12.04.1 1:24.3.0+build2-0ubuntu0.12.04.1 I found above line in the logs so I suspect that's what brought about the regression. I'll try to downgrade for confirmation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1289202/+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 194573] Re: sound in thunderbird
thanks, closing ** Changed in: thunderbird (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/194573 Title: sound in thunderbird Status in Mozilla Thunderbird Mail and News: Invalid Status in “thunderbird” package in Ubuntu: Invalid Bug description: Binary package hint: thunderbird bug could also be in alsa or pulse or something Instead of the new mail sound, thunderbird just freezes, screen darkens,and several minutes later unfreezes. This is with ubuntu 8.4 with all latest upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/194573/+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 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed.
** Changed in: sun-java6 (Ubuntu Hardy) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/87947 Title: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed. Status in “libx11” package in Ubuntu: Fix Released Status in “libxcb” package in Ubuntu: Fix Released Status in “sun-java6” package in Ubuntu: Fix Released Status in “libx11” source package in Hardy: Invalid Status in “libxcb” source package in Hardy: Invalid Status in “sun-java6” source package in Hardy: Won't Fix Status in “libx11” package in Debian: Fix Released Bug description: Hello, many things crash with following information[1] [1] xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed. Step to reproduce: install fcitx, xterm, then run $ export XMODIFIERS=@im=fcitx $ export GTK_IM_MODULE=xim $ fcitx $ xterm then press Ctrl+Space in the xterm window, then xterm crashed with the previous information. ii libxcb-xlib0 1.0-1.1 X C Binding, Xlib/XCB interface library ii libxcb-xlib0-dev 1.0-1.1 X C Binding, Xlib/XCB interface library, development files ii libxcb1 1.0-1.1 X C Binding ii libxcb1-dev 1.0-1.1 X C Binding, development files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/87947/+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 526203] Re: a specially crafted message can cause thunderbird message control to be hidden
does this ever occur in trusty or later? ** Changed in: thunderbird (Ubuntu) Status: New = Incomplete ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) = Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/526203 Title: a specially crafted message can cause thunderbird message control to be hidden Status in “thunderbird” package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird 1) eve:[~]% lsb_release -rd Description: Ubuntu lucid (development branch) Release: 10.04 2) eve:[~]% apt-cache policy thunderbird thunderbird: Installed: 3.0.1+nobinonly-0ubuntu1 Candidate: 3.0.1+nobinonly-0ubuntu1 Version table: *** 3.0.1+nobinonly-0ubuntu1 0 500 http://uk.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status eve:[~]% 3) A message to put displayed with the normal, delete, archive, junk, etc. buttons. 4) The buttons were not displayed. Please find attached two screenshots illustrating the problem. 5) I have flagged this a security bug because, if you can visually exceed the widget buffer it might be possible to cause a buffer overflow that is more damaging (you can still process the message just with keyboard shortcuts) ProblemType: Bug Architecture: i386 Date: Tue Feb 23 03:49:40 2010 DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.1+nobinonly-0ubuntu1 ProcEnviron: LANGUAGE=en_AU.utf8 PATH=(custom, user) LANG=en_AU.utf8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: thunderbird Uname: Linux 2.6.32-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/526203/+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 427602] Re: rhythmbox crashed with SIGSEGV in g_cclosure_marshal_VOID__STRING()
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: rhythmbox (Ubuntu Hardy) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/427602 Title: rhythmbox crashed with SIGSEGV in g_cclosure_marshal_VOID__STRING() Status in “rhythmbox” package in Ubuntu: Invalid Status in “rhythmbox” source package in Hardy: Won't Fix Status in “rhythmbox” source package in Karmic: Invalid Bug description: Binary package hint: rhythmbox CVE-2008-7185 Hardy: http://packetstormsecurity.org/0806-advisories/rhythmbox-dos.txt Intrepid, Jaunty, Karmic are not affected. Likely the same as bug 270139. Seems to be executing heap (!!) after calling playlist_load_ended_cb(). $ mkdir /tmp/i $ cd /tmp/i $ apport-unpack /tmp/_usr_bin_rhythmbox.1000.crash . $ python /usr/share/apport/general-hooks/parse_segv.py Registers Disassembly ProcMaps executing writable VMA [heap] reading unknown VMA Segfault happened at: 0x8461c5e: sbb(%eax),%cl PC (0x08461c5e) in non-executable VMA region: 0x080dc000-0x08c39000 rw-p [heap] source (%eax) (0x40082ee1) not located in a known VMA region (needed readable region)! destination %cl ok ProblemType: Crash Architecture: i386 Date: Thu Sep 10 15:42:22 2009 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.5-0ubuntu8 PackageArchitecture: i386 ProcCmdline: rhythmbox ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () ?? () g_cclosure_marshal_VOID__STRING () g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in g_cclosure_marshal_VOID__STRING() Uname: Linux 2.6.24-24-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy plugdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/427602/+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 212510] Re: [gutsy] [hardy]No signal with Samsung SyncMaster 750s
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-ati (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/212510 Title: [gutsy] [hardy]No signal with Samsung SyncMaster 750s Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Status in “xserver-xorg-video-ati” source package in Hardy: Won't Fix Status in “xserver-xorg-video-ati” source package in Intrepid: Fix Released Bug description: Video card: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] Monitor: Samsung SyncMaster 750s Monitor in stand-by video: http://it.youtube.com/watch?v=hr7p6WXLCQk It works with VESA driver... Bug affects Gutsy and Hardy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/212510/+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 372118] Re: CUPS does not work with Firefox, HTTPS bug (Hardy LTS)
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: cups (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/372118 Title: CUPS does not work with Firefox, HTTPS bug (Hardy LTS) Status in “cups” package in Ubuntu: Fix Released Status in “cups” source package in Hardy: Won't Fix Status in “cups” package in Debian: Fix Released Bug description: Binary package hint: cups CUPS forces the use of httpS connection to add a new printer. There is a bug in CUPS-1.3.7 with httpS connection when connecting interface with Firefox 3. The official CUPS bug report is here : http://www.cups.org/str.php?L2892 The bug is corrected in CUPS-1.3.9. This version is present on Ubuntu Jaunty. * Hardy/LTS will be supported for 5 years long. * It is impossible to add a printer with Firefox 3 on LTS (do not want to push users to use IE instead). Is it possible to backport CUPS from Jaunty to LTS (Hardy) ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/372118/+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 330756] Re: [GM45] X freezes when playing ogg vorbis, ogg theora or mp3 in Totem
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Triaged = Won't Fix -- 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/330756 Title: [GM45] X freezes when playing ogg vorbis, ogg theora or mp3 in Totem Status in “xorg” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xorg” source package in Hardy: Invalid Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Bug description: Binary package hint: totem Totem hangs my system anytime I try to play media files. It is Totem 2.22.1 running on Hardy 8.04.2 on an IBM Thinkpad R400. I tried the example video Experience ubuntu.ogg, the example audio ubuntu Sax.ogg and an MP3 file. I tried the MP3 file after installing the gstreamer plugins. I will be glad to provide more hardware details. I have tried it with and without desktop effects enabled. The screen resolution is 1280x800. When the system hangs, only the mouse moves. All other activity is frozen. I have to force a power off to recover. WORKAROUND: https://bugs.edge.launchpad.net/ubuntu/+bug/330756/comments/23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/330756/+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 293346] Re: [i945gme] [Hardy] 3D Graphic stop working after resume and resolution change
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/293346 Title: [i945gme] [Hardy] 3D Graphic stop working after resume and resolution change Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Bug description: Binary package hint: xserver-xorg-video-intel This bug can be reproduced the following way: 1) xrandr --size 800x600 2) sudo pm-hibernate 3) resume 4) xrandr --size 1024x600 The 3D graphics disappear and a white frame is shown, with 2D graphics continuing to work. After switching to virtual console and back the 3D graphics are restored. lspci output on the graphics hardware: lspci -nn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) lspci -nn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) lspci -vnn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) lspci -vnn: Subsystem: Toshiba America Info Systems Unknown device [1179:ff1e] lspci -vnn: Flags: bus master, fast devsel, latency 0, IRQ 23 lspci -vnn: Memory at 5428 (32-bit, non-prefetchable) [size=512K] lspci -vnn: I/O ports at 40f0 [size=8] lspci -vnn: Memory at 4000 (32-bit, prefetchable) [size=256M] lspci -vnn: Memory at 5430 (32-bit, non-prefetchable) [size=256K] lspci -vnn: Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- lspci -vnn: Capabilities: [d0] Power Management version 2 lspci -vnn: lspci -vnn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) lspci -vnn: Subsystem: Toshiba America Info Systems Unknown device [1179:ff1e] lspci -vnn: Flags: bus master, fast devsel, latency 0 lspci -vnn: Memory at 5420 (32-bit, non-prefetchable) [size=512K] lspci -vnn: Capabilities: [d0] Power Management version 2 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/293346/+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 297245] Re: [i965] Dell Studio 15 White Screen on X startup
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/297245 Title: [i965] Dell Studio 15 White Screen on X startup Status in X.org xf86-video-intel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “xorg” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “linux” source package in Hardy: Invalid Status in “xorg” source package in Hardy: Invalid Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Status in “linux” source package in Intrepid: Invalid Status in “xorg” source package in Intrepid: Invalid Status in “xserver-xorg-video-intel” source package in Intrepid: Fix Released Bug description: [Problem] On X server load, displays white screen with scattered 1 pixel lines when using -intel driver. [Impact] Affects users owning hardware with certain LVDS displays produced by AUO, such as used in the Dell Studio 15 and Studio 1535; reportedly some Sony systems may be fixed by this as well. These are currently shipping models from Dell; they had been shipped with Ubuntu pre-installed, making this a particularly severe problem. [Development Branch] Same patch is deployed to Jaunty in version 2.5.1-1ubuntu9 This patch is a correction to a long standing bug where the -intel driver generates slightly incorrect modelines. Most systems tolerate the slight error, but others (like the ones affected by this bug) don't. [Patch] From upstream - https://bugs.freedesktop.org/show_bug.cgi?id=18342 Identical patch used in Intrepid and Jaunty [Test Case] Boot LiveCD on hardware with affected LVDS; will result in white screen following usplash. [Regression Potential] This changes the modeline calculations in general (i.e. it is not a hardware-specific quirk). Regression could occur under two theoretical circumstances: 1. Logic error. If the patch is mis-coded, it could cause all modelines to be miscalculated. This is not felt to be very likely, especially since the patch is very simple. However if it does happen, it will be exceedingly obvious... 2. Uncovering secondary bugs. It is entirely possible (but perhaps extraordinarily unlikely) that some hardware has slightly buggy timing dependencies the other way round, and are dependent on the buggy timing calculations, and could exhibit problems once the issue is fixed. However the risk of this is probably vanishingly small, and if it does happen will probably affect only a few systems, and the fix ought to be fairly straightforward. In both the above cases, ample testing will mitigate the risk levels. [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Unknown device [1028:0254] [Original Report] I purchased a Dell Studio 15 with Ubuntu pre-installed. The graphics adapter is an Intel x3100 The LCD is 1280x800. I suspect that the LCD is not compatible with the current version of the Linux driver. Out of the box, the loading screens appear just fine. Once the X server loads, the screen goes mostly white, with some scattered lines, each about 1 pixel wide. I then booted to recovery mode and selected the option for the system to attempt to fix X on its own. This resulted in a White Screen of Death as well. Any attempt to use the Intel driver results in a White Screen of Death. Vesa will not recognize a 1280x800 resolution and only gives 800x600 upon initial installation. After installing KDE the screen results in 1024x768 but still will not work in 1280x800, even though those resolutions are listed in the Modelines in xorg.conf. Bug is present in Ubuntu 8.04 and 8.10, if not more. The worst part is that even the replacement Dell Studio 15 has this same problem. I suspect that Dell is knowingly selling a model of laptop that is supposedly approved hardware that they never got to work in the first place. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/297245/+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 188732] Re: Blinking cursor can not be deactivated anymore
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: gnome-terminal (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/188732 Title: Blinking cursor can not be deactivated anymore Status in GNOME Terminal: Fix Released Status in “gnome-terminal” package in Ubuntu: Fix Released Status in “gnome-terminal” source package in Hardy: Won't Fix Bug description: Binary package hint: gnome-terminal Using a fully upgraded Ubuntu Hardy Heron Development Release (as of today Sun Feb 3 2008) and gnome-terminal 2.21.90, there is no option to disable the blinking of the cursor in the terminal anymore. This option used to be located in the Edit Current Profile menu. I even tried to activate it through gconf-editor, to no avail (in apps/gnome- terminal/profiles/Default). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/188732/+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 212761] Re: gnome-terminal crashes when customizing colors
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: gnome-terminal (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/212761 Title: gnome-terminal crashes when customizing colors Status in GNOME Terminal: Expired Status in “gnome-terminal” package in Ubuntu: Fix Released Status in “gnome-terminal” source package in Hardy: Won't Fix Bug description: Binary package hint: gnome-terminal When having terminal windows open with different profiles, customizing the background color in one of them will crash gnome-terminal and all terminal windows will die. In my case, - have a remote irssi screen open in a gnome-terminal window with profile=irssi - open another terminal with profile=default - customize the background color of the default profile -- gnome-terminal will crash. ProblemType: Crash Architecture: i386 Date: Sun Apr 6 13:09:55 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gnome-terminal Package: gnome-terminal 2.22.0-0ubuntu1 PackageArchitecture: i386 ProcCmdline: gnome-terminal --window-with-profile=irssi --geometry=93x30 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gnome-terminal Stacktrace: #0 0x0807008c in ?? () #1 0x in ?? () StacktraceTop: ?? () ?? () Title: gnome-terminal crashed with SIGSEGV Uname: Linux 2.6.24-14-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/212761/+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 200462] Re: Copying Files From CD/DVD Sets Permissions To Read Only
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: gvfs (Ubuntu Hardy) Status: Triaged = Won't Fix -- 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/200462 Title: Copying Files From CD/DVD Sets Permissions To Read Only Status in GVFS: Fix Released Status in “gvfs” package in Ubuntu: Fix Released Status in “gvfs” source package in Hardy: Won't Fix Bug description: Binary package hint: nautilus When I copy files from a CD or DVD to my Home directory, the files that are copied are given read only permissions. Prior to Hardy, the user that copied the files would have read/write permissions. Steps to reproduce: 1.) Burn a data cd or dvd 2.) Copy the files to your Desktop or Home directories 3.) The files that were saved will be read only Regression Details Discovered in version: gvfs 0.2.3-0ubuntu4? (8.04) Last known good version: nautilus 1:2.20.0-0ubuntu7? (7.10) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/200462/+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 229229] Re: Right mouse wheel tilt kills xorg
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xorg-server (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/229229 Title: Right mouse wheel tilt kills xorg Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Hardy: Won't Fix Status in “xorg-server” package in Debian: Fix Released Bug description: Binary package hint: xserver-xorg-input-evdev When using a MS Wireless 5000 mouse configured with evdev, tilting the wheel to the right which should be a button event kills the xorg server. Relevant part of the xorg.conf : - Paste # this is the evdev version of the mouse declaration Section InputDevice Identifier MS Wireless 5000 Driver evdev option device /dev/input/event2 # option device /dev/input/mouse0 # Using the link doesn't work ?? # option device /dev/input/by-id/usb-Microsoft_Microsoft_Wireless_Optical_Mouse_1.00-mouse option CorePointer # Reference by name only below doesn't seem to work # option name Microsoft Microsoft Wireless Optical Mouse® 1.00 option Phys usb-:00:1a.7-3.1.2/input0 option Buttons 9 option ZAxisMapping 4 5 EndSection - End Paste I also tried using the mouse driver, letting it pick the protocol (it picked PS/2) which didn't work, then picking USB which seemed appropriate but the mouse driver didn't know what to make of it. When the X server fails, it outputs the following message (from Xorg.0.log) --- paste Fatal server error: Bad valuators reported for device MS Wireless 5000 (II) MS Wireless 5000: Off -- End paste I reported this as being from evdev as it seems to be a bug that has been nailed in xfree : https://bugs.freedesktop.org/show_bug.cgi?id=14342 but might not have trickled down to production versions yet. I didn't see that many references to that thing, let me know if you need more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/229229/+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 156824] Re: [915GM] closing lid breaks X (jumping cursor, sluggish, high cpu usage ... )
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/156824 Title: [915GM] closing lid breaks X (jumping cursor, sluggish, high cpu usage ... ) Status in X.Org X server: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Bug description: Binary package hint: xorg I recently updated to Gutsy on my HP Compaq TC4200. It's a tablet that uses mostly Intel hardware, a Broadcom wired ethernet (it works), and a Texas Instruments card reader, for what it's worth. When I come back to it after I've closed the lid (Under Power Management Preferences I have it set to When laptop lid is closed: Blank screen, the default), the poor thing becomes possessed: * The cursor jumps around insanely when I move the mouse. * Everything becomes painfully sluggish and unusable. * Sometimes windows I'm working with go dark and unresponsive (Compiz effect, though I have this same issue if I turn off desktop effects, so it's probably not Compiz related) * top shows that Xorg is hogging up between 40% and 70% of CPU cycles. * I can't get a Ctrl-Alt-F1-F6 consoles to come up (They flash onscreen for a split second and then the screen goes black, sometimes with a white arrow cursor frozen on it somewhere...). * When I do a Ctrl-Alt-Backspace to reset the X server, I notice the characters ^@ start appearing across the screen. * A Ctrl-Alt-Backspace doesn't fix the problem. * Sometimes the X server resets itself with no outside influence (behaves like I'd hit Ctrl-Alt-Backspace) * Sometimes/eventually the laptop becomes completely unresponsive. I only recently figured out that the problem seemed to happen after I closed the lid and opened it back up. I'm going to try switching my When laptop lid is closed: option to Do nothing to see if that helps me avoid this crippling and seemingly random (before I figured out that it might be related to the lid closing) possession. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/156824/+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 244413] Re: unichrome pro igp 1019:aa51 supported but not detected
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-openchrome (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/244413 Title: unichrome pro igp 1019:aa51 supported but not detected Status in “xserver-xorg-video-openchrome” package in Ubuntu: Fix Released Status in “xserver-xorg-video-openchrome” source package in Hardy: Won't Fix Status in “xserver-xorg-video-openchrome” source package in Intrepid: Fix Released Bug description: Binary package hint: xserver-xorg-video-openchrome This PCI ID is not listed in /usr/share/xserver- xorg/pci/openchrome.ids, so when X starts, it doesn't realise openchrome supports the device and tries to fall back to VESA. This fails (it looks like X starts but dies very quickly). I added 'Driver openchrome' to the Device section, and X starts and works beautifully. Haven't tested things like 3D yet, but the machine can certainly handle very demanding browser usage (it's a web kiosk). This bug impacts just-works out-of-the-box operation on 8.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/244413/+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 150187] Re: Evince has very bad quality when printing pdf files.
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: poppler (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/150187 Title: Evince has very bad quality when printing pdf files. Status in Poppler: Fix Released Status in “cupsys” package in Ubuntu: Invalid Status in “poppler” package in Ubuntu: Fix Released Status in “cupsys” source package in Hardy: Invalid Status in “poppler” source package in Hardy: Won't Fix Bug description: Evince prints every pdf I send, with very bad quality, and printing is very slow. Kpdf does not suffer of this problem, printing is high quality and fast. Looks like evince is rendering pdf to a very low quality image. I also tried printing some text from gedit, and it is of perfect quality too. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/150187/+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 252885] Re: Drag-and-drop theme from web page fails
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: gnome-control-center (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/252885 Title: Drag-and-drop theme from web page fails Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Hardy: Won't Fix Bug description: Binary package hint: gnome-control-center http://www.arsgeek.org/2008/05/31/six-annoyances-in-hardy-heron- ubuntu/ reports that it is no longer possible to drag-and-drop themes from a web page into System - Preferences - Appearance (Theme tab), as of Hardy. This appears to be because theme_drag_data_received_cb does g_file_get_path on a GFile constructed on the dragged-and-dropped URI, which only returns non-NULL on local files. Something would need to arrange to actually download the theme if it isn't local. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/252885/+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 207881] Re: [Gutsy, Hardy] Black screen with mouse pointer on i830, intel driver (PipeA quirk needed)
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/207881 Title: [Gutsy, Hardy] Black screen with mouse pointer on i830, intel driver (PipeA quirk needed) Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Status in “xserver-xorg-video-intel” source package in Intrepid: Fix Released Bug description: On request, moved this bug report from bug 123283. Which covers very similar symptoms on ATI hardware. Binary package hint: xserver-xorg-video-intel Here's what happened on my laptop in Hardy: - Xubuntu Hardy beta live CD - Insert CD, boot to desktop - wait several minutes with no mouse activity - screen goes completely blank - move mouse - screen came back - wait few minutes - screen completely blank. While the screen is completely black, I can see feint detail on the screen (like the back-light is off but the screen still has stuff on it). - move mouse. When I move the mouse the back-light comes on but the screen is black apart from the mouse pointer. - mouse pointer appeared but screen still blank, mouse responds to movement and cursor changes when hovering over a text field for example, computer appears to respond to input (clicking etc.) - VT switch to terminal 1 - VT switch to terminal 7 - screen came back to normal. In Gutsy, I cannot VT switch but if I ssh into the box and temporarily start a new X server and then kill it, that restores the original screen (possibly because it causes a VT switch). To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/207881/+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 111674] Re: [FireGL V5000] can't change resolution on compaq nw8240
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-ati (Ubuntu Hardy) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/111674 Title: [FireGL V5000] can't change resolution on compaq nw8240 Status in X.Org X server: Fix Released Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Status in “xserver-xorg-video-ati” source package in Hardy: Won't Fix Bug description: Binary package hint: xserver-xorg-driver-ati I'm using an HP Compaq NW8240 notebook with an ATI Mobility FireGL V5000 PCIE chipset. Under 6.10, I could use either the ati driver or the fglrx driver to have both widescreen and normal resolutions from 1920x1200 down to 640x480. In 7.04 the OSS ati driver seems to suffer from an inability to use any resolution other than 1920x1200. It seems to autodetect all the resolutions my notebook supports, but setting any resolution other than 1920x1200 results the screenshot I'm about to attach, along with my xorg.conf. The fglrx driver enabled by Restricted Drivers Manager works just fine (although no AIGLX support with that). With the ATI driver I do get both hardware accel and AIGLX, I'm just stuck with that one resolution To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/111674/+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 221673] Re: ALSA failing with PulseAudio in Hardy
Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: alsa-plugins (Ubuntu Hardy)
Status: Triaged = Won't Fix
--
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/221673
Title:
ALSA failing with PulseAudio in Hardy
Status in “alsa-lib” package in Ubuntu:
Fix Released
Status in “alsa-plugins” package in Ubuntu:
Fix Released
Status in “pulseaudio” package in Ubuntu:
Invalid
Status in “alsa-lib” source package in Hardy:
Won't Fix
Status in “alsa-plugins” source package in Hardy:
Won't Fix
Status in “pulseaudio” source package in Hardy:
Invalid
Bug description:
Binary package hint: pulseaudio
I had been using PulseAudio in Gutsy for the past several months, so
all the mundane stuff (groups, permissions, config files) is
configured correctly. Since the upgrade to Hardy, ALSA is unable to
use PulseAudio anymore. Details follow:
- I am in the groups pulse-rt and pulse-access
- ALSA without PulseAudio works just fine
- PulseAudio seems to work fine with GStreamer
Here's what my .asoundrc looks like:
===
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
pcm.!default { type pulse }
ctl.!default { type pulse }
===
I'm attaching my default.pa with the bug.
Here's the output of 'pulseaudio -vvv' when I try to run speaker-test (only
relevant portion here, full output attached):
I: client.c: Created 1 Native client (UNIX socket client)
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 1 changed name from Native client (UNIX socket client)
to ALSA plug-in [speaker-test]
I: client.c: Freed 1 ALSA plug-in [speaker-test]
I: protocol-native.c: connection died.
speaker-test fails with the following:
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 43 to 349525
Period size range from 21 to 87382
Using max buffer size 349524
Periods = 4
was set period_size = 87381
was set buffer_size = 349524
*** PULSEAUDIO: Unable to create stream.
Unable to set hw params for playback: Input/output error
Setting of hwparams failed: Input/output error
speaker-test: pcm_pulse.c:115: pulse_stop: Assertion `pcm-stream' failed.
Aborted
TEST CASE:
1. Create an .asoundrc file in your home directory to direct alsa to use the
pulseaudio plugin by default for all sound output. This is done with the
command asoundconf set-pulseaudio
2. Attempt to run speaker-test with the following command: speaker-test
-twav -c2
3. You should get the following error:
*** PULSEAUDIO: Unable to create stream.
speaker-test: pcm_pulse.c:115: pulse_stop: Assertion `pcm-stream' failed.
speaker-test 1.0.15
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 128 to 1048576
Period size range from 64 to 262144
Using max buffer size 1048576
Periods = 4
was set period_size = 262144
was set buffer_size = 1048576
Unable to set hw params for playback: Input/output error
Setting of hwparams failed: Input/output error
NOTE: This SRU is in two parts, one for alsa-lib, and the other for
alsa-plugins. The new revision of alsa-plugins requires the new revision of
alsa-lib in order to function properly.
Intrepid status:
This bug is fixed with alsa-lib 1.0.16 and alsa-plugins 1.0.16 which are both
in intrepid.
Regression potential:
The diffs in comments 8 and 9 introduce fixes and in the case of alsa-lib,
new symbols to be used by alsa-plugins to allow the pulse alsa-plugin to
functino properly No other plugin's functionality should be affected with these
changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/221673/+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 221673] Re: ALSA failing with PulseAudio in Hardy
Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as Won't Fix.
** Changed in: alsa-lib (Ubuntu Hardy)
Status: Triaged = Won't Fix
--
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/221673
Title:
ALSA failing with PulseAudio in Hardy
Status in “alsa-lib” package in Ubuntu:
Fix Released
Status in “alsa-plugins” package in Ubuntu:
Fix Released
Status in “pulseaudio” package in Ubuntu:
Invalid
Status in “alsa-lib” source package in Hardy:
Won't Fix
Status in “alsa-plugins” source package in Hardy:
Won't Fix
Status in “pulseaudio” source package in Hardy:
Invalid
Bug description:
Binary package hint: pulseaudio
I had been using PulseAudio in Gutsy for the past several months, so
all the mundane stuff (groups, permissions, config files) is
configured correctly. Since the upgrade to Hardy, ALSA is unable to
use PulseAudio anymore. Details follow:
- I am in the groups pulse-rt and pulse-access
- ALSA without PulseAudio works just fine
- PulseAudio seems to work fine with GStreamer
Here's what my .asoundrc looks like:
===
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
pcm.!default { type pulse }
ctl.!default { type pulse }
===
I'm attaching my default.pa with the bug.
Here's the output of 'pulseaudio -vvv' when I try to run speaker-test (only
relevant portion here, full output attached):
I: client.c: Created 1 Native client (UNIX socket client)
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 1 changed name from Native client (UNIX socket client)
to ALSA plug-in [speaker-test]
I: client.c: Freed 1 ALSA plug-in [speaker-test]
I: protocol-native.c: connection died.
speaker-test fails with the following:
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 43 to 349525
Period size range from 21 to 87382
Using max buffer size 349524
Periods = 4
was set period_size = 87381
was set buffer_size = 349524
*** PULSEAUDIO: Unable to create stream.
Unable to set hw params for playback: Input/output error
Setting of hwparams failed: Input/output error
speaker-test: pcm_pulse.c:115: pulse_stop: Assertion `pcm-stream' failed.
Aborted
TEST CASE:
1. Create an .asoundrc file in your home directory to direct alsa to use the
pulseaudio plugin by default for all sound output. This is done with the
command asoundconf set-pulseaudio
2. Attempt to run speaker-test with the following command: speaker-test
-twav -c2
3. You should get the following error:
*** PULSEAUDIO: Unable to create stream.
speaker-test: pcm_pulse.c:115: pulse_stop: Assertion `pcm-stream' failed.
speaker-test 1.0.15
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 128 to 1048576
Period size range from 64 to 262144
Using max buffer size 1048576
Periods = 4
was set period_size = 262144
was set buffer_size = 1048576
Unable to set hw params for playback: Input/output error
Setting of hwparams failed: Input/output error
NOTE: This SRU is in two parts, one for alsa-lib, and the other for
alsa-plugins. The new revision of alsa-plugins requires the new revision of
alsa-lib in order to function properly.
Intrepid status:
This bug is fixed with alsa-lib 1.0.16 and alsa-plugins 1.0.16 which are both
in intrepid.
Regression potential:
The diffs in comments 8 and 9 introduce fixes and in the case of alsa-lib,
new symbols to be used by alsa-plugins to allow the pulse alsa-plugin to
functino properly No other plugin's functionality should be affected with these
changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/221673/+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 242191] Re: Xdmx packages missing in hardy
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xorg-server (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/242191 Title: Xdmx packages missing in hardy Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Hardy: Won't Fix Bug description: Binary package hint: xserver-xorg Filed against xserver-xorg, since choosing Xdmx (which is recognized correctly) results in an error. Hello, for some unknown reason the packages xdmx and xdmx-tools are missing in hardy. xdmx provides network distributed X multihead support, a feature i can not find in any other package or software. Please see discussion at [1]. The xdmx packages from gutsy ([2] and [3]) seem to work fine in hardy though. So there's no real reason I can see why the were removed. Please provide these packages again in the future. [1] http://ubuntuforums.org/showthread.php?t=331801 [2] http://packages.ubuntu.com/gutsy/xdmx [3] http://packages.ubuntu.com/gutsy/x11/xdmx-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/242191/+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 211663] Re: evolution crashed with SIGSEGV after importing Digg feed
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: evolution-rss (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/211663 Title: evolution crashed with SIGSEGV after importing Digg feed Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Invalid Status in “evolution-rss” package in Ubuntu: Fix Released Status in “evolution” source package in Hardy: Invalid Status in “evolution-rss” source package in Hardy: Won't Fix Bug description: Binary package hint: evolution Using evolution-rss, Digg feed: http://digg.com/rss/index.xml ProblemType: Crash Architecture: i386 Date: Thu Apr 3 23:52:23 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: nvidia Package: evolution 2.22.0-0ubuntu2 PackageArchitecture: i386 ProcCmdline: evolution --component=mail ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: evolution StacktraceTop: ?? () ?? () ?? () ?? () from /usr/lib/libxml2.so.2 ?? () Title: evolution crashed with SIGSEGV Uname: Linux 2.6.24-14-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/211663/+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 124706] Re: Cancel 'Wireles Key Required' dialog, can't connect on subsequent attempt
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: network-manager (Ubuntu Hardy) Status: In Progress = Won't Fix -- 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/124706 Title: Cancel 'Wireles Key Required' dialog, can't connect on subsequent attempt Status in The acton project: Fix Released Status in NetworkManager: Expired Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Hardy: Won't Fix Status in “network-manager” source package in Intrepid: Fix Released Bug description: Binary package hint: network-manager - Sometimes, NM tries to connect, but thinks association failed because of wrong credentials. - NM and asks for a password then. - I press 'Cancel' and try again. - Most of the cases, connection then works If this bug happens, I always have this snippet in the log: Jul 8 09:59:33 faui44a NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed Jul 8 09:59:33 faui44a NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed Version information: ii network-manager 0.6.5-0ubuntu6 network management framework daemon To manage notifications about this bug go to: https://bugs.launchpad.net/acton/+bug/124706/+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 247480] Re: evolution crashed with SIGSEGV in e_cal_menu_target_new_select()
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: evolution (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/247480 Title: evolution crashed with SIGSEGV in e_cal_menu_target_new_select() Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Fix Released Status in “evolution” source package in Hardy: Won't Fix Bug description: Binary package hint: evolution Evolution crashed while my laptop was left unattended. Therefore I cannot tell which action lead to this crash. In the terminal where I started evolution, the following messages were displayed before the crash: (evolution:2814): Gtk-CRITICAL **: gtk_status_icon_set_visible: assertion `GTK_IS_STATUS_ICON (status_icon)' failed (evolution:2814): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed camel-Message: -- Making error camel-Message: -- (evolution:2814): calendar-gui-CRITICAL **: e_cal_model_get_component_at: assertion `row = 0 row priv-objects-len' failed (evolution:2814): calendar-gui-CRITICAL **: e_cal_model_copy_component_data: assertion `comp_data != NULL' failed [1]+ Segmentation fault (core dumped) evolution (wd: ~) ProblemType: Crash Architecture: i386 Date: Thu Jul 10 19:53:49 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: fglrx Package: evolution 2.22.3.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: evolution Signal: 11 SourcePackage: evolution StacktraceTop: e_cal_menu_target_new_select () tasks_control_sensitize_commands () ?? () from /usr/lib/evolution/2.22/components/libevolution-calendar.so g_cclosure_marshal_VOID () from /usr/lib/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 Title: evolution crashed with SIGSEGV in e_cal_menu_target_new_select() Uname: Linux 2.6.24-19-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev pulse-rt scanner staff video To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/247480/+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 277069] Re: Slow performance with remote X applications (java, firefox/xul, etc.)
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: libxcb (Ubuntu Hardy) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/277069 Title: Slow performance with remote X applications (java, firefox/xul, etc.) Status in libxcb: Fix Released Status in “ia32-libs” package in Ubuntu: Fix Released Status in “libx11” package in Ubuntu: Invalid Status in “libxcb” package in Ubuntu: Fix Released Status in “ia32-libs” source package in Hardy: Won't Fix Status in “libx11” source package in Hardy: Invalid Status in “libxcb” source package in Hardy: Won't Fix Status in “ia32-libs” source package in Intrepid: Invalid Status in “libx11” source package in Intrepid: Invalid Status in “libxcb” source package in Intrepid: Invalid Status in “ia32-libs” source package in Jaunty: Won't Fix Status in “libx11” source package in Jaunty: Invalid Status in “libxcb” source package in Jaunty: Won't Fix Status in “ia32-libs” source package in Karmic: Fix Released Status in “libx11” source package in Karmic: Invalid Status in “libxcb” source package in Karmic: Fix Released Status in Debian GNU/Linux: Fix Released Status in “libx11” package in Fedora: Fix Released Status in Suse Linux: New Bug description: With xcb every write (in _XFlush) is followed by a read (_XEventsQueued) which is the cause of the very poor performance. The read usually returns EAGAIN because there is nothing to be read, but it is a severe performace hit anyhow. And why _XEvenetsQueued/read is being called when select/poll has previously returned indicating only a single file descriptor was ready is anybody's guess. [Original Report] I've submitted this bug as https://bugs.freedesktop.org/show_bug.cgi?id=17868 as well. Though the problem may not be in ia32-libs -package, it contains the /usr/lib32/libX11.so.6.2.0 library that appears to be somehow relevant to the problem at hand. Some Java applications, such as the trial version in http://www.typingmaster.com/, run unusably slow when used over a remote X connection. I'm using Ubuntu Hardy 8.04.1 with LTSP5, Linux kernel 2.6.24-19-server, with 32-bit firefox and 32-bit Java-plugin. The relevant package versions are here: firefox32 2.0.0.17 sun-java32 1.6.0.5 sun-java6-jre 6-06-0ubuntu1 ia32-libs 2.2ubuntu11 The issue does not appear to be Java-version related (it exists in 1.5 and 1.6 versions). I have not tested the very latest Java-versions though. The reason I'm reporting this as a possible XCB-related issue is that one can workaround the problem by using an X11-library that does not link to XCB. In current Ubuntu version (Hardy), /usr/lib32/libX11.so.6.2.0 library links to /usr/lib32/libxcb-xlib.so.0 and /usr/lib32/libxcb.so.1 libraries, XCB version is 1.1. In previous Ubuntu version (Gutsy) the X11-library does not do this. When the new library shared object replaced with the old one, the problem disappears, and Java applications that had problems run fine. There may be some other differences between the X11-libraries, but using XCB as an underlying implementation seems to be a major change, or is it? All other applications do not appear to have these problems, Java applications appear to be the sole source of these problems. I'm adding two attachments that show tshark-dump of network traffic in both cases, perhaps it helps to analyze the issue. What happens there is one keypress on typingmaster Java-version, on Hardy/XCB case it takes half a minute to process one keypress and switch a screen, on Gutsy/no-XCB case it takes maybe a second. Juha [lspci] 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8623 [Apollo CLE266] [1106:3123] Subsystem: VIA Technologies, Inc. Unknown device [1106:] 01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics [1106:3122] (rev 03) (prog-if 00 [VGA controller]) Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics [1106:3122] To manage notifications about this bug go to: https://bugs.launchpad.net/libxcb/+bug/277069/+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 196429] Re: evince/evolution/gtk-print-dialog printing and system-config-printer fail when using client.conf with IP address for which there is no reverse look-up available
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: system-config-printer (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/196429 Title: evince/evolution/gtk-print-dialog printing and system-config-printer fail when using client.conf with IP address for which there is no reverse look-up available Status in “gtk+2.0” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “gtk+2.0” source package in Hardy: Won't Fix Status in “system-config-printer” source package in Hardy: Won't Fix Bug description: I ran into the 'greyed out print button' in evince in gutsy 7.10. I was working with a network printer and it worked via lpr and in fact any tool that did not rely on the GTK print dialog. Evince and evolution were clearly broken. As was the system printer configurator via the menu. It kept dying after reporting an error connecting to cups. I could use xpdf instead of evince and print fine. I could also use the GTK dialog to print to a file and then send the file to the printer using any non-GTK tool. In /etc/cups/client.conf I had put ServerName 192.168.1.16 In the end the problem was that I did not have an entry in /etc/hosts for 192.168.1.16. If I add an entry like 192.168.1.16 printer.mydomain.tld printer then everything works well including evince and evolution. Without that entry or a similar one in /etc/hosts, all the programs that use the GTK print dialog malfunction and the system print configurator dies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/196429/+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 174756] Re: [i965] Inspiron 1420: Intel GM965 s-video TV-out shows wrong colors on Ubuntu 7.10
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/174756 Title: [i965] Inspiron 1420: Intel GM965 s-video TV-out shows wrong colors on Ubuntu 7.10 Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” source package in Gutsy: Won't Fix Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Status in “xserver-xorg-video-intel” source package in Intrepid: Fix Released Status in “xserver-xorg-video-intel” package in Debian: Fix Released Bug description: I'm using Ubuntu 7.10 on a Dell Inspiron 1420 with Intel Mobile GM965/PM965/GL960 Express Integrated Graphics Controller with the default drivers and X configuration. When the s-video tv-out is used, the image showed on TV is too bright and the colors are satured and shifted to yellow. It's not a hardware problem: using M$ Vista the colors on the TV are showed equal to the notebook screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/174756/+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 1377177] Re: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing
Is there really no easy way to grab the output of the BR3 Script driver? via CUPS, USB or LAN? LAN would be the last way to go but I could capture the traffic with wireshark, tcpdump or so. Would you be up to have a look at it? Anway, thanks for your commitment, Pascal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1377177 Title: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing Status in “foomatic-db” package in Ubuntu: Confirmed Bug description: printer driver: Brother MFC9840CDW Foomatic/pxlcolor (color, 2-sided printing) Result when trying to print sth. with it: PCL XL error Subsystem: TEXT Error: IllegalBitmapResolutionSegment Position: 9 reproducible: always ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 3 16:08:17 2014 Lpstat: device for MFC9840CDW: socket://10.0.0.20:9100 device for MFC9840CDW_pxlcolor: socket://10.0.0.20:9100 MachineType: Packard Bell DOTS E2 Papersize: a4 PpdFiles: MFC9840CDW: Brother MFC9840CDW Foomatic/Postscript MFC9840CDW_pxlcolor: Brother MFC9840CDW Foomatic/pxlcolor ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-36-generic root=UUID=16250f8e-725d-430c-8ccc-95387d8f9ba7 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V3.16(DDR3) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE02_PT_E dmi.board.vendor: Packard Bell dmi.board.version: V3.16(DDR3) dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V3.16(DDR3) dmi.modalias: dmi:bvnPackardBell:bvrV3.16(DDR3):bd04/22/2011:svnPackardBell:pnDOTSE2:pvrV3.16(DDR3):rvnPackardBell:rnSJE02_PT_E:rvrV3.16(DDR3):cvnPackardBell:ct10:cvrV3.16(DDR3): dmi.product.name: DOTS E2 dmi.product.version: V3.16(DDR3) dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1377177/+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 188910] Re: package texlive-formats-extra None failed to install/upgrade: trying to overwrite `/usr/share/texmf-texlive/tex/latex/latexconfig/mllatex.ini', which is also in pac
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: texlive-extra (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/188910 Title: package texlive-formats-extra None failed to install/upgrade: trying to overwrite `/usr/share/texmf- texlive/tex/latex/latexconfig/mllatex.ini', which is also in package texlive-latex-base Status in “texlive-extra” package in Ubuntu: Fix Released Status in “texlive-extra” source package in Hardy: Won't Fix Bug description: upgrade from fgutsy to hardy. ProblemType: Package Architecture: i386 Date: Mon Feb 4 00:02:31 2008 Dependencies: DistroRelease: Ubuntu 8.04 ErrorMessage: trying to overwrite `/usr/share/texmf-texlive/tex/latex/latexconfig/mllatex.ini', which is also in package texlive-latex-base Package: texlive-formats-extra None PackageArchitecture: all SourcePackage: texlive-extra Title: package texlive-formats-extra None failed to install/upgrade: trying to overwrite `/usr/share/texmf-texlive/tex/latex/latexconfig/mllatex.ini', which is also in package texlive-latex-base Uname: Linux helsinki 2.6.24-5-rt #1 SMP PREEMPT RT Thu Jan 24 21:57:04 UTC 2008 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/188910/+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 236725] Re: UserAgent should have a slash after Gecko
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: epiphany-browser (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/236725 Title: UserAgent should have a slash after Gecko Status in “epiphany-browser” package in Ubuntu: Fix Released Status in “epiphany-browser” source package in Hardy: Won't Fix Bug description: Binary package hint: epiphany-browser Epiphany's useragent in hardy includes the string Gecko Epiphany/2.22. Most websites check for a string like Gecko/20080101, including Yahoo, UbuntuForums, and even some javascript wysiwyg editors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/236725/+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 235116] Re: imap flags are not regularly synch'd with server
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: evolution (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/235116 Title: imap flags are not regularly synch'd with server Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Fix Released Status in “evolution” source package in Hardy: Won't Fix Bug description: Evolution does not sync imap unless you exit the program or (sometimes) switch folders. There is a patch that has been committed upstream though, could it be cherry-picked for the upcoming evolution updates in 8.04? To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/235116/+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 235973] Re: Cannot add attachments from network drive
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: evolution (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/235973 Title: Cannot add attachments from network drive Status in “evolution” package in Ubuntu: Fix Released Status in “evolution” source package in Hardy: Won't Fix Bug description: Hi I have a serious problem since I'm using evolution 2.22.1.1 on ubuntu 8.04. I cannot add attachements from a network drive. I allways get the error message: * Evolution-Fehler Sie können die Datei »smb://192.168.114.10/tausch/dell%20ram%20bestellung.pdf« dieser Nachricht nicht beilegen. Dateiende in english Evolution-Error You cannot add the file »smb://192.168.114.10/tausch/dell%20ram%20bestellung.pdf« to this message. End of File It worked fine with evolution on ubuntu 7.10. Can you help please? Thanks very much. Beat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/235973/+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 283162] Re: gdmsetup crashed with SIGSEGV in g_file_load_partial_contents_finish()
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: glib2.0 (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/283162 Title: gdmsetup crashed with SIGSEGV in g_file_load_partial_contents_finish() Status in The G Library - GLib: Fix Released Status in “glib2.0” package in Ubuntu: Fix Released Status in “glib2.0” source package in Hardy: Won't Fix Bug description: Binary package hint: gdm Nautilus crashed on sturtup, after trying to send bugreport this new crash happened. ProblemType: Crash Architecture: amd64 CrashCounter: 1 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/sbin/gdmsetup NonfreeKernelModules: nvidia Package: gdm 2.20.7-0ubuntu1.1 ProcAttrCurrent: unconfined ProcCmdline: gdmsetup ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=hu_HU.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gdm StacktraceTop: g_file_load_partial_contents_finish () ?? () ?? () from /usr/lib/libgio-2.0.so.0 ?? () from /usr/lib/libgio-2.0.so.0 g_main_context_dispatch () Title: gdmsetup crashed with SIGSEGV in g_file_load_partial_contents_finish() Uname: Linux 2.6.24-21-generic x86_64 UserGroups: sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/283162/+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 118605] Re: [fglrx] freezes upon Logout or Switch user [patch]
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: fglrx-installer (Ubuntu Hardy) Status: Confirmed = Won't Fix -- 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/118605 Title: [fglrx] freezes upon Logout or Switch user [patch] Status in “fglrx-installer” package in Ubuntu: Invalid Status in “gdm” package in Ubuntu: Invalid Status in “linux-restricted-modules-2.6.24” package in Ubuntu: Invalid Status in “linux-restricted-modules-envy-2.6.24” package in Ubuntu: Won't Fix Status in “fglrx-installer” source package in Hardy: Won't Fix Status in “gdm” source package in Hardy: Invalid Status in “linux-restricted-modules-2.6.24” source package in Hardy: Invalid Status in “linux-restricted-modules-envy-2.6.24” source package in Hardy: Won't Fix Status in Mandriva Linux: Unknown Bug description: Using Feisty, Gnome and GDM: 1) log in as any user 2) Log out or Switch user on the Quit screen The screen goes black, Ctrl+Alt+Backspace does not work, nor does the Ctrl+Alt+F1-12. Interestingly, Numlock LED is still responsive. The only way out is hard reboot. I looked for the solution on forums. One advice was to turn on Restart the X server with each login, however, it did not help. I am not aware of any non-default configuration, I can supply my gdm .conf-custom if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/118605/+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 118605] Re: [fglrx] freezes upon Logout or Switch user [patch]
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu Hardy) Status: Confirmed = Won't Fix -- 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/118605 Title: [fglrx] freezes upon Logout or Switch user [patch] Status in “fglrx-installer” package in Ubuntu: Invalid Status in “gdm” package in Ubuntu: Invalid Status in “linux-restricted-modules-2.6.24” package in Ubuntu: Invalid Status in “linux-restricted-modules-envy-2.6.24” package in Ubuntu: Won't Fix Status in “fglrx-installer” source package in Hardy: Won't Fix Status in “gdm” source package in Hardy: Invalid Status in “linux-restricted-modules-2.6.24” source package in Hardy: Invalid Status in “linux-restricted-modules-envy-2.6.24” source package in Hardy: Won't Fix Status in Mandriva Linux: Unknown Bug description: Using Feisty, Gnome and GDM: 1) log in as any user 2) Log out or Switch user on the Quit screen The screen goes black, Ctrl+Alt+Backspace does not work, nor does the Ctrl+Alt+F1-12. Interestingly, Numlock LED is still responsive. The only way out is hard reboot. I looked for the solution on forums. One advice was to turn on Restart the X server with each login, however, it did not help. I am not aware of any non-default configuration, I can supply my gdm .conf-custom if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/118605/+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 425215] Re: 2.4.1 doesn't lock open documents
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: openoffice.org (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/425215 Title: 2.4.1 doesn't lock open documents Status in “openoffice.org” package in Ubuntu: Fix Released Status in “openoffice.org” source package in Hardy: Won't Fix Bug description: Binary package hint: openoffice.org I am running office 2.4.1 on Hardy 32 bit with LTSP set-up. Documents and spreadsheets opened with openoffice by different thin client users are not protected. In version 3.0 and higher this problem is solved. Unfortunately version 3.0 is not envisioned to be included in Hardy. Hardy will be in use another 9 months in productive environments where this bug can lead to complete data loss if a document or spreadsheet is edited at the same time by different users. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: openoffice.org-core 1:3.0.1-9ubuntu3 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.28-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/425215/+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 279924] Re: [gm45] Intel Cantiga graphics not showing gdm login page on Tecra A10 running Hardy (backport -intel to Hardy)
Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as Won't Fix. ** Changed in: xserver-xorg-video-intel (Ubuntu Hardy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/279924 Title: [gm45] Intel Cantiga graphics not showing gdm login page on Tecra A10 running Hardy (backport -intel to Hardy) Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” source package in Hardy: Won't Fix Bug description: I'm running a new installation of Hardy on a Toshiba Tecra A10 which happens to contain an Intel Cantiga graphics controller. After rebooting, the gdm appears as a bright white screen some vertical lines. The running kernel is: Linux ubuntu 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux I am attaching a few additional relevant files. [lspci] 00:00.0 Host bridge [0600]: Intel Corporation Cantiga Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Toshiba America Info Systems Unknown device [1179:0001] 00:02.0 VGA compatible controller [0300]: Intel Corporation Cantiga Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Unknown device [1179:0004] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/279924/+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 1165104] Re: oneconf is only showing the pc you are on in raring and isn't sharing to other machines
Broken in 14.10 too - brunonova: your fix still works! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1165104 Title: oneconf is only showing the pc you are on in raring and isn't sharing to other machines Status in One Hundred Papercuts: Triaged Status in “oneconf” package in Ubuntu: Triaged Bug description: In Raring I see only the machince I'm on. In the precise box beside it I see a couple of boxes but not this one. Please see the screenshots attached. I have a feeling that some how the sync has broken but I'm not sure what technology it is use on the backend. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: oneconf 0.3.3 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: Fri Apr 5 18:18:24 2013 InstallationDate: Installed on 2013-04-02 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402) MarkForUpload: True PackageArchitecture: all SourcePackage: oneconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1165104/+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 1311257] Re: Wifi cannot connect or unstable after suspend 14.04
Same problem on a Ku buntu 14.04 system, as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1311257 Title: Wifi cannot connect or unstable after suspend 14.04 Status in “gnome-nettool” package in Ubuntu: Confirmed Bug description: I've tried every solution, such as 1. editing /etc/pm/config.d to add SUSPEND_MODULES=iwlwifi 2. editing /etc/modprobe/d/wilwifi.conf to add: options iwlwifi bt_coex_active=0 options iwlwifi 11n_disable=1 3. running: sudo rmmod iwlwifi sudo modprobe iwlwifi 4. stopping, starting, or restarting Network Manager Nothing seems to work. When I had 13.10, my wifi worked without a problem, but once I erased it and installed 14.04, wifi will not connect after suspend. Ethernet works fine. The only way I've found to resolve this is to restart my computer. I have a Lenovo T420. If I try to connect after suspend, it shows the Wifi Networks, tries to connect, and says Disconnected... every time. ~$ sudo apt-get update; sudo apt-get install hwinfo grep rfkill; sudo lshw -C network; rfkill list; sudo iwlist scan | egrep -i 'chan|ssid'; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; lsusb; nmcli nm status; sudo lshw -short; uname -a; dmesg | egrep '02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|rt2|rt3|rt5|rt6|rt7|usb|witch|wl';sudo dmidecode|egrep 'anufact|roduct|erial|elease'; iwconfig; cat /etc/modprobe.d/* | egrep '80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl'; cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps -aux|egrep 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; sudo lsmod Ign http://dl.google.com stable InRelease Hit http://dl.google.com stable Release.gpg Hit http://dl.google.com stable Release Hit http://repository.spotify.com stable InRelease Ign http://us.archive.ubuntu.com trusty InRelease Hit http://dl.google.com stable/main amd64 Packages Hit http://dl.google.com stable/main i386 Packages Ign http://extras.ubuntu.com trusty InRelease Hit http://repository.spotify.com stable/non-free amd64 Packages Ign http://security.ubuntu.com trusty-security InRelease Ign http://us.archive.ubuntu.com trusty-updates InRelease Hit http://repository.spotify.com stable/non-free i386 Packages Hit http://extras.ubuntu.com trusty Release.gpg Hit http://security.ubuntu.com trusty-security Release.gpg Ign http://us.archive.ubuntu.com trusty-backports InRelease Hit http://extras.ubuntu.com trusty Release Ign http://us.archive.ubuntu.com trusty-proposed InRelease Hit http://security.ubuntu.com trusty-security Release Hit http://extras.ubuntu.com trusty/main Sources Ign http://dl.google.com stable/main Translation-en_US Hit http://us.archive.ubuntu.com trusty Release.gpg Ign http://dl.google.com stable/main Translation-en Hit http://security.ubuntu.com trusty-security/main Sources Hit http://extras.ubuntu.com trusty/main amd64 Packages Hit http://us.archive.ubuntu.com trusty-updates Release.gpg Hit http://security.ubuntu.com trusty-security/restricted Sources Hit http://extras.ubuntu.com trusty/main i386 Packages Hit http://us.archive.ubuntu.com trusty-backports Release.gpg Hit http://security.ubuntu.com trusty-security/universe Sources Hit http://us.archive.ubuntu.com trusty-proposed Release.gpg Hit http://security.ubuntu.com trusty-security/multiverse Sources Hit http://us.archive.ubuntu.com trusty Release Ign http://ppa.launchpad.net trusty InRelease Hit http://security.ubuntu.com trusty-security/main amd64 Packages Hit http://us.archive.ubuntu.com trusty-updates Release Ign http://ppa.launchpad.net trusty InRelease Hit http://security.ubuntu.com trusty-security/restricted amd64 Packages Ign http://repository.spotify.com stable/non-free Translation-en_US Hit http://us.archive.ubuntu.com trusty-backports Release Ign http://ppa.launchpad.net trusty InRelease Ign http://repository.spotify.com stable/non-free Translation-en Hit http://security.ubuntu.com trusty-security/universe amd64 Packages Hit http://us.archive.ubuntu.com trusty-proposed Release Ign http://ppa.launchpad.net trusty InRelease Hit http://security.ubuntu.com trusty-security/multiverse amd64 Packages Hit http://us.archive.ubuntu.com trusty/main Sources Ign http://ppa.launchpad.net trusty InRelease Hit http://security.ubuntu.com trusty-security/main i386 Packages Hit http://us.archive.ubuntu.com trusty/restricted Sources Hit http://ppa.launchpad.net trusty Release.gpg Hit http://security.ubuntu.com trusty-security/restricted i386 Packages Hit http://ppa.launchpad.net trusty Release.gpg Hit
[Desktop-packages] [Bug 1385369] Re: After Upgrade to 14.10 Unity No Longer Loads
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer (Ubuntu) Status: New = Confirmed -- 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/1385369 Title: After Upgrade to 14.10 Unity No Longer Loads Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: Laptop is an Acer Aspire V5-552PG-X809. AMD A10-5757M Processor with Dual Graphics (Radeon HD 8560M embedded, and Radeon 8750M dedicated). FGLRX driver was working fantastically prior to upgrade to Ubuntu 14.10. After upgrade, after login to desktop Unity will not fully load (desktop loads, but Dash and unity side bar does not). FGLRXINFO reports no devices found. I have tried the FGLRX, FGLRX-UPDATES, and the latest driver straight from AMD, none of them have worked for me. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Oct 24 12:04:33 2014 DistUpgraded: 2014-10-23 19:21:14,997 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 14.201, 3.16.0-23-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:080f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:080f] InstallationDate: Installed on 2013-12-26 (301 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Acer Aspire V5-552PG ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=c126d440-b212-4f57-8e81-2cd27426c1d2 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: Upgraded to utopic on 2014-10-23 (0 days ago) dmi.bios.date: 05/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd05/28/2013:svnAcer:pnAspireV5-552PG:pvrV2.02:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552PG dmi.product.version: V2.02 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Oct 24 11:57:40 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1385369/+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 1395493] [NEW] nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build
Public bug reported: problem after startup and login ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-24-generic Date: Sun Nov 23 18:13:29 2014 InstallationDate: Installed on 2013-04-10 (591 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-23 (30 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1395493 Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: problem after startup and login ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-24-generic Date: Sun Nov 23 18:13:29 2014 InstallationDate: Installed on 2013-04-10 (591 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-23 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1395493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
Has anyone been able to successfully compile with the patch? Towards the end when I compile i get an error that I can't seem to work around. *dpkg-shlibdeps: error: no dependency information found for /usr/lib/libGL.so.1 (used by debian/xserver-xorg-core/usr/lib/xorg/modules/extensions/libglx.so)* Would someone be able to guide me around this? On Wed, Nov 19, 2014 at 2:29 AM, Erno Kuusela e...@iki.fi wrote: End users: Please use another forum (eg. ubuntuforums) for user discussion talking about workarounds, manually applying the patch, me toos, or other peripheral discussions. This bug tracker is about developing Ubuntu, and now you are with all this chatter spamming countless developers whose efforts should be focused on getting this fixed inside Ubuntu and in xorg. Not to mention all us end users monitoring this bug and waiting the packages to be fixed, at least 167 of us going by the affects count. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in “nvidia-graphics-drivers-319” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-343” package in Ubuntu: Invalid Status in “nvidia-prime” package in Ubuntu: Invalid Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in “nvidia-graphics-drivers-319” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-343” package in Ubuntu: Invalid Status in “nvidia-prime” package in Ubuntu: Invalid Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1370175] Re: Libav security fixes Sept 2014
** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1370175 Title: Libav security fixes Sept 2014 Status in “libav” package in Ubuntu: Confirmed Status in “libav” source package in Precise: Fix Released Status in “libav” source package in Trusty: Confirmed Status in “libav” source package in Utopic: Confirmed Bug description: Libav 9.17 and 0.8.16 are out, and fix a number of critical functional and security issues (many of which have CVE identifiers assigned) http://www.libav.org/news.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1370175/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Same error I got... except my system also wanted gl. found nothing on google. found nothing with apt-cache or apt-file either! If you find a solution please report back as freezing is driving me bonkers and bumblebee just wont work for me either -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in “nvidia-graphics-drivers-319” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-343” package in Ubuntu: Invalid Status in “nvidia-prime” package in Ubuntu: Invalid Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
and amen stefan, amen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in “nvidia-graphics-drivers-319” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-343” package in Ubuntu: Invalid Status in “nvidia-prime” package in Ubuntu: Invalid Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1393281] Re: Print settings window reports Print service is unavailable - Bad file descriptor until cups is restarted
When bug is present, cups is running: $ sudo service cups status cups start/running Attaching /var/log/boot.log ** Attachment added: boot.log https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1393281/+attachment/4266232/+files/boot.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1393281 Title: Print settings window reports Print service is unavailable - Bad file descriptor until cups is restarted Status in “cups” package in Ubuntu: Incomplete Bug description: In the KDE Print Settings window, there are no settings (as expected) but a message reading Print service is unavailable - Bad file descriptor: http://wstaw.org/m/2014/11/17/plasma-desktopKB2526.png When I restart the cups service, all is well and I can see print settings. Kubuntu 14.10 $ apt-cache policy cups cups: Installed: 1.7.5-3ubuntu2 Candidate: 1.7.5-3ubuntu2 Version table: *** 1.7.5-3ubuntu2 0 500 http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ utopic/main amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-04-18 (216 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) Lpstat: device for Dell-C1760nw: dnssd://Dell%20C1760nw%20Color%20Printer%20(B7%3A5F%3A1D)._pdl-datastream._tcp.local/ MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: fglrx Package: cups 1.7.5-3ubuntu2 PackageArchitecture: amd64 Papersize: letter PpdFiles: Dell-C1760nw: Xerox Phaser 6000B v1.0 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b4a856d9-5d57-455a-b81d-6f21fc094155 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b4a856d9-5d57-455a-b81d-6f21fc094155 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Tags: utopic Uname: Linux 3.16.0-24-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-26 (24 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd12/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1393281/+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 1395501] [NEW] input devices found, but there is no input level
Public bug reported: My input devices is found, but no not working. Get no input level from the devices. They are not muted! pavucontrol Input Devices no input level from any of my input devices! System settings Sound Input no input level from any of my input devices! My computer is a Dell XPS 15 9530. Ubuntu 14.04 Kernel release:3.13.0-39-generic. ARECORD List of CAPTURE Hardware Devices card 1: G4ME1 [Sennheiser 3D G4ME1], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 0: ALC668 Analog [ALC668 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh chmod +x ./alsa-info.sh ./alsa-info.sh gives: http://www.alsa-project.org/db/?f=916914afd5195a1d4ed40f3f38fa0d37285d1039 Screenshot from alsamixer, pavucontrol and sound control menu. https://mrkr.io/pemHMWlKHR Teamspeak works fine, if I select recording device in pavucontrol for teamspeak. https://mrkr.io/5D0ZUSVyLC https://mrkr.io/T6nQX77HAD Testing in skype, no input is registered! https://mrkr.io/xMbrev28bR https://mrkr.io/zqu6AFVjld ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1395501 Title: input devices found, but there is no input level Status in “alsa-driver” package in Ubuntu: New Bug description: My input devices is found, but no not working. Get no input level from the devices. They are not muted! pavucontrol Input Devices no input level from any of my input devices! System settings Sound Input no input level from any of my input devices! My computer is a Dell XPS 15 9530. Ubuntu 14.04 Kernel release:3.13.0-39-generic. ARECORD List of CAPTURE Hardware Devices card 1: G4ME1 [Sennheiser 3D G4ME1], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 0: ALC668 Analog [ALC668 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh chmod +x ./alsa-info.sh ./alsa-info.sh gives: http://www.alsa-project.org/db/?f=916914afd5195a1d4ed40f3f38fa0d37285d1039 Screenshot from alsamixer, pavucontrol and sound control menu. https://mrkr.io/pemHMWlKHR Teamspeak works fine, if I select recording device in pavucontrol for teamspeak. https://mrkr.io/5D0ZUSVyLC https://mrkr.io/T6nQX77HAD Testing in skype, no input is registered! https://mrkr.io/xMbrev28bR https://mrkr.io/zqu6AFVjld To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1395501/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
Debian actually does not have this problem after all. does that help anything? -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in “network-manager” package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 797485] Re: Status Bar Covers File Name at Bottom
Ubuntu 14.04 updated to november '14 still shows this behaviour. Please, add a fixed user enabled/disabled bottom status bar, not the floating one. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/797485 Title: Status Bar Covers File Name at Bottom Status in Nautilus: Confirmed Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus In Nautilus when you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. I realize this is likely a rare occurrence, and can be gotten around by adjusting the width of the window, but it is a minor bug. Possible solutions: Move status bar to the left side when working with files in that corner. Do not show status bar while renaming. Best IMHO: Give the file area a bottom margin of the height of the status bar. Ubuntu 11.04, Gnome-Shell (Although it should just be nautilus in general.) nautilus: 1:3.0.2-0ubuntu2~natty1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+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 1395510] [NEW] package libgtk-3-0:amd64 3.12.2-0ubuntu16 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Error while doing an apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libgtk-3-0:amd64 3.12.2-0ubuntu16 ProcVersionSignature: Ubuntu 3.18.0-3.4-generic 3.18.0-rc4 Uname: Linux 3.18.0-3-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Sun Nov 23 11:10:28 2014 DuplicateSignature: package:libgtk-3-0:amd64:3.12.2-0ubuntu16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-28 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141027) SourcePackage: gtk+3.0 Title: package libgtk-3-0:amd64 3.12.2-0ubuntu16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1395510 Title: package libgtk-3-0:amd64 3.12.2-0ubuntu16 failed to install/upgrade: triggers looping, abandoned Status in “gtk+3.0” package in Ubuntu: New Bug description: Error while doing an apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libgtk-3-0:amd64 3.12.2-0ubuntu16 ProcVersionSignature: Ubuntu 3.18.0-3.4-generic 3.18.0-rc4 Uname: Linux 3.18.0-3-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Sun Nov 23 11:10:28 2014 DuplicateSignature: package:libgtk-3-0:amd64:3.12.2-0ubuntu16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-28 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141027) SourcePackage: gtk+3.0 Title: package libgtk-3-0:amd64 3.12.2-0ubuntu16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1395510/+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 1395343] Re: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop
Hello, have you checked disk for errors? Run fsck. Also please run apport-collect 1395343 Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1395343 Title: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop Status in “pm-utils” package in Ubuntu: New Bug description: The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I first tried with the Live CD, on failing that, and thinking that suspend might need some disk to write to for the suspend info, I did a HD installation. But still, suspend/resume is still not working. On second attempt (after HD installation), I switched to console and close my Laptop lid. It suspended well, as it has always been. On resume, I see the repeating errors of `sda1` soft reset failure (or something like that). Minutes later, I start to see all kinds of disk related errors, disk sector writing error, ext4 journal error, etc. I thus think the reason of `resume` not working is that the HD is not waken up. This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic. Any more info that I can provide? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1395343/+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 1090543] Re: Slow traffic pass through disconnected wired connection
** Changed in: network-manager-applet Status: Unknown = Invalid ** Changed in: network-manager-applet Importance: Unknown = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1090543 Title: Slow traffic pass through disconnected wired connection Status in Network Manager GNOME Applet: Invalid Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: I was doing a fresh install of 12.04 on my desktop PC, which is connected to my home network. I have installed the Gnome3 classic desktop environment, and while doing some configurations, I decided to disconnect from the network in order to protect my PC while it is still in a vulnerable state. (I have noticed for some time before that one of the other PC's on the LAN, with a Win 7 OS, is somewhat noisy on the network). When installing the System Monitor applet, I also activated the Network portion, taking samples at 1.5 second intervals on the network connection, and producing a small graph (60 pixels wide) showing the network traffic. I then noticed that traffic was still getting through at a rate of 40 bytes/sec on the now disconnected wired connection. I then did a few tests, and found: - for some reason there is also the option of Disabling the network on the applet. - both Disconnect and Disable produce the same message Disconnected - you are now offline. - Disconnecting the wired connection, with the network Enabled still allows slow traffic through, however browsing the Internet and downloading is not possible. - Disabling the network, without disconnecting the connection, stops all traffic. This is a security flaw, since Disconnecting the LAN should have the same effect as unplugging the LAN cable from the network port, thus not allowing any traffic to get through. The attached screenshots show that for a period of 2 minutes 45 seconds, my PC have received 109 packets (6.4 kB) and sent 2 packets (0.2 kB), while being disconnected. When clicking on the network applet icon, I see the following lines/options: Wired network Wired connection 1 Disconnect VPN connections Enable Networking (Checked) Connection Information Edit Connections I suspect that the disconnect/disable anomaly is the result of installing Gnome3 over Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1090543/+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 189155] marcus 2
*** This bug is a duplicate of bug 138586 *** https://bugs.launchpad.net/bugs/138586 http://icredg.ir/vif/gfggjjqluzxqkzigahaquxh.wapzttezhijtzqkdqpvcl Tony -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/189155 Title: gnometris goes out of control half way through a game, with pieces speeding up, and not responding to commands. I hear the extra pull on the system during this time. Status in “gnome-games” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-games not even half way through a game, and the pieces speed up and don't respond to commands quickly enough to keep the game from running out. I can hear the fans kicking in during this time and the machine is pulling hard. Then it will return to normal speed and power, but too late to return to normal gameplay. I have a 3 gig pentium 4, and 1.5 gig of ram. I don't have trouble with any outer programs, including cad, photoshop , or preimere (while dual booting xp). I've run many different versions of linux on this machine, and I fail to understand why this simple game is giving trouble. This is similar to a previous bug, except in this bug the pieces speed up. ProblemType: Bug Architecture: i386 Date: Mon Feb 4 23:38:10 2008 DistroRelease: Ubuntu 7.10 NonfreeKernelModules: ath_hal Package: gnome-games 1:2.20.1-0ubuntu1 PackageArchitecture: i386 SourcePackage: gnome-games Uname: Linux silversurfer 2.6.22-14-generic #1 SMP Fri Feb 1 04:59:50 UTC 2008 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/189155/+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 1377177] Re: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing
I did some reverse engineering with Windows driver (the PJL command seems to be @PJL SET APTMODE=ON4), can you test whether the PPD in attachment does High Quality / 2400x600dpi printing. Do you get crisper and slower output with this setting compared to Normal Quality / 600x600dpi ? I also changed Draft Quality to 300x300dpi, does it gives lower output than Normal / 600x600dpi setting? ** Attachment added: Brother-MFC9840CDW-apt.ppd https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1377177/+attachment/4266292/+files/Brother-MFC9840CDW-apt.ppd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1377177 Title: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing Status in “foomatic-db” package in Ubuntu: Confirmed Bug description: printer driver: Brother MFC9840CDW Foomatic/pxlcolor (color, 2-sided printing) Result when trying to print sth. with it: PCL XL error Subsystem: TEXT Error: IllegalBitmapResolutionSegment Position: 9 reproducible: always ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 3 16:08:17 2014 Lpstat: device for MFC9840CDW: socket://10.0.0.20:9100 device for MFC9840CDW_pxlcolor: socket://10.0.0.20:9100 MachineType: Packard Bell DOTS E2 Papersize: a4 PpdFiles: MFC9840CDW: Brother MFC9840CDW Foomatic/Postscript MFC9840CDW_pxlcolor: Brother MFC9840CDW Foomatic/pxlcolor ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-36-generic root=UUID=16250f8e-725d-430c-8ccc-95387d8f9ba7 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V3.16(DDR3) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE02_PT_E dmi.board.vendor: Packard Bell dmi.board.version: V3.16(DDR3) dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V3.16(DDR3) dmi.modalias: dmi:bvnPackardBell:bvrV3.16(DDR3):bd04/22/2011:svnPackardBell:pnDOTSE2:pvrV3.16(DDR3):rvnPackardBell:rnSJE02_PT_E:rvrV3.16(DDR3):cvnPackardBell:ct10:cvrV3.16(DDR3): dmi.product.name: DOTS E2 dmi.product.version: V3.16(DDR3) dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1377177/+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 1395343] Re: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop
This is a rarely used computer. I'm sure it is not disk errors, as it never gave any problem before, but failed to wake up the HD instead, each and every time that I tried. I got disk errors on other machines before, so I know what it means. I.e., if it is disk errors, the the error sequence reported above will be entirely different. No I can't use apport-collect, as it's function is to automatically generate crash reports for debugging. However my machine/SW does not crash, but freeze up entirely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1395343 Title: Ubuntu 14.10 Utopic suspend/resume not working for my Laptop Status in “pm-utils” package in Ubuntu: New Bug description: The Ubuntu 14.10 Utopic suspend/resume is not working for my Laptop. I first tried with the Live CD, on failing that, and thinking that suspend might need some disk to write to for the suspend info, I did a HD installation. But still, suspend/resume is still not working. On second attempt (after HD installation), I switched to console and close my Laptop lid. It suspended well, as it has always been. On resume, I see the repeating errors of `sda1` soft reset failure (or something like that). Minutes later, I start to see all kinds of disk related errors, disk sector writing error, ext4 journal error, etc. I thus think the reason of `resume` not working is that the HD is not waken up. This is Acer Aspire AS5536, with XUbuntu 14.10 Utopic. Any more info that I can provide? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1395343/+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 1377177] Re: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing
oopsla: PCL XL error Subsystem: TEXT Error: IllegalBitmapResolutionSegment Operator: ReadFontHeader Position: 29 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1377177 Title: Brother MFC9840CDW pxlcolor driver fails to intialize for bitmap printing Status in “foomatic-db” package in Ubuntu: Confirmed Bug description: printer driver: Brother MFC9840CDW Foomatic/pxlcolor (color, 2-sided printing) Result when trying to print sth. with it: PCL XL error Subsystem: TEXT Error: IllegalBitmapResolutionSegment Position: 9 reproducible: always ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 3 16:08:17 2014 Lpstat: device for MFC9840CDW: socket://10.0.0.20:9100 device for MFC9840CDW_pxlcolor: socket://10.0.0.20:9100 MachineType: Packard Bell DOTS E2 Papersize: a4 PpdFiles: MFC9840CDW: Brother MFC9840CDW Foomatic/Postscript MFC9840CDW_pxlcolor: Brother MFC9840CDW Foomatic/pxlcolor ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-36-generic root=UUID=16250f8e-725d-430c-8ccc-95387d8f9ba7 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V3.16(DDR3) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SJE02_PT_E dmi.board.vendor: Packard Bell dmi.board.version: V3.16(DDR3) dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V3.16(DDR3) dmi.modalias: dmi:bvnPackardBell:bvrV3.16(DDR3):bd04/22/2011:svnPackardBell:pnDOTSE2:pvrV3.16(DDR3):rvnPackardBell:rnSJE02_PT_E:rvrV3.16(DDR3):cvnPackardBell:ct10:cvrV3.16(DDR3): dmi.product.name: DOTS E2 dmi.product.version: V3.16(DDR3) dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1377177/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled
Alexander's patch also works nicely for me! So awesome to have a font I can read again and not to have to mess with Linux every time I turn off the receiver or switch it to a different input. Nice work! -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “xfce4-settings” package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode NULL After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello supe...@ubuntu.com OUTPUT=HDMI-0 BAD_MODE=1280x720 GOOD_MODE=1920x1080 for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1395530] [NEW] lightdm post-install script doesn't create /var/lib/lightdm if user already exists, preventing lightdm from starting
Public bug reported: I'm not sure if this really counts as a bug or if it's just an unsupported configuration, but the post-install script (lightdm.postinst) doesn't ensure that /var/lib/lightdm exists and has the correct permissions if the user already exists, since it is relying upon adduser to create the home directory and only does so if the lightdm user doesn't already exist. This prevents lightdm from starting and leads to a fallback X session being created instead, which doesn't give any helpful information about the underlying problem. The reason I already had a lightdm user in passwd is because I was bootstrapping Ubuntu in a chroot and copied passwd/shadow/group/gshadow into it before installing packages, since I wanted to make sure UID/GIDs would be consistent between the two installations. It would be nice if this case could be more gracefully handled, since I don't think it's all that unusual. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Summary changed: - lightdm post-install script doesn't create var/lib/lightdm if user already exists, preventing lightdm from starting + lightdm post-install script doesn't create /var/lib/lightdm if user already exists, preventing lightdm from starting ** Description changed: I'm not sure if this really counts as a bug or if it's just an unsupported configuration, but the post-install script - (lightdm.postinst) doesn't ensure that var/lib/lightdm exists and has + (lightdm.postinst) doesn't ensure that /var/lib/lightdm exists and has the correct permissions if the user already exists, since it is relying upon adduser to create the home directory and only does so if the lightdm user doesn't already exists. This prevents lightdm from - starting and leads to a fallback X session being created instead. + starting and leads to a fallback X session being created instead, which + doesn't give any helpful information about the underlying problem. The reason I already had a lightdm user in passwd is because I was bootstrapping lightdm in a chroot and copied passwd/shadow/group/gshadow into it before installing packages, since I wanted to make sure UID/GIDs would be consistent between the two installations. It would be nice if - this case were more gracefully handled. + this case could be more gracefully handled. ** Description changed: I'm not sure if this really counts as a bug or if it's just an unsupported configuration, but the post-install script (lightdm.postinst) doesn't ensure that /var/lib/lightdm exists and has the correct permissions if the user already exists, since it is relying upon adduser to create the home directory and only does so if the lightdm user doesn't already exists. This prevents lightdm from starting and leads to a fallback X session being created instead, which doesn't give any helpful information about the underlying problem. The reason I already had a lightdm user in passwd is because I was - bootstrapping lightdm in a chroot and copied passwd/shadow/group/gshadow + bootstrapping Ubuntu in a chroot and copied passwd/shadow/group/gshadow into it before installing packages, since I wanted to make sure UID/GIDs would be consistent between the two installations. It would be nice if this case could be more gracefully handled. ** Description changed: I'm not sure if this really counts as a bug or if it's just an unsupported configuration, but the post-install script (lightdm.postinst) doesn't ensure that /var/lib/lightdm exists and has the correct permissions if the user already exists, since it is relying upon adduser to create the home directory and only does so if the lightdm user doesn't already exists. This prevents lightdm from starting and leads to a fallback X session being created instead, which doesn't give any helpful information about the underlying problem. The reason I already had a lightdm user in passwd is because I was bootstrapping Ubuntu in a chroot and copied passwd/shadow/group/gshadow into it before installing packages, since I wanted to make sure UID/GIDs would be consistent between the two installations. It would be nice if - this case could be more gracefully handled. + this case could be more gracefully handled, since I don't think it's all + that unusual. ** Description changed: I'm not sure if this really counts as a bug or if it's just an unsupported configuration, but the post-install script (lightdm.postinst) doesn't ensure that /var/lib/lightdm exists and has the correct permissions if the user already exists, since it is relying upon adduser to create the home directory and only does so if the - lightdm user doesn't already exists. This prevents lightdm from + lightdm user doesn't already exist. This prevents lightdm from starting and leads to a fallback X session being created instead, which doesn't give any helpful information about the underlying problem. The reason
[Desktop-packages] [Bug 1394899] Re: Merge simple-scan 3.15.1-1 (main) from Debian unstable (main)
This bug was fixed in the package simple-scan - 3.15.2-0ubuntu1 --- simple-scan (3.15.2-0ubuntu1) vivid; urgency=medium * New upstream release: - Store density information in bitmap formats (JPEG, PNG, TIFF). -- Robert Ancell robert.anc...@canonical.com Mon, 24 Nov 2014 09:29:30 +1300 ** Changed in: simple-scan (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1394899 Title: Merge simple-scan 3.15.1-1 (main) from Debian unstable (main) Status in “simple-scan” package in Ubuntu: Fix Released Bug description: simple-scan (3.15.1-1) unstable; urgency=medium * New upstream release: - Updated translations. * debian/simple-scan.bug-script: - Correct typo. (Closes: #764700) * debian/control: - For missing icons gnome-icon-theme-symbolic removed from Depends. (Closes: #761292) -- Jörg Frings-Fürst deb...@jff-webhosting.net Tue, 28 Oct 2014 09:38:02 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1394899/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.
I have removed Ubuntu from this machine, so can't test under Ubuntu. I am now running Sparky Linux (Debian testing). Stellarium still crashes after displaying the startup screen, but I'm now getting this error message: stellarium: ../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104: get_hw_format: Assertion `0' failed. For whatever it's worth, I did the routine you described. The Stellarium startup screen appeared but didn't disappear. I had to kill the process. Here's the output: (gdb) run Starting program: /usr/local/bin/stellarium [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. Using default graphics system specified at build time: raster [New Thread 0xb43deb40 (LWP 1146)] --- [ This is Stellarium 0.12.4 - http://www.stellarium.org ] [ Copyright (C) 2000-2013 Fabien Chereau et al ] --- Writing log file to: /home/user/.stellarium/log.txt File search paths: 0 . /home/user/.stellarium 1 . /usr/local/share/stellarium Attempting to use an existing older config file. Config file is: /home/user/.stellarium/config.ini Going to initialize the OpenGL 2 renderer OpenGL supported version: 1.2 Mesa 10.3.2 Qt GL paint engine is: OpenGL [New Thread 0xb1eacb40 (LWP 1157)] StelQGL2Renderer::init : Failed because Qt paint engine is not OpenGL2 If paint engine is OpenGL3 or higher, this code needs to be updated Failed to initialize the OpenGL 2 renderer, falling back to the OpenGL 1 renderer [Thread 0xb1eacb40 (LWP 1157) exited] OpenGL supported version: 1.2 Mesa 10.3.2 Qt GL paint engine is: OpenGL [New Thread 0xb1eacb40 (LWP 1158)] GL vendor is Nouveau GL renderer is Mesa DRI nv18 x86/MMX+/3DNow!+/SSE2 Cache directory is: /home/harrington/.cache/stellarium/stellarium Sky language is en_US Application language is en_US Loading Solar System data ... Loaded 75 / 75 planet orbits from /home/user/.stellarium/data/ssystem.ini Loading star data ... Loading /usr/local/share/stellarium/stars/default/stars_0_0v0_3.cat: 0_0v0_2; 4963 Loading /usr/local/share/stellarium/stars/default/stars_1_0v0_3.cat: 1_0v0_2; 21598 Loading /usr/local/share/stellarium/stars/default/stars_2_0v0_3.cat: 2_0v0_2; 150090 Loading /usr/local/share/stellarium/stars/default/stars_3_1v0_2.cat: 3_1v0_1; 423540 Finished loading star catalogue data, max_geodesic_level: 3 navigation/preset_sky_time is a double - treating as jday: 2.45151e+06 Loaded 10051 NGC records Loading NGC name data ... Loaded 412 / 412 NGC name records successfully Loading star names from /usr/local/share/stellarium/skycultures/western/star_names.fab Loaded 236 / 236 common star names Loading star names from /usr/local/share/stellarium/stars/default/name.fab Loaded 4359 / 4359 scientific star names Loading variable stars from /usr/local/share/stellarium/stars/default/gcvs_hip_part.dat Loaded 6886 / 6886 variable stars Loaded 88 / 88 constellation records successfully for culture western Loaded 85 / 85 constellation art records successfully for culture western Loaded 89 / 89 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Not using any viewport effect [New Thread 0xafe90b40 (LWP 1159)] Creating GUI ... Loading shortcuts... Can't find plugin with id RendererStatistics Can't find plugin with id RendererStatistics Loaded plugin Oculars . Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for configuration. Oculars::validateIniFile ocular.ini exists at: /home/harrington/.stellarium/modules/Oculars/ocular.ini . Checking version... Oculars::validateIniFile found existing ini file version 2 Loaded plugin Satellites . Satellites: loading catalog file: /home/harrington/.stellarium/modules/Satellites/satellites.json Satellite has invalid orbit: SL-3 R/B 10861 Satellite has invalid orbit: TIANGONG 1 37820 Loaded plugin SolarSystemEditor . Using the ssystem.ini file that already exists in the user directory... Loaded plugin TimeZoneConfiguration . QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. QGLFramebufferObject: Framebuffer incomplete attachment. OpenGL error detected at drawWindow() start : GL_INVALID_VALUE stellarium: ../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104: get_hw_format: Assertion `0' failed. Program received
[Desktop-packages] [Bug 684745] Re: Alt-tab causes compiz assert failure: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b = 0' failed.
** Changed in: mesa Status: Incomplete = Invalid ** Changed in: mesa (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/684745 Title: Alt-tab causes compiz assert failure: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b = 0' failed. Status in Mesa: Invalid Status in “mesa” package in Ubuntu: Invalid Bug description: Binary package hint: compiz there is a strange dashed line in the upper panel ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: compiz-core 1:0.9.2.1+glibmainloop2-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.37-7.19-generic 2.6.37-rc3 Uname: Linux 2.6.37-7-generic i686 NonfreeKernelModules: fglrx Architecture: i386 AssertionMessage: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b = 0' failed. CompizPlugins: No value set for `/apps/compiz/general/allscreens/options/active_plugins' Date: Fri Dec 3 14:15:25 2010 ExecutablePath: /usr/bin/compiz LiveMediaBuild: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20101202) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PciDisplay: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M96 [Mobility Radeon HD 4650] [1002:9480] (prog-if 00 [VGA controller]) ProcCmdline: /usr/bin/compiz ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz RelatedPackageVersions: xserver-xorg 1:7.5+6ubuntu3b1 libgl1-mesa-glx 7.9+repack-1ubuntu2 libdrm2 2.4.22-2ubuntu1 xserver-xorg-video-intel 2:2.13.901-2ubuntu1 xserver-xorg-video-ati 1:6.13.2-1ubuntu2 Signal: 6 SourcePackage: compiz StacktraceTop: __kernel_vsyscall () raise () from /lib/libc.so.6 abort () from /lib/libc.so.6 __assert_fail () from /lib/libc.so.6 ?? () from /usr/lib/dri/libdricore.so Title: compiz assert failure: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b = 0' failed. UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 02/24/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3064 dmi.board.vendor: Quanta dmi.board.version: 19.0B dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.03:bd02/24/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3064:rvr19.0B:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard glxinfo: Error: [Errno 2] No such file or directory system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/684745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled
Hey can you please send me some install information so that I can try it out. Cheers Doug On Nov 23, 2014 3:40 PM, Chris christopherdbenn...@armyspy.com wrote: Alexander's patch also works nicely for me! So awesome to have a font I can read again and not to have to mess with Linux every time I turn off the receiver or switch it to a different input. Nice work! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “xfce4-settings” package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode NULL After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello supe...@ubuntu.com OUTPUT=HDMI-0 BAD_MODE=1280x720 GOOD_MODE=1920x1080 for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “xfce4-settings” package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode NULL After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello supe...@ubuntu.com OUTPUT=HDMI-0 BAD_MODE=1280x720 GOOD_MODE=1920x1080 for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
As I said already, 14.10 has another problem. Go to Network Settings or Network Connections, edit the Eduroam connection, and go to the WiFi Security tab. Here set the authentication type to Protected EAP instead of the default Tunneled TLS which is wrong for eduroam, at least on my university. It is unrelated to this bug so feel free to open a new bug for it, if you did not need to do this in past releases of Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Saucy: Won't Fix Status in “network-manager-applet” source package in Trusty: Fix Released Status in “network-manager-applet” source package in Utopic: Fix Released Status in Gentoo Linux: Fix Released Status in “network-manager” package in openSUSE: Confirmed Bug description: SRU Justification: [Impact] When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. [Test Case] Attempt to connect to a WPA2/PEAP/MSCHAPv2 network without CA_Certificate using Network Manager [Regression Potential] This has been fixed in Utopic already and it a backport of an upstream patch. -- === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
I tried applying the patch in comment 22 to my 14.04 installation (3.13.0-39-generic, upgraded from 12.04) and rebooting, but it didn't solve the problem with my Logitec webcam microphone. I still get the same error. ubuntu-drivers-common 1:0.2.91.7 is the currently installed version. Are they any other scripts that might be doing the same thing? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. Status in “alsa-plugins” package in Ubuntu: Invalid Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “alsa-plugins” source package in Trusty: Invalid Status in “ubuntu-drivers-common” source package in Trusty: Triaged Bug description: On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/deattaching of usb-headset and other stuff impossible because the two instances fight ove rthe events. Tow reproduce just boot up the current image and do a ps -ef | grep pulseaudio ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgh2336 F pulseaudio sgh2796 F pulseaudio /dev/snd/controlC0: sgh2336 F pulseaudio sgh2796 F pulseaudio CurrentDesktop: KDE Date: Sun Mar 23 22:36:50 2014 InstallationDate: Installed on 2013-12-24 (89 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+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 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
Forgot to mention I am using Gnome3 shell, not Unity or KDE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. Status in “alsa-plugins” package in Ubuntu: Invalid Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “alsa-plugins” source package in Trusty: Invalid Status in “ubuntu-drivers-common” source package in Trusty: Triaged Bug description: On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/deattaching of usb-headset and other stuff impossible because the two instances fight ove rthe events. Tow reproduce just boot up the current image and do a ps -ef | grep pulseaudio ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgh2336 F pulseaudio sgh2796 F pulseaudio /dev/snd/controlC0: sgh2336 F pulseaudio sgh2796 F pulseaudio CurrentDesktop: KDE Date: Sun Mar 23 22:36:50 2014 InstallationDate: Installed on 2013-12-24 (89 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+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 1283863] Re: disabling touchpad is not persistent
** Tags added: vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1283863 Title: disabling touchpad is not persistent Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Happens also with g-s-d Current Test case: On a laptop with a usb mouse connected disable touchpad in system settings Mouse Touchpad Reboot Touchpad will be re-enabled Test case 2: with touchpad disabled suspend laptop after coming out of suspend touchpad will be re-enabled Could be related to this - with external mouse connected disable touchpad, it will stop working. remove external mouse, touchpad is immediately re-enabled. Possibly during the course of normal use, restarts ect. it is 'sensed' that the mouse is not connected touchpad -enabled is mistakenly restored? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140221.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 23 19:28:13 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1283863/+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 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.
stellarium: ../../../../../../../src/mesa/drivers/dri/nouveau/nv10_render.c:104: get_hw_format: Assertion `0' failed. That also appears to mean invalid format, so is probably the same bug. For whatever it's worth, I did the routine you described. The Stellarium startup screen appeared but didn't disappear. That's expected when something crashes under a debugger: please switch back to the debugger window (Alt+Tab), type thread apply all bt full and post the output. (You can then close the debugger and program with quit.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1079011 Title: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed. Status in “flightgear” package in Ubuntu: New Status in “mesa” package in Ubuntu: Incomplete Status in “stellarium” package in Ubuntu: Confirmed Bug description: Stellarium crashes a few seconds after displaying the startup screen with this message in terminal: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed. I have an nvidia GeForce4 MX 4000 video card, and have installed libgl1-mesa-dri and libgl1-mesa-dri-experimental, version 9.0-0ubuntu1. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: stellarium 0.11.3-1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Wed Nov 14 22:52:36 2012 InstallationDate: Installed on 2012-04-05 (224 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: stellarium UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flightgear/+bug/1079011/+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 1388259] Re: gnome-keyring SRU breaks ECDSA keys
** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) = Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1388259 Title: gnome-keyring SRU breaks ECDSA keys Status in “gnome-keyring” package in Ubuntu: New Bug description: Previously I had been using ssh-add with ECDSA keys. (OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014) After my system updated to gnome-keyring 3.10.1-1ubuntu4.1 (picking up the fix for #1271591) they stopped working: wry@onyx:~$ ssh-add ~/.ssh/id_ecdsa Enter passphrase for /home/wry/.ssh/id_ecdsa: Error reading response length from authentication socket. Could not add identity: /home/wry/.ssh/id_ecdsa Downgrading to gnome-keyring 3.10.1-1ubuntu4 resolves the issue. This appears to be because gnome-keyring does not support ECDSA. https://bugzilla.gnome.org/show_bug.cgi?id=641082 refers. This means that the fix for #1271591 is an overall system regression for anybody who uses ECDSA keys. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 10:34:45 2014 SourcePackage: gnome-keyring UpgradeStatus: Upgraded to trusty on 2014-09-20 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1388259/+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 1391775] Re: SSH_AUTH_SOCK and GPG_AGENT_INFO unset
** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) = Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1391775 Title: SSH_AUTH_SOCK and GPG_AGENT_INFO unset Status in “gnome-keyring” package in Ubuntu: New Bug description: I use Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty After some of the recent updates when using from terminal ssh or gpg started to ask key passphrase. I noticed that SSH_AUTH_SOCK and GPG_AGENT_INFO are unset. After playing around I found out that they are only unset when launching terminal using Alt-F2. If using Dash (Super), then it is fine.. env dump attached for both cases. you can see that env-alt-f2.txt has no SSH_AUTH_SOCK or GPG_AGENT_INFO set. Bad one has JOB=xsession-init. Good one has JOB=dbus. I am not sure if the problem of gnome-keyring.. - Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1391775/+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 1270747] Re: No more passphare dialog on SSH
** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) = Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1270747 Title: No more passphare dialog on SSH Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: Previously when I opened a terminal and made an SSH connection I would get pop-up dialog asking to unlock the public key with the passphrase. Well, the dialog is no longer appearing. I can unlock the public key in the terminal, but the unlocked key is not saved in the keyring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 10:47:48 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-23 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1270747/+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 1339360] Re: Update to 3.12
** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) = Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1339360 Title: Update to 3.12 Status in “gnome-keyring” package in Ubuntu: Triaged Bug description: Upstream is 3.12.2, Debian is 3.12.0-2, Ubuntu is 3.10.1-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1339360/+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 1387303] Re: regression: gnome-keyring components can't be disabled anymore
** Changed in: gnome-keyring (Ubuntu) Status: Won't Fix = Incomplete ** Changed in: gnome-keyring (Ubuntu) Status: Incomplete = In Progress ** Description changed: To disable user session gnome-keyring upstart job: $ echo manual ~/.config/upstart/gnome-keyring.override + ... and also disable the XDG auto-start jobs (Startup Applications) + == - - GNOME Keyring is by default a rather invasive service, which meddles with security sensitive processes invasively. This may or may not be wise depending on a users situation. + GNOME Keyring is by default a rather invasive service, which meddles + with security sensitive processes invasively. This may or may not be + wise depending on a users situation. One particular case is GNOME Keyring's gpg-agent implementation, which is incomplete and therefore doesn't support GPG's OpenPGP smartcard support. gpg simply fails (with smartcards) when GNOME Keyring is impersonating gpg-agent... So to be able to use OpenPGP smartcards on Ubuntu, one needs to disable GNOME Keyring from impersonating gpg-agent, which for quite some time now has been trivial to effectively do: echo 'X-GNOME-Autostart-enabled=false' /etc/xdg/autostart/gnome- keyring-gpg.desktop With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this seems to have been broken by the addition of: /usr/share/upstart/sessions/gnome-keyring.conf So it seems the /etc/xdg/autostart/gnome-keyring files are either being ignored, or the started process is supplanted by the process started by the upstart session config. What is unclear to me is what the upstart session configuration is supposed to achieve? And if it is meant to supplant the xdg/autostart files, those should probably have been removed to prevent them from causing any confusion as to how gnome-keyring is started/managed. Presuming the upstart session is meant to stay, I would suggest to remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent confusion as mentioned above. And in my opinion a mechanism should be provided so users can control which gnome-keyring components '-- components=pkcs11,secrets,ssh,gpg' are activated using some configuration file in /etc, as files in /usr aren't meant to be user edited. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 29 18:14:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-07 (205 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2014-04-09T19:49:03.884840 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1387303 Title: regression: gnome-keyring components can't be disabled anymore Status in “gnome-keyring” package in Ubuntu: In Progress Bug description: To disable user session gnome-keyring upstart job: $ echo manual ~/.config/upstart/gnome-keyring.override ... and also disable the XDG auto-start jobs (Startup Applications) == GNOME Keyring is by default a rather invasive service, which meddles with security sensitive processes invasively. This may or may not be wise depending on a users situation. One particular case is GNOME Keyring's gpg-agent implementation, which is incomplete and therefore doesn't support GPG's OpenPGP smartcard support. gpg simply fails (with smartcards) when GNOME Keyring is impersonating gpg-agent... So to be able to use OpenPGP smartcards on Ubuntu, one needs to disable GNOME Keyring from impersonating gpg-agent, which for quite some time now has been trivial to effectively do: echo 'X-GNOME-Autostart-enabled=false' /etc/xdg/autostart/gnome- keyring-gpg.desktop With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this seems to have been broken by the addition of: /usr/share/upstart/sessions/gnome-keyring.conf So it seems the /etc/xdg/autostart/gnome-keyring files are either being ignored, or the started process is supplanted by the process started by the upstart session config. What is unclear to me is what the upstart session configuration is supposed to achieve? And if it is meant to supplant the xdg/autostart files, those should probably have been removed to prevent them from causing any confusion as to how gnome-keyring is started/managed. Presuming the upstart session is meant to stay, I would suggest to remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent confusion as
[Desktop-packages] [Bug 1387303] Re: regression: gnome-keyring components can't be disabled anymore
Meh, i've looked more into this, and I'm still annoyed. I've tried to use gpg smartcard by default for both gpg signing/encryption and ssh authentication and it's harder than it should be. Thus I'm gonna flip NoDisplay=true keys on gpg/ssh components such that one can toggle those off in the UI. Split the gpg/ssh components from the default upstart job, and make those be sensitive on X-GNOME-Autostart-enabled=false in the matching xdg autostart keys (either global /etc/xdg/autostart/gnome-keyring- ssh|gpg.desktop or per user ~/.config/autostart/gnome-keyring- ssh|gpg.desktop) The net effect should be that if one disables the gnome-keyring- ssh.desktop via UI, or any standard way, a standard ssh-agent will be used. Ditto with gnome-keyring-gpg.desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1387303 Title: regression: gnome-keyring components can't be disabled anymore Status in “gnome-keyring” package in Ubuntu: In Progress Bug description: To disable user session gnome-keyring upstart job: $ echo manual ~/.config/upstart/gnome-keyring.override ... and also disable the XDG auto-start jobs (Startup Applications) == GNOME Keyring is by default a rather invasive service, which meddles with security sensitive processes invasively. This may or may not be wise depending on a users situation. One particular case is GNOME Keyring's gpg-agent implementation, which is incomplete and therefore doesn't support GPG's OpenPGP smartcard support. gpg simply fails (with smartcards) when GNOME Keyring is impersonating gpg-agent... So to be able to use OpenPGP smartcards on Ubuntu, one needs to disable GNOME Keyring from impersonating gpg-agent, which for quite some time now has been trivial to effectively do: echo 'X-GNOME-Autostart-enabled=false' /etc/xdg/autostart/gnome- keyring-gpg.desktop With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this seems to have been broken by the addition of: /usr/share/upstart/sessions/gnome-keyring.conf So it seems the /etc/xdg/autostart/gnome-keyring files are either being ignored, or the started process is supplanted by the process started by the upstart session config. What is unclear to me is what the upstart session configuration is supposed to achieve? And if it is meant to supplant the xdg/autostart files, those should probably have been removed to prevent them from causing any confusion as to how gnome-keyring is started/managed. Presuming the upstart session is meant to stay, I would suggest to remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent confusion as mentioned above. And in my opinion a mechanism should be provided so users can control which gnome-keyring components '-- components=pkcs11,secrets,ssh,gpg' are activated using some configuration file in /etc, as files in /usr aren't meant to be user edited. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 29 18:14:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-07 (205 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2014-04-09T19:49:03.884840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303/+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 1387303] Re: regression: gnome-keyring components can't be disabled anymore
** Patch added: gnome-keyring.patch https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303/+attachment/4266383/+files/gnome-keyring.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1387303 Title: regression: gnome-keyring components can't be disabled anymore Status in “gnome-keyring” package in Ubuntu: In Progress Bug description: To disable user session gnome-keyring upstart job: $ echo manual ~/.config/upstart/gnome-keyring.override ... and also disable the XDG auto-start jobs (Startup Applications) == GNOME Keyring is by default a rather invasive service, which meddles with security sensitive processes invasively. This may or may not be wise depending on a users situation. One particular case is GNOME Keyring's gpg-agent implementation, which is incomplete and therefore doesn't support GPG's OpenPGP smartcard support. gpg simply fails (with smartcards) when GNOME Keyring is impersonating gpg-agent... So to be able to use OpenPGP smartcards on Ubuntu, one needs to disable GNOME Keyring from impersonating gpg-agent, which for quite some time now has been trivial to effectively do: echo 'X-GNOME-Autostart-enabled=false' /etc/xdg/autostart/gnome- keyring-gpg.desktop With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this seems to have been broken by the addition of: /usr/share/upstart/sessions/gnome-keyring.conf So it seems the /etc/xdg/autostart/gnome-keyring files are either being ignored, or the started process is supplanted by the process started by the upstart session config. What is unclear to me is what the upstart session configuration is supposed to achieve? And if it is meant to supplant the xdg/autostart files, those should probably have been removed to prevent them from causing any confusion as to how gnome-keyring is started/managed. Presuming the upstart session is meant to stay, I would suggest to remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent confusion as mentioned above. And in my opinion a mechanism should be provided so users can control which gnome-keyring components '-- components=pkcs11,secrets,ssh,gpg' are activated using some configuration file in /etc, as files in /usr aren't meant to be user edited. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 29 18:14:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-07 (205 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2014-04-09T19:49:03.884840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303/+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 1387303] Re: regression: gnome-keyring components can't be disabled anymore
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1387303 Title: regression: gnome-keyring components can't be disabled anymore Status in “gnome-keyring” package in Ubuntu: In Progress Bug description: To disable user session gnome-keyring upstart job: $ echo manual ~/.config/upstart/gnome-keyring.override ... and also disable the XDG auto-start jobs (Startup Applications) == GNOME Keyring is by default a rather invasive service, which meddles with security sensitive processes invasively. This may or may not be wise depending on a users situation. One particular case is GNOME Keyring's gpg-agent implementation, which is incomplete and therefore doesn't support GPG's OpenPGP smartcard support. gpg simply fails (with smartcards) when GNOME Keyring is impersonating gpg-agent... So to be able to use OpenPGP smartcards on Ubuntu, one needs to disable GNOME Keyring from impersonating gpg-agent, which for quite some time now has been trivial to effectively do: echo 'X-GNOME-Autostart-enabled=false' /etc/xdg/autostart/gnome- keyring-gpg.desktop With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this seems to have been broken by the addition of: /usr/share/upstart/sessions/gnome-keyring.conf So it seems the /etc/xdg/autostart/gnome-keyring files are either being ignored, or the started process is supplanted by the process started by the upstart session config. What is unclear to me is what the upstart session configuration is supposed to achieve? And if it is meant to supplant the xdg/autostart files, those should probably have been removed to prevent them from causing any confusion as to how gnome-keyring is started/managed. Presuming the upstart session is meant to stay, I would suggest to remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent confusion as mentioned above. And in my opinion a mechanism should be provided so users can control which gnome-keyring components '-- components=pkcs11,secrets,ssh,gpg' are activated using some configuration file in /etc, as files in /usr aren't meant to be user edited. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 29 18:14:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-07 (205 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2014-04-09T19:49:03.884840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
I have been testing nmahale's patch the last couple of days. It does indeed seem to have fixed the freezing.. However, in place of the freezing, I'm seeing the touchpad periodically stop responding to scroll and RMB clicks. This happens with extreme frequency. Usually once I start doing a scroll with two fingers, I can only scroll very briefly before the scrolling locks up. This tends to happen most frequently when cycling between windows. I've tested booting to an ubuntu iso via usb, and the problem goes away. Things I've found that unfreeze the touchpad include toggling the touchpad off/on, either via key command (fn+F9 on my laptop) or via 'modprobe -r psmouse; modprobe psmouse', or hitting the enter key. This happens inside of all applications, including browsers and terminals. Not seeing anything useful in the logs. It's possible that this is an unrelated problem, but I've only been seeing it when running the patched xorg. Linux 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux KDE 4.13.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in “nvidia-graphics-drivers-319” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-343” package in Ubuntu: Invalid Status in “nvidia-prime” package in Ubuntu: Invalid Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1395182] Re: Screen tears on xrandr orientation inverted
** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1395182 Title: Screen tears on xrandr orientation inverted Status in X.org xf86-video-intel: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: When xrandr -o inverted is run, the resulting image is split down the middle. This happens 95% of the time; it has worked once or twice without tearing. Rotation can be activated through unity-control- center Display Settings rotation field, and that reliably works fine. When xrandr -o normal is run, the display returns to normal (although bug #1376760 is observed). xrandr -o right and xrandr -o left also reliably work without issue; this only occurs on xrandr -o inverted. The same behaviors are observed with the longer form of the command xrandr --output eDP1 --rotation inverted, etc. This has also been reported at https://github.com/pfps/yoga- laptop/issues/28, which uses xrandr commands to invert the display. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 21 15:09:03 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2217] InstallationDate: Installed on 2014-11-21 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CDCTO1WW ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=d032fffc-748c-4ea7-9e61-3c53648c9e27 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0ET22WW (1.09) dmi.board.asset.tag: Not Available dmi.board.name: 20CDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrB0ET22WW(1.09):bd09/09/2014:svnLENOVO:pn20CDCTO1WW:pvrThinkPadS1Yoga:rvnLENOVO:rn20CDCTO1WW:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20CDCTO1WW dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 21 14:47:30 2014 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1079 vendor LGD xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1395182/+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 1390234] Re: Unity desktop misbehaves with some applications with the FGLRX driver
** Changed in: fglrx-installer (Ubuntu) Importance: Undecided = High -- 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/1390234 Title: Unity desktop misbehaves with some applications with the FGLRX driver Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: I've been using Ubuntu 14.10 for a while now, and I ended up switching to the FGLRX driver for performance reasons. My laptop is an Acer Aspire 5742G-7353 with an ATI Mobility Radeon HD 5470 video chip on it. I have noticed that some applications (So far, I've only seen Blender and Chromium do this) displays a little bit (maybe 10-20 pixels?) to the right when maximized. The drivers that are available from the ATI website worked fine, but I had to use the version from the repos since it no longer works with 14.10. Problem only exists in the repo version. http://ubuntuforums.org/showthread.php?t=2225451 http://ubuntuforums.org/showthread.php?t=2241392 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: fglrx 2:14.201-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Nov 6 17:00:08 2014 DistUpgraded: 2014-10-26 22:08:12,603 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: fglrx-core, 14.201, 3.16.0-24-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0487] InstallationDate: Installed on 2014-10-21 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 5742G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=4c5be90d-5004-4ef9-9229-6692e492d1e5 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: Upgraded to utopic on 2014-10-27 (10 days ago) dmi.bios.date: 09/27/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742G dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd09/27/2010:svnAcer:pnAspire5742G:pvrV1.07:rvnAcer:rnAspire5742G:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5742G dmi.product.version: V1.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Nov 6 16:51:13 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1390234/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1359486] Re: [PPA] Use LibreOffice Dialogs setting is ignored in KDE
** Changed in: libreoffice (Ubuntu) Importance: Undecided = Medium ** Changed in: qt4-x11 (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1359486 Title: [PPA] Use LibreOffice Dialogs setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in “libreoffice” package in Ubuntu: Fix Released Status in “qt4-x11” package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option Use LibreOffice Dialogs is ticked or not. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+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 1360732] Re: [utopic] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1360732 Title: [utopic] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: This is essentially the same issue as bug #1360545 but on utopic. On utopic there are also some kernel backtraces as shown below. The system was completely unresponsive and I had to actually unplug the displayport dongle to be able to file this bug report. In addition to the interrupt storm message I got on trusty I also saw: [3.713503] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe C [3.713536] [drm:ivb_err_int_handler] *ERROR* Pipe C FIFO underrun The numerous backtraces looked similar to this each time, they appear to be happening about 3 times per second until I unplugged the dongle. [3.721942] [ cut here ] [3.721959] WARNING: CPU: 0 PID: 83 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_dp.c:3122 intel_dp_link_down+0x1a9/0x230 [i915]() [3.721960] Modules linked in: mxm_wmi i915 igb psmouse e1000e firewire_ohci drm_kms_helper dca firewire_core drm ahci ptp crc_itu_t i2c_algo_bit libahci pps_core wmi video [3.721969] CPU: 0 PID: 83 Comm: kworker/0:1 Not tainted 3.16.0-10-generic #15-Ubuntu [3.721970] Hardware name: Gigabyte Technology Co., Ltd. Z87X-UD5H/Z87X-UD5H-CF, BIOS 10c 06/12/2014 [3.721978] Workqueue: events i915_hotplug_work_func [i915] [3.721979] 0009 8807ee2f7c88 82777e9f [3.721981] 8807ee2f7cc0 8206fced 8807e8b2 8002 [3.721983] 8807ee642800 0003 8807ee6460d8 8807ee2f7cd0 [3.721984] Call Trace: [3.721989] [82777e9f] dump_stack+0x45/0x56 [3.721991] [8206fced] warn_slowpath_common+0x7d/0xa0 [3.721993] [8206fdca] warn_slowpath_null+0x1a/0x20 [3.722002] [c028f069] intel_dp_link_down+0x1a9/0x230 [i915] [3.722011] [c0294505] intel_dp_complete_link_train+0x105/0x390 [i915] [3.722020] [c0294da8] intel_dp_check_link_status+0xb8/0x1b0 [i915] [3.722028] [c028ba98] intel_ddi_hot_plug+0x28/0x30 [i915] [3.722035] [c0251f74] i915_hotplug_work_func+0x1f4/0x340 [i915] [3.722037] [8208d812] process_one_work+0x182/0x4e0 [3.722039] [8208dbdb] worker_thread+0x6b/0x6a0 [3.722041] [8277ab6d] ? __schedule+0x39d/0x890 [3.722042] [8208db70] ? process_one_work+0x4e0/0x4e0 [3.722045] [82094a1b] kthread+0xdb/0x100 [3.722047] [82094940] ? kthread_create_on_node+0x1c0/0x1c0 [3.722048] [8277fe7c] ret_from_fork+0x7c/0xb0 [3.722050] [82094940] ? kthread_create_on_node+0x1c0/0x1c0 [3.722051] ---[ end trace eb9925ee23e16705 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.343 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Aug 24 01:23:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140822) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD5H ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash -- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD5H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte
[Desktop-packages] [Bug 1338812] Re: [hsw mesa] False GPU lockup IPEHR: 0x780c0000 IPEHR: 0x0b140001
** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1338812 Title: [hsw mesa] False GPU lockup IPEHR: 0x780c IPEHR: 0x0b140001 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Error report just appeared while testing 14.10 ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 8 00:01:23 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DuplicateSignature: GPU lockup IPEHR: 0x780c IPEHR: 0x0b140001 Ubuntu 14.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2014-07-07 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 MachineType: ASUS All Series ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-generic root=UUID=430f6f83-f04f-4f28-9ad0-f63af5c55d78 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.54-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x780c IPEHR: 0x0b140001 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd05/19/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81I-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 8 00:16:58 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 694 vendor SAM xserver.version: 2:1.15.1-0ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1338812/+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 1371481] Re: Network Manager's Upstart configuration is wrong - Network Manager doesn't start in case of faulty ifupdown configuration
** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: network-manager (Ubuntu) Importance: Undecided = Low ** Changed in: hundredpapercuts Importance: Undecided = Low ** Changed in: hundredpapercuts Importance: Low = High ** Changed in: network-manager (Ubuntu) Importance: Low = High -- 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/1371481 Title: Network Manager's Upstart configuration is wrong - Network Manager doesn't start in case of faulty ifupdown configuration Status in One Hundred Papercuts: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: Hi everyone, If you add a faulty entry to ifupdown's configuration (/etc/network/interfaces or sourced in files) then Network Manager doesn't get started by Upstart. As an example add this block for a non-existent network interface to /etc/network/interfaces: auto bogus0 iface bogus0 inet dhcp If you reboot your machine then Network Manager won't be started by Upstart. The issue with Network Manager's Upstart configuration is that it starts on the following condition: start on (local-filesystems and started dbus and static-network-up) This is wrong as the static-network-up event is never emitted in case the ifupdown configuration is (partially) invalid. In order to fix this issue please use the following start on condition: start on (local-filesystems and started dbus and started networking) This is an issue in all currently supported Ubuntu releases. Please let me know if you have any further questions. Best, Michael Schaller To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1371481/+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 1378438] Re: Printer dialog stuck on Getting printer information...
** Changed in: cups (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1378438 Title: Printer dialog stuck on Getting printer information... Status in “cups” package in Ubuntu: Confirmed Bug description: In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered printer, the Status field changes to Getting printer information... and the mouse cursor goes into spinning icon, and the Print button stays disabled, so I cannot print. In Firefox, the status tells me the printer is low on toner, but allows me to print. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: cups 1.7.5-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CupsErrorLog: E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address - Permission denied E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address - Permission denied E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address - Permission denied CurrentDesktop: GNOME Date: Tue Oct 7 09:29:43 2014 InstallationDate: Installed on 2014-02-24 (224 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140218) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro11,3 Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago) dmi.bios.date: 10/18/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B02.1310181745 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.name: MacBookPro11,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1378438/+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
