[Desktop-packages] [Bug 1311899] Re: Popup is too small to display Facebook authorization
** Summary changed: - Popup is too small to display Facebook authorization + Popup is too small to display Facebook authorization -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1311899 Title: Popup is too small to display Facebook authorization Status in “gnome-online-accounts” package in Ubuntu: Confirmed Bug description: Description of problem: Unable to grant permissions to Gnome application on Facebook due to window size. Version-Release number of selected component (if applicable): gnome-online-accounts-3.8.5-7.el7.x86_64 How reproducible: always Steps to Reproduce: 0. Remove Gnome from: https://www.facebook.com/settings?tab=applications 1. Login to Facebook through Online Accounts Actual results: Your popup is too small to display this page. Please enlarge it to proceed. see screenshot Expected results: Webview dialog asking to give permissions to Gnome application on Facebook. This bug report is copied from: https://bugzilla.redhat.com/show_bug.cgi?id=1081520 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-online-accounts 3.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Apr 23 23:47:07 2014 InstallationDate: Installed on 2012-12-07 (502 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to trusty on 2014-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1311899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
can you add snd_printk to print / find out whether it can read wcaps 0x200500 from node 0x3e after changing codec-num_nodes ? nid = codec-start_nid; for (i = 0; i codec-num_nodes; i++, nid++) codec-wcaps[i] = snd_hda_param_read(codec, nid, AC_PAR_AUDIO_WIDGET_CAP); -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
for (i = 0; i codec-num_nodes; i++, nid++) {
codec-wcaps[i] = snd_hda_param_read(codec, nid,
AC_PAR_AUDIO_WIDGET_CAP);
printk(MIK: nid = %d, wcaps = %d\n, nid, codec-wcaps[i]);
}
Result:
[7.491195] MIK: nid = 62, wcaps = 2098432 (62 = 0x3e, 2098432 =
0x200500)
Full log: http://pastebin.com/LbghKFg5
--
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/1313904
Title:
[W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
suspend/resume
Status in ALSA driver:
Unknown
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
No sound in headphones jack after suspend/resume.
But sound in headphones jack is OK after cold boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Uname: Linux 3.15.0-031500rc2-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 28 23:20:59 2014
InstallationDate: Installed on 2014-04-26 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275416] Re: touchscreen do not work after suspend/resume
I have a Lenovo x201 tablet running 14.04.1 LTS. Neither of the workarounds in #7, #15 restore the stylus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1275416 Title: touchscreen do not work after suspend/resume Status in “xinput” package in Ubuntu: Confirmed Bug description: My laptop (Thinkpad X200T with multi-touch screen) installed the 'Trusty' ubuntu 14.04 (64bits), touchscreen works well after cold boot! But after suspend/resume, touchsreen do not response. Execute 'xsetwacom --list' in terminal, there is nothing, both 'wacom touch' and 'wacom stylus' are gone. I must logout and relogin or reboot, the touchscreen can be normal again. By the way, the same problem happens in the 'Saucy' ubuntu 13.10 (64bits). But in 'Raring' ubuntu 13.04 (64bits), this problem does no exist, touchscreen WORKS WELL after suspend/resume. This Thinkpad X200T updated the newest BIOS, and keep ubuntu OS up to date. Please fix this bug, because 14.04 is a very important version for touchscreen devices, and i think 'suspend/resume' function is important too. Thanks! --- Feb 4, 2014 update Oh I'm sorry, I find a new change for this bug that I never noticed before. I keep Trusty ubuntu up to date(Feb 4, 2014). When the OS's first boot from cold boot, touchscreen works well. Then if suspend/resume for the first time, touchscreen will not response. At this moment, logout and relogin, touchscreen works well again even after suspend/resume. Simply put, touchscreen do not response only after the first suspend/resume since a cold boot. Once the OS logout and relogin, touchscreen will work well after any suspend/resume. The key point is that the OS must logout and relogin for at least one time. Always keep 'Trusty' ubuntu OS updated. that's a strange bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349273] Re: NM does not retry opening mobile data on reboot
This happened for touch image #149, with network-manager version 0.9.8.8-0ubuntu23 . syslog for a simulated case where the APN name is wrong (APN err.airtelwap.es), then ofono is stopped, the APN corrected (airtelwap.es) and the phone rebooted is attached. The result is that no context is activated. However, I would not say that this is exactly the same case as the one in the description, as in this case after restarting system settings has data set as 2G/3G/4G instead of Off. Probably the APN name change makes NM behave slightly different. ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1349273/+attachment/4164788/+files/syslog -- 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/1349273 Title: NM does not retry opening mobile data on reboot Status in “network-manager” package in Ubuntu: Incomplete Bug description: In case NM has failed to open any mobile data context, it will not re- try when rebooting the phone. This happened with a pre-paid SIM with no credit: opening a data context for it obviously failed. After adding credit to the SIM, I followed the instructions from the operator to reboot the phone to get data. However, after rebooting I had no mobile data. Taking a look to system settings, cellular data was set to Off and I was able to revert the situation marking the 2G/3G/4G option. Make NM retry the list of contexts in case no context was ever active on previous boot would make life easier for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1349273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 807620] Re: Fixes tablets not working after suspend
Adding SUSPEND_MODULES=wacom wacom_w8001 to /usr/lib/pm-utils/defaults works for me. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/807620 Title: Fixes tablets not working after suspend Status in “xf86-input-wacom” package in Ubuntu: Won't Fix Bug description: I have an HP 2710p Tablet PC running Xubuntu 11.04, which features a wacom tablet. The stylus always works on first boot, but as soon as I sleep and then resume the system, the stylus stops working. It's still listed in xinput list, but it just wouldn't work. It seems the problem lies in the kernel module, so I'm not sure that this is the right way to do this, but unloading the wacom module before sleep and then adding it back after resume seems to make everything work correctly. Question: why isn't this included in Ubuntu by default? I've had this problem since leaving Xubuntu 10.04 for 10.10, and now 11.04.. I've attached a patch to apply to /var/lib/dpkg/info/xserver-xorg- input-wacom.preinst But if you want to just fix your own system, simply make a script in /etc/pm/sleep.d named 75_wacom, and put this into it: #!/bin/sh # load and unload wacom module for suspend and hibernate case $1 in thaw|resume) modprobe wacom ;; suspend|hibernate) modprobe -r wacom ;; esac Then run sudo chmod +x /etc/pm/sleep.d/75_wacom and hey presto! Your tablet works again. Thanks, Ubuntu is cool. p.s. this was based off of moaxey's work at http://ubuntuforums.org/archive/index.php/t-1686278.html ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jul 8 12:19:44 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30c8] Subsystem: Hewlett-Packard Company Device [103c:30c8] InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release amd64 (20110427) MachineType: Hewlett-Packard HP Compaq 2710p (#ABA) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=10075b3d-bbec-4b09-93e0-b9a42fcc47c8 ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MOU Ver. F.15 dmi.board.name: 30C8 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 74.3A dmi.chassis.asset.tag: BlehBleh dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MOUVer.F.15:bd01/22/2010:svnHewlett-Packard:pnHPCompaq2710p(#ABA):pvrF.15:rvnHewlett-Packard:rn30C8:rvrKBCVersion74.3A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 2710p (#ABA) dmi.product.version: F.15 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/807620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275416] Re: touchscreen do not work after suspend/resume
Sorry for noise. Following Comment #2 in Bug 807620 seems to have fixed the problem for me. Specifically, in /usr/lib/pm-utils/defaults I uncommented the # SUSPEND_MODULES= line and replaced it by SUSPEND_MODULES=wacom wacom_w8001. When I resume my stylus touch screen work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1275416 Title: touchscreen do not work after suspend/resume Status in “xinput” package in Ubuntu: Confirmed Bug description: My laptop (Thinkpad X200T with multi-touch screen) installed the 'Trusty' ubuntu 14.04 (64bits), touchscreen works well after cold boot! But after suspend/resume, touchsreen do not response. Execute 'xsetwacom --list' in terminal, there is nothing, both 'wacom touch' and 'wacom stylus' are gone. I must logout and relogin or reboot, the touchscreen can be normal again. By the way, the same problem happens in the 'Saucy' ubuntu 13.10 (64bits). But in 'Raring' ubuntu 13.04 (64bits), this problem does no exist, touchscreen WORKS WELL after suspend/resume. This Thinkpad X200T updated the newest BIOS, and keep ubuntu OS up to date. Please fix this bug, because 14.04 is a very important version for touchscreen devices, and i think 'suspend/resume' function is important too. Thanks! --- Feb 4, 2014 update Oh I'm sorry, I find a new change for this bug that I never noticed before. I keep Trusty ubuntu up to date(Feb 4, 2014). When the OS's first boot from cold boot, touchscreen works well. Then if suspend/resume for the first time, touchscreen will not response. At this moment, logout and relogin, touchscreen works well again even after suspend/resume. Simply put, touchscreen do not response only after the first suspend/resume since a cold boot. Once the OS logout and relogin, touchscreen will work well after any suspend/resume. The key point is that the OS must logout and relogin for at least one time. Always keep 'Trusty' ubuntu OS updated. that's a strange bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349712] [NEW] Unreliable operation for some Super shortcuts
Public bug reported: I am using Ubuntu 14.04 with flashback metacity session. I configured the launch terminal on the Supers shortcut. I also searched and replaced in dconf all other shortcuts with Super+s However, the operation of this shortcut is extremely unreliable : sometimes it does not work at all, some other times it does work but only if i keep the Super key pressed significantly longer. More than that, in order to work i have to : press super - press s - release s - release super. I also configured a Super+e shortcut for home folder. This one works every time provided that the long sequence above is respected : press super - press e - release e - release super. I would expect : 1.Super+s to work every time (it seems that something else may consume the event but i cannot find what it is, as nothing seems to happen visually when super+s does not launch the terminal. 2. When the shortcuts are processed, i would expect the configured script/execution/action to be executed right after press super- press shortcut letter, WITHOUT requiring the long super press. What is even more weird is that if i use flashback session with compiz, the shortcuts seem to always work and to work fast (without long super press). DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04.1 LTS ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: shortcuts super trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1349712 Title: Unreliable operation for some Super shortcuts Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: I am using Ubuntu 14.04 with flashback metacity session. I configured the launch terminal on the Supers shortcut. I also searched and replaced in dconf all other shortcuts with Super+s However, the operation of this shortcut is extremely unreliable : sometimes it does not work at all, some other times it does work but only if i keep the Super key pressed significantly longer. More than that, in order to work i have to : press super - press s - release s - release super. I also configured a Super+e shortcut for home folder. This one works every time provided that the long sequence above is respected : press super - press e - release e - release super. I would expect : 1.Super+s to work every time (it seems that something else may consume the event but i cannot find what it is, as nothing seems to happen visually when super+s does not launch the terminal. 2. When the shortcuts are processed, i would expect the configured script/execution/action to be executed right after press super- press shortcut letter, WITHOUT requiring the long super press. What is even more weird is that if i use flashback session with compiz, the shortcuts seem to always work and to work fast (without long super press). DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1349712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/hda/hda_proc.c
it is because nodes is read from codec again in print_codec_info()
need to fix this value
nodes = snd_hda_get_sub_nodes(codec, codec-afg, nid);
if (! nid || nodes 0) {
snd_iprintf(buffer, Invalid AFG subtree\n);
snd_hda_power_down(codec);
return;
}
print_gpio(buffer, codec, codec-afg);
if (codec-proc_widget_hook)
codec-proc_widget_hook(buffer, codec, codec-afg);
for (i = 0; i nodes; i++, nid++) {
unsigned int wid_caps =
snd_hda_param_read(codec, nid,
AC_PAR_AUDIO_WIDGET_CAP);
--
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/1313904
Title:
[W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
suspend/resume
Status in ALSA driver:
Unknown
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
No sound in headphones jack after suspend/resume.
But sound in headphones jack is OK after cold boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Uname: Linux 3.15.0-031500rc2-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 28 23:20:59 2014
InstallationDate: Installed on 2014-04-26 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
int snd_hda_get_sub_nodes(struct hda_codec *codec, hda_nid_t nid,
hda_nid_t *start_id)
{
unsigned int parm;
parm = snd_hda_param_read(codec, nid, AC_PAR_NODE_COUNT);
if (parm == -1)
return 0;
/* this mean we need to fix the param when codec is vt1802 */
*start_id = (parm 16) 0x7fff;
return (int)(parm 0x7fff);
}
--
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/1313904
Title:
[W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
suspend/resume
Status in ALSA driver:
Unknown
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
No sound in headphones jack after suspend/resume.
But sound in headphones jack is OK after cold boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Uname: Linux 3.15.0-031500rc2-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 28 23:20:59 2014
InstallationDate: Installed on 2014-04-26 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
snd_hda_get_sub_nodes(struct hda_codec *codec, hda_nid_t nid,
hda_nid_t *start_id)
{
unsigned int parm;
parm = snd_hda_param_read(codec, nid, AC_PAR_NODE_COUNT);
if (parm == -1)
return 0;
*start_id = (parm 16) 0x7fff;
/* this mean we need to fix the return value param when codec is vt1802 and
nid is functional group */
return (int)(parm 0x7fff);
}
--
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/1313904
Title:
[W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
suspend/resume
Status in ALSA driver:
Unknown
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
No sound in headphones jack after suspend/resume.
But sound in headphones jack is OK after cold boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Uname: Linux 3.15.0-031500rc2-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 28 23:20:59 2014
InstallationDate: Installed on 2014-04-26 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1345602] Re: Remmina Remote Desktop Client doesn't save Quality option changes
** Tags added: cherry-pick ** Description changed: Upstream bug report: https://github.com/FreeRDP/Remmina/issues/283 1) lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) apt-cache policy remmina remmina: Installed: 1.0.0-4ubuntu3 Candidate: 1.0.0-4ubuntu3 Version table: *** 1.0.0-4ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens Remmina Remote Desktop Client - Connection - New - Name test - Server 192.168.1.2 - User name test - Password test - Save Then, highlight the test entry - Edit Preferences - RDP tab - change Quality option Poor (fastest) to Best (slowest) - Close button and this would persist if one goes back into Preferences. 4) What happens instead is it is back to Poor (fastest). As well, trying to choose Best (slowest) when creating the connection doesn't persist either. + Upstream's position is this already fixed in MASTER, and may be fixed + via https://github.com/FreeRDP/Remmina/pull/276 . + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: remmina 1.0.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:41:58 2014 InstallationDate: Installed on 2014-06-21 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1345602 Title: Remmina Remote Desktop Client doesn't save Quality option changes Status in Remmina - The GTK+ Remote Desktop Client: New Status in “remmina” package in Ubuntu: Triaged Bug description: Upstream bug report: https://github.com/FreeRDP/Remmina/issues/283 1) lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) apt-cache policy remmina remmina: Installed: 1.0.0-4ubuntu3 Candidate: 1.0.0-4ubuntu3 Version table: *** 1.0.0-4ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens Remmina Remote Desktop Client - Connection - New - Name test - Server 192.168.1.2 - User name test - Password test - Save Then, highlight the test entry - Edit Preferences - RDP tab - change Quality option Poor (fastest) to Best (slowest) - Close button and this would persist if one goes back into Preferences. 4) What happens instead is it is back to Poor (fastest). As well, trying to choose Best (slowest) when creating the connection doesn't persist either. Upstream's position is this already fixed in MASTER, and may be fixed via https://github.com/FreeRDP/Remmina/pull/276 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: remmina 1.0.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:41:58 2014 InstallationDate: Installed on 2014-06-21 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/remmina/+bug/1345602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349751] [NEW] CTRL-space is a bad choice for shortcut as it is used by emacs
Public bug reported: On what operating system? OS (Linux distributions, UNIX or ...):Linux Mint 17 Architecture (i386, x86_64):x86_64 IBus version:1.5.5 Input method name and version: Python version:2.7.6 dbus version:? dbus-python version:? gtk version (if bug is about gtk applications): qt version (if bug is about qt applications): What steps will reproduce the problem? 1. Install Linux Mint XFCE 2. Start emacs 3. Mark a block using CTRL-space 4. Get confused why CTRL-space does not work 1. Go to duolingo.com 2. Go to a listening lesson 3. Press CTRL-space to listen to the audio at a slower speed 4. Get confused why CTRL-space does not work What is the expected output? What do you see instead? I expect CTRL-space to be given to emacs/duolingo. I see that CTRL-space is intercepted. Please provide any additional information below. According to the ibus people http://code.google.com/p/ibus/issues/detail?id=1732#c4 the default shortcut is Super+space. Ubuntu uses a patch (debian/patches/ibus-xx-ctrl-space.patch) which changes the Super+space to CTRL+space. That is a bad choice as CTRL+space is also used alot in Emacs. I have been unable to find the rationale behind overriding the default of Super+space, and thus I will suggest you simply remove the patch. - o - The problem is that I as a user am not told which program intercepts CTRL-space, so it is very hard for me to figure out which program eats my CTRL-space. ibus does not give a warning, and if you (like me) have a single input method engine installed, you do not see any change from pressing CTRL-space - making it even harder to figure out. I spent 2 frustrating hours figuring out what caused problem, and I expect other emacs/duolingo.com users will experience the same. There are several ways in which this could be improved: * Disable the shortcut if there is only one input method engine * Give a pop-up dialog box the first time the user activates the shortcut, so that the user is aware that this shortcut is run by ibus and how to disable it if that is not what the user wants. * Disable the shortcut by default - I would imagine the people that have the need for multiple input engines would have to select the input engines anyway, so they will see the preferences anyway and see that they can select a shortcut. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4 Uname: Linux 3.13.0-32-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Tue Jul 29 11:05:42 2014 InstallationDate: Installed on 2013-10-10 (291 days ago) InstallationMedia: Linux Mint 15 Olivia - Release amd64 (20130520) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug qiana third-party-packages ** Summary changed: - CTRL-space is a bad chose for shortcut as it is used by emacs + CTRL-space is a bad choice for shortcut as it is used by emacs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1349751 Title: CTRL-space is a bad choice for shortcut as it is used by emacs Status in “ibus” package in Ubuntu: New Bug description: On what operating system? OS (Linux distributions, UNIX or ...):Linux Mint 17 Architecture (i386, x86_64):x86_64 IBus version:1.5.5 Input method name and version: Python version:2.7.6 dbus version:? dbus-python version:? gtk version (if bug is about gtk applications): qt version (if bug is about qt applications): What steps will reproduce the problem? 1. Install Linux Mint XFCE 2. Start emacs 3. Mark a block using CTRL-space 4. Get confused why CTRL-space does not work 1. Go to duolingo.com 2. Go to a listening lesson 3. Press CTRL-space to listen to the audio at a slower speed 4. Get confused why CTRL-space does not work What is the expected output? What do you see instead? I expect CTRL-space to be given to emacs/duolingo. I see that CTRL-space is intercepted. Please provide any additional information below. According to the ibus people http://code.google.com/p/ibus/issues/detail?id=1732#c4 the default shortcut is Super+space. Ubuntu uses a patch (debian/patches/ibus-xx-ctrl-space.patch) which changes the Super+space to CTRL+space. That is a bad choice as CTRL+space is also used alot in Emacs. I have been unable to find the rationale behind overriding the default of Super+space, and thus I will suggest you simply remove the patch. - o - The problem is that I as a user am not told which program intercepts CTRL-space, so it is very hard for me to figure out which program eats my CTRL-space. ibus does not give a warning,
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
Done:
int snd_hda_get_sub_nodes(struct hda_codec *codec, hda_nid_t nid,
hda_nid_t *start_id)
{
unsigned int parm;
parm = snd_hda_param_read(codec, nid, AC_PAR_NODE_COUNT);
if (parm == -1)
return 0;
*start_id = (parm 16) 0x7fff;
if (codec-vendor_id == 0x11068446)
return 55;
return (int)(parm 0x7fff);
}
Here is new alsa-info with 0x3e: http://www.alsa-
project.org/db/?f=7c253b9d2d1dbec0d060a43e074fc9190150db3f
But after suspend/resume there are still no sound in headphone jack.
--
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/1313904
Title:
[W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
suspend/resume
Status in ALSA driver:
Unknown
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
No sound in headphones jack after suspend/resume.
But sound in headphones jack is OK after cold boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Uname: Linux 3.15.0-031500rc2-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 28 23:20:59 2014
InstallationDate: Installed on 2014-04-26 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Вбудоване аудіо - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mik2139 F pulseaudio
/dev/snd/controlC1: mik2139 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1258230] Re: gnome-terminal multiline search
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New = Confirmed -- 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/1258230 Title: gnome-terminal multiline search Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Gnome-terminal can't find word if it splitted (due finite terminal's width) between several lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1258230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349751] Re: CTRL-space is a bad choice for shortcut as it is used by emacs
*** This bug is a duplicate of bug 1278569 *** https://bugs.launchpad.net/bugs/1278569 ** This bug has been marked a duplicate of bug 1278569 ibus breaks emacs and eclipse control-space keybinding -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1349751 Title: CTRL-space is a bad choice for shortcut as it is used by emacs Status in “ibus” package in Ubuntu: New Bug description: On what operating system? OS (Linux distributions, UNIX or ...):Linux Mint 17 Architecture (i386, x86_64):x86_64 IBus version:1.5.5 Input method name and version: Python version:2.7.6 dbus version:? dbus-python version:? gtk version (if bug is about gtk applications): qt version (if bug is about qt applications): What steps will reproduce the problem? 1. Install Linux Mint XFCE 2. Start emacs 3. Mark a block using CTRL-space 4. Get confused why CTRL-space does not work 1. Go to duolingo.com 2. Go to a listening lesson 3. Press CTRL-space to listen to the audio at a slower speed 4. Get confused why CTRL-space does not work What is the expected output? What do you see instead? I expect CTRL-space to be given to emacs/duolingo. I see that CTRL-space is intercepted. Please provide any additional information below. According to the ibus people http://code.google.com/p/ibus/issues/detail?id=1732#c4 the default shortcut is Super+space. Ubuntu uses a patch (debian/patches/ibus-xx-ctrl-space.patch) which changes the Super+space to CTRL+space. That is a bad choice as CTRL+space is also used alot in Emacs. I have been unable to find the rationale behind overriding the default of Super+space, and thus I will suggest you simply remove the patch. - o - The problem is that I as a user am not told which program intercepts CTRL-space, so it is very hard for me to figure out which program eats my CTRL-space. ibus does not give a warning, and if you (like me) have a single input method engine installed, you do not see any change from pressing CTRL-space - making it even harder to figure out. I spent 2 frustrating hours figuring out what caused problem, and I expect other emacs/duolingo.com users will experience the same. There are several ways in which this could be improved: * Disable the shortcut if there is only one input method engine * Give a pop-up dialog box the first time the user activates the shortcut, so that the user is aware that this shortcut is run by ibus and how to disable it if that is not what the user wants. * Disable the shortcut by default - I would imagine the people that have the need for multiple input engines would have to select the input engines anyway, so they will see the preferences anyway and see that they can select a shortcut. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4 Uname: Linux 3.13.0-32-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Tue Jul 29 11:05:42 2014 InstallationDate: Installed on 2013-10-10 (291 days ago) InstallationMedia: Linux Mint 15 Olivia - Release amd64 (20130520) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1349751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
I am experiencing a very similar bug. ALthough I am using the nouveau driver. I made a separate bug report for my issues: #1349121 I also switched to the proprietary driver and tried the fix submitted, it did however not solve my issues. Are these different issues? -- 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/1296020 Title: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04) Status in “nvidia-prime” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: In Progress Status in “ubuntu-drivers-common” source package in Precise: Invalid Status in “nvidia-prime” source package in Trusty: Invalid Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: SRU Request Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. [Impact] * The ghost VGA output confuses lightdm and the gnome-settings-daemon making the system unusable. [Test Case] * Install the nvidia binary driver, reboot, and check the output of the xrandr -q command - Expected: only the outputs that are actually connected will be marked as active. - Bad behavior: a non-existent VGA device will show up in the output. [Regression Potential] * Low, as it only disables CRT outputs in the nvidia driver. [Other Info] * N/A -- There is a non existent display detected in both intel driver only and nvidia 331 driver installation. The non existent display is Unknown Display shown in gnome-control-center -- display and CRT-0 in nvidia-settings, and VGA-0 in xrandr -q output. It will cause gdm failed to start. gnome-shell has some crazy layouts. lightdm will only occupy 2/3 of monitor in top left corner. I tested this in intel driver only environment. and nvidia-331 installation environment. My laptop is Asus U36JC. My monitor correct resolution is 1366x768. The following is the output of xrandr -q in gnome-shell with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 680x384+0+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x384 60.0*+ 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x720 60.0 928x696 60.1 896x672 60.0 960x600 60.0 960x540 60.0 800x600 60.0 60.3 56.2 840x525 60.0 59.9 800x512 60.2 700x525 60.0 640x512 60.0 720x450 59.9 640x480 60.0 59.9 680x384 59.8 60.0 576x432 60.1 512x384 60.0 400x300 60.3 56.3 320x240 60.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 total 1472 skew 0 clock 47.1KHz v: height 768 start 773 end 782 total 785 clock 60.0Hz 1360x768 (0x48) 72.0MHz h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 680x384 (0x5c) 36.0MHz h: width 680 start 704 end 720 total 760 skew 0 clock 47.4KHz v: height 384 start 385 end 390 total 395 clock 60.0Hz The following is the output of xrandr -q in lxde with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 1024x768+31+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x38460.0 + 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x72060.0 928x69660.1 896x67260.0 960x60060.0 960x54060.0 800x60060.0 60.3 56.2 840x52560.0 59.9 800x51260.2 700x52560.0 640x51260.0 720x45059.9 640x48060.0 59.9 680x38459.8 60.0 576x43260.1 512x38460.0 400x30060.3 56.3 320x24060.1 VGA-1-0 disconnected (normal
[Desktop-packages] [Bug 1349766] [NEW] New release 10.2.4 (OK - Package in Debian)
Public bug reported: https://launchpad.net/debian/sid/+source/mesa ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mesa-common-dev 10.2.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 29 06:00:11 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0d7] InstallationDate: Installed on 2014-04-27 (92 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=13144268-2374-4154-83f1-c35d81306190 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 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: Mon Jul 28 22:50:45 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu8 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu utopic -- 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/1349766 Title: New release 10.2.4 (OK - Package in Debian) Status in “mesa” package in Ubuntu: New Bug description: https://launchpad.net/debian/sid/+source/mesa ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mesa-common-dev 10.2.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 29 06:00:11 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0d7] InstallationDate: Installed on 2014-04-27 (92 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=13144268-2374-4154-83f1-c35d81306190 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
[Desktop-packages] [Bug 1269181] Re: Update to 0.24
This bug was fixed in the package exiv2 - 0.24-2ubuntu1
---
exiv2 (0.24-2ubuntu1) utopic; urgency=medium
* Rebase on Debian, remaining Ubuntu changes: (LP: #1269181)
* debian/patches/libtool-ppc64el.diff:
- Apply libtool patch for powerpc*le-linux support, copied from libtool
2.4.2-1.3ubuntu2.
* debian/patches/config-updates.diff:
- Update config.{guess,sub} for AArch64.
-- Robert Ancell robert.anc...@canonical.com Fri, 04 Jul 2014 11:46:22
+1200
** Changed in: exiv2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1269181
Title:
Update to 0.24
Status in “exiv2” package in Ubuntu:
Fix Released
Bug description:
Update to 0.24
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1269181/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 46586] Re: Logitech Media Keyboard Elite not fully supported
Still affected by this bug in 13.04
Media keys are only partially supported.
Unsupported keys:
Reset zoom (no keycode)
Zoom in (keycode 418)
Zoom out (keycode 419)
Word key (keycode 421)
Excel key (keycode 423)
Powerpoint key (keycode 425)
Launch A (keycode 328)
Launch B (keycode 329)
Launch C (keycode 330)
Launch D (keycode 331)
** Changed in: xkeyboard-config (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/46586
Title:
Logitech Media Keyboard Elite not fully supported
Status in “xkeyboard-config” package in Ubuntu:
Confirmed
Bug description:
The media keys on the Logitech Media Keyboard Elite are not supported
properly - the layout appears to be different than the others already
included and the kernel does not recognise many of the media/extra
keys. Currently I have the keyboard hooked up through the USB port.
I have made the following changes to my system to attempt to support
this keyboard. Caution: Pressing the key I have mapped as XF86LaunchC
(F11 with the F-mode light off) will reliably crash and reboot the
system - I have no idea why.
At boot time, the following script is run to map the scancodes to the
console level codes. I assume that this keyboard really requires
fixes in the kernel code to recognise this keyboard without the use of
extra scan codes.
# Kernel level keycode mappings for the Logitech Media Keyboard Elite USB
# 6a 190 Zoom In
# e004 191 Zoom Out
# 6b 192 Zoom Reset
# e011 193 Messenger
# e05a 194 Mode F (switch function keys)
# e03b 195 (F1 )Help
# e03c 196 (F2 )Word
# e03d 197 (F3 )Excel
# e03e 198 (F4 )Powerpoint
# e03f 199 (F5 )Undo
# e040 200 (F6 )Redo
# e041 201 (F7 )Print
# e042 202 (F8 )Save
# e043 203 (F9 )Box A
# e044 204 (F10)Box B
# e057 205 (F11)Box C
# e058 206 (F12)Box D
setkeycodes \
6a 190 \
e004 191 \
6b 192 \
e011 193 \
e05a 194 \
e03b 195 \
e03c 196 \
e03d 197 \
e03e 198 \
e03f 199 \
e040 200 \
e041 201 \
e042 202 \
e043 203 \
e044 204 \
e057 205 \
e058 206
# ---
I also made the following alterations to the symbols in
/etc/X11/xkb/symbols/inet:
--- inet.20060516 2006-05-16 20:44:30.0 -0400
+++ inet2006-05-16 20:59:41.0 -0400
@@ -1244,6 +1244,39 @@
key I2D { [ XF86AudioRaiseVolume ] };
};
+// Logitech Media Keyboard Elite
+partial alphanumeric_keys
+xkb_symbols logimedelite {
+include inet(logitech_base)
+
+key K5A { [ XF86ZoomIn] };
+key K74 { [ XF86ZoomOut ] };
+key I79 { [ XF86Clear ] };
+key I22 { [ XF86AudioPlay, XF86AudioPause ] };
+key I24 { [ XF86AudioStop ] };
+key I19 { [ XF86AudioNext ] };
+key K6D { [ XF86Messenger ] };
+key K21 { [ XF86Calculator] };
+key K6F { [ XF86ModeLock ] };
+
+key I15 { [ XF86Help ] };
+key I16 { [ XF86Word ] };
+key I1A { [ XF86Excel ] };
+key I1B { [ XF86Finance ] };
+
+key I27 { [ XF86Back ] };
+key I28 { [ XF86Forward ] };
+key I29 { [ XF86Book ] };
+key I2B { [ XF86Save ] };
+
+key I2C { [ XF86LaunchA ] };
+key I2D { [ XF86LaunchB ] };
+key I25 { [ XF86LaunchC ] };
+key I2F { [ XF86LaunchD ] };
+
+};
+
+
partial alphanumeric_keys
xkb_symbols logiultrax {
include inet(logitech_base)
Then the three rules files in /etc/X11/xkb/rules were updated as follows:
toby@nexus:/etc/X11/xkb/rules$ diff -Naur base.20060516 base
--- base.20060516 2006-05-16 21:00:45.0 -0400
+++ base2006-05-16 21:01:43.0 -0400
@@ -38,7 +38,7 @@
honeywell_euroboard \
rapidaccess rapidaccess2 rapidaccess2a \
ltcd logiaccess logicdp logicdpa logicdit logicink logiciink \
- logiinkse logiinkseusb logiitc logiik itouch logiultrax \
+ logiinkse logiinkseusb logiitc logiik itouch logimedelite
logiultrax \
mx1998
[Desktop-packages] [Bug 1349777] [NEW] Ubuntu 14.04 crashes with error path usr/bin/Xorg regularly
Public bug reported: On my i7 2.80 GH, 8 GB RAM HP desktop tower, Ubuntu 14.04 has crashed regularly, roughly every 10 minutes, and on reboot gives several different executable paths starting with Xorg (ie usr7bin/Xorg). This has happened when I am running in LibreOffice 4.2.1 or even About Me. Running Ubuntu 14.04.1 LTS, Release 14.04. It happened several ties while running LibreOfffice, so here is that programme's info: LibreOffice Candidate: 1:4.2.4-0ubuntu2 Version table: 1:4.2.4-0ubuntu2 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 1:4.2.3~rc3-0ubuntu2 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages I expected the system not to crash. It crashed...repeatedly...six time until now in last hour. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1349777 Title: Ubuntu 14.04 crashes with error path usr/bin/Xorg regularly Status in “evolution-data-server” package in Ubuntu: New Bug description: On my i7 2.80 GH, 8 GB RAM HP desktop tower, Ubuntu 14.04 has crashed regularly, roughly every 10 minutes, and on reboot gives several different executable paths starting with Xorg (ie usr7bin/Xorg). This has happened when I am running in LibreOffice 4.2.1 or even About Me. Running Ubuntu 14.04.1 LTS, Release 14.04. It happened several ties while running LibreOfffice, so here is that programme's info: LibreOffice Candidate: 1:4.2.4-0ubuntu2 Version table: 1:4.2.4-0ubuntu2 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 1:4.2.3~rc3-0ubuntu2 0 500 http://ch.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages I expected the system not to crash. It crashed...repeatedly...six time until now in last hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1349777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349781] [NEW] nvidia-331-uvm 331.89-0ubuntu2: nvidia-331-uvm kernel module failed to build
Public bug reported: during apt-get dist-upgrade, no further information, system still works after reboot ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.89-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.16.0-6-generic Date: Tue Jul 29 12:19:44 2014 InstallationDate: Installed on 2011-10-03 (1030 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) PackageVersion: 331.89-0ubuntu2 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.89-0ubuntu2: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-07-09 (19 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages 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/1349781 Title: nvidia-331-uvm 331.89-0ubuntu2: nvidia-331-uvm kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: during apt-get dist-upgrade, no further information, system still works after reboot ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.89-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.16.0-6-generic Date: Tue Jul 29 12:19:44 2014 InstallationDate: Installed on 2011-10-03 (1030 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) PackageVersion: 331.89-0ubuntu2 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.89-0ubuntu2: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-07-09 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1349781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349785] [NEW] Unable to open AMD Catalyst Control Center (Administrative Mode) on 14.04
Public bug reported: When trying to open the AMD Catalyst Control Center in Administrative mode by using the launcher found in dash, you will be ask to enter password for it, but it always shows su: authentication failure and exit. Steps: 1. Install 14.04 on a I+A system, boot to desktop 2. Try to open the Control Center in administrative mode by searching AMD in dash 3. Enter password Expected result: * AMD Catalyst Control Center opened Actual result: * The authentication windows closed with failure message This bug will be a blocker to 14.04 certificate for all I+A (or even A+A) GPU switchable systems, since user won't be able to switch between GPUs without using the command line commands. WORKAROUND: run sudo amdcccle in the terminal, you will be able to switch between GPUs. Note: similar bug reported before: bug 801952 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jul 29 06:41:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-30-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:217b] Subsystem: Hewlett-Packard Company Device [103c:217b] InstallationDate: Installed on 2014-06-12 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP 242 G2 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=da76c2a9-3ca6-4578-987e-97a95db7f346 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 217B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 34.0E dmi.chassis.asset.tag: 738DIP105Y dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.0B:bd10/08/2013:svnHewlett-Packard:pnHP242G2NotebookPC:pvr099C200620100:rvnHewlett-Packard:rn217B:rvrKBCVersion34.0E:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 242 G2 Notebook PC dmi.product.version: 099C200620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 29 06:40:07 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. 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] fglrx(0): XMM: Fail to unregister UVDFWVIRQ! (EE) fglrx(0): xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx ** Affects: hwe-next Importance: Undecided Status: New ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Assignee: Anthony Wong (anthonywong) Status: New ** Tags: 201309-14197 amd64 apport-bug blocks-hwcert compiz-0.9 taipei-lab trusty ubuntu ** Tags added: taipei-lab ** Also affects: hwe-next Importance: Undecided Status: New ** Description changed: When trying to open the AMD Catalyst Control Center in Administrative mode by using the launcher found in dash, you will be ask to enter
[Desktop-packages] [Bug 1349786] Re: Long delay while loading the greeter background
Adding greeter logs. Note the ~24s. delay around these lines: [+2,05s] DEBUG: Prompt user with 1 message(s) [+2,85s] DEBUG: settings-daemon.vala:75: Acquired org.gnome.SessionManager [+2,85s] DEBUG: settings-daemon.vala:102: Acquired org.gnome.ScreenSaver [+2,85s] DEBUG: settings-daemon.vala:159: All bus names acquired, starting unity-settings-daemon [+2,98s] DEBUG: unity-greeter.vala:235: starting system-ready sound [+26,87s] DEBUG: Connected to Application Indicator Service. [+26,93s] DEBUG: menubar.vala:537: Adding indicator object 0x997b3a4 at position 0 [+26,93s] DEBUG: menubar.vala:537: Adding indicator object 0x997b524 at position 1 [+26,95s] DEBUG: menubar.vala:537: Adding indicator object 0x99b98a4 at position 2 ** Attachment added: x-0-greeter.log https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1349786/+attachment/4165023/+files/x-0-greeter.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1349786 Title: Long delay while loading the greeter background Status in “unity-greeter” package in Ubuntu: New Bug description: There exists a long delay in the unity greeter between showing the user accounts (no background still loaded, dotted bg and some indicators missing) and been able to click to select the user account, or even input the password. Note that only when the background and the missing indicators show up, I'm able to do any action to start the session. Even if the main graphical controls are already on screen, clicking on them or inputting text, does nothing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 29 12:41:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-24 (4 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: unity-greeter UpgradeStatus: Upgraded to trusty on 2014-07-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1349786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349786] [NEW] Long delay while loading the greeter background
Public bug reported: There exists a long delay in the unity greeter between showing the user accounts (no background still loaded, dotted bg and some indicators missing) and been able to click to select the user account, or even input the password. Note that only when the background and the missing indicators show up, I'm able to do any action to start the session. Even if the main graphical controls are already on screen, clicking on them or inputting text, does nothing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 29 12:41:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-24 (4 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: unity-greeter UpgradeStatus: Upgraded to trusty on 2014-07-28 (0 days ago) ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1349786 Title: Long delay while loading the greeter background Status in “unity-greeter” package in Ubuntu: New Bug description: There exists a long delay in the unity greeter between showing the user accounts (no background still loaded, dotted bg and some indicators missing) and been able to click to select the user account, or even input the password. Note that only when the background and the missing indicators show up, I'm able to do any action to start the session. Even if the main graphical controls are already on screen, clicking on them or inputting text, does nothing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 29 12:41:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-24 (4 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: unity-greeter UpgradeStatus: Upgraded to trusty on 2014-07-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1349786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Hi Alberto, Thanks for compiling all this information. There's a couple of pieces missing though. This bug doesn't happen as far as I know with vanilla Gtk. It happens when the Unity Gtk extensions (dbusmenu and overlay scrollbar) are loaded. They are Gtk plugins and one or both of them open dbus connections as soon as they are loaded. They are loaded at Gtk init and that dbus connection becomes invalid after the fork, but Gtk tries to reuse it anyway. That causes it to hang. As a result of the above, this bug only happens if you have Unity installed alongside the affected software eg Xfce. So a good way to spot duplicates is to ask if the user also has Unity installed if they are not using it. Another thing is that those Gtk extensions should not be loaded at all outside of Unity. There is a bug about that: https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator- plugin/+bug/1307657 Finally, we don't have a metabug like this upstream at Xfce because bugzilla is not good at handling those types of bugs, but we are aware of the issue and there is a thread on the mailing list about it. https://mail.xfce.org/pipermail/xfce4-dev/2014-May/030715.html The conclusion we reached is that even though this is ultimately caused by Unity extensions, each application should be fixed to fork *before* it calls Gtk init, because you never know what extra plugins might get loaded and subsequently break. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: giflib (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a Status in “giflib” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349793] [NEW] bzr-gtk does not exist any more, don't reference it
Public bug reported: bzr-gtk does not exist any more, don't reference it. ** Affects: gedit-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1349793 Title: bzr-gtk does not exist any more, don't reference it Status in “gedit-plugins” package in Ubuntu: New Bug description: bzr-gtk does not exist any more, don't reference it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit-plugins/+bug/1349793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
** Summary changed: - Several XFCE applications appear irresponsible after communicating with a daemon + Several XFCE applications appear unresponsive after communicating with a daemon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183742] Re: Unable to install card themes
** Tags added: utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/1183742 Title: Unable to install card themes Status in One Hundred Papercuts: Triaged Status in “aisleriot” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE - Go to the View / Card style / Install card themes * BEHAVIOUR * - EXPECTED: To be able to install new card themes. - REAL: The error message The catalogue file «/usr/share/aisleriot/aisleriot.catalog» doesn't exist. is shown. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: aisleriot 1:3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 24 11:50:28 2013 InstallationDate: Installed on 2013-05-21 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1183742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261818] Re: Can't type user password in lightdm
*** This bug is a duplicate of bug 128 *** https://bugs.launchpad.net/bugs/128 I would confirm this is a security issue. With this problem when you are typing the focus remains on the desktop. I mean you can open applications, and type commands in a terminal or whatever. The only restricction for a hacker in a locked computer it that he can use only a keyboard and he gets no visual feedback (but that pretty much means that a hacker can do at will). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1261818 Title: Can't type user password in lightdm Status in “unity-greeter” package in Ubuntu: Triaged Bug description: If I want to log in to Ubuntu in lightdm I can't type a password in the box. This is if you boot and you want to log in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 17 17:08:41 2013 InstallationDate: Installed on 2013-12-16 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131216) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1261818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
** Also affects: xfce4-volumed-pulse (Ubuntu) Importance: Undecided Status: New ** No longer affects: xfce4-volumed-pulse (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1014234] Re: Firefox hogs all memory and swap
Happens almost every day, but only if comp is left idle for some time (an hour or two). Ubuntu 12.04, Firefox 28.0 started from a folder (not installed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1014234 Title: Firefox hogs all memory and swap Status in “firefox” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04 i386 on thinkpad x41 The installed firefox often hang and hog all memory and swap. Most times when a flasvideo is running, the whole computer stopped then. Sometimes it is possible to switch to a console, there after 10 minutes for login (its really that slow) TOP shows that firefox and a plugin-container process eat all ram and then all swap. After 15min or else a dialog jscript hanging appears on the desktop, when stopped the memory comes back. Firefox turns to normal operation until next hang. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 13.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 2118 F pulseaudio BuildID: 20120601173917 Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 26 Simple ctrls : 18 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 74HT26WW-1.01' Mixer name : 'ThinkPad EC 74HT26WW-1.01' Components : '' Controls : 2 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 14 Mono: Playback 6 [43%] [on] Channel: release Date: Sun Jun 17 10:40:55 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.103 metric 2 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) VLC Multimedia Plugin (compatible Totem 3.0.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) Windows Media Player Plug-in 10 (compatible; Totem) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=13.0/20120601173917 (In use) RelatedPackageVersions: totem-mozilla 3.0.1-0ubuntu21 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2006 dmi.bios.vendor: IBM dmi.bios.version: 74ET64WW (2.09 ) dmi.board.name: 2526Y8P dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: TRP 05055 dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr74ET64WW(2.09):bd12/14/2006:svnIBM:pn2526Y8P:pvrThinkPadX41:rvnIBM:rn2526Y8P:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2526Y8P dmi.product.version: ThinkPad X41 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1014234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
** No longer affects: xfce4-volumed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1185065] Re: autopilot should prevent screen from locking during test runs
** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: unity Status: New = Invalid -- 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/1185065 Title: autopilot should prevent screen from locking during test runs Status in Autopilot: Won't Fix Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: On the phone, autopilot tests get interrupted by the screen locking. Autopilot should prevent the screen from being locked while running tests. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1185065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243557]
Hi, sorry for barging in but I'm also hitting this on the same graphics card (NVS 4200M) on a Dell Latitude E6520 running Arch Linux. I'm trying to use PRIME for a VA-API + VDPAU setup and also for some games but as soon as I start I get this message in dmesg : kernel: nouveau E[ PFIFO][:01:00.0] INTR 0x0080 kernel: nouveau W[ PFIFO][:01:00.0] INTR 0x0100: 0x0005 I'm running the 3.15.6-1-ARCH kernel with the following packages: intel-dri-git 10.3.0_devel.64000-1 lib32-intel-dri-git 10.3.0_devel.64007-1 lib32-mesa-git 10.3.0_devel.64007-1 lib32-mesa-libgl-git 10.3.0_devel.64007-1 lib32-nouveau-dri-git 10.3.0_devel.64007-1 lib32-opencl-mesa-git 10.3.0_devel.64007-1 lib32-svga-dri-git 10.3.0_devel.64007-1 libdrm-git 2.4.54.19.gc0b34dc-1 mesa-git 10.3.0_devel.64000-1 mesa-libgl-git 10.3.0_devel.64000-1 nouveau-dri-git 10.3.0_devel.64000-1 opencl-mesa-git 10.3.0_devel.64000-1 xf86-video-nouveau-git 1.0.10.34.gedd1608-1 If I stop the application the uses the NVIDIA card as soon as I see the message, everything is OK. But if I continue, X freezes and the only way I can regain control is by a cold reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1243557 Title: 10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled status 0x0080 Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: With the Nouveau driver selected, my system freezes within a few minutes of boot if on battery, but only on heavy graphics load (flightgear in maximized window) if on mains. The mouse pointer still moves at first, but often freezes later; the keyboard LEDs do not react. Sounds already playing continue until finished, but don't repeat if set to (i.e. applications are frozen). Alt+SysRq works (provided bug 1244312 is fixed first). The kernel log nearly always contains the line nouveau ![ PFIFO][:01:00.0] unhandled status 0x0080 and sometimes other errors as well, while the Xorg log often contains EQ overflow errors; the full logs are attached. WORKAROUND: This does not occur with the nvidia-319 driver. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 23 08:19:06 2013 DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] InstallationDate: Installed on 2012-01-25 (636 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) [auto-install] kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use) MachineType: Dell Inc. Latitude E6520 MarkForUpload: True PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J4TFW dmi.board.vendor:
[Desktop-packages] [Bug 1243557]
Created attachment 103302 system log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1243557 Title: 10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled status 0x0080 Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: With the Nouveau driver selected, my system freezes within a few minutes of boot if on battery, but only on heavy graphics load (flightgear in maximized window) if on mains. The mouse pointer still moves at first, but often freezes later; the keyboard LEDs do not react. Sounds already playing continue until finished, but don't repeat if set to (i.e. applications are frozen). Alt+SysRq works (provided bug 1244312 is fixed first). The kernel log nearly always contains the line nouveau ![ PFIFO][:01:00.0] unhandled status 0x0080 and sometimes other errors as well, while the Xorg log often contains EQ overflow errors; the full logs are attached. WORKAROUND: This does not occur with the nvidia-319 driver. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 23 08:19:06 2013 DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] InstallationDate: Installed on 2012-01-25 (636 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) [auto-install] kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use) MachineType: Dell Inc. Latitude E6520 MarkForUpload: True PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct
[Desktop-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
*** This bug is a duplicate of bug 1163041 *** https://bugs.launchpad.net/bugs/1163041 ** Also affects: nautilus Importance: Undecided Status: New -- 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/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in Nautilus: New Status in Unity: Triaged Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1170647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243557]
Created attachment 103307 system log nouveau kernel linux-3.16 branch I've compiled the kernel on the linux-3.16 branch from http://cgit.freedesktop.org/nouveau/linux-2.6/ and X still freezes but now it recovers temporarily. After it I can close the program that caused the freeze and then I can't use the nouveau card anymore (glxgears would cause another temporary freeze followed by a black window). After a while, though, everything started to become unresponsive and I had to cold reboot to do anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1243557 Title: 10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, unhandled status 0x0080 Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: With the Nouveau driver selected, my system freezes within a few minutes of boot if on battery, but only on heavy graphics load (flightgear in maximized window) if on mains. The mouse pointer still moves at first, but often freezes later; the keyboard LEDs do not react. Sounds already playing continue until finished, but don't repeat if set to (i.e. applications are frozen). Alt+SysRq works (provided bug 1244312 is fixed first). The kernel log nearly always contains the line nouveau ![ PFIFO][:01:00.0] unhandled status 0x0080 and sometimes other errors as well, while the Xorg log often contains EQ overflow errors; the full logs are attached. WORKAROUND: This does not occur with the nvidia-319 driver. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 23 08:19:06 2013 DistUpgraded: 2013-10-21 23:03:05,341 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] InstallationDate: Installed on 2012-01-25 (636 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use) [auto-install] kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use) MachineType: Dell Inc. Latitude E6520 MarkForUpload: True PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b491a34a-6045-4ad4-a2b8-b9ca018c5d41 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx
[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
Should I create a new bug or do you think this is the same bug? Jul 29 13:46:22 imac kernel: [ 9194.185587] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:46:23 imac kernel: [ 9194.269541] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:46:23 imac kernel: [ 9194.594437] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:46:23 imac bluetoothd[791]: /org/bluez/791/hci0/dev_00_23_7F_B4_82_57/fd0: fd(24) ready Jul 29 13:46:28 imac bluetoothd[791]: Audio connection got disconnected Jul 29 13:46:28 imac kernel: [ 9199.993603] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:46:28 imac kernel: [ 9199.997737] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:46:41 imac kernel: [ 9213.037178] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:46:42 imac kernel: [ 9213.298044] Bluetooth: Unexpected continuation frame (len 0) Jul 29 13:47:21 imac kernel: [ 9252.736140] Bluetooth: hci0 SCO packet for unknown connection handle 6 Jul 29 13:47:21 imac kernel: [ 9252.736147] Bluetooth: hci0 SCO packet for unknown connection handle 6 Jul 29 13:47:21 imac kernel: [ 9252.736149] Bluetooth: hci0 SCO packet for unknown connection handle 6 Jul 29 13:46:59 imac bluetoothd[791]: Audio connection got disconnected Jul 29 13:49:26 imac bluetoothd[791]: Unable to get service record: Connection timed out (110) It is impossible to re-connect the headset after that. Anything I can do to provide more data? -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in “blueman” package in Ubuntu: Confirmed Status in “gnome-bluetooth” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: Invalid Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183742] Re: Unable to install card themes
I think that simply running the command is the best solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/1183742 Title: Unable to install card themes Status in One Hundred Papercuts: Triaged Status in “aisleriot” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE - Go to the View / Card style / Install card themes * BEHAVIOUR * - EXPECTED: To be able to install new card themes. - REAL: The error message The catalogue file «/usr/share/aisleriot/aisleriot.catalog» doesn't exist. is shown. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: aisleriot 1:3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 24 11:50:28 2013 InstallationDate: Installed on 2013-05-21 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1183742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
** Also affects: nux Importance: Undecided Status: New ** Also affects: nux (Ubuntu) Importance: Undecided Status: New -- 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/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12
[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
** Changed in: nvidia-graphics-drivers-319 (Ubuntu) Status: Confirmed = Triaged ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Confirmed = Triaged ** Changed in: nvidia-prime (Ubuntu) Status: Opinion = Triaged -- 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 “nvidia-graphics-drivers-319” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-prime” package in Ubuntu: Triaged 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/ubuntu/+source/nvidia-graphics-drivers-319/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
** No longer affects: unity (Ubuntu) ** No longer affects: freetype (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: Confirmed 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/ubuntu/+source/cairo/+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 1349785] Re: Unable to open AMD Catalyst Control Center (Administrative Mode) on 14.04
** Changed in: fglrx-installer (Ubuntu) Importance: Undecided = Medium -- 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/1349785 Title: Unable to open AMD Catalyst Control Center (Administrative Mode) on 14.04 Status in HWE Next Project: New Status in “fglrx-installer” package in Ubuntu: New Bug description: When trying to open the AMD Catalyst Control Center in Administrative mode by using the launcher found in dash, you will be ask to enter password for it, but it always shows su: authentication failure and exit. Steps: 1. Install 14.04 on a I+A system, boot to desktop 2. Try to open the Control Center in administrative mode by searching AMD in dash 3. Enter password Expected result: * AMD Catalyst Control Center opened Actual result: * The authentication windows closed with failure message This bug will be a blocker to 14.04 certificate for all I+A (or even A+A) GPU switchable systems, since user won't be able to switch between GPUs without using the command line commands. WORKAROUND: run sudo amdcccle in the terminal, you will be able to switch between GPUs. Note: similar bug reported before: bug 801952 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jul 29 06:41:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-30-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:217b] Subsystem: Hewlett-Packard Company Device [103c:217b] InstallationDate: Installed on 2014-06-12 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP 242 G2 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=da76c2a9-3ca6-4578-987e-97a95db7f346 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 217B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 34.0E dmi.chassis.asset.tag: 738DIP105Y dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.0B:bd10/08/2013:svnHewlett-Packard:pnHP242G2NotebookPC:pvr099C200620100:rvnHewlett-Packard:rn217B:rvrKBCVersion34.0E:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 242 G2 Notebook PC dmi.product.version: 099C200620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 29 06:40:07 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. 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] fglrx(0): XMM: Fail to unregister UVDFWVIRQ! (EE) fglrx(0): xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2
[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
dovercrash: I'm having that issue with chrome as well. $ sudo apt-cache policy google-chrome-stable google-chrome-stable: Installed: 36.0.1985.125-1 Same versions of unity and compiz that you have. Tried to reproduce it with other applications (gedit, gnome-terminal, firefox), but it does only happen in Google Chrome. My workaround is to click some of the icons on the taskbar (the battery icon, or the keyboard layout selector i.e). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1344990] Re: Volume control jumps back and forth
** Also affects: indicator-sound Importance: Undecided Status: New ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- 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/1344990 Title: Volume control jumps back and forth Status in Sound Menu: New Status in Unity: New Status in “indicator-sound” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen to music via Audacious 2) Open volume control from Unity's panel 3) Try to change the volume What happens: - The volume control doesn't follow mouse properly and jumps back and forth What should happen: - The obvious thing I believe this is regression as didn't notice anything weird in 13.10 with exactly same setup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jul 19 19:51:32 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1344990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
It severely affects packages beyond the one that causes the flaw. ** Changed in: cairo (Ubuntu) Importance: High = Critical ** Bug watch added: freedesktop.org Bugzilla #81874 https://bugs.freedesktop.org/show_bug.cgi?id=81874 ** Also affects: libcairo via https://bugs.freedesktop.org/show_bug.cgi?id=81874 Importance: Unknown Status: Unknown ** Changed in: cairo (Ubuntu) Status: Confirmed = Triaged ** Summary changed: - compiz crashed with SIGSEGV in af_latin_hints_compute_edges() + Huge multi-threading violations in cairo -- 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: Unknown 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 1291821] Re: Xubuntu 14.04 - keyboard-layout is only changed after resetting ibus
From the screenshot, it looks like that dialog is for setting the display language, not the keyboard layout. Also, the indicator is the IBus one, and since the display language is set to Dutch, it translates the German - Belgian keyboard layout as Duits - Belgian. So I don't think this is a bug tbh. ** Changed in: indicator-keyboard (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1291821 Title: Xubuntu 14.04 - keyboard-layout is only changed after resetting ibus Status in “indicator-keyboard” package in Ubuntu: Invalid Bug description: When one tries to alter the keyboard-layout, the indicator on top of the display keeps displaying the old layout. After resetting ibus (right click on the icon - reset), the new layout is shown. Also notice that the indicated layout for Belgian is wrong. The name Duits-Belgian is shown, which make no sense. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Thu Mar 13 09:02:34 2014 InstallationDate: Installed on 2014-03-12 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140312) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1291821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349579] Re: whoopsie-upload-all uses an incorrect assumption regarding what to upload
This bug was fixed in the package apport - 2.14.5-0ubuntu1 --- apport (2.14.5-0ubuntu1) utopic; urgency=medium * New upstream bug fix release. Changes since last snapshot: - apt/dpkg get_file_package(): If checking for uninstalled packages, don't use package information from the host system, but always look it up in the correct indexes. Otherwise this returns wrong results when files move to a different package between releases. Thanks Brian Murray! (LP: #1336062) - apt/dpkg install_packages(): Disable fetching apt translation indexes, to save some bandwidth. - whoopsie-upload-all: Ignore crash reports with incomplete core dumps instead of crashing on them. Thanks Brian Murray. (LP: #1329520) - etc/default/apport: Fix comment to use service instead of calling the init.d script directly. - whoopsie-upload-all: Collect hooks information to gather ApportVersion, NonfreeKernelModules, and SystemImageInfo. Do this before collecting package data to minimize hook run time. (LP: #1349579) - Adjust report.test_get_logind_session test to work with systemd = 205. - Fix report.test_check_interpreted_twistd test to skip instead of fail if twisted is not installed. * Drop automatix.py general hook. Automatix is long gone. * etc/apport/blacklist.d/apport: Drop long obsolete npviewer/npplayer entries. * Drop unnecessary python-gi build dependency. * Drop python-twisted-core build dependency. It's just used for one test, and will still run in autopkgtest. (Avoids current twisted uninstallability in main) -- Martin Pitt martin.p...@ubuntu.com Tue, 29 Jul 2014 12:26:23 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1349579 Title: whoopsie-upload-all uses an incorrect assumption regarding what to upload Status in “apport” package in Ubuntu: Fix Released Bug description: There is a comment in whoopsie-upload-all which states: errors.ubuntu.com does not collect any hook data anyway, so we do not need to bother collecting it. This is incorrect, while errors.ubuntu.com does not use any package hook data at least some of the Ubuntu general hook and the generic hook would be useful (their data would appear on a specific OOPS's page). whoopsie currently uploads the following fields which are not collected by whoopsie-upload-all: ApportVersion NonfreeKernelModules Additionally, while whoopsie does not currently upload SystemImageInfo (which would come from add_release_info in the Ubuntu general hook) it would be very useful to have but whoopsie-upload-all does not collect it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1349579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329520] Re: whoopsie-upload-all crashes while processing crash file
This bug was fixed in the package apport - 2.14.5-0ubuntu1 --- apport (2.14.5-0ubuntu1) utopic; urgency=medium * New upstream bug fix release. Changes since last snapshot: - apt/dpkg get_file_package(): If checking for uninstalled packages, don't use package information from the host system, but always look it up in the correct indexes. Otherwise this returns wrong results when files move to a different package between releases. Thanks Brian Murray! (LP: #1336062) - apt/dpkg install_packages(): Disable fetching apt translation indexes, to save some bandwidth. - whoopsie-upload-all: Ignore crash reports with incomplete core dumps instead of crashing on them. Thanks Brian Murray. (LP: #1329520) - etc/default/apport: Fix comment to use service instead of calling the init.d script directly. - whoopsie-upload-all: Collect hooks information to gather ApportVersion, NonfreeKernelModules, and SystemImageInfo. Do this before collecting package data to minimize hook run time. (LP: #1349579) - Adjust report.test_get_logind_session test to work with systemd = 205. - Fix report.test_check_interpreted_twistd test to skip instead of fail if twisted is not installed. * Drop automatix.py general hook. Automatix is long gone. * etc/apport/blacklist.d/apport: Drop long obsolete npviewer/npplayer entries. * Drop unnecessary python-gi build dependency. * Drop python-twisted-core build dependency. It's just used for one test, and will still run in autopkgtest. (Avoids current twisted uninstallability in main) -- Martin Pitt martin.p...@ubuntu.com Tue, 29 Jul 2014 12:26:23 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1329520 Title: whoopsie-upload-all crashes while processing crash file Status in “apport” package in Ubuntu: Fix Released Bug description: summary: whoopsie-upload-all crashes while processing crash file steps: 1. have a crash file on mako/n4 2. touch /var/lib/apport/autoreport 3. run ubuntu-bug channel: ubuntu-touch/utopic-proposed build_number: 79 version_detail: ubuntu=20140612,device=20140530,version=79 apport: Installed: 2.14.3-0ubuntu1 Candidate: 2.14.3-0ubuntu1 Collecting info for /var/crash/_usr_bin_unity8.32011.crash... Traceback (most recent call last): File /usr/share/apport/whoopsie-upload-all, line 137, in module stamps = collect_info() File /usr/share/apport/whoopsie-upload-all, line 88, in collect_info res = process_report(r) File /usr/share/apport/whoopsie-upload-all, line 55, in process_report r.add_gdb_info() File /usr/lib/python3/dist-packages/apport/report.py, line 677, in add_gdb_info gdb_cmd = self.gdb_command(rootdir) File /usr/lib/python3/dist-packages/apport/report.py, line 1516, in gdb_command self['CoreDump'].write(f) File /usr/lib/python3/dist-packages/problem_report.py, line 75, in write block = gz.read(1048576) File /usr/lib/python3.4/gzip.py, line 365, in read if not self._read(readsize): File /usr/lib/python3.4/gzip.py, line 449, in _read self._read_eof() File /usr/lib/python3.4/gzip.py, line 482, in _read_eof crc32, isize = struct.unpack(II, self._read_exact(8)) File /usr/lib/python3.4/gzip.py, line 286, in _read_exact raise EOFError(Compressed file ended before the EOFError: Compressed file ended before the end-of-stream marker was reached Collecting info for /var/crash/_usr_bin_unity8.32011.crash... Traceback (most recent call last): File /usr/share/apport/whoopsie-upload-all, line 137, in module stamps = collect_info() File /usr/share/apport/whoopsie-upload-all, line 88, in collect_info res = process_report(r) File /usr/share/apport/whoopsie-upload-all, line 55, in process_report r.add_gdb_info() File /usr/lib/python3/dist-packages/apport/report.py, line 677, in add_gdb_info gdb_cmd = self.gdb_command(rootdir) File /usr/lib/python3/dist-packages/apport/report.py, line 1516, in gdb_command self['CoreDump'].write(f) File /usr/lib/python3/dist-packages/problem_report.py, line 75, in write block = gz.read(1048576) File /usr/lib/python3.4/gzip.py, line 365, in read if not self._read(readsize): File /usr/lib/python3.4/gzip.py, line 449, in _read self._read_eof() File /usr/lib/python3.4/gzip.py, line 482, in _read_eof crc32, isize = struct.unpack(II, self._read_exact(8)) File /usr/lib/python3.4/gzip.py, line 286, in _read_exact raise EOFError(Compressed file ended before the EOFError: Compressed file ended before the end-of-stream marker was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1329520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1347565] Re: apport recommends gdb
This bug was fixed in the package apport - 2.14.5-0ubuntu1 --- apport (2.14.5-0ubuntu1) utopic; urgency=medium * New upstream bug fix release. Changes since last snapshot: - apt/dpkg get_file_package(): If checking for uninstalled packages, don't use package information from the host system, but always look it up in the correct indexes. Otherwise this returns wrong results when files move to a different package between releases. Thanks Brian Murray! (LP: #1336062) - apt/dpkg install_packages(): Disable fetching apt translation indexes, to save some bandwidth. - whoopsie-upload-all: Ignore crash reports with incomplete core dumps instead of crashing on them. Thanks Brian Murray. (LP: #1329520) - etc/default/apport: Fix comment to use service instead of calling the init.d script directly. - whoopsie-upload-all: Collect hooks information to gather ApportVersion, NonfreeKernelModules, and SystemImageInfo. Do this before collecting package data to minimize hook run time. (LP: #1349579) - Adjust report.test_get_logind_session test to work with systemd = 205. - Fix report.test_check_interpreted_twistd test to skip instead of fail if twisted is not installed. * Drop automatix.py general hook. Automatix is long gone. * etc/apport/blacklist.d/apport: Drop long obsolete npviewer/npplayer entries. * Drop unnecessary python-gi build dependency. * Drop python-twisted-core build dependency. It's just used for one test, and will still run in autopkgtest. (Avoids current twisted uninstallability in main) -- Martin Pitt martin.p...@ubuntu.com Tue, 29 Jul 2014 12:26:23 +0200 ** Changed in: apport (Ubuntu Utopic) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1347565 Title: apport recommends gdb Status in “apport” package in Ubuntu: Fix Released Status in “apport” source package in Trusty: Fix Committed Status in “apport” source package in Utopic: Fix Released Bug description: apport-kde (and apport-gtk) recommends gdb | gdb-minimal This brings in gdb and with it libc6-dbg onto the images which are now oversized (looking at trusty 12.04.1 candidates today). I'd like to switch this so gdb-minimal is recommended first for apport-kde. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1347565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1336062] Re: apport-retrace uses system package lists which may return a different source package for a binary
This bug was fixed in the package apport - 2.14.5-0ubuntu1 --- apport (2.14.5-0ubuntu1) utopic; urgency=medium * New upstream bug fix release. Changes since last snapshot: - apt/dpkg get_file_package(): If checking for uninstalled packages, don't use package information from the host system, but always look it up in the correct indexes. Otherwise this returns wrong results when files move to a different package between releases. Thanks Brian Murray! (LP: #1336062) - apt/dpkg install_packages(): Disable fetching apt translation indexes, to save some bandwidth. - whoopsie-upload-all: Ignore crash reports with incomplete core dumps instead of crashing on them. Thanks Brian Murray. (LP: #1329520) - etc/default/apport: Fix comment to use service instead of calling the init.d script directly. - whoopsie-upload-all: Collect hooks information to gather ApportVersion, NonfreeKernelModules, and SystemImageInfo. Do this before collecting package data to minimize hook run time. (LP: #1349579) - Adjust report.test_get_logind_session test to work with systemd = 205. - Fix report.test_check_interpreted_twistd test to skip instead of fail if twisted is not installed. * Drop automatix.py general hook. Automatix is long gone. * etc/apport/blacklist.d/apport: Drop long obsolete npviewer/npplayer entries. * Drop unnecessary python-gi build dependency. * Drop python-twisted-core build dependency. It's just used for one test, and will still run in autopkgtest. (Avoids current twisted uninstallability in main) -- Martin Pitt martin.p...@ubuntu.com Tue, 29 Jul 2014 12:26:23 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1336062 Title: apport-retrace uses system package lists which may return a different source package for a binary Status in “apport” package in Ubuntu: Fix Released Bug description: I was trying to retrace a whoopsie crash from Utopic and ran into the following error: ubuntu@juju-openstack-machine-11:~$ sudo PYTHONPATH=$PYTHONPATH:/srv/daisy.staging.ubuntu.com/production/apport python3 /srv/daisy.staging.ubuntu.com/production/apport/bin/apport-retrace /home/ubuntu/_usr_bin_whoopsie.109.crash -c -S /srv/daisy.staging.ubuntu.com/production/daisy/retracer/config --sandbox-dir /srv/daisy.staging.ubuntu.com/production/cache/Ubuntu\ 14.10/cache-DhmXbj/sandbox -C /srv/daisy.staging.ubuntu.com/pro duction/cache/Ubuntu\ 14.10/cache-DhmXbj/cache -o /tmp/_usr_bin_whoopsie.109.crash.updated WARNING: /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0.4101.0 is needed, but cannot be mapped to a package WARNING: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0.4101.0 is needed, but cannot be mapped to a package WARNING: /usr/lib/arm-linux-gnueabihf/libgmodule-2.0.so.0.4101.0 is needed, but cannot be mapped to a package WARNING: /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4101.0 is needed, but cannot be mapped to a package WARNING: /usr/lib/arm-linux-gnueabihf/libtasn1.so.6.2.3 is needed, but cannot be mapped to a package Installing extra package whoopsie to get ExecutablePath E: Ignore unavailable version '0.2.33' of package 'whoopsie' E: Unable to find a source package for whoopsie-daisy I'm guessing its because the whoopsie package changed names from precise to trusty and apport does a source package look up in the host (not sandbox) environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1336062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1348176] Re: New upstream microreleases 9.3.5, 9.1.14, 8.4.22
I just uploaded the two missing ones for keeping upgrades working: postgresql-8.4_8.4.22 0ubuntu0.12.04 (precise) and postgresql-9.1 9.1.14-0ubuntu0.14.04 (trusty). Unfortunately I can't resurrect the bug tasks for those. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1348176 Title: New upstream microreleases 9.3.5, 9.1.14, 8.4.22 Status in “postgresql-8.4” package in Ubuntu: Invalid Status in “postgresql-9.1” package in Ubuntu: Invalid Status in “postgresql-9.3” package in Ubuntu: Fix Released Status in “postgresql-8.4” source package in Lucid: In Progress Status in “postgresql-9.1” source package in Precise: In Progress Status in “postgresql-9.3” source package in Trusty: In Progress Status in “postgresql-9.3” source package in Utopic: Fix Released Bug description: New postgresql bug fix releases today: http://www.postgresql.org/about/news/1534/ As per the standing MRE these should go into stables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1348176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308354] Re: Password revealed when pasted with Ctrl-V
** Changed in: software-center Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1308354 Title: Password revealed when pasted with Ctrl-V Status in Ubuntu Software Center: Fix Released Status in “software-center” package in Ubuntu: Fix Released Status in “software-center” source package in Trusty: Fix Released Bug description: Xubuntu 14.04 amd64 upgraded from 13.10 software-center 13.10-0ubuntu4 1) Open Software Center 2) Click down-arrow beside All Software button 3) Click For Purchase 4) Choose an item fx Fragment 5) Click Buy... button 6) Ubuntu single signon login screen appears 7) Copy password from password manager 8) Focus password field 9) Press Ctrl-V 10) Instead of filling the password field, new screen appears (see attached screenshot) 11) Password is revealed on screen and also run through some fuzzy search service (probably local, but who knows) To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1308354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199571] Re: Huge multi-threading violations in cairo
Launchpad has imported 1 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=81874. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-07-29T12:20:17+00:00 Alberto Salvia Novella wrote: I looked at the implementation of cairo-ft-font.c and it seems that there are huge multi-threading violations in cairo. The reason is that FreeType API documentation clearly states: In multi-threaded applications, make sure that the same FT_Library object or any of its children doesn't get accessed in parallel. Cairo initializes FT_Library for its font map and there's a lock for that, however it's only used for font map manipulations, the actual FT_ library calls are completely unprotected with that lock, although they should be! What adds to the injury is that cairo-ft-font.c even has this comment on one of its functions: You must be careful when using this function in a library or in a threaded application, because freetype's design makes it unsafe to call freetype functions simultaneously from multiple threads, (even if using distinct FT_Face objects) Reply at: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1199571/comments/15 ** Changed in: libcairo Status: Unknown = Confirmed ** Changed in: libcairo Importance: Unknown = Critical -- 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 1349465] Re: Please sync libxml2 (main) 2.9.1+dfsg1-4 from Debian testing (main)
This bug was fixed in the package libxml2 - 2.9.1+dfsg1-4 Sponsored for Aron Xu (happyaron) --- libxml2 (2.9.1+dfsg1-4) unstable; urgency=low [ Christian Svensson ] * Do not build-depend on readline (Closes: #742350) [ Daniel Schepler ] * Patch to bootstrap without python (Closes: #738080) [ Helmut Grohne ] * Drop unneeded B-D on perl and binutils (Closes: #753005) [ Adam Conrad ] * Actually run dh_autoreconf, which the old/new mixed rules file misses. [ Matthias Klose ] * Add patch to fix python multiarch issue * Allow the package to cross-build by tweaking B-Ds on python * Set PYTHON_LIBS for cross builds [ Aron Xu ] * Use correct $CC * Configure udeb without python * New round of cherry-picking upstream fixes - Includes fixes for CVE-2014-0191 (Closes: #747309). * Call prename with -vf * Require python-all-dev (= 2.7.5-5~) * Bump std-ver: 3.9.4 - 3.9.5, no change -- Aron Xu a...@debian.org Wed, 09 Jul 2014 05:40:15 +0800 ** Changed in: libxml2 (Ubuntu) Status: New = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-0191 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1349465 Title: Please sync libxml2 (main) 2.9.1+dfsg1-4 from Debian testing (main) Status in “libxml2” package in Ubuntu: Fix Released Bug description: Please sync libxml2 (main) 2.9.1+dfsg1-4 from Debian testing (main) Why Ubuntu delta can be dropped: all changes are merged into Debian. libxml2 (2.9.1+dfsg1-4) unstable; urgency=low [ Christian Svensson ] * Do not build-depend on readline (Closes: #742350) [ Daniel Schepler ] * Patch to bootstrap without python (Closes: #738080) [ Helmut Grohne ] * Drop unneeded B-D on perl and binutils (Closes: #753005) [ Adam Conrad ] * Actually run dh_autoreconf, which the old/new mixed rules file misses. [ Matthias Klose ] * Add patch to fix python multiarch issue * Allow the package to cross-build by tweaking B-Ds on python * Set PYTHON_LIBS for cross builds [ Aron Xu ] * Use correct $CC * Configure udeb without python * New round of cherry-picking upstream fixes - Includes fixes for CVE-2014-0191 (Closes: #747309). * Call prename with -vf * Require python-all-dev (= 2.7.5-5~) * Bump std-ver: 3.9.4 - 3.9.5, no change -- Aron Xu a...@debian.org Wed, 09 Jul 2014 05:40:15 +0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1349465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349858] [NEW] Cannot override certain key combinations involving Super
Public bug reported: When defining keyboard shortcuts in System Settings - Keyboard - Shortcuts, several combinations are never honoured. These include setting: - Launchers - Launch calculator to Super+C (launches search photos instead) - Launchers - Launch email client to Super+M (launches search music instead) - Launchers - Launch terminal to Super+T (launches Rubbish bin instead) - Launchers - Launch web browser to Super+F (launches search files folders instead) - Launchers - Search to Super+S (launches Workspace Switcher) - Navigation - Switch to workspace # to Super+# (launches the corresponding launcher icon instead) It is non-obvious that this shortcut change has not been honoured, and there is no list of keys to which this applies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jul 30 00:01:48 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1349858 Title: Cannot override certain key combinations involving Super Status in “unity” package in Ubuntu: New Bug description: When defining keyboard shortcuts in System Settings - Keyboard - Shortcuts, several combinations are never honoured. These include setting: - Launchers - Launch calculator to Super+C (launches search photos instead) - Launchers - Launch email client to Super+M (launches search music instead) - Launchers - Launch terminal to Super+T (launches Rubbish bin instead) - Launchers - Launch web browser to Super+F (launches search files folders instead) - Launchers - Search to Super+S (launches Workspace Switcher) - Navigation - Switch to workspace # to Super+# (launches the corresponding launcher icon instead) It is non-obvious that this shortcut change has not been honoured, and there is no list of keys to which this applies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Jul 30 00:01:48 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349761] Re: [Wishlist] Opening Launcher popup menu on mouseover after a couple of seconds
** Changed in: unity Status: New = Opinion ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = Opinion -- 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/1349761 Title: [Wishlist] Opening Launcher popup menu on mouseover after a couple of seconds Status in Unity: Opinion Status in “unity” package in Ubuntu: Opinion Bug description: Currently Unity Launcher icons elegantly display the Title on mouseover, and you need to right click to access a popup menu including any Shortcuts available, which is also very useful. However, I think it would be much more efficient and useful if this popup menu could also become visible when the mouseover action persists for a couple of seconds (making the right click action redundant), which shouldn't be too costly I guess. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349869] [NEW] [S400CA, Realtek ALC269VB, Speaker, Internal] No sound at all
Public bug reported: Since I isntalled ubuntu on Asus Vivobook s400, no sound at all! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: london 1657 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 29 15:39:09 2014 InstallationDate: Installed on 2014-07-27 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: london 1657 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [S400CA, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S400CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S400CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.208:bd02/05/2013:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S400CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1349869 Title: [S400CA, Realtek ALC269VB, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Since I isntalled ubuntu on Asus Vivobook s400, no sound at all! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: london 1657 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 29 15:39:09 2014 InstallationDate: Installed on 2014-07-27 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: london 1657 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [S400CA, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S400CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S400CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.208:bd02/05/2013:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S400CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1349869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247736] Please test proposed package
Hello Jorma, or anyone else affected, Accepted nvidia-graphics-drivers-331-updates into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/331.38-0ubuntu7.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1247736 Title: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd Status in “nvidia-cuda-toolkit” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-340” package in Ubuntu: Confirmed Status in “ocl-icd” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” source package in Trusty: Invalid Status in “nvidia-graphics-drivers-304” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Fix Committed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Fix Committed Status in “nvidia-graphics-drivers-340” source package in Trusty: Invalid Status in “ocl-icd” source package in Trusty: Invalid Bug description: [Impact] Users with proprietary Nvidia graphics drivers are unable to co-install CUDA and OpenCL applications. The patches in comment #21 and #22 backport the fix from Utopic and resolve this issue by allowing nvidia-opencl-icd-* (Nvidia's OpenCL ICD) to be co-installed with ocl-icd-libopencl1 (the generic OpenCL ICD loader). [Test Case] sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install python-pycuda sudo apt-get install python-pyopencl This will result in the error message below. The following packages have unmet dependencies: python-pyopencl : Depends: libopencl-1.1-1 Depends: libopencl-1.2-1 Depends: ocl-icd-libopencl1 but it is not going to be installed E: Unable to correct problems, you have held broken packages. A similar conflict exists between wine and nvidia-cuda-toolkit. sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install wine sudo apt-get install nvidia-cuda-toolkit This will result in a warning similar to the one below. The following extra packages will be installed: nvidia-libopencl1-331 nvidia-opencl-dev The following packages will be REMOVED: ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64 wine1.6-i386:i386 The following NEW packages will be installed: nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev [Regression Potential] This fix only affects the relationships between packages and should not introduce any new bugs. However, since packages that were previously difficult to install together will now be co-installable, new bugs in those packages may be exposed. [Other Info] It is possible to work around this issue by first installing the CUDA application, then installing ocl-icd-opencl-dev, and finally installing the OpenCL application. (See comment #7) --- Don't know. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: ocl-icd-libopencl1 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 14:03:41 2013 DpkgTerminalLog: Unpacking ocl-icd-libopencl1:amd64 (from .../ocl-icd-libopencl1_2.0.2-1ubuntu1_amd64.deb) ... dpkg: error processing
[Desktop-packages] [Bug 1247736] Re: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd
Hello Jorma, or anyone else affected, Accepted nvidia-graphics-drivers-331 into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-331/331.38-0ubuntu7.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty) Status: Confirmed = Fix Committed ** Tags added: verification-needed ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1247736 Title: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd Status in “nvidia-cuda-toolkit” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-340” package in Ubuntu: Confirmed Status in “ocl-icd” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” source package in Trusty: Invalid Status in “nvidia-graphics-drivers-304” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Fix Committed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Fix Committed Status in “nvidia-graphics-drivers-340” source package in Trusty: Invalid Status in “ocl-icd” source package in Trusty: Invalid Bug description: [Impact] Users with proprietary Nvidia graphics drivers are unable to co-install CUDA and OpenCL applications. The patches in comment #21 and #22 backport the fix from Utopic and resolve this issue by allowing nvidia-opencl-icd-* (Nvidia's OpenCL ICD) to be co-installed with ocl-icd-libopencl1 (the generic OpenCL ICD loader). [Test Case] sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install python-pycuda sudo apt-get install python-pyopencl This will result in the error message below. The following packages have unmet dependencies: python-pyopencl : Depends: libopencl-1.1-1 Depends: libopencl-1.2-1 Depends: ocl-icd-libopencl1 but it is not going to be installed E: Unable to correct problems, you have held broken packages. A similar conflict exists between wine and nvidia-cuda-toolkit. sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install wine sudo apt-get install nvidia-cuda-toolkit This will result in a warning similar to the one below. The following extra packages will be installed: nvidia-libopencl1-331 nvidia-opencl-dev The following packages will be REMOVED: ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64 wine1.6-i386:i386 The following NEW packages will be installed: nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev [Regression Potential] This fix only affects the relationships between packages and should not introduce any new bugs. However, since packages that were previously difficult to install together will now be co-installable, new bugs in those packages may be exposed. [Other Info] It is possible to work around this issue by first installing the CUDA application, then installing ocl-icd-opencl-dev, and finally installing the OpenCL application. (See comment #7) --- Don't know. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: ocl-icd-libopencl1 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion:
[Desktop-packages] [Bug 1349866] Re: display blank after resume (consistent)
FWIW, this is the output of radeontool (sudo radeontool light on had no effect at all): $ sudo radeontool regs RADEON_DAC_CNTL RADEON_DAC_EXT_CNTL RADEON_DAC_MACRO_CNTL RADEON_DAC_CNTL2 RADEON_TV_DAC_CNTL c100a080 RADEON_DISP_OUTPUT_CNTL RADEON_CONFIG_MEMSIZE RADEON_AUX_SC_CNTL RADEON_CRTC_EXT_CNTL RADEON_CRTC_GEN_CNTL RADEON_CRTC2_GEN_CNTL RADEON_DEVICE_ID RADEON_DISP_MISC_CNTL 0010 RADEON_GPIO_MONID RADEON_GPIO_MONIDB RADEON_GPIO_CRT2_DDC RADEON_GPIO_DVI_DDC RADEON_GPIO_VGA_DDC RADEON_LVDS_GEN_CNTL RADEON_LVDS_PLL_CNTL RADEON_FP_GEN_CNTL RADEON_FP2_GEN_CNTL RADEON_PPLL_CNTL RADEON_PPLL_REF_DIV RADEON_PPLL_DIV_3 RADEON_PIXCLKS_CNTL RADEON_P2PLL_CNTL RADEON_P2PLL_REF_DIV RADEON_P2PLL_DIV_0 RADEON_VCLK_ECP_CNTL RADEON_MEM_TIMING_CNTL RADEON_TMDS_PLL_CNTL RADEON_TMDS_TRANSMITTER_CNTL RADEON_CRTC_MORE_CNTL RADEON_FP_H_SYNC_STRT_WID RADEON_FP_V_SYNC_STRT_WID RADEON_FP_CRTC_H_TOTAL_DISP RADEON_FP_CRTC_V_TOTAL_DISP RADEON_FP_HORZ_STRETCH RADEON_FP_VERT_STRETCH RADEON_FP_HORZ_VERT_ACTIVE RADEON_CRTC_H_TOTAL_DISP0001f478 RADEON_CRTC_H_SYNC_STRT_WID 040f0001 RADEON_CRTC_V_TOTAL_DISP RADEON_CRTC_V_SYNC_STRT_WID RADEON_CRTC2_H_TOTAL_DISP 000f RADEON_CRTC2_H_SYNC_STRT_WID3f3f RADEON_CRTC2_V_TOTAL_DISP RADEON_CRTC2_V_SYNC_STRT_WID0002 -- 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/1349866 Title: display blank after resume (consistent) Status in “xorg” package in Ubuntu: New Bug description: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-06-27 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8f659b6c-ad5b-49ef-8f46-052d943c2cb5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.26:bd10/29/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 1349866] [NEW] display blank after resume (consistent)
Public bug reported: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7420G] [1002:9992] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:194e] InstallationDate: Installed on 2014-06-27 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 455 G1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8f659b6c-ad5b-49ef-8f46-052d943c2cb5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 194E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.26:bd10/29/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2018CD200:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 455 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jul 29 16:24:26 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1349866 Title: display blank after resume (consistent) Status in “xorg” package in Ubuntu: New Bug description: With the hardware as shown in automatically attached files (HP ProBook 455), display never recovers from resume, although the computer works fine otherwise (it can be connected to over ssh, in particular). I disabled the discrete GPU BIOS (that is the current stand) but the problem remains. Contrary to #1010683, where some people were helped by using pm-suspend --quirk-test --quirk-s3-mode, this problem is exhibited without discrete graphics (thus ruling out problems with vgaswitcheroo). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 29 16:32:42 2014 DistUpgraded: Fresh install
[Desktop-packages] [Bug 1349879] [NEW] powering off an usb3 device causes kernel to resume immediately after suspend
Public bug reported: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1349879 Title: powering off an usb3 device causes kernel to resume immediately after suspend Status in “udisks2” package in Ubuntu: New Bug description: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1349879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247736] Re: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd
** Branch linked: lp:ubuntu/trusty-proposed/nvidia-graphics- drivers-331-updates ** Branch linked: lp:ubuntu/trusty-proposed/nvidia-graphics-drivers-331 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1247736 Title: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd Status in “nvidia-cuda-toolkit” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-340” package in Ubuntu: Confirmed Status in “ocl-icd” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” source package in Trusty: Invalid Status in “nvidia-graphics-drivers-304” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Fix Committed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Fix Committed Status in “nvidia-graphics-drivers-340” source package in Trusty: Invalid Status in “ocl-icd” source package in Trusty: Invalid Bug description: [Impact] Users with proprietary Nvidia graphics drivers are unable to co-install CUDA and OpenCL applications. The patches in comment #21 and #22 backport the fix from Utopic and resolve this issue by allowing nvidia-opencl-icd-* (Nvidia's OpenCL ICD) to be co-installed with ocl-icd-libopencl1 (the generic OpenCL ICD loader). [Test Case] sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install python-pycuda sudo apt-get install python-pyopencl This will result in the error message below. The following packages have unmet dependencies: python-pyopencl : Depends: libopencl-1.1-1 Depends: libopencl-1.2-1 Depends: ocl-icd-libopencl1 but it is not going to be installed E: Unable to correct problems, you have held broken packages. A similar conflict exists between wine and nvidia-cuda-toolkit. sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install wine sudo apt-get install nvidia-cuda-toolkit This will result in a warning similar to the one below. The following extra packages will be installed: nvidia-libopencl1-331 nvidia-opencl-dev The following packages will be REMOVED: ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64 wine1.6-i386:i386 The following NEW packages will be installed: nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev [Regression Potential] This fix only affects the relationships between packages and should not introduce any new bugs. However, since packages that were previously difficult to install together will now be co-installable, new bugs in those packages may be exposed. [Other Info] It is possible to work around this issue by first installing the CUDA application, then installing ocl-icd-opencl-dev, and finally installing the OpenCL application. (See comment #7) --- Don't know. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: ocl-icd-libopencl1 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 14:03:41 2013 DpkgTerminalLog: Unpacking ocl-icd-libopencl1:amd64 (from .../ocl-icd-libopencl1_2.0.2-1ubuntu1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/ocl-icd-libopencl1_2.0.2-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 DuplicateSignature: package:ocl-icd-libopencl1:(not installed):trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64 5.0.35-7ubuntu1 InstallationDate: Installed on 2013-10-28 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: ocl-icd Title: package ocl-icd-libopencl1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package nvidia-opencl-dev:amd64
[Desktop-packages] [Bug 1334998] Re: When using Super+L keys autohide not working properly
*** This bug is a duplicate of bug 1320438 *** https://bugs.launchpad.net/bugs/1320438 ** This bug has been marked a duplicate of bug 1320438 Unity launcher auto hide fails on screen unlock using Super+L -- 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/1334998 Title: When using Super+L keys autohide not working properly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When using the super+l keys to lock the screen, the unity panel gets stuck. This happens whenever the user first clicks on the super key and then the L key. Clicking simutaniously works as expected. The issue was also reported on Ask Ubuntu: http://askubuntu.com/questions/459585/launcher-auto-hide-not-working- ubuntu-14-04/469732?noredirect=1#comment652314_469732 There is a workaround (the user has to double tap the super key) however, this is one of those papercuts that gets rather annoying over time. I would expect the system to be a little more tolerant in terms of the sequnce of keys pressed. If I first click on the super key and then the L key, the panel will not be locked when I log back in. === Description: Ubuntu 14.04 LTS Release: 14.04 === unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages === Screenshot: http://i.imgur.com/e3AePQ8.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 27 09:23:52 2014 InstallationDate: Installed on 2014-03-16 (103 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1334998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1328537] Re: Can't find where to shut off showing the user's wallpaper in Unity locker
com.canonical.unity.unity-greeter-draw-user-backgrounds is the correct option. If it does not work please reopen the bug. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/1328537 Title: Can't find where to shut off showing the user's wallpaper in Unity locker Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Sorry I could not select the unity package to report this. When the session is locked in Trusty Tahr 14.04 the background picture is the user wallpaper instead of a generic/common/local public picture. This is the same whatever the way the lockscreen is triggered, Super+L or elapsed inactivity. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1328537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349078]
It was indeed that easy to confirm. Setting to: New - confirmed Major - essentially loss of data (or addition of data that is unwanted) High - default seems fine. Would be nice to know if this one is a regression - unfortunately my main machine with older versions installed is down until at least tomorrow. If it's a regression please put what version it works on, add regression to keyword, and bibisectRequest to whiteboard. Thanks! -- 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/1349078 Title: [upstream] Impress FORMATTING: Slide master fields are duplicated when saving to .fodp Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: Once converted a presentation to flat ODP format all master fields(page number...etc.) are duplicated and not removable after editing file and reload. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1349078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349078]
Created attachment 103536 Comparison of the slide master after converting -- 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/1349078 Title: [upstream] Impress FORMATTING: Slide master fields are duplicated when saving to .fodp Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: Once converted a presentation to flat ODP format all master fields(page number...etc.) are duplicated and not removable after editing file and reload. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1349078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349078]
Created attachment 103535 Vdragon's bug reproduce document(after converted to fodp using LibO4.2.4.2 -- 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/1349078 Title: [upstream] Impress FORMATTING: Slide master fields are duplicated when saving to .fodp Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: Once converted a presentation to flat ODP format all master fields(page number...etc.) are duplicated and not removable after editing file and reload. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1349078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349078]
Setting to UNCONFIRMED. Note: REOPENED is for a bug that a developer says they fixed (thus the bug is put into RESOLVED - FIXED) but a user can still see the problem on a version that should be fixed. For bugs never confirmed by a neutral third party the correct status is UNCONFIRMED. Thanks! -- 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/1349078 Title: [upstream] Impress FORMATTING: Slide master fields are duplicated when saving to .fodp Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: Once converted a presentation to flat ODP format all master fields(page number...etc.) are duplicated and not removable after editing file and reload. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1349078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349078]
Joel, I just confirmed the bug with independent configurations in version 4.1.5.3 under Windows and 4.2.4.2 in Linux. It takes less than a minute to do so. Just open the first simple odp, save it as fodp, reload it and check the footer. -- 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/1349078 Title: [upstream] Impress FORMATTING: Slide master fields are duplicated when saving to .fodp Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: Once converted a presentation to flat ODP format all master fields(page number...etc.) are duplicated and not removable after editing file and reload. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1349078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292467] Re: Dual screen greeter can break 3D acceleration
Hi Andy, You changed the status of this bug from New to Fix Released on April 17. Are you referring to the workaround you documented in the description, or was a fix for this bug actually implemented? I do not see this bug (1292467) listed in the change summary for Ubuntu 14.04.1 at https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/ChangeSummary/14.04.1. Thanks, Pat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Dual screen greeter can break 3D acceleration Status in Release Notes for Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). WORKAROUND: * Plug in external monitor after login (1) * Boot with video=LVDS-1:d (2) (1) Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. (2) This will completely disable the internal screen for that boot. It cannot be enabled through the settings dialogue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
@ Alistair, I don't explicitly have Unity installed (I'm on Xubuntu 14.04), but a search via synaptic shows that I do have these Unity-related packages installed, possibly as dependencies for some piece of software I was compiling: gir1.2-unity-5.0 7.1.4+14.04.20140210-0ubuntu1 libunity-protocol-private0 7.1.4+14.04.20140210-0ubuntu1 libunity-scopes-json-def-desktop 7.1.4+14.04.20140210-0ubuntu1 libunity9 7.1.4+14.04.20140210-0ubuntu1 unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1 unity-gtk2-module 0.0.0+14.04.20140403-0ubuntu1 unity-gtk3-module 0.0.0+14.04.20140403-0ubuntu1 Also, I don't have any overlay-scrollbar packages installed, but I do have these dbusmenu packages installed: gir1.2-dbusmenu-glib-0.4 12.10.3+14.04.20140612-0ubuntu1 libdbusmenu-qt-dev 0.9.3+14.04.20140314-0ubuntu1 libdbusmenu-qt2 0.9.3+14.04.20140314-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
ode 0x08 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name=Headphone Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name=VT1802 Analog, type=Audio, device=0 Device: name=VT1802 Alt Analog, type=Audio, device=2 the two devices cannot share headphone audio output when multistreaming playback, alt analog device can play another audio stream for the headphone while analog device play audio stream on line out did you disable independent headphone since it is a bug in hda_generic to allow independent headphone when HP nid was put in multiout.dac ? HP should be put into multiout.hp -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
http://www.intel.com/support/motherboards/desktop/sb/CS-034206.htm for desktop, those rear panel line out jacks output support multi channel playback and the front panel headphone can support multi streaming on some hda codec -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349009] Re: Renamed program name locally and Software Center Apps Directory replaced original name with local one
sam, thanks for the report. Launchpad shows that the executable was already called pdfsam in 12.04, and as far back as 10.04. http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/pdfsam/precise/view/head:/debian/pdfsam.desktop http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/pdfsam/lucid/view/head:/debian/pdfsam.desktop So I don't know how you got a PDF Split and Merge executable that wasn't called pdfsam to begin with, but you can rest easy that your renaming didn't cause any changes to the app directory. ** Changed in: software-center (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1349009 Title: Renamed program name locally and Software Center Apps Directory replaced original name with local one Status in “software-center” package in Ubuntu: Invalid Bug description: I'm under shock. In my local Ubuntu 12.04 I installed plenty of time (years) ago the package PDF Split and Merge through the Ubuntu Software Center. Locally, I renamed the executable name to pdfsam. I know, a very bad practice, but for some reasons it was the quickest for me at that time. I might have rated/commented on the software in the USC, I don't remember. Now, with another computer and Ubuntu 14.04, I'm shocked to see in the USC the software pdfsam listed. Moreover, it's also in the Apps Directory: https://apps.ubuntu.com/cat/applications/pdfsam/ I imagine that somehow when I rated the software, it took the name locally and uploaded a new entry in the db with such name? Or even replaced the original!? Is that possible? I cannot understand otherwise what's going on here. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-center 13.10-0ubuntu4.1 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.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 26 23:23:11 2014 InstallationDate: Installed on 2014-07-25 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1349009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273498] Re: cant load digital camera to computer
I updated Ubuntu about a week ago and now Ubuntu will recognise my digital camera. Fixed? -- 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/1273498 Title: cant load digital camera to computer Status in “nautilus” package in Ubuntu: New Bug description: cant load my fuji finepix 3300 camera to computer can you tell me why ProblemType: Bug Architecture: lpia Date: Tue Jan 28 01:05:59 2014 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/nautilus NonfreeKernelModules: wl Package: nautilus 1:2.22.5.1-0ubuntu1netbook1 PackageArchitecture: lpia ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus Uname: Linux 2.6.24-29-lpia i686 UnreportableReason: This is not a genuine Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1273498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171878] Update Released
The verification of the Stable Release Update for compiz has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1171878 Title: Adding/Removing an external monitor causes maximized windows to move to another workspace Status in Compiz: Fix Committed Status in Compiz Core: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Fix Released Bug description: [Impact] If I plug in external monitor, move a window to it, maximize window and remove external monitor, window is moved to the same workspace primary screen - this is correct behavior, but when I un-maximize it - window moves to different workspace. This most likely is because original window positions are not updated after removing the monitor and un-maximize still uses those old values to move the window to supposedly original position. Another use case is when window movement is somewhat wrong - external monitor plugged in, window is maximized on primary screen, move focus to different workspace, unplug the monitor, move back to the workspace when we have fullscreen window, unmaximize it - window un-maximizes not to original position, it's moved away by the same mount of pixels as external monitor width is. I expect that window stays on the same workspace - once it's on it it should not move unless I do that manually, also I expect that un- maximizing moves window to original position, not different. This is continuation of bug https://bugs.launchpad.net/compiz/+bug/763148, fullscreen window bug was separated as per Christopher Townsend (townsend) wrote on 2013-04-18. P.S. Most likely bug can be fixed quite easy as behavior is similar to bug I mentioned, hopefully this can be included in the same SRU. thanks in advance Eduards [Test Case] ** Test Case 1 1. plug in external monitor and move a windows to it 2. maximize window 3. unplug external monitor 4. window moves to the primary display of the same workspace (this is correct) 5. un-maximize window 6. window un-maximizes to a different workspace (this is incorrect) ** Test Case 2 1. plug in external monitor 2. maximize window on primary (laptop display) 3. change to a different workspace 4. unplug external monitor 5. return to workspace with maximized window 6. un-maximize window 7. window un-maximizes to wrong position. instead of the original position it is shifted over by the same number of pixels as the width of the external monitor (also incorrect) [Other information] The bug fix also address bug LP: #763148 on precise. [Regression] None determined expected. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1171878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 763148] Update Released
The verification of the Stable Release Update for compiz has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/763148 Title: Adding/Removing an external monitor causes open windows to move to another workspace Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Compiz Core: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Fix Released Bug description: [Impact] Many users will put different windows in different workspaces for better work flow. If a user connects and/or disconnects an external monitor or projector, all of these windows will be put in the first workspace. Having to go back and move all of the windows back to their workspaces is very frustrating and time consuming. [Test Case] #. Open some applications in different workspaces. #. Plug in an external monitor. [Regression Potential] Very low possibility that a window still ends up in the wrong workspace. Original description: well, i plug in my external screen. expected behaviour would be, if all of my windows would stay in the workspaces i aligned them to, and if they'd be on the same screen i had them in the first place. unfortunatly in unity, if i plug-in (or plug-off) my external screen the windows are all around, but not where i'd expect them to be (namely in the same place they were before). so i always have to toggle expo-mode and re-align all of my windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/763148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171878] Re: Adding/Removing an external monitor causes maximized windows to move to another workspace
This bug was fixed in the package compiz - 1:0.9.7.12-0ubuntu4 --- compiz (1:0.9.7.12-0ubuntu4) precise; urgency=low * debian/patches/fix_external_monitor_hotplug.patch - Cherry-pick fixes upstream for window mismanagement when adding and/or removing an external monitor. (LP: #763148) (LP: #1171878) -- Chris Townsend christopher.towns...@canonical.com Mon, 07 Jul 2014 15:15:43 -0400 ** Changed in: compiz (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1171878 Title: Adding/Removing an external monitor causes maximized windows to move to another workspace Status in Compiz: Fix Committed Status in Compiz Core: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Fix Released Bug description: [Impact] If I plug in external monitor, move a window to it, maximize window and remove external monitor, window is moved to the same workspace primary screen - this is correct behavior, but when I un-maximize it - window moves to different workspace. This most likely is because original window positions are not updated after removing the monitor and un-maximize still uses those old values to move the window to supposedly original position. Another use case is when window movement is somewhat wrong - external monitor plugged in, window is maximized on primary screen, move focus to different workspace, unplug the monitor, move back to the workspace when we have fullscreen window, unmaximize it - window un-maximizes not to original position, it's moved away by the same mount of pixels as external monitor width is. I expect that window stays on the same workspace - once it's on it it should not move unless I do that manually, also I expect that un- maximizing moves window to original position, not different. This is continuation of bug https://bugs.launchpad.net/compiz/+bug/763148, fullscreen window bug was separated as per Christopher Townsend (townsend) wrote on 2013-04-18. P.S. Most likely bug can be fixed quite easy as behavior is similar to bug I mentioned, hopefully this can be included in the same SRU. thanks in advance Eduards [Test Case] ** Test Case 1 1. plug in external monitor and move a windows to it 2. maximize window 3. unplug external monitor 4. window moves to the primary display of the same workspace (this is correct) 5. un-maximize window 6. window un-maximizes to a different workspace (this is incorrect) ** Test Case 2 1. plug in external monitor 2. maximize window on primary (laptop display) 3. change to a different workspace 4. unplug external monitor 5. return to workspace with maximized window 6. un-maximize window 7. window un-maximizes to wrong position. instead of the original position it is shifted over by the same number of pixels as the width of the external monitor (also incorrect) [Other information] The bug fix also address bug LP: #763148 on precise. [Regression] None determined expected. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1171878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 763148] Re: Adding/Removing an external monitor causes open windows to move to another workspace
This bug was fixed in the package compiz - 1:0.9.7.12-0ubuntu4 --- compiz (1:0.9.7.12-0ubuntu4) precise; urgency=low * debian/patches/fix_external_monitor_hotplug.patch - Cherry-pick fixes upstream for window mismanagement when adding and/or removing an external monitor. (LP: #763148) (LP: #1171878) -- Chris Townsend christopher.towns...@canonical.com Mon, 07 Jul 2014 15:15:43 -0400 ** Changed in: compiz (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/763148 Title: Adding/Removing an external monitor causes open windows to move to another workspace Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Compiz Core: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Fix Released Bug description: [Impact] Many users will put different windows in different workspaces for better work flow. If a user connects and/or disconnects an external monitor or projector, all of these windows will be put in the first workspace. Having to go back and move all of the windows back to their workspaces is very frustrating and time consuming. [Test Case] #. Open some applications in different workspaces. #. Plug in an external monitor. [Regression Potential] Very low possibility that a window still ends up in the wrong workspace. Original description: well, i plug in my external screen. expected behaviour would be, if all of my windows would stay in the workspaces i aligned them to, and if they'd be on the same screen i had them in the first place. unfortunatly in unity, if i plug-in (or plug-off) my external screen the windows are all around, but not where i'd expect them to be (namely in the same place they were before). so i always have to toggle expo-mode and re-align all of my windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/763148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292467] Re: Dual screen greeter can break 3D acceleration
Hi Patricia, that was only the release-notes task. So we just noted wrote down there that this can happen and how to work around it. I have not seen or heard anyone fixing (or even looking at) the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Dual screen greeter can break 3D acceleration Status in Release Notes for Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). WORKAROUND: * Plug in external monitor after login (1) * Boot with video=LVDS-1:d (2) (1) Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. (2) This will completely disable the internal screen for that boot. It cannot be enabled through the settings dialogue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
Disabled independent HP by commenting the line in patch_via.c: //spec-gen.indep_hp = 1; Headphones does not works after resume. alsa-info before suspend: http://www.alsa-project.org/db/?f=c7f2d491818afda332e303228f893447e71f37e8 alsa-info after resume: http://www.alsa-project.org/db/?f=75c3f86d7a1a3c65b0851d402dfa4186b7f15bb0 -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349963] [NEW] package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: failed to install ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-latex-base 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Jul 30 02:52:26 2014 DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-10-22 (1011 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1349963 Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “texlive-base” package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-latex-base 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Jul 30 02:52:26 2014 DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-10-22 (1011 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1349963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
** Tags added: regression-release saucy
** Tags added: trusty
--
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/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm surround51
}
I can reproduce problem in Exaile with the custom sink pipeline set to
alsasink device=surround51 and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349953] Re: Screen locking issue
** Information type changed from Private Security to Public ** Package changed: gnome-screensaver (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1349953 Title: Screen locking issue Status in “unity” package in Ubuntu: New Bug description: After coming out of sleep mode, my keyboard cannot type to the password entry field. When I try to type to the password entry field, the computer sends my input to whatever window I had open before my computer went to sleep. This means that if I type my password and press enter, and the last window I had open was, say, a gchat, I will send my password to the person with whom I was talking. It seems like this bug only occurs when I had a text entry field selected before putting my computer to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 29 09:40:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 1800 InstallationDate: Installed on 2012-12-24 (582 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-07-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1348734] Re: SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all
** Changed in: alsa-driver (Ubuntu) Importance: Undecided = Medium -- 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/1348734 Title: SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: ALSA info page http://www.alsa- project.org/db/?f=35e0e257c3193758fe2129db6d39552c1af3d687 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vladimir 1512 F pulseaudio /dev/snd/controlC1: vladimir 1512 F pulseaudio /dev/snd/pcmC1D0p: vladimir 1512 F...m pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 21:22:39 2014 HibernationDevice: RESUME=UUID=bf69b978-a32b-4de3-a839-4c1ef87ae5fd InstallationDate: Installed on 2014-07-24 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Acer Aspire One 522 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e2267848-1bb4-486d-81e0-ec8507180a34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.09 dmi.board.name: Aspire One 522 dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.09:bd03/21/2011:svnAcer:pnAspireOne522:pvrV1.09:rvnAcer:rnAspireOne522:rvrV1.09:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire One 522 dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1348734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964673] Re: keyboard shortcut overlay needs more consistent wording
This was merged 2012-08-27 and shipped in Ubuntu 12.10, the Fix is as Released as it's going to get. ** Changed in: unity Status: Incomplete = Fix Released ** Changed in: unity (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/964673 Title: keyboard shortcut overlay needs more consistent wording Status in Ayatana Design: New Status in Ubuntu Translations: Triaged Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: I'm submitting a merge proposal to go with this. The keyboard shortcut overlay (when you hold down the Windows key) has several wording issues: - Inconsistent verb tenses (open and opens) - Minimise (Minimize is the correct spelling in US English, which is what the C locale should use) - Super (Press) is confusing; changing the text to Super (Hold) makes it more clear that holding down the Super key will show the overlay - Cursor keys; I think a typical person calls them arrow keys This won't affect ubuntu-docs, but it does create new strings for the translators. Translators notified: https://lists.ubuntu.com/archives/ubuntu-translators/2012-April/005297.html ProblemType: BugDistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Mar 25 13:19:15 2012SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/964673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295207] Re: Migrate to farsight 0.2* / gstreamer 1.0
The Pidgin version in upstream git (seems to be for version 3.x), can be built --with-gstreamer=1.0 The released (2.10.9) version always wants gstremer0.10. (I'm not sure if there are other changes between them that makes gstreamer1.0 work better..) If you grep configure.ac and yours has gst10_pkg that indicates you're on the gstreamer1.0 compatible one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1295207 Title: Migrate to farsight 0.2* / gstreamer 1.0 Status in “pidgin” package in Ubuntu: Confirmed Status in “pidgin” package in Fedora: Unknown Bug description: 1) Ubuntu 14.04 2) 1:2.10.9-0ubuntu2 3) I expect it to depend against the latest farsight/gstreamer 1.0 4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty cd, through libpurple. It seems upstream already supports building against farstream-0.2 and gstreamer1.0, see: https://developer.pidgin.im/wiki/Dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1295207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1349983] [NEW] GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host accounts.google.com not found while network available
Public bug reported: While calling signon_auth_session_new from accounts-polld i kept getting 2014/07/28 19:26:05 Account 2 failed to authenticate: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host accounts.google.com not found But network was available. Error was not transient as this call was repeated every 5 minutes for a long time and network on the phone was available (tested browser and scopes). Tested on: $ system-image-cli -i current build number: 154 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-07-28 15:59:27 version version: 154 version ubuntu: 20140728 version device: 20140725.1 ** Affects: signon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1349983 Title: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host accounts.google.com not found while network available Status in “signon” package in Ubuntu: New Bug description: While calling signon_auth_session_new from accounts-polld i kept getting 2014/07/28 19:26:05 Account 2 failed to authenticate: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.NoConnection: Host accounts.google.com not found But network was available. Error was not transient as this call was repeated every 5 minutes for a long time and network on the phone was available (tested browser and scopes). Tested on: $ system-image-cli -i current build number: 154 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-07-28 15:59:27 version version: 154 version ubuntu: 20140728 version device: 20140725.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1349983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964673] Re: keyboard shortcut overlay needs more consistent wording
** No longer affects: ubuntu-translations -- 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/964673 Title: keyboard shortcut overlay needs more consistent wording Status in Ayatana Design: New Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: I'm submitting a merge proposal to go with this. The keyboard shortcut overlay (when you hold down the Windows key) has several wording issues: - Inconsistent verb tenses (open and opens) - Minimise (Minimize is the correct spelling in US English, which is what the C locale should use) - Super (Press) is confusing; changing the text to Super (Hold) makes it more clear that holding down the Super key will show the overlay - Cursor keys; I think a typical person calls them arrow keys This won't affect ubuntu-docs, but it does create new strings for the translators. Translators notified: https://lists.ubuntu.com/archives/ubuntu-translators/2012-April/005297.html ProblemType: BugDistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Mar 25 13:19:15 2012SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/964673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1350004] [NEW] package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git
Public bug reported: i can't upgrade my ubuntu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Tue Jul 29 10:19:12 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libavutil.so.51.22.2] [origin: unknown] libc6 2.19-0ubuntu6 [modified: lib/x86_64-linux-gnu/ld-2.19.so lib/x86_64-linux-gnu/libc-2.19.so lib/x86_64-linux-gnu/libcrypt-2.19.so lib/x86_64-linux-gnu/libdl-2.19.so lib/x86_64-linux-gnu/libm-2.19.so lib/x86_64-linux-gnu/libnsl-2.19.so lib/x86_64-linux-gnu/libpthread-2.19.so lib/x86_64-linux-gnu/libresolv-2.19.so lib/x86_64-linux-gnu/librt-2.19.so lib/x86_64-linux-gnu/libutil-2.19.so] libgcc1 1:4.9-20140406-0ubuntu1 [modified: lib/x86_64-linux-gnu/libgcc_s.so.1] multiarch-support 2.19-0ubuntu6 DuplicateSignature: package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]:libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances InstallationDate: Installed on 2013-03-26 (490 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: libav Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances UpgradeStatus: Upgraded to trusty on 2014-06-01 (58 days ago) ** Affects: libav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages 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/1350004 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances Status in “libav” package in Ubuntu: New Bug description: i can't upgrade my ubuntu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Tue Jul 29 10:19:12 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libavutil.so.51.22.2] [origin: unknown] libc6 2.19-0ubuntu6 [modified: lib/x86_64-linux-gnu/ld-2.19.so lib/x86_64-linux-gnu/libc-2.19.so lib/x86_64-linux-gnu/libcrypt-2.19.so lib/x86_64-linux-gnu/libdl-2.19.so lib/x86_64-linux-gnu/libm-2.19.so lib/x86_64-linux-gnu/libnsl-2.19.so lib/x86_64-linux-gnu/libpthread-2.19.so lib/x86_64-linux-gnu/libresolv-2.19.so lib/x86_64-linux-gnu/librt-2.19.so lib/x86_64-linux-gnu/libutil-2.19.so] libgcc1 1:4.9-20140406-0ubuntu1 [modified: lib/x86_64-linux-gnu/libgcc_s.so.1] multiarch-support 2.19-0ubuntu6 DuplicateSignature: package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]:libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances InstallationDate: Installed on 2013-03-26 (490 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: libav Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances UpgradeStatus: Upgraded to trusty on 2014-06-01 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1350004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1350004] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20
** Tags removed: need-duplicate-check -- 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/1350004 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances Status in “libav” package in Ubuntu: New Bug description: i can't upgrade my ubuntu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Tue Jul 29 10:19:12 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libavutil.so.51.22.2] [origin: unknown] libc6 2.19-0ubuntu6 [modified: lib/x86_64-linux-gnu/ld-2.19.so lib/x86_64-linux-gnu/libc-2.19.so lib/x86_64-linux-gnu/libcrypt-2.19.so lib/x86_64-linux-gnu/libdl-2.19.so lib/x86_64-linux-gnu/libm-2.19.so lib/x86_64-linux-gnu/libnsl-2.19.so lib/x86_64-linux-gnu/libpthread-2.19.so lib/x86_64-linux-gnu/libresolv-2.19.so lib/x86_64-linux-gnu/librt-2.19.so lib/x86_64-linux-gnu/libutil-2.19.so] libgcc1 1:4.9-20140406-0ubuntu1 [modified: lib/x86_64-linux-gnu/libgcc_s.so.1] multiarch-support 2.19-0ubuntu6 DuplicateSignature: package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0]:libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances InstallationDate: Installed on 2013-03-26 (490 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: libav Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 [modified: usr/lib/x86_64-linux-gnu/libpostproc.so.52.0.0] failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances UpgradeStatus: Upgraded to trusty on 2014-06-01 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1350004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218294] Re: [dialer app] During a live call, there's no volume adjustment available
just tested on Utopic build 157 and volume adjustment during call doesn't seem to control the volume of the earpiece, only the speaker phone. And turning the volume all the way down even when the speakerphone is on doesn't turn off all the sound as I expected, it just lowers it to a certain point. ** No longer affects: pulseaudio (Ubuntu Saucy) ** Changed in: pulseaudio (Ubuntu) Status: Fix Released = Confirmed ** Changed in: pulseaudio (Ubuntu) Assignee: David Henningsson (diwic) = Ricardo Salveti (rsalveti) ** No longer affects: dialer-app (Ubuntu Saucy) ** No longer affects: dialer-app (Ubuntu) ** No longer affects: dialer-app ** Tags added: rtm14 ** Summary changed: - [dialer app] During a live call, there's no volume adjustment available + During a live call, volume adjustment doesn't work in earpiece -- 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/1218294 Title: During a live call, volume adjustment doesn't work in earpiece Status in Ubuntu UX bugs: Fix Committed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Current situation: Can't adjust the voice volume during a live call, making it difficult to hear the receiver Desired: Can adjust volume during a live call (Eg using the volume buttons on the device) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1218294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 319354] Re: MSN user name change to often causes msg box overflow and kills client
Closing due to age. If a similar bug appears in Ubuntu 14.04 please open a new report. ** Changed in: pidgin (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/319354 Title: MSN user name change to often causes msg box overflow and kills client Status in “pidgin” package in Ubuntu: Invalid Bug description: Binary package hint: pidgin If the MSN user changes its name too often, then there is an error msg that shows up, it does not say which user, just that it was too often. If the name continues to change too often, there will be hundreds of such boxes open. this is a form of an attack,and can kill the client process and block then entire session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/319354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461068] Re: [karmic] apport-kde reports bug for wrong package
Closing due to age. If a similar bug appears in Ubuntu 14.04 please open a new report. ** Changed in: apport (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/461068 Title: [karmic] apport-kde reports bug for wrong package Status in “apport” package in Ubuntu: Invalid Bug description: This bug was reported from Karbon but Apport (from the Report Bug menu item) decided that it is supposed to report it against kdelibs. The same seem to happen when I try to report a bug from any other package. ProblemType: Bug Architecture: amd64 Date: Mon Oct 26 14:11:47 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/kdeinit4 Package: kdelibs-bin 4:4.3.2-0ubuntu7 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: kde4libs Uname: Linux 2.6.31-14-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (npviewer.bin:4074): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/461068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 635127] Re: apport-collect errno 13
Closing due to age. If a similar bug appears in Ubuntu 14.04 please open a new report. ** Changed in: apport (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/635127 Title: apport-collect errno 13 Status in “apport” package in Ubuntu: Invalid Bug description: Binary package hint: apport $ apport-collect 635076 Traceback (most recent call last): File /usr/share/apport/apport-gtk, line 368, in module app.run_argv() File /usr/lib/python2.6/dist-packages/apport/ui.py, line 560, in run_argv return self.run_update_report() File /usr/lib/python2.6/dist-packages/apport/ui.py, line 422, in run_update_report if not self.crashdb.can_update(self.options.update_report): File /usr/lib/python2.6/dist-packages/apport/crashdb_impl/launchpad.py, line 451, in can_update if bug.duplicate_of: File /usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py, line 643, in __getattr__ return super(Entry, self).__getattr__(name) File /usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py, line 305, in __getattr__ return self.lp_get_parameter(attr) File /usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py, line 196, in lp_get_parameter self._ensure_representation() File /usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py, line 331, in _ensure_representation representation = self._root._browser.get(self._wadl_resource) File /usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py, line 287, in get response, content = self._request(url, extra_headers=headers) File /usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py, line 242, in _request str(url), method=method, body=data, headers=headers) File /usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py, line 211, in _request_and_retry url, method=method, body=body, headers=headers) File /usr/lib/python2.6/dist-packages/httplib2/__init__.py, line 1112, in request _updateCache(headers, merged_response, content, self.cache, cachekey) File /usr/lib/python2.6/dist-packages/httplib2/__init__.py, line 396, in _updateCache cache.set(cachekey, text) File /usr/lib/python2.6/dist-packages/httplib2/__init__.py, line 664, in set f = file(cacheFullPath, wb) IOError: [Errno 13] Permission denied: '/home/keimpe/.launchpadlib/api.edge.launchpad.net/cache/api.edge.launchpad.net,1.0,bugs,635076-application,json,d2cb75d1db219bb37e3c583d33a0a5f2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/635127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 349745] Re: Opened sudo gedit - Apport said pidgin crashed... when it didn't. - gedit crashed - apport failed to report the pidgin crash - apport notified me of gedit crash
Closing due to age. If a similar bug appears in Ubuntu 14.04 please open a new report. ** Changed in: apport (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/349745 Title: Opened sudo gedit - Apport said pidgin crashed... when it didn't. - gedit crashed - apport failed to report the pidgin crash - apport notified me of gedit crashing 3 minutes later. Status in “apport” package in Ubuntu: Invalid Bug description: interestingly enough, non-sudo gedit stayed online. I was running the suspend/resume testing just before i rebooted and tried to do this (unrelated) stuff pidgin didn't crash.. I don't know why it said it did. I don't know what to tell you.. half of the time when apport says something crashed I don't even know what i was doing at the time, nor what the package it claims crashed does or is. This is the only time a program that *I* started within a few minutes of boot crashed and apport reported it, normally about 5 or 4 programs that I don't even know about crash. heres a screenshot.. I don't know how to reproduce this issue, nor do I really know exactly what happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/349745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
