[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
I've filed this issue with upstream: https://bugzilla.gnome.org/show_bug.cgi?id=710986 ** Bug watch added: GNOME Bug Tracker #710986 https://bugzilla.gnome.org/show_bug.cgi?id=710986 ** Changed in: gvfs Importance: Undecided = Unknown ** Changed in: gvfs Status: New = Unknown ** Changed in: gvfs Remote watch: None = GNOME Bug Tracker #710986 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1205647 Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() Status in GVFS: Unknown Status in “gvfs” package in Ubuntu: Confirmed Bug description: Unmounting share from nautilus ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 27 15:58:03 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-smb InstallationDate: Installed on 2013-07-20 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=fr_FR LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7fad3ebbfff1:cmpb $0x0,(%rax) PC (0x7fad3ebbfff1) ok source $0x0 ok destination (%rax) (0x0170) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 ?? () g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1205647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245344] [NEW] package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: i have probleme with texlive-base install, i don't know why. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: texlive-base 2009-15 ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51 Uname: Linux 3.2.0-55-generic i686 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: texlive-base: Configure texlive-luatex: Configure Architecture: i386 Date: Sun Oct 27 11:17:31 2013 DuplicateSignature: package:texlive-base:2009-15:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 MarkForUpload: True PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to precise on 2013-10-27 (0 days ago) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- 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/1245344 Title: package texlive-base 2009-15 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in “texlive-base” package in Ubuntu: New Bug description: i have probleme with texlive-base install, i don't know why. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: texlive-base 2009-15 ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51 Uname: Linux 3.2.0-55-generic i686 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: texlive-base: Configure texlive-luatex: Configure Architecture: i386 Date: Sun Oct 27 11:17:31 2013 DuplicateSignature: package:texlive-base:2009-15:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 MarkForUpload: True PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to precise on 2013-10-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1245344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245344] Re: package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
** Tags removed: need-duplicate-check -- 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/1245344 Title: package texlive-base 2009-15 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in “texlive-base” package in Ubuntu: New Bug description: i have probleme with texlive-base install, i don't know why. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: texlive-base 2009-15 ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51 Uname: Linux 3.2.0-55-generic i686 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: texlive-base: Configure texlive-luatex: Configure Architecture: i386 Date: Sun Oct 27 11:17:31 2013 DuplicateSignature: package:texlive-base:2009-15:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 MarkForUpload: True PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-base 2009-15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to precise on 2013-10-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1245344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
hi ,this is only my second day using ubuntu , so don't laugh at me . all the above workaround didn't work for me , however launching eclipse as root did work flawlessly for me . so may be a permission problem ? Version: Kepler Service Release 1 Build id: 20130919-0819 ubuntu 13.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) Expected: The content of the submenus show up Actual: Only the top-level headers seem to be available. Nothing happens when I click on them either. They don't show up in the HUD either. It worked fine on 13.04, so I'm not sure what changed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1241007] Re: FTBFS in saucy
Arm64 builds are usually fixed by running dh_autoreconf or autotools-dev from the debian/rules file. While this may have worked, i wouldn't recommend it. ** Description changed: - Not sure if libgnome-media profile will be replaced in Ubuntu Saucy but - I fixed ftbs. + Not sure if libgnome-media-profiles will be replaced in Ubuntu Saucy but + I fixed ftbfs. See ftbs buildlog (2013-10-16): https://launchpadlibrarian.net/153893423 /buildlog_ubuntu-saucy-arm64.libgnome-media- profiles_3.0.0-1ubuntu1_FAILEDTOBUILD.txt.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnome-media-profiles in Ubuntu. https://bugs.launchpad.net/bugs/1241007 Title: FTBFS in saucy Status in “libgnome-media-profiles” package in Ubuntu: New Bug description: Not sure if libgnome-media-profiles will be replaced in Ubuntu Saucy but I fixed ftbfs. See ftbs buildlog (2013-10-16): https://launchpadlibrarian.net/153893423/buildlog_ubuntu-saucy-arm64 .libgnome-media-profiles_3.0.0-1ubuntu1_FAILEDTOBUILD.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnome-media-profiles/+bug/1241007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working
setup the speaker pin complex 0x16 if the subwoofer is connected before boot +static void alc663_fixup_asus_sonicmaster(struct hda_codec *codec, + const struct hda_fixup *fix, int action) +{ + if (action != HDA_FIXUP_ACT_PRE_PROBE) + return; + if (snd_hda_pin_sense(codec, 0x18) == AC_PINSENSE_PRESENCE) + snd_hda_codec_set_pincfg(codec, 0x16, 0x99130111); +} -- 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/1040873 Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Hi, this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/871808 because #871808 stands for a different hardware with a different solution, so people may get confused. Here is a summary (see post #48 to #54 of #871808): The subwoofer of Asus N56VZ laptop doesn't work out of the box. #sudo hda-jack-sense-test -a : *** Without subwoofer: Pin 0x1e (Black SPDIF Out): present = No *** With subwoofer: Pin 0x1e (Black SPDIF Out): present = Yes http://www.alsa- project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a -- There are two ways of making it work: #1 a. Add to rc.local : echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs echo 1 /sys/class/sound/hwC0D0/reconfig b. Add options snd-hda-intel model=asus-mode4 in /etc/modprobe.d/alsa-base.conf c. Reboot d. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 output in the sound settings panel. You have to do this each time you reboot!!! #2 a. Add to rc.local : echo 0x16 0x99130111 /sys/class/sound/hwC0D0/user_pin_configs echo 0x1e 0x99130112 /sys/class/sound/hwC0D0/user_pin_configs echo 1 /sys/class/sound/hwC0D0/reconfig b. Reboot c. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 output in the sound settings panel. You have to do this each time you reboot!!! Both give the same results and fix the bug. -- Can you make it work out of the box? There is still two other bugs on this laptop : - crackling audio when playing with sound volume: see https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867 - When I put the omputer in sleep mode, there is no way to get sound working on resume: should I open a new bug to investigate this? Regards Sam ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1898 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431477,0012' Controls : 23 Simple ctrls : 13 CheckboxSubmission: 54021779511d0213081a2b1707bf951c CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a Date: Thu Aug 23 22:38:00 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.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: 1898 sam F pulseaudio PID ACCESS COMMAND Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ 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.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ
[Desktop-packages] [Bug 1245347] [NEW] Screen keeps blinking after boot
Public bug reported: Please see here. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Invalid -- 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/1245347 Title: Screen keeps blinking after boot Status in “xorg” package in Ubuntu: Invalid Bug description: Please see here. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1245347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245349] [NEW] After waking up from sleep mode, active window moves to first display
Public bug reported: - Connect two monitors (I use builtin laptop monitor (first) and one external (second)) - Start some programs, move some window to second monitor and make it active - Go into sleep mode - Wake up the computer - Now last active window had moved to first monitor (and possibly resized) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 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: Mon Oct 28 10:18:40 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21bb] InstallationDate: Installed on 2013-10-23 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4403RP2 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 81ET60WW (1.36 ) dmi.board.name: 4403RP2 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4403RP2 dmi.product.version: ThinkPad L412 dmi.sys.vendor: LENOVO 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.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: Fri Oct 25 17:34:23 2013 xserver.configfile: default xserver.errors: RADEON(0): failed to set mode: Permission denied(II) RADEON(0): VRAM usage limit set to 451580K xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon ** Affects: compiz Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1245349 Title: After waking up from sleep mode, active window moves to first display Status in Compiz: New Status in “xorg” package in Ubuntu: New Bug description: - Connect two monitors (I use builtin laptop monitor (first) and one external (second)) - Start some programs, move some window to second monitor and make it active - Go into sleep mode - Wake up the computer - Now last active window had moved to first monitor (and possibly resized) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 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: Mon Oct 28 10:18:40 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21bb] InstallationDate: Installed on 2013-10-23 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4403RP2 MarkForUpload: True ProcKernelCmdLine:
[Desktop-packages] [Bug 1245347] Re: Screen keeps blinking after boot
For some reason it was filled under xorg. Please ignore. ** Changed in: xorg (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/xorg/+question/238193 -- 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/1245347 Title: Screen keeps blinking after boot Status in “xorg” package in Ubuntu: Invalid Bug description: Please see here. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1245347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243261] Re: apparent GPU hang on haswell laptop when playing movie on libreoffice
I see the same problem on my Haswell laptop (Sony VAIO Pro) running Saucy when I play a video with mplayer or vlc. -- 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/1243261 Title: apparent GPU hang on haswell laptop when playing movie on libreoffice Status in “xorg” package in Ubuntu: New Bug description: How to reproduce: 1. open libreoffice - file - new - presentation 2. paste any movie; insert - movie this bug is quite reproducible and this movie file can be anything that libreoffice/gstreamer can play. 3. verify you correctly pasted the movie by selecting the movie in the slide and clicking the play botton bottom left. check if the movie *plays* ok. 4. then start slideshow from the slideshow menu or F5. Symptom: * a screen hang. this continues at least ten seconds or more. after that you can somehow quit the slideshow mode. * ESC and other keys do not stop the slideshow, except ctrl+alt+F1 * switching to VT and getting back to X helps sometimes. Configuration: * Thinkpad-X240s * tried both Saucy's default kernel and 3.11.6-031106 (ppa) dmesg: [ 2209.663234] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2214.672447] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2218.658213] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ .656003] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2226.653754] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2230.651538] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2234.649319] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2238.623129] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2238.623162] [drm:i915_hangcheck_elapsed] *ERROR* no progress on render ring [ 2238.623300] [drm:i915_set_reset_status] *ERROR* render ring hung flushing bo (0x1d06e000 ctx 0) at 0x320b500 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Device 0a0c (rev 09) 00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-V (rev 04) 00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 (rev e4) 00:1c.1 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4) 00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5227 (rev 01) 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.11.6-031106-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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: Wed Oct 23 00:07:55 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2214] InstallationDate: Installed on 2013-10-22 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20AJA00P00 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.6-031106-generic root=UUID=30382826-322c-4457-a4a7-e6852d23ed8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GIET35WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AJA00P00 dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Desktop-packages] [Bug 1245354] [NEW] Screen keeps blinking after boot
Public bug reported: Please see below. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064 ** Affects: xserver-xorg-video-sis (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-sis in Ubuntu. https://bugs.launchpad.net/bugs/1245354 Title: Screen keeps blinking after boot Status in “xserver-xorg-video-sis” package in Ubuntu: New Bug description: Please see below. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1245354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228506] Re: [prime] unsynchronised rendering on secondary displays
After install nvidia driver external monitor works fine, but internal not work, because internal videocard (intel) disabled. If enable internal video card, external again not works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1228506 Title: [prime] unsynchronised rendering on secondary displays Status in Accelerated Xorg driver for nVidia cards: Unknown Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Symptoms are the same as in bug https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1221399 For example, see attached photo, replicable 100% just by moving the mouse fast. In bug https://bugs.launchpad.net/xmir/+bug/1218735 I was told to fill a new bug. Note that this Thinkpad has two video cards. I don't know how to tell if Intel or Nvidia is being used. I'm using the default saucy install, no additional drivers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu4 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: Sat Sep 21 10:35:28 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f5] InstallationDate: Installed on 2013-09-13 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909) MachineType: LENOVO 2449A22 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=d9f16f85-5511-470f-972f-687054e80e8f ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 2449A22 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET90WW(2.50):bd12/21/2012:svnLENOVO:pn2449A22:pvrThinkPadW530:rvnLENOVO:rn2449A22:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2449A22 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 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-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Sep 20 13:38:20 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1228506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245200] Re: [HDA-Intel - HDA Intel, playback] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1245200 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [ 226.036095] usb 3-1: USB disconnect, device number 2 [ 267.538113] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Date: Sun Oct 27 14:54:41 2013 InstallationDate: Installed on 2013-10-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True 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:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245200] Re: [HDA-Intel - HDA Intel, playback] No sound at all
Seems I have the same or similar problem. See my post in https://answers.launchpad.net/ubuntu/+question/238161 How can I do the 'hda-jack-sense-test' and what is the text below the statement of jack detection in previous answer? (how to use it?) -- 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/1245200 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [ 226.036095] usb 3-1: USB disconnect, device number 2 [ 267.538113] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Date: Sun Oct 27 14:54:41 2013 InstallationDate: Installed on 2013-10-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True 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:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231447] Re: Alt+Print Screen only takes picture of the HUD
I removed the duplicate status here after a commenter of bug #1169904 seconded my view (comment #17 in that bugreport). ** This bug is no longer a duplicate of bug 1169904 Save screenshot dialog window has wrong focus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1231447 Title: Alt+Print Screen only takes picture of the HUD Status in “gnome-screenshot” package in Ubuntu: Confirmed Bug description: In 13.10, pressing Alt+Print Screen always takes a screenshot of the HUD and not of the active window. This was fixed in 13.04, ref. bug number 1072199. To replicate: 1. Start a program such as gedit. 2. Press Alt+PrintScreen * What happens: gnome-screenshot takes a screenshot of the HUD (due to the Dash that gets invoked). * What should happen: gnome-screenshot should take a screenshot of just the gedit window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1231447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1169904] Re: Save screenshot dialog window has wrong focus
The problem addressed by Norbert is filed as bug #1231447. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1169904 Title: Save screenshot dialog window has wrong focus Status in One Hundred Papercuts: In Progress Status in “gnome-screenshot” package in Ubuntu: Fix Released Status in “gnome-screenshot” source package in Raring: Fix Released Bug description: [SRU] The debdiff attached to comment #7 backports the upstream fix for Raring. [IMPACT] After taking a screenshot users should immediately be able to type in a filename, instead they need to use the mouse to give focus to the filename field which then loses the highlight of the suggested filename. [Test Case] Take a screenshot by pressing PrintScreen or Alt- PrintScreen then attempt to enter a filename. [Regression Potential] Low, the single-line-fix has been in upstream for 3 months already. When you take a screenshot with the Print Screen key, you get a dialog asking you to name the file. It *looks* like the focus is on the name of the file (selected in orange like the File Rename dialog in Nautilus), but you can't type - I suspect focus is really on the Save button. Nor can you tab to the filename field, so you have to use your mouse to select what is already visually selected in order to type a name. Correct behaviour would be to let the user directly type to this dialog box without any further action. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-screenshot 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Wed Apr 17 12:35:26 2013 InstallationDate: Installed on 2011-12-09 (494 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to quantal on 2012-11-09 (158 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1169904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1072199] Re: Alt+Print Screen shortcut does not work in Ubuntu
** This bug is no longer a duplicate of bug 1169904 Save screenshot dialog window has wrong focus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1072199 Title: Alt+Print Screen shortcut does not work in Ubuntu Status in Unity: Confirmed Status in “gnome-screenshot” package in Ubuntu: Confirmed Bug description: According to Ubuntu Desktop Guide (see attached screenshot of the Ubuntu Desktop Guide) pressing Alt+Print Screen should take a screenshot of a window. However when I press Alt+Print Screen it always takes the screenshot of the launcher and not of the active window. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1072199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174014] [NEW] No desktop after 13.04 upgrade
You have been subscribed to a public bug: Existing/working quantal Lubuntu system using lightdm/openbox. 'do- release-upgrade' ran with no errors, on reboot system displayed lightdm login screen. After entering password, login boxes disappeared, leaving the lightdm background, and no further response from system. Power button performed clean shutdown properly. Reboot into kernel 3.5 shows same behavior, as does selecting different environments (Lubuntu, LXDE, Openbox, Gnome, etc.). Mouse also functions... Reboot into recovery mode, check dmesg/syslog, no errors found except a udevd message that SYSFS is no longer used (related to Logitech mouse). Corrected by booting to recovery mode and running root shell, 'mount -o remount,rw /', 'dpkg-reconfigure lightdm' and selecting lightdm as display manager. After rebooting, desktop appears correctly. Unsure if this is display manager or window manager related, was unable to find any errors indicating either. Was unable to locate any release notes, etc. showing this as a problem. Can pull logs as desired. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openbox 3.5.0-7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CheckboxSubmission: afccc869b4440e688c81cfe0d9ad372f CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Sun Apr 28 09:03:25 2013 InstallationDate: Installed on 2010-03-03 (1151 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True SourcePackage: openbox UpgradeStatus: Upgraded to raring on 2013-04-27 (1 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- No desktop after 13.04 upgrade https://bugs.launchpad.net/bugs/1174014 You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174921] [NEW] Wrong color depth
You have been subscribed to a public bug: Intel Graphics 82865G dont work well. Bad colors. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openbox 3.5.0-7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.330 Date: Tue Apr 30 20:50:11 2013 LiveMediaBuild: Lubuntu 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openbox Importance: Undecided Status: New ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- Wrong color depth https://bugs.launchpad.net/bugs/1174921 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174921] Re: Wrong color depth
** Package changed: openbox (Ubuntu) = xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1174921 Title: Wrong color depth Status in OpenBox window manager: New Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Intel Graphics 82865G dont work well. Bad colors. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openbox 3.5.0-7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.330 Date: Tue Apr 30 20:50:11 2013 LiveMediaBuild: Lubuntu 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openbox/+bug/1174921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174014] Re: No desktop after 13.04 upgrade
** Package changed: openbox (Ubuntu) = lightdm (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1174014 Title: No desktop after 13.04 upgrade Status in “lightdm” package in Ubuntu: New Bug description: Existing/working quantal Lubuntu system using lightdm/openbox. 'do- release-upgrade' ran with no errors, on reboot system displayed lightdm login screen. After entering password, login boxes disappeared, leaving the lightdm background, and no further response from system. Power button performed clean shutdown properly. Reboot into kernel 3.5 shows same behavior, as does selecting different environments (Lubuntu, LXDE, Openbox, Gnome, etc.). Mouse also functions... Reboot into recovery mode, check dmesg/syslog, no errors found except a udevd message that SYSFS is no longer used (related to Logitech mouse). Corrected by booting to recovery mode and running root shell, 'mount -o remount,rw /', 'dpkg-reconfigure lightdm' and selecting lightdm as display manager. After rebooting, desktop appears correctly. Unsure if this is display manager or window manager related, was unable to find any errors indicating either. Was unable to locate any release notes, etc. showing this as a problem. Can pull logs as desired. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openbox 3.5.0-7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CheckboxSubmission: afccc869b4440e688c81cfe0d9ad372f CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Sun Apr 28 09:03:25 2013 InstallationDate: Installed on 2010-03-03 (1151 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True SourcePackage: openbox UpgradeStatus: Upgraded to raring on 2013-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1174014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1238937] Re: i7-3610QM processor turbo boost not working properly
** Changed in: xorg (Ubuntu) Status: New = Invalid ** Changed in: xorg (Ubuntu) Assignee: (unassigned) = cyberalex4life (cyberalex4life) -- 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/1238937 Title: i7-3610QM processor turbo boost not working properly Status in “xorg” package in Ubuntu: Invalid Bug description: The problem is simple: turbo boost works only from 230 to 2301000. bios_limit is set to 2301000 My machine: Asus K55VD (laptop) Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8 Intel® Ivybridge Mobile NVidia GeForce 610M/PCIe/SSE2 64-bit Ubuntu Gnome 13.04 (same problem on 13.10) 750 GB Hard Disk Hitachi HTS547575A9E384 (JE4OA6A0) 8GB RAM I tried some of the solutions online but didn't get anywhere. I found this problem with indicato-cpufreq, but I also monitored the frequency without it installed. The maximum frequency should be about 3,1GHz on all cores, 3.2GHz on two cores and 3.3GHz on one core. Please give me a good solution or, if not safe, warn me about the problems. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 11 21:50:49 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.8.0-31-generic, x86_64: installed nvidia-304, 304.88, 3.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1457] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-10-10 (1 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. K55VD MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-31-generic root=UUID=c7225e23-8cc0-4ce8-b735-88a9ff6b9170 ro quiet splash acpi_osi=!Windows 2012 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD 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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri Oct 11 20:18:46 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1238937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237329] Re: Apple Wireless Keyboard/Mouse is not listed as its original name. It stripped non-ascii characters (UTF-8 valid).
I have tested upower 0.9.15-3git1ubuntu0.1 on precise with linux kernel 3.2 and 3.5, and they both work fine. I have tested upower 0.9.20-1ubuntu0.1 on raring with linux kernel 3.8 and it works fine. ** Tags removed: verification-needed ** Tags added: precise quantal raring verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1237329 Title: Apple Wireless Keyboard/Mouse is not listed as its original name. It stripped non-ascii characters (UTF-8 valid). Status in “upower” package in Ubuntu: Fix Released Status in “upower” source package in Precise: Fix Committed Status in “upower” source package in Quantal: Confirmed Status in “upower” source package in Raring: Fix Committed Status in “upower” source package in Saucy: Fix Released Bug description: [Impact] * For some Bluetooth devices such as Apple Wireless Keyboard/Mouse, you can name them by valid UTF-8 string. However those UTF-8 strings are not showed. It is very annoying for the users that they can not see those valid UTF-8 strings. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Open gnome-power-statistics, you have find that the 'Model' field of Apple Wireless Mouse shows only ASCII without the correct name. [Regression Potential] * There is no obvious regression as I know. [Other Info] * This issue is fixed in Saucy but not in Precise, Quantal and Raring. * We still need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard show. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1237329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
I have tested upower 0.9.15-3git1ubuntu0.1 on precise with linux kernel 3.2 and 3.5, and they both work fine. I have tested upower 0.9.20-1ubuntu0.1 on raring with linux kernel 3.8 and it works fine. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Invalid Status in “upower” source package in Precise: Fix Committed Status in “gnome-power-manager” source package in Quantal: Invalid Status in “upower” source package in Quantal: Confirmed Status in “gnome-power-manager” source package in Raring: Invalid Status in “upower” source package in Raring: Fix Committed Status in “gnome-power-manager” source package in Saucy: Invalid Status in “upower” source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions:
[Desktop-packages] [Bug 1245371] [NEW] D Fn Wi-Ubuntu Gnome 13.10 Asus K55VFi key not working by default
Public bug reported: This is a bug, and also a fix. The Wi-fi LED doesn't light in any circumstance, but this is not a problem, since the LED only lights in Windows 8 after installing the requiered drivers. In Windows 8 the Wi-Fi Fn key works by switching airplane mode ON/OFF and it works right after first boot (but no LED). In my case it doesn't work by default at all (even the code is not caught by any programs like easystroke, etc). ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1245371 Title: D Fn Wi-Ubuntu Gnome 13.10 Asus K55VFi key not working by default Status in “xorg” package in Ubuntu: New Bug description: This is a bug, and also a fix. The Wi-fi LED doesn't light in any circumstance, but this is not a problem, since the LED only lights in Windows 8 after installing the requiered drivers. In Windows 8 the Wi-Fi Fn key works by switching airplane mode ON/OFF and it works right after first boot (but no LED). In my case it doesn't work by default at all (even the code is not caught by any programs like easystroke, etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1245371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245371] Re: D Fn Wi-Ubuntu Gnome 13.10 Asus K55VFi key not working by default
And now the fix: sudo gedit /etc/default/grub Find the line with: GRUB_CMDLINE_LINUX_DEFAULT=splash quiet and modify it to look like this: GRUB_CMDLINE_LINUX_DEFAULT=splash quiet acpi_osi='!Windows 2012' Save and close editor. Then: sudo update-grub and restart. Wi-Fi Fn key should work by switching ON/OFF Airplane Mode PS: I haven't tested this, but if in earlier versions of Ubuntu you had problems with Fn keys not working and some other fix did the job for you, that fix may be the match for this case. ** Changed in: xorg (Ubuntu) Status: New = Fix Committed -- 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/1245371 Title: D Fn Wi-Ubuntu Gnome 13.10 Asus K55VFi key not working by default Status in “xorg” package in Ubuntu: Fix Committed Bug description: This is a bug, and also a fix. The Wi-fi LED doesn't light in any circumstance, but this is not a problem, since the LED only lights in Windows 8 after installing the requiered drivers. In Windows 8 the Wi-Fi Fn key works by switching airplane mode ON/OFF and it works right after first boot (but no LED). In my case it doesn't work by default at all (even the code is not caught by any programs like easystroke, etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1245371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245200] Re: [HDA-Intel - HDA Intel, playback] No sound at all
https://launchpad.net/~diwic/+archive/hda just plug in headphone and run the test the value returned yes for the node repeat the test with the Mic plugged in in theory, you have to find out the missing node of the speaker by trial and error with hda-jack-retask those unconnected pin complex with pin cap support output to speaker one at a time but some time you need to trigger those gpio http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/Documentation/sound/alsa /HD-Audio.txt http://git.alsa-project.org/?p=alsa-tools.git;a=blob_plain;f=hdajackretask/README;h=68f62b166d2a8411f027f89ed9913d8e0ee58996;hb=HEAD -- 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/1245200 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound on anything whether playing cd/dvd or listening to music /radio there's just no sound, i have an hda-intel ALC260 on a philips freevents laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio CurrentDmesg: [ 142.597606] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [ 226.036095] usb 3-1: USB disconnect, device number 2 [ 267.538113] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:90:01:3b:8f:f5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Date: Sun Oct 27 14:54:41 2013 InstallationDate: Installed on 2013-10-26 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True 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:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2187 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080013:bd05/10/2006:svnDIXONSXP:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: DIXONSXP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245278] Re: Shift+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy
*** This bug is a duplicate of bug 1244548 *** https://bugs.launchpad.net/bugs/1244548 ** This bug has been marked a duplicate of bug 1244548 Keyboard shortcut for changing keyboard layout does not work on lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1245278 Title: Shift+Shift hotkey for keyboard layout switching do not work in gnome- screensaver in Saucy Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Shift+Shift hotkey for keyboard layout change does not work in GNOME screensaver of Ubuntu 13.10. This hotkey combination is set with packages from ppa:attente/1218322. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Mon Oct 28 01:15:08 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-20 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245256] Re: Alt+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy
*** This bug is a duplicate of bug 1244548 *** https://bugs.launchpad.net/bugs/1244548 ** This bug has been marked a duplicate of bug 1244548 Keyboard shortcut for changing keyboard layout does not work on lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1245256 Title: Alt+Shift hotkey for keyboard layout switching do not work in gnome- screensaver in Saucy Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Alt+Shift hotkey for keyboard layout change does not work in GNOME screensaver of Ubuntu 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sun Oct 27 23:07:25 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-20 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245270] Re: Ctrl+Shift hotkey for keyboard layout switching do not work in gnome-screensaver in Saucy
*** This bug is a duplicate of bug 1244548 *** https://bugs.launchpad.net/bugs/1244548 ** This bug has been marked a duplicate of bug 1244548 Keyboard shortcut for changing keyboard layout does not work on lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1245270 Title: Ctrl+Shift hotkey for keyboard layout switching do not work in gnome- screensaver in Saucy Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Ctrl+Shift hotkey for keyboard layout change does not work in GNOME screensaver of Ubuntu 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Mon Oct 28 00:15:19 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-20 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
Confirm this bug too, I am using EN and TH (Thai) layout. - This bug only affected libreoffice, removing libreoffice-{gnome,gtk} fix it as suggested by comment above. - Strangely, the Super+1 (switch to first application pinned to Dash) always not work (emitting ๅ instead). -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Committed Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242420] Re: Memory leak in Gimp 2.8.6
*** This bug is a duplicate of bug 1199877 *** https://bugs.launchpad.net/bugs/1199877 Thank you for your reply. I'll mark this bug as duplicate of bug #1199877. Please feel free to report any bug you find in Ubuntu! ** This bug has been marked a duplicate of bug 1199877 unity-panel-service memory leak and 100% CPU usage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1242420 Title: Memory leak in Gimp 2.8.6 Status in “gimp” package in Ubuntu: New Bug description: I just upgraded from 13.10 from 13.04. My wife is a professional photographer and relies on Gimp for the brunt of her editing. After the upgrade, the system would routinely slow to a crawl while she is working. This is on a modern system with 4GB of RAM. We started watching memory usage in Top while she edited to try to see what the problem was. Every time a new filter, plugin, tool, etc is used - the used memory goes up and the free memory goes down. When the tool/filter/plugin is finished, this memory is never freed back up. This continues all the way until we are using swap space and things then really slow to a crawl. Closing Gimp frees all of the memory, then it will work fine again for a while during use until all the free memory leaks over again, at which time she must save her work, close gimp and start again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1242420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1156530] [NEW] Edit connections fails to identify the changes made, immediately
You have been subscribed to a public bug: When you edit connections to say change the IPv4 address, the changes are not applied immediately after you click ok. They aren't applied until you remove and reinsert the network cable. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- Edit connections fails to identify the changes made, immediately https://bugs.launchpad.net/bugs/1156530 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
Forgot to mentioned the version of related packages in my machine gnome-control-center 3.6.3-0ubuntu45ppa1 gnome-settings-daemon 3.8.5-0ubuntu11.1 -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Committed Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029670] Re: *** glibc detected *** ./src/simple-scan: double free or corruption (fasttop): 0x00007f4f5c06dc90 ***
I also had this crash with the version installed for ubuntu 12.04, and also with version 2.6.0 and 3.6.1 on ubuntu 12.04 My scanner is an HP Deskjet F380 lsusb returns : Bus 002 Device 002: ID 03f0:5511 Hewlett-Packard DeskJet F300 series I joined crash log captured with 3.4.x (I dont remember) installed with 12.04 A+ ** Attachment added: crash log https://bugs.launchpad.net/simple-scan/+bug/1029670/+attachment/3893503/+files/simplescan-crash.txt.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1029670 Title: *** glibc detected *** ./src/simple-scan: double free or corruption (fasttop): 0x7f4f5c06dc90 *** Status in Simple Scan: Confirmed Status in “simple-scan” package in Ubuntu: Confirmed Bug description: I can readily reproduce this by doing the following: 1) Open simple-scan 2) scan a page 3) while some way through scanning the page, hit the cancel button and wait for it to finish 4) clicking the scan button now will crash the program The error appears as *** glibc detected *** ./src/simple-scan: double free or corruption (fasttop): 0x7f4f5c06dc90 *** i'll attach some data below. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1029670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245398] [NEW] Cannot enter non-latin password characters in lock screen if layout set to english before lock
Public bug reported: - Configure 2 keyboard layouts: - default: english - secondary: something else - Set your password to something containing non-english characters - Switch keyboard layout to English - Lock screen - Now you can't change keyboard layout on lock screen (hotkey does not work (#1244548) and there is no clickable layout indicator), so you can't enter password and unlock. For some reason, clickable layout indicator appears on lock screen only if non-english layout (or non-default layout?) is active before locking screen. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 12:54:09 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1245398 Title: Cannot enter non-latin password characters in lock screen if layout set to english before lock Status in “gnome-screensaver” package in Ubuntu: New Bug description: - Configure 2 keyboard layouts: - default: english - secondary: something else - Set your password to something containing non-english characters - Switch keyboard layout to English - Lock screen - Now you can't change keyboard layout on lock screen (hotkey does not work (#1244548) and there is no clickable layout indicator), so you can't enter password and unlock. For some reason, clickable layout indicator appears on lock screen only if non-english layout (or non-default layout?) is active before locking screen. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 12:54:09 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1156530] Re: Edit connections fails to identify the changes made, immediately
** Package changed: xubuntu-meta (Ubuntu) = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1156530 Title: Edit connections fails to identify the changes made, immediately Status in “network-manager-applet” package in Ubuntu: New Bug description: When you edit connections to say change the IPv4 address, the changes are not applied immediately after you click ok. They aren't applied until you remove and reinsert the network cable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1156530/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 688700] Re: gvfsd-sftp several minutes consumes all available CPU resources , if try connect to unreachable SSH host.
Looks like i just encountered this issue. I have a sftp host which was unaccessible for some time (ssh connection just hangs). The host started working but I was wondering why the computer felt slow. This is the reason (output from top): PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4742 vranki20 0 38208 3200 2720 S 49,8 0,0 15:37.13 gvfsd-sftp 4728 vranki20 0 38208 3192 2724 S 49,5 0,0 16:20.64 gvfsd-sftp 4558 vranki20 0 38208 3188 2724 S 49,2 0,0 17:17.47 gvfsd-sftp 4595 vranki20 0 38208 3200 2724 S 49,2 0,0 16:45.67 gvfsd-sftp 4530 vranki20 0 38208 3188 2716 S 48,8 0,0 18:01.79 gvfsd-sftp 4603 vranki20 0 38208 3192 2712 S 48,5 0,0 16:38.69 gvfsd-sftp 4585 vranki20 0 38208 3184 2716 S 45,2 0,0 16:40.84 gvfsd-sftp 4778 vranki20 0 38208 3204 2720 S 45,2 0,0 15:05.80 gvfsd-sftp 3783 vranki20 0 1117m 357m 45m S 5,3 4,6 6:22.19 firefox Looks like gfvsd-sftp does not handle the error condition properly and is stuck in busy loop. Backtrace of the situation (doesn't look very helpful): (gdb) bt #0 0xb77d6182 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0xb739f9db in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb74e82db in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb74d96d0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb74d9c2b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x0805571c in ?? () #6 0x0804c053 in ?? () #7 0xb72d6935 in __libc_start_main (main=0x804bfe0, argc=4, ubp_av=0xbfe802b4, init=0x80557b0, fini=0x8055820, rtld_fini=0xb77e4600 _dl_fini, stack_end=0xbfe802ac) at libc-start.c:260 #8 0x0804c079 in ?? () I'm not sure if the issue can be easily reproduced but there seems to be a bug. ** Changed in: gvfs (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/688700 Title: gvfsd-sftp several minutes consumes all available CPU resources , if try connect to unreachable SSH host. Status in “gvfs” package in Ubuntu: New Bug description: Binary package hint: gvfs gvfsd-sftp several minutes consumes all available CPU resources , if try connect to unreachable SSH host. Ubuntu 11.04 Natty x86 2.6.37-8-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/688700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 934347] Re: chromium-browser crashed with SIGSEGV in getaddrinfo()
*** This bug is a duplicate of bug 929219 *** https://bugs.launchpad.net/bugs/929219 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/934347 Title: chromium-browser crashed with SIGSEGV in getaddrinfo() Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: maybe related to https://bugs.launchpad.net/bugs/929219 [ 137.393836] chromium-browse[2276]: segfault at 17 ip 7faeb399cc2e sp 7faeb97fa5c0 error 6 in libc-2.15.so[7faeb3873000+1b1000] ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.56~r121963-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 17 18:17:49 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DuplicateOf: https://bugs.launchpad.net/bugs/931082 EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /usr/lib/chromium-browser/chromium-browser ProcEnviron: SegvAnalysis: Segfault happened at: 0x7faeb399cc2e:lock xadd %eax,0x18(%rdi) PC (0x7faeb399cc2e) ok source %eax ok destination 0x18(%rdi) (0x0017) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 getaddrinfo () from /lib/x86_64-linux-gnu/libc.so.6 ?? () Title: chromium-browser crashed with SIGSEGV in getaddrinfo() UpgradeStatus: Upgraded to precise on 2012-01-25 (23 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/934347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245412] [NEW] Enable/Disable Touchpad not working correctly
Public bug reported: I am on Ubuntu 13.10 amd64 and from the begining I noticed that every time the distro boots and, after login, the touchpad is active, even if before shutting it down I have had disabled it. This was not a problem in 13.04, if the laptop was shutt down with touchpad disabled it would have started with it disabled. Now of course I loved that, so I decided to make a tweak based on gsettings. I mean reading 'org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled' value at log out, saving it in a file, then, at login reading that value with a startup script and writing it to the same location. I didn't test it all the way, because when playing with 'gsettings set', 'gsettings get', and the Fn touchpad key I've noticed discrepancies in the settings read with dconf and the actual results of disabling/enabling touchpad with the Fn key. Disabling touchpad with keyboard, doesn't necessary change 'org.gnome .settings-daemon.peripherals.touchpad touchpad-enabled' value and the same way arround (at least not immedeatly). The syncronization is faulty. This is mostly likely the reason why Touchpad Indicator Extension (https://extensions.gnome.org/extension/131/touchpad-indicator/) does not work well (It is not able to reenable touchpad after mouse being unplugged). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 28 11:51:25 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: acpi-call, 20130623, 3.11.0-12-generic, x86_64: installed bbswitch, 0.7, 3.11.0-12-generic, x86_64: installed nvidia-304, 304.88, 3.11.0-12-generic, x86_64: installed tp-smapi, 0.41, 3.11.0-12-generic, x86_64: installed vboxhost, 4.3.0, 3.11.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1457] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-10-17 (10 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MachineType: ASUSTeK COMPUTER INC. K55VD MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=8bc18e61-3e17-496d-9cad-c098160e0e98 ro splash quiet acpi_osi=!Windows 2012 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD 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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A 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.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: Mon Oct 28 09:36:14 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9964 vendor AUO xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy 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/1245412 Title: Enable/Disable Touchpad not working correctly Status in “xorg” package in Ubuntu: New Bug description: I am on Ubuntu 13.10 amd64 and from the begining I noticed that every time the distro boots and, after login, the touchpad is active, even if before shutting it down I have had disabled it. This was not a problem in 13.04, if the laptop was shutt down
[Desktop-packages] [Bug 1245414] [NEW] Update to 25.0
Public bug reported: ... ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1245414 Title: Update to 25.0 Status in “firefox” package in Ubuntu: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1245414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245188] Re: Unable to set keyboard indicator to show alternative layout in gnome-control-center keyboard in Saucy
** Summary changed: - Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy + Unable to set keyboard indicator to show alternative layout in gnome-control-center keyboard in Saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1245188 Title: Unable to set keyboard indicator to show alternative layout in gnome- control-center keyboard in Saucy Status in GNOME Control Center: New Status in One Hundred Papercuts: Confirmed Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.04 I was able to set keyboard LED to show alternative layout in gnome-control-center keyboard (Caps Lock, Num Lock or Scroll Lock). In Ubuntu 13.10 I can't set it from gnome-control-center. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sun Oct 27 17:11:41 2013 InstallationDate: Installed on 2013-10-20 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1245188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 20622] Re: Rhythmbox Segfault on reading rhythmdb.xml file
This issue is not fixed in rhythmbox v2.99.1 (ubuntu 13.10 64bit, 3.11.0-13-generic ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/20622 Title: Rhythmbox Segfault on reading rhythmdb.xml file Status in “rhythmbox” package in Ubuntu: Fix Released Bug description: Rythmbox crashes on startup when reading database of music files, giving the following backtrace. #0 0x002a9a705902 in strcmp () from /lib/libc.so.6 #1 0x00444281 in g_sequence_get_ptr_at_pos () #2 0x004443f1 in g_sequence_insert_sorted () #3 0x0044c803 in rhythmdb_query_model_get_duration () #4 0x0044ccdb in rhythmdb_query_model_get_duration () #5 0x002a9a1c93c0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #6 0x002a9a1d7f2c in g_signal_stop_emission () from /usr/lib/libgobject-2.0.so.0 #7 0x002a9a1d93ec in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #8 0x002a9a1d97a3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #9 0x00448319 in rhythmdb_entry_song_get_type () #10 0x0044f849 in rhythmdb_tree_new () #11 0x002a977f5472 in xmlSkipBlankChars () from /usr/lib/libxml2.so.2 #12 0x002a978000e8 in xmlParseElement () from /usr/lib/libxml2.so.2 #13 0x002a977fe8c7 in xmlParseContent () from /usr/lib/libxml2.so.2 #14 0x002a978000a9 in xmlParseElement () from /usr/lib/libxml2.so.2 #15 0x002a9780074a in xmlParseDocument () from /usr/lib/libxml2.so.2 #16 0x0044e4c0 in rhythmdb_tree_get_type () #17 0x00446448 in rhythmdb_load () #18 0x0042431f in rb_shell_construct () #19 0x004205b1 in main () It crashes when a particular entry is present: entry type=song titleNever/title genreUnknown/genre artistCoil/artist albumUnnatural History (Compilation Tracks Compiled)/album track-number10/track-number duration276/duration file-size5353854/file-size locationfile:///home/ian/music/Coil/Unnatural%20History%20(Compilation%20Tracks%20Compiled)/10%20-%20Never.ogg/location mountpointfile:///home/mountpoint mtime1121962688/mtime first-seen1125081600/first-seen last-seen1125334930/last-seen rating2.64/rating auto-rate1/auto-rate play-count1/play-count last-played1124215108/last-played bitrate160/bitrate mimetypeapplication/ogg/mimetype /entry but works if the above is the only entry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/20622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245414] Re: Update to 25.0
** Branch linked: lp:~mozillateam/firefox/firefox.raring ** Branch linked: lp:~mozillateam/firefox/firefox.quantal ** Branch linked: lp:~mozillateam/firefox/firefox.precise -- 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/1245414 Title: Update to 25.0 Status in “firefox” package in Ubuntu: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1245414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1158781] Re: dom/plugins/test/test_crashing.html and dom/plugins/test/test_hanging.html mochitest failures
** Branch linked: lp:~mozillateam/firefox/firefox.raring ** Branch linked: lp:~mozillateam/firefox/firefox.quantal ** Branch linked: lp:~mozillateam/firefox/firefox.precise -- 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/1158781 Title: dom/plugins/test/test_crashing.html and dom/plugins/test/test_hanging.html mochitest failures Status in “firefox” package in Ubuntu: Fix Committed Bug description: 189207 INFO TEST-START | /tests/dom/plugins/test/test_crashing.html [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 Xlib: extension RANDR missing on display :99. XPCOM_MEM_BLOAT_LOG: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks.log Writing to log: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks_plugin_pid23781.log [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv 189208 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | p.crash() should throw an exception ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189209 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189210 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189211 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189212 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189213 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv 189214 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | p.setColor should throw after the plugin crashes [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 Xlib: extension RANDR missing on display :99. 189215 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | Reloading worked 189216 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/plugins/test/test_crashing.html | This test did not leave any crash dumps behind, but we were expecting some! 189217 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/plugins/test/test_crashing.html | This test left crash dumps behind, but we weren't expecting it to! 189218 INFO TEST-INFO | Found unexpected crash dump file /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/minidumps/635160c8-3f0b-e3a4-296a1862-204f9545.dmp. 189219 INFO TEST-INFO | Found unexpected crash dump file /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/minidumps/635160c8-3f0b-e3a4-296a1862-204f9545.extra. 189220 INFO TEST-END | /tests/dom/plugins/test/test_crashing.html | finished in 687ms 189513 INFO TEST-START | /tests/dom/plugins/test/test_hanging.html XPCOM_MEM_BLOAT_LOG: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks.log Writing to log: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks_plugin_pid23784.log [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 [Parent 21760] WARNING: Failed to deliver SIGKILL to 21808!(3).: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc, line 118 189514 INFO TEST-PASS | /tests/dom/plugins/test/test_hanging.html | p.hang() should throw an exception ###!!! [Parent][RPCChannel]
[Desktop-packages] [Bug 1194448] Re: js/xpconnect/tests/mochitest/test_sameOriginPolicy.html mochitest failure since about 24.0~a1~hg20130612r134700
** Branch linked: lp:~mozillateam/firefox/firefox.raring ** Branch linked: lp:~mozillateam/firefox/firefox.quantal ** Branch linked: lp:~mozillateam/firefox/firefox.precise -- 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/1194448 Title: js/xpconnect/tests/mochitest/test_sameOriginPolicy.html mochitest failure since about 24.0~a1~hg20130612r134700 Status in “firefox” package in Ubuntu: Fix Committed Bug description: 238231 INFO TEST-START | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html 238232 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | 0 is correctly (in)accessible for read 238233 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | window is correctly (in)accessible for read 238234 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | document is correctly (in)accessible for read 238235 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | InstallTrigger is correctly (in)accessible for read 238236 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | SpecialPowers is correctly (in)accessible for read 238237 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | SimpleTest is correctly (in)accessible for read 238238 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | parentRunner is correctly (in)accessible for read 238239 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isPrimaryTestWindow is correctly (in)accessible for read 238240 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | createEl is correctly (in)accessible for read 238241 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | ok is correctly (in)accessible for read 238242 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | is is correctly (in)accessible for read 238243 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isnot is correctly (in)accessible for read 238244 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | ise is correctly (in)accessible for read 238245 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | todo is correctly (in)accessible for read 238246 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | todo_is is correctly (in)accessible for read 238247 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | todo_isnot is correctly (in)accessible for read 238248 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isDeeply is correctly (in)accessible for read 238249 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | info is correctly (in)accessible for read 238250 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | gOldOnError is correctly (in)accessible for read 238251 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | repr is correctly (in)accessible for read 238252 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | partial is correctly (in)accessible for read 238253 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | getElement is correctly (in)accessible for read 238254 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | $ is correctly (in)accessible for read 238255 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | addLoadEvent is correctly (in)accessible for read 238256 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | computedStyle is correctly (in)accessible for read 238257 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | check is correctly (in)accessible for read 238258 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | crossOriginReadableWindowProps is correctly (in)accessible for read 238259 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isCrossOriginReadable is correctly (in)accessible for read 238260 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isCrossOriginWritable is correctly (in)accessible for read 238261 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | testAll is correctly (in)accessible for read 238262 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | loadCount is correctly (in)accessible for read 238263 INFO
[Desktop-packages] [Bug 989750] Re: repeatedly asks for encryption password when backing up, even though remember password is ticked
Can I add to this, I am expericeing this bug as well. It started occuring on 27 October 2013, just after Ubuntu had done a software update. I'm running Ubuntu 12.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/989750 Title: repeatedly asks for encryption password when backing up, even though remember password is ticked Status in “deja-dup” package in Ubuntu: Confirmed Bug description: I've set deja-dup to back up automatically, and to encrypt files. But it never gets far: every few seconds, it brings up a password needed window somewhere out of sight (behind other windows; but that is another problem/feature), even though I've told it to remember the password. So using this backup software seems entirely impractical; it will never finish. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 27 09:50:47 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/989750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245340] [NEW] Internal michrophone works only in System testing
You have been subscribed to a public bug: I have Packard Bell Dot S netbook (with internal microphone) To reproduce: 1. Start 'System Testing' 2. Select 'Audio tests' 3. During audio test note that you *can* hear yourself (but rather poorly, it's internal mic after all) 4. Go to Sound Settings, Tab-Input 5. 'Record sound from' is empty, input volume is grayed out. 6. Start audacity 7. Press record, speak, press stop 8. Press play 9. Nothing is audible What i expect to happen: If system testing was able to record from the internal mic, i expect other systems to be able to do that as well. What actually happens: System testing is able to perform tasks that other parts of the system are unable to do. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment microphone sound system-testing -- Internal michrophone works only in System testing https://bugs.launchpad.net/bugs/1245340 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243261] Re: apparent GPU hang on haswell laptop when playing movie on libreoffice
In addition to in slideshow mode in libreoffice, I confirmed this problem when playing high bitrate movies in fullscreen mode (any movie players). Interestingly, a mp4 movie pasted on a slide in libreoffice that hangs the GPU doesn't induce the same problem when it is played on a movie player. However, playing a high bitrate (say, a DVD iso) movie on a movie player hangs. Probably it occurs when GPU gets high load or sometime of buffer overflow (speculation). Perhaps this is a duplicate of other bugs observed on haswell's integrated GPUs. thanks. -- 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/1243261 Title: apparent GPU hang on haswell laptop when playing movie on libreoffice Status in “xorg” package in Ubuntu: New Bug description: How to reproduce: 1. open libreoffice - file - new - presentation 2. paste any movie; insert - movie this bug is quite reproducible and this movie file can be anything that libreoffice/gstreamer can play. 3. verify you correctly pasted the movie by selecting the movie in the slide and clicking the play botton bottom left. check if the movie *plays* ok. 4. then start slideshow from the slideshow menu or F5. Symptom: * a screen hang. this continues at least ten seconds or more. after that you can somehow quit the slideshow mode. * ESC and other keys do not stop the slideshow, except ctrl+alt+F1 * switching to VT and getting back to X helps sometimes. Configuration: * Thinkpad-X240s * tried both Saucy's default kernel and 3.11.6-031106 (ppa) dmesg: [ 2209.663234] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2214.672447] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2218.658213] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ .656003] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2226.653754] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2230.651538] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2234.649319] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2238.623129] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 2238.623162] [drm:i915_hangcheck_elapsed] *ERROR* no progress on render ring [ 2238.623300] [drm:i915_set_reset_status] *ERROR* render ring hung flushing bo (0x1d06e000 ctx 0) at 0x320b500 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Device 0a0c (rev 09) 00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-V (rev 04) 00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 (rev e4) 00:1c.1 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4) 00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5227 (rev 01) 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.11.6-031106-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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: Wed Oct 23 00:07:55 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2214] InstallationDate: Installed on 2013-10-22 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20AJA00P00 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.6-031106-generic root=UUID=30382826-322c-4457-a4a7-e6852d23ed8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1245414] Re: Update to 25.0
** Branch linked: lp:firefox/stable -- 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/1245414 Title: Update to 25.0 Status in “firefox” package in Ubuntu: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1245414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1194448] Re: js/xpconnect/tests/mochitest/test_sameOriginPolicy.html mochitest failure since about 24.0~a1~hg20130612r134700
** Branch linked: lp:firefox/stable -- 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/1194448 Title: js/xpconnect/tests/mochitest/test_sameOriginPolicy.html mochitest failure since about 24.0~a1~hg20130612r134700 Status in “firefox” package in Ubuntu: Fix Committed Bug description: 238231 INFO TEST-START | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html 238232 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | 0 is correctly (in)accessible for read 238233 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | window is correctly (in)accessible for read 238234 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | document is correctly (in)accessible for read 238235 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | InstallTrigger is correctly (in)accessible for read 238236 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | SpecialPowers is correctly (in)accessible for read 238237 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | SimpleTest is correctly (in)accessible for read 238238 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | parentRunner is correctly (in)accessible for read 238239 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isPrimaryTestWindow is correctly (in)accessible for read 238240 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | createEl is correctly (in)accessible for read 238241 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | ok is correctly (in)accessible for read 238242 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | is is correctly (in)accessible for read 238243 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isnot is correctly (in)accessible for read 238244 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | ise is correctly (in)accessible for read 238245 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | todo is correctly (in)accessible for read 238246 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | todo_is is correctly (in)accessible for read 238247 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | todo_isnot is correctly (in)accessible for read 238248 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isDeeply is correctly (in)accessible for read 238249 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | info is correctly (in)accessible for read 238250 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | gOldOnError is correctly (in)accessible for read 238251 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | repr is correctly (in)accessible for read 238252 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | partial is correctly (in)accessible for read 238253 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | getElement is correctly (in)accessible for read 238254 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | $ is correctly (in)accessible for read 238255 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | addLoadEvent is correctly (in)accessible for read 238256 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | computedStyle is correctly (in)accessible for read 238257 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | check is correctly (in)accessible for read 238258 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | crossOriginReadableWindowProps is correctly (in)accessible for read 238259 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isCrossOriginReadable is correctly (in)accessible for read 238260 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | isCrossOriginWritable is correctly (in)accessible for read 238261 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | testAll is correctly (in)accessible for read 238262 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | loadCount is correctly (in)accessible for read 238263 INFO TEST-PASS | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | go is correctly (in)accessible for read 238264 INFO TEST-PASS
[Desktop-packages] [Bug 1243806] Re: Folder names in Location area keeps the width (13.10)
confirm -- 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/1243806 Title: Folder names in Location area keeps the width (13.10) Status in “nautilus” package in Ubuntu: Confirmed Bug description: Folder names in Location area keeps the width even though when I go back to upper folder. First of all this new downgraded nautilus folder section holds its width and I cannot even change the width at all. Then when I go deep down lower folders or open folder with long name, it would squeeze down the Name part and I cannot even see names anymore. Then when I go up to upper folder or root, I cannot see the names anymore becaue location column takes up all the space. Once I click one of the unseen folder, I may see the names again. This is one of too many problems of 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243806] Re: Folder names in Location area keeps the width (13.10)
That is how it looks like. I can not change the width of any column. ** Attachment added: illustration https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+attachment/3893539/+files/Screenshot%20from%202013-10-28%2010%3A32%3A01.png -- 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/1243806 Title: Folder names in Location area keeps the width (13.10) Status in “nautilus” package in Ubuntu: Confirmed Bug description: Folder names in Location area keeps the width even though when I go back to upper folder. First of all this new downgraded nautilus folder section holds its width and I cannot even change the width at all. Then when I go deep down lower folders or open folder with long name, it would squeeze down the Name part and I cannot even see names anymore. Then when I go up to upper folder or root, I cannot see the names anymore becaue location column takes up all the space. Once I click one of the unseen folder, I may see the names again. This is one of too many problems of 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245340] Re: Internal michrophone works only in System testing
I don't know what package this is about. Let's try pulseaudio. ** Package changed: ubuntu = pulseaudio (Ubuntu) -- 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/1245340 Title: Internal michrophone works only in System testing Status in “pulseaudio” package in Ubuntu: New Bug description: I have Packard Bell Dot S netbook (with internal microphone) To reproduce: 1. Start 'System Testing' 2. Select 'Audio tests' 3. During audio test note that you *can* hear yourself (but rather poorly, it's internal mic after all) 4. Go to Sound Settings, Tab-Input 5. 'Record sound from' is empty, input volume is grayed out. 6. Start audacity 7. Press record, speak, press stop 8. Press play 9. Nothing is audible What i expect to happen: If system testing was able to record from the internal mic, i expect other systems to be able to do that as well. What actually happens: System testing is able to perform tasks that other parts of the system are unable to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1245340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243806] Re: Folder names in Location area keeps the width (13.10)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- 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/1243806 Title: Folder names in Location area keeps the width (13.10) Status in “nautilus” package in Ubuntu: Confirmed Bug description: Folder names in Location area keeps the width even though when I go back to upper folder. First of all this new downgraded nautilus folder section holds its width and I cannot even change the width at all. Then when I go deep down lower folders or open folder with long name, it would squeeze down the Name part and I cannot even see names anymore. Then when I go up to upper folder or root, I cannot see the names anymore becaue location column takes up all the space. Once I click one of the unseen folder, I may see the names again. This is one of too many problems of 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1158781] Re: dom/plugins/test/test_crashing.html and dom/plugins/test/test_hanging.html mochitest failures
** Branch linked: lp:firefox/stable -- 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/1158781 Title: dom/plugins/test/test_crashing.html and dom/plugins/test/test_hanging.html mochitest failures Status in “firefox” package in Ubuntu: Fix Committed Bug description: 189207 INFO TEST-START | /tests/dom/plugins/test/test_crashing.html [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 Xlib: extension RANDR missing on display :99. XPCOM_MEM_BLOAT_LOG: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks.log Writing to log: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks_plugin_pid23781.log [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv 189208 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | p.crash() should throw an exception ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189209 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189210 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189211 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189212 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv 189213 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | unknown identifier in crashed plugin should fail silently ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv 189214 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | p.setColor should throw after the plugin crashes [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 Xlib: extension RANDR missing on display :99. 189215 INFO TEST-PASS | /tests/dom/plugins/test/test_crashing.html | Reloading worked 189216 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/plugins/test/test_crashing.html | This test did not leave any crash dumps behind, but we were expecting some! 189217 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/plugins/test/test_crashing.html | This test left crash dumps behind, but we weren't expecting it to! 189218 INFO TEST-INFO | Found unexpected crash dump file /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/minidumps/635160c8-3f0b-e3a4-296a1862-204f9545.dmp. 189219 INFO TEST-INFO | Found unexpected crash dump file /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/minidumps/635160c8-3f0b-e3a4-296a1862-204f9545.extra. 189220 INFO TEST-END | /tests/dom/plugins/test/test_crashing.html | finished in 687ms 189513 INFO TEST-START | /tests/dom/plugins/test/test_hanging.html XPCOM_MEM_BLOAT_LOG: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks.log Writing to log: /tmp/tmp.oc17p3auwn/dsc0t-mochitest-testtmp/tmpdir/tmpr2x0HL/runtests_leaks_plugin_pid23784.log [Parent 21760] WARNING: waitpid failed pid:21808 errno:10: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/base/process_util_posix.cc, line 260 [Parent 21760] WARNING: Failed to deliver SIGKILL to 21808!(3).: file /build/buildd/firefox-20.0~b4+build1/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc, line 118 189514 INFO TEST-PASS | /tests/dom/plugins/test/test_hanging.html | p.hang() should throw an exception ###!!! [Parent][RPCChannel] Error: Channel timeout: cannot send/recv ###!!! [Parent][RPCChannel] Error: Channel timeout: cannot send/recv 189515 INFO TEST-PASS |
[Desktop-packages] [Bug 1245422] [NEW] Update to 24.1
Public bug reported: ... ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1245422 Title: Update to 24.1 Status in “thunderbird” package in Ubuntu: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1245422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** No longer affects: indicator-keyboard (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu Saucy) ** No longer affects: indicator-keyboard (Ubuntu Saucy) ** No longer affects: hundredpapercuts ** Project changed: indicator-keyboard = hundredpapercuts ** No longer affects: gnome-settings-daemon ** Project changed: hundredpapercuts = gnome-settings-daemon ** Changed in: gnome-settings-daemon Status: Invalid = Fix Committed -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Confirmed Status in Ubuntu GNOME: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working under greeter (https://bugs.launchpad.net/unity-greeter/+bug/1228207) * Lost ability to remap Caps Lock to Ctrl
[Desktop-packages] [Bug 1235785] Re: Light Display Manager is offered as login option
Same thing on me Ubuntu 13.10 64bit. -- 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/1235785 Title: Light Display Manager is offered as login option Status in “unity-greeter” package in Ubuntu: Triaged Bug description: Test case: Fresh install of current image (10/05 here Log in to guest account, log out Light Display Manager is now a login option ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 17:10:44 2013 InstallationDate: Installed on 2013-10-05 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131005) MarkForUpload: True SourcePackage: unity-greeter 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/1235785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245188] Re: Unable to set keyboard indicator to show alternative layout in gnome-control-center keyboard in Saucy
Trying to configure input method from the indicator, I'm able to see the control panel where to change from input layouts; so what really is going on is the control panel icon to be hidden. After been installed, it's the indicator-keyboard package the one which should tell the control panel to show that icon. ** Also affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-keyboard (Ubuntu) Status: New = Triaged ** Also affects: indicator-keyboard Importance: Undecided Status: New ** Changed in: indicator-keyboard Status: New = Confirmed ** Changed in: hundredpapercuts Status: Confirmed = Triaged ** Changed in: hundredpapercuts Assignee: (unassigned) = Papercuts Ninja (papercuts-ninja) ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed = Invalid ** Changed in: gnome-control-center Status: New = Invalid ** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: gnome-control-center ** Description changed: - In Ubuntu 12.04 I was able to set keyboard LED to show alternative layout in gnome-control-center keyboard (Caps Lock, Num Lock or Scroll Lock). + In Ubuntu 12.04 I was able to set keyboard indicator to show alternative layout in gnome-control-center keyboard (Caps Lock, Num Lock or Scroll Lock). In Ubuntu 13.10 I can't set it from gnome-control-center. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sun Oct 27 17:11:41 2013 InstallationDate: Installed on 2013-10-20 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: - activity-log-manager 0.9.7-0ubuntu4 - deja-dup 27.3.1-0ubuntu1 - gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 - gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 - gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 + activity-log-manager 0.9.7-0ubuntu4 + deja-dup 27.3.1-0ubuntu1 + gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 + gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 + gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1245188 Title: Unable to set keyboard indicator to show alternative layout in gnome- control-center keyboard in Saucy Status in One Hundred Papercuts: Triaged Status in Indicator keyboard: Confirmed Status in Ubuntu GNOME: Confirmed Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: In Ubuntu 12.04 I was able to set keyboard indicator to show alternative layout in gnome-control-center keyboard (Caps Lock, Num Lock or Scroll Lock). In Ubuntu 13.10 I can't set it from gnome-control-center. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Sun Oct 27 17:11:41 2013 InstallationDate: Installed on 2013-10-20 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1245188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu
It's best to use transition tracker: http://people.canonical.com/~ubuntu-archive/transitions/lcms2.html It shows proper dependencies rounds rathers information based on the archive state across both source and binary packages across all architectures. ** Description changed: Many packages in Ubuntu use the liblcms1 library (source package lcms). This library is discontinued upstream and replaced by liblcms2. Due to this, bugs in liblcms1 are not fixed any more upstream and important improvements in color reproduction and safety against crashes are not done. Therefore we should remove lcms1 and migrate all programs using it to lcms2. + + Launchpad doesn't usually scale to track transitions like these. Please see a tracker instead: + http://people.canonical.com/~ubuntu-archive/transitions/lcms2.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/885324 Title: Completely replace lcms1 by lcms2 in Ubuntu Status in digiKam - digital photo management: Fix Released Status in Enblend: Fix Released Status in Inkscape: A Vector Drawing Tool: Fix Released Status in Wine: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “dcraw” package in Ubuntu: New Status in “digikam” package in Ubuntu: Fix Released Status in “enblend” package in Ubuntu: New Status in “enblend-enfuse” package in Ubuntu: New Status in “f-spot” package in Ubuntu: Triaged Status in “geeqie” package in Ubuntu: New Status in “gimp” package in Ubuntu: Triaged Status in “imagemagick” package in Ubuntu: Fix Released Status in “inkscape” package in Ubuntu: Fix Released Status in “lcms” package in Ubuntu: New Status in “libkdcraw” package in Ubuntu: Fix Released Status in “libmng” package in Ubuntu: New Status in “libraw” package in Ubuntu: Fix Released Status in “openjdk-6” package in Ubuntu: New Status in “poppler” package in Ubuntu: Fix Released Status in “python-imaging” package in Ubuntu: New Status in “rawstudio” package in Ubuntu: New Status in “scribus” package in Ubuntu: New Status in “shotwell” package in Ubuntu: Fix Released Status in “ufraw” package in Ubuntu: New Status in “wine1.4” package in Ubuntu: Triaged Status in “xsane” package in Ubuntu: New Bug description: Many packages in Ubuntu use the liblcms1 library (source package lcms). This library is discontinued upstream and replaced by liblcms2. Due to this, bugs in liblcms1 are not fixed any more upstream and important improvements in color reproduction and safety against crashes are not done. Therefore we should remove lcms1 and migrate all programs using it to lcms2. Launchpad doesn't usually scale to track transitions like these. Please see a tracker instead: http://people.canonical.com/~ubuntu-archive/transitions/lcms2.html To manage notifications about this bug go to: https://bugs.launchpad.net/digikam/+bug/885324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Tags removed: verification-needed ** Tags added: verification-failed ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Committed = Triaged ** Changed in: gnome-settings-daemon (Ubuntu Saucy) Status: Fix Committed = Triaged ** Changed in: ubuntu-gnome Status: Fix Committed = Confirmed ** Changed in: gnome-settings-daemon Status: Fix Committed = Confirmed ** Changed in: gnome-settings-daemon (Ubuntu) Assignee: (unassigned) = William Hua (attente) ** Changed in: gnome-settings-daemon (Ubuntu Saucy) Assignee: (unassigned) = William Hua (attente) ** Changed in: gnome-settings-daemon Assignee: (unassigned) = William Hua (attente) -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Confirmed Status in Ubuntu GNOME: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working
[Desktop-packages] [Bug 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites
same problem here after few minutes i start using a browser. I thought it was zram related issue and upgraded the kernel to 3.12, but the problem persists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1184451 Title: Ubuntu 13.10 random screen freeze while Normal OS activites Status in “xorg-server” package in Ubuntu: Confirmed Bug description: I have recently, re-installed fresh ubuntu 13.10 distribution release. But everything worked fine. until recently i had strange problem of my display screen getting freezed randomly; but no response to either mouse/keyboard. But i want to point it out; it happens randomly and is not specific ? Other day, i had music player playing in background, but screen freezed. but my music was still running. Kindly note, i used multiple monitor setup and same issue of screen freeze also cropped up. I,am not sure, whether it is bug ? thanks for the expertise support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1234394] Re: I can't log off or shutdown witn gnome-panel ubuntu 13.10
Does this issue remain with the final release? (no problems here) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1234394 Title: I can't log off or shutdown witn gnome-panel ubuntu 13.10 Status in “gnome-panel” package in Ubuntu: New Bug description: I just installed a fresh ubuntu 13.10 last beta after that: sudo apt-get install gnome-panel then I log off and choos gnome panel flashback session with effects and then... Just try to shut down or log off under gnome-panel and u can't... is not working, no menu appear to logg off or shut down... IMPORTANT, IN A FRESH INSTALL OF UBUNTU 13.10 BETA 2 DE PROBLEM IS NOT THERE, BUT AFTER THAT IF YOU UPDATE UBUNTU 13.10 THE BUG WILL BE THERE AND YOU CANT LOG OFF OR SHUT DOWN.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1234394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
As for me, it also affect IntelliJ software. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Committed Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245433] [NEW] Ubuntu logs out when libreoffice calc opens and spotify is playing music
Public bug reported: Everytime I try to open calc while spotify is open on the background, Ubuntu logs off. It only happens once for every time the pc is restarted, that is, to replicate the unwanted log off, I need to restart the pc, open spotify and then try to open a calc file. I'm running Ubuntu 13.04, libreoffice-calc: 1:4.0.2-0ubuntu1 and the latest spotify release for Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-calc ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Mon Oct 28 11:52:59 2013 InstallationDate: Installed on 2013-08-28 (60 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug calc libreoffice raring spotify ** Description changed: Everytime I try to open calc while spotify is open on the background, Ubuntu logs off. I'm running Ubuntu 13.04, libreoffice-calc: 1:4.0.2-0ubuntu1 and the latest spotify release for Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 - Package: libreoffice (not installed) + Package: libreoffice-calc ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Mon Oct 28 11:52:59 2013 InstallationDate: Installed on 2013-08-28 (60 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Attachment removed: HookError_cloud_archive.txt https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1245433/+attachment/3893582/+files/HookError_cloud_archive.txt ** Description changed: Everytime I try to open calc while spotify is open on the background, - Ubuntu logs off. + Ubuntu logs off. It only happens once for every time the pc is + restarted, that is, to replicate the unwanted log off, I need to restart + the pc, open spotify and then try to open a calc file. I'm running Ubuntu 13.04, libreoffice-calc: 1:4.0.2-0ubuntu1 and the latest spotify release for Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-calc ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Mon Oct 28 11:52:59 2013 InstallationDate: Installed on 2013-08-28 (60 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1245433 Title: Ubuntu logs out when libreoffice calc opens and spotify is playing music Status in “libreoffice” package in Ubuntu: New Bug description: Everytime I try to open calc while spotify is open on the background, Ubuntu logs off. It only happens once for every time the pc is restarted, that is, to replicate the unwanted log off, I need to restart the pc, open spotify and then try to open a calc file. I'm running Ubuntu 13.04, libreoffice-calc: 1:4.0.2-0ubuntu1 and the latest spotify release for Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-calc ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Mon Oct 28 11:52:59 2013 InstallationDate: Installed on 2013-08-28 (60 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1245433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
As for me, when layout switching is set to Ctrl-Shift, it affects Ctrl- Shift-any-letter hotkeys. It wasn`t a problem in 13.04. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Confirmed Status in Ubuntu GNOME: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working under greeter (https://bugs.launchpad.net/unity-greeter/+bug/1228207) * Lost ability to remap Caps Lock to Ctrl (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/) * gnome-control-center keyboard no longer has way to modify caps lock key behavior (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224575) -- Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. Shift, CapsLock keys are just ignored in settings. Also the default shortcut was set to
[Desktop-packages] [Bug 1048485] Re: [ASUS P8Z77-V DELUXE, Realtek ALC898, Green Line Out, Rear] fails after a while
It appears to be fixed this time on 13.10. -- 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/1048485 Title: [ASUS P8Z77-V DELUXE, Realtek ALC898, Green Line Out, Rear] fails after a while Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: After playing some songs the audio corrupts forever until I go to gnome sound preferences and change the output to something else and them change back again to 5.1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: haz1882 F pulseaudio /dev/snd/pcmC0D0p: haz1882 F...m pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d1 irq 69' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0899,104384d8,0013 HDA:80862806,80860101,0010' Controls : 58 Simple ctrls : 24 CheckboxSubmission: c8ba500d34a6c43b0dbe757a75c54611 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Mon Sep 10 07:00:17 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 Precise Pangolin - amd64 (GNOME Shell Remix) PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en TERM=xterm PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio Interno - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, Realtek ALC898, Green Line Out, Rear] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1504 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1504:bd08/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1048485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244647] Re: LibreOffice not responsive for a while
Thanks. Now I have noticed that it seems that it is a more general graphical problem, I've seen this same behavior in evince. So I will close this bug and investigate further to see if I can reproduce it in my graphical environment. ** Changed in: libreoffice (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1244647 Title: LibreOffice not responsive for a while Status in “libreoffice” package in Ubuntu: Invalid Bug description: After upgrading to Ubuntu 13.10 (and the corresponding version of LibreOffice) I sometimes get irresponsiveness. By irresponsiveness I mean I click in the document and it takes more than 10 seconds for the cursor to move where I clicked. I have noticed this for Write and for Calc. For Write I have to close the document and open it again and it goes back to normal. For Calc if the unresponsiveness in all the window (I click in cells and it takes a while to respond), I have to close the document. Sometimes I also get irresponsiveness when a dialog opens. For instance I just had this while trying to change the name of a worksheet. I attach a video, the cursor that you see moving it's just me clicking in different places of the field, the cursor does not move. Closing and opening the window, sometimes more than once, gets the behavior back to normal. I don't see anything like this in any other application that I use. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice 1:4.1.2~rc3-0ubuntu1 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: Fri Oct 25 14:33:33 2013 InstallationDate: Installed on 2010-10-25 (1095 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to saucy on 2013-09-12 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1244647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1209306] Re: Webcam doesnt work cheese shows nothing
** Changed in: cheese (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1209306 Title: Webcam doesnt work cheese shows nothing Status in “cheese” package in Ubuntu: Incomplete Bug description: The cheese app doesnt show the webcam image. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cheese 3.6.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Wed Aug 7 18:16:06 2013 InstallationDate: Installed on 2013-08-07 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1209306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244231] Re: Package breaks unity with i915 because GLX cannot be loaded
I did some more digging, seems like a virtual package is to blame. libopencv-dev depends on libopencv-ocl-dev libopencv-ocl-dev depends on libopencv-ocl2.4 libopencv-ocl2.4 on the virtual package libopencl1, provided by nvidia-304, nvidia-304-updates, nvidia-319, nvidia-319-updates, ocl-icd- libopencl1 apt decided to use nvidia-319-updates, which broke the system. To fix this I removed all nvidia packages, along with libopencv-dev. Then installed ocl-icd-libopencl1, then libopencv-dev. Now all is good. In my opinion ocl-icd-libopencl1 should be chosen by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1244231 Title: Package breaks unity with i915 because GLX cannot be loaded Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: New Bug description: When nvidia-graphics-drivers-319-updates is installed I cannot log in into Unity because GLX cannot be loaded: From Xorg.0.log: [ 4872.070] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) This somewhat makes sense, because I do not have a NVIDIA card, but rather this: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 20e4 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 45 Region 0: Memory at f200 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4152 Capabilities: [d0] Power Management version 3 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 Once nvidia-graphics-drivers-319-updates is removed I can log in to Unity again. XFCE would work fine even with the package installed, but GLX would not be available. The reason nvidia-graphics-drivers-319-updates was installed is because I need libopencv-dev, which depends on nvidia-graphics- drivers-319-updates. So the problem is either that libopencv-dev depends on nvidia- graphics-drivers-319-updates, or that nvidia-graphics- drivers-319-updates breaks logging in with the Intel i915 card. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-319-updates (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 15:18:49 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-25 (272 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nvidia-graphics-drivers-319-updates UpgradeStatus: Upgraded to saucy on 2013-09-28 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1244231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1221403] Re: Pressing Caps Lock toggles LED even when mapped to another key
Norbert: see below. Also I should add that I switched this machine back to the non-xmir stack and the LED behaves as expected. Switching back to xmir (i.e. uncommenting type=unity in /etc/lightdm/lightdm.conf.d/10 -unity-system-compositor.conf) still exhibits the issue. $ cat /etc/default/keyboard # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=us XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1221403 Title: Pressing Caps Lock toggles LED even when mapped to another key Status in “xorg-server” package in Ubuntu: New Bug description: I have the the Caps Lock and Esc keys swapped; that is, pressing Caps Lock generates an Esc keycode and vice versa. This was done using the options in the keyboard settings, which seem to have disappeared recently. With this setup, pressing either the Esc and Caps Lock keys will toggle the Caps Lock LED. As a result the LED does not accurately reflect the state of the caps lock function. My expectation is that only the key which toggles the caps lock function (in this case Esc) should toggle the LED, and that the state of the LED should always accurately reflect the state of the caps lock function. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-system-compositor 0.0.1+13.10.20130903-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Thu Sep 5 14:04:28 2013 EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00eb] InstallationDate: Installed on 2012-10-24 (316 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) LightDMLog: Error: [Errno 13] Permission denied: '/var/log/lightdm/lightdm.log' MarkForUpload: True SourcePackage: unity-system-compositor UnitySystemCompositorLog: Error: [Errno 13] Permission denied: '/var/log/lightdm/unity-system-compositor.log' UpgradeStatus: Upgraded to saucy on 2013-05-01 (127 days ago) version.libdrm: libdrm2 2.4.46-1 version.lightdm: lightdm 1.7.12-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1221403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
Ahmed, does your /usr/share/applications/eclipse.desktop look like this?: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) Expected: The content of the submenus show up Actual: Only the top-level headers seem to be available. Nothing happens when I click on them either. They don't show up in the HUD either. It worked fine on 13.04, so I'm not sure what changed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245433] Re: Ubuntu logs out when libreoffice calc opens and spotify is playing music
Diogo Almeida, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect 1245433 ** Package changed: libreoffice (Ubuntu) = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- 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/1245433 Title: Ubuntu logs out when libreoffice calc opens and spotify is playing music Status in “xorg” package in Ubuntu: Incomplete Bug description: Everytime I try to open calc while spotify is open on the background, Ubuntu logs off. It only happens once for every time the pc is restarted, that is, to replicate the unwanted log off, I need to restart the pc, open spotify and then try to open a calc file. I'm running Ubuntu 13.04, libreoffice-calc: 1:4.0.2-0ubuntu1 and the latest spotify release for Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-calc ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Mon Oct 28 11:52:59 2013 InstallationDate: Installed on 2013-08-28 (60 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1245433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
** Description changed: - Steps to reproduce: + + HOW TO REPRODUCE + + 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) - Expected: The content of the submenus show up + ** + EXPECTED BEHAVIOUR + ** - Actual: Only the top-level headers seem to be available. Nothing happens - when I click on them either. They don't show up in the HUD either. + - The content of the submenus show up. - It worked fine on 13.04, so I'm not sure what changed. + ** + REAL BEHAVIOUR + ** + + - Only the top-level headers are available. + - Nothing happens when clicking on them + - They don't show up in the HUD either. + + *** + WORK-AROUND + *** + + To modify /usr/share/applications/eclipse.desktop to look like this: + + [Desktop Entry] + Type=Application + Name=Eclipse + Comment=Eclipse Integrated Development Environment + Icon=eclipse + Exec=env UBUNTU_MENUPROXY= eclipse + Terminal=false + Categories=Development;IDE;Java; + + + RELEVANT DETAILS + + + - Doesn't affect Ubuntu releases prior to 13.10. + + ** + TECHNICAL INFO + ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse 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 eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245354] Re: Screen keeps blinking after boot
Please don't create bug reports like this (that simply link to existing bugs). Both bugs are probably duplicate of: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- sis/+bug/1066464 See my PPA for patched SiS packages: https://launchpad.net/~dtl131/+archive/mediahacks Let us know if it works. Thanks. ** Changed in: xserver-xorg-video-sis (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-sis in Ubuntu. https://bugs.launchpad.net/bugs/1245354 Title: Screen keeps blinking after boot Status in “xserver-xorg-video-sis” package in Ubuntu: Incomplete Bug description: Please see below. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1245354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244617] Re: Graphics too slow after upgrading to 13.10
Could anybody guide me how to get around this? I can follow instructions even if they are too technical -- 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/1244617 Title: Graphics too slow after upgrading to 13.10 Status in “xorg” package in Ubuntu: New Bug description: System graphics are too slow. Alt+Tab takes a lot of time (seconds). Laptop heats up a lot. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 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: Fri Oct 25 16:03:42 2013 DistUpgraded: 2013-10-24 20:00:04,294 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, i686: installed virtualbox, 4.2.16, 3.5.0-15-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b0] InstallationDate: Installed on 2012-05-22 (520 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Inspiron N5110 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=5c4b011d-4bd3-4bf0-946a-b785d9b6981b ro recovery nomodeset SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-24 (0 days ago) dmi.bios.date: 03/16/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 034W60 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/16/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 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.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
** Description changed: - Unmounting share from nautilus + + HOW TO REPRODUCE + + + 1. Open a Nautilus window. + 2. Open a new tab. + 3. In the new tab, navigate to a Samba share. + 4. A new entry for the share appears under Network in the left side panel. + 5. Close the new tab. + 6. In the left side panel, under Network, click the unmount icon next to Samba share entry. + + ** + EXPECTED BEHAVIOUR + ** + + - Samba share to be unmounted. + + ** + REAL BEHAVIOUR + ** + + - gvfsd-smb crashes. + - Get two alert boxes: + + 1. Oops! Something went wrong. + Unhandled error message: The connection is closed + + 2. Unable to unmount share name + The connection is closed + + ** + TECHNICAL INFO + ** ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 27 15:58:03 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-smb InstallationDate: Installed on 2013-07-20 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7 ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR=set - PATH=(custom, no user) - LANGUAGE=fr_FR - LANG=fr_FR.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR=set + PATH=(custom, no user) + LANGUAGE=fr_FR + LANG=fr_FR.UTF-8 SegvAnalysis: - Segfault happened at: 0x7fad3ebbfff1:cmpb $0x0,(%rax) - PC (0x7fad3ebbfff1) ok - source $0x0 ok - destination (%rax) (0x0170) not located in a known VMA region (needed writable region)! - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7fad3ebbfff1:cmpb $0x0,(%rax) + PC (0x7fad3ebbfff1) ok + source $0x0 ok + destination (%rax) (0x0170) not located in a known VMA region (needed writable region)! + Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 - ?? () - g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so - ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so - ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 + ?? () + g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so + ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so + ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Changed in: gvfs (Ubuntu) Status: Confirmed = Triaged ** Summary changed: - gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() + gvfsd-smb crashes when unmounted from Nautilus ** Summary changed: - gvfsd-smb crashes when unmounted from Nautilus + gvfsd-smb crashes when been unmounted from Nautilus ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: hundredpapercuts Importance: Undecided = Low ** Changed in: hundredpapercuts Status: Confirmed = Triaged ** Changed in: hundredpapercuts Assignee: (unassigned) = Papercuts Ninja (papercuts-ninja) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1205647 Title: gvfsd-smb crashes when been unmounted from Nautilus Status in GVFS: Unknown Status in One Hundred Papercuts: Triaged Status in “gvfs” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Open a Nautilus window. 2. Open a new tab. 3. In the new tab, navigate to a Samba share. 4. A new entry for the share appears under Network in the left side panel. 5. Close the new tab. 6. In the left side panel, under Network, click the unmount icon next to Samba share entry. ** EXPECTED BEHAVIOUR ** - Samba share to be unmounted. ** REAL BEHAVIOUR ** - gvfsd-smb crashes. - Get two alert boxes: 1. Oops! Something went wrong. Unhandled error message: The connection is closed 2. Unable to unmount share name The connection is closed ** TECHNICAL INFO ** ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 27 15:58:03
[Desktop-packages] [Bug 1034470] Re: Mouse pointer flicker or disappear when moving it with left mouse button down
I have the same mobo as rasmus, using the fb driver (xubuntu 12.04 32bit) causes some cursor flicker. It is really bad on the Scribus work area ( i.e. the page plus side area), making the program unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-fbdev in Ubuntu. https://bugs.launchpad.net/bugs/1034470 Title: Mouse pointer flicker or disappear when moving it with left mouse button down Status in “xserver-xorg-video-fbdev” package in Ubuntu: Confirmed Bug description: Acer Aspire One D270 (Intel Atom N2600, Intel NM10 Express, Intel GMA 3600). Xubuntu 12.04 (also reproduced on Ubuntu 12.04). Fresh install with latest updates. Problem appears when moving mouse pointer with left mouse button down. For example, when moving window by dragging its caption. Or when performing rectangular selection on Desktop. Or when dragging the scrollbar handle. When mouse pointer moving that way it flicker (blink) on every move. When I stop moving it (still holding left mouse button down) it disappears and appears again when I continue moving. Also it just disappears when I left-click without move and appears again only after mouse move. Interesting, that issue doesn't reproduces directly after the boot (or Xorg restart). No flickering when dragging windows, for example. However, after some program changes mouse cursor shape to animated rotating progress indicator (something like this http://cur.cursors- 4u.net/cursors/images6/cur593.gif) the curso begins to flicker when moving with button pressed (until next reboot or Xorg restart). Such program can be Update Manager or Ubuntu Software Center - they both switch mouse pointer shape to animated in progress indicator. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Wed Aug 8 20:10:39 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/1034470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245452] [NEW] package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2
Public bug reported: during do-release-upgrade on 12.10 system running on a ZaReason Teo netbook ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libufe-xidgetter0 2.4.7-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 CheckboxSubmission: 2578103fd90166afafd3eb329949e571 CheckboxSystem: 9a6d2af3ffb5e20526ca0ccf9ca2c0bf Date: Mon Oct 28 02:00:03 2013 DuplicateSignature: package:libufe-xidgetter0:2.4.7-0ubuntu0.2:ErrorMessage: subprocess dpkg-split returned error exit status 2 EcryptfsInUse: Yes ErrorMessage: ErrorMessage: subprocess dpkg-split returned error exit status 2 InstallationDate: Installed on 2013-09-24 (33 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True SourcePackage: unity-firefox-extension Title: package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-10-28 (0 days ago) ** Affects: unity-firefox-extension (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-firefox-extension in Ubuntu. https://bugs.launchpad.net/bugs/1245452 Title: package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 Status in “unity-firefox-extension” package in Ubuntu: New Bug description: during do-release-upgrade on 12.10 system running on a ZaReason Teo netbook ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libufe-xidgetter0 2.4.7-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 CheckboxSubmission: 2578103fd90166afafd3eb329949e571 CheckboxSystem: 9a6d2af3ffb5e20526ca0ccf9ca2c0bf Date: Mon Oct 28 02:00:03 2013 DuplicateSignature: package:libufe-xidgetter0:2.4.7-0ubuntu0.2:ErrorMessage: subprocess dpkg-split returned error exit status 2 EcryptfsInUse: Yes ErrorMessage: ErrorMessage: subprocess dpkg-split returned error exit status 2 InstallationDate: Installed on 2013-09-24 (33 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True SourcePackage: unity-firefox-extension Title: package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1245452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245452] Re: package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-firefox-extension in Ubuntu. https://bugs.launchpad.net/bugs/1245452 Title: package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 Status in “unity-firefox-extension” package in Ubuntu: New Bug description: during do-release-upgrade on 12.10 system running on a ZaReason Teo netbook ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libufe-xidgetter0 2.4.7-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 CheckboxSubmission: 2578103fd90166afafd3eb329949e571 CheckboxSystem: 9a6d2af3ffb5e20526ca0ccf9ca2c0bf Date: Mon Oct 28 02:00:03 2013 DuplicateSignature: package:libufe-xidgetter0:2.4.7-0ubuntu0.2:ErrorMessage: subprocess dpkg-split returned error exit status 2 EcryptfsInUse: Yes ErrorMessage: ErrorMessage: subprocess dpkg-split returned error exit status 2 InstallationDate: Installed on 2013-09-24 (33 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True SourcePackage: unity-firefox-extension Title: package libufe-xidgetter0 2.4.7-0ubuntu0.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-split returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1245452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245226] Re: HDMI: audio-video playback too fast
** Package changed: gnome-control-center (Ubuntu) = alsa-driver (Ubuntu) ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- 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/1245226 Title: HDMI: audio-video playback too fast Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 13.10, selecting HDMI as audio output device is broken. Audio is played back at high speed. When playing back video clips, the video frames are also too fast. This is similar to an old bug I reported some time ago, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008 . In that case, adding radeon.audio=1 to the kernel command line solved. Now, the configuration is unchanged since when Ubuntu 13.04 was running $cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 vt.handoff=7 yet audio is broken. Note that, when selecting headphone as audio output device, everything works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 18:00:53 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2010-11-07 (1085 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244682] Re: package postgresql-9.1 9.1.9-0ubuntu12.04 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1
* Stopping PostgreSQL 8.4 database server ESC[112G ESC[31m*ESC[39;49m Error: Could not create log file /var/log/postgresql/postgresql-8.4-main.log Please show me the output of ls -ld /var /var/log/ /var/log/postgresql/ I suppose permissions on these got damaged somehow. ** Summary changed: - package postgresql-9.1 9.1.9-0ubuntu12.04 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 + package postgresql-9.1 9.1.9-0ubuntu12.04 failed to install/upgrade: could not create log file ** Changed in: postgresql-9.1 (Ubuntu) Status: New = Incomplete -- 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/1244682 Title: package postgresql-9.1 9.1.9-0ubuntu12.04 failed to install/upgrade: could not create log file Status in “postgresql-9.1” package in Ubuntu: Incomplete Bug description: Estaba trabajando en google chorme ProblemType: Package DistroRelease: Ubuntu 12.04 Package: postgresql-9.1 9.1.9-0ubuntu12.04 ProcVersionSignature: Ubuntu 3.2.0-44.69-generic 3.2.44 Uname: Linux 3.2.0-44-generic i686 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Fri Oct 25 09:14:17 2013 DuplicateSignature: package:postgresql-9.1:9.1.9-0ubuntu12.04:el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 MarkForUpload: True SourcePackage: postgresql-9.1 Title: package postgresql-9.1 9.1.9-0ubuntu12.04 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1244682/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245456] [NEW] package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64
Public bug reported: doi ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libavcodec53 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 AptOrdering: libavcodec53: Install libavutil-extra-51: Configure libavcodec53: Configure Architecture: amd64 Date: Mon Oct 28 17:21:09 2013 DuplicateSignature: package:libavcodec53:(not installed):conflicting packages - not installing libavcodec53:amd64 ErrorMessage: conflicting packages - not installing libavcodec53:amd64 InstallationDate: Installed on 2013-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: libav Title: package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- 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/1245456 Title: package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64 Status in “libav” package in Ubuntu: New Bug description: doi ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libavcodec53 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 AptOrdering: libavcodec53: Install libavutil-extra-51: Configure libavcodec53: Configure Architecture: amd64 Date: Mon Oct 28 17:21:09 2013 DuplicateSignature: package:libavcodec53:(not installed):conflicting packages - not installing libavcodec53:amd64 ErrorMessage: conflicting packages - not installing libavcodec53:amd64 InstallationDate: Installed on 2013-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: libav Title: package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1245456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245456] Re: package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64
** 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/1245456 Title: package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64 Status in “libav” package in Ubuntu: New Bug description: doi ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libavcodec53 (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 AptOrdering: libavcodec53: Install libavutil-extra-51: Configure libavcodec53: Configure Architecture: amd64 Date: Mon Oct 28 17:21:09 2013 DuplicateSignature: package:libavcodec53:(not installed):conflicting packages - not installing libavcodec53:amd64 ErrorMessage: conflicting packages - not installing libavcodec53:amd64 InstallationDate: Installed on 2013-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: libav Title: package libavcodec53 (not installed) failed to install/upgrade: conflicting packages - not installing libavcodec53:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1245456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 14392] Re: [network-admin] WEP key stored in world-readable /etc/network/interfaces
I found that after doing a fresh install of 13.10 server, the wpa passphrase for the network used during install was stored in plain text in /etc/network/interfaces and by default the file has 644 permissions. As stated by the original creator, this is a potential security risk. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/14392 Title: [network-admin] WEP key stored in world-readable /etc/network/interfaces Status in “gnome-system-tools” package in Ubuntu: Fix Released Status in “wireless-tools” package in Ubuntu: Invalid Status in “gnome-system-tools” package in Debian: Incomplete Bug description: the WEP key is stored in cleartext in /etc/network/interfaces and the file has mode 644. I'd consider this a security breach. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/14392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245461] [NEW] Missing texlive-lang-finnish
Public bug reported: Finnish hyphenation support was previously provided by the package texlive-lang-finnish. It is however no longer available in the package manager in Ubuntu 13.10 Saucy Salamander. This seems to be mostly a documentation bug, as it seems that the features have been moved to the package texlive-lang-european. It would however be nice if this could be discovered more easily (who knows, perhaps this bug report will help). ** Affects: texlive-lang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1245461 Title: Missing texlive-lang-finnish Status in “texlive-lang” package in Ubuntu: New Bug description: Finnish hyphenation support was previously provided by the package texlive-lang-finnish. It is however no longer available in the package manager in Ubuntu 13.10 Saucy Salamander. This seems to be mostly a documentation bug, as it seems that the features have been moved to the package texlive-lang-european. It would however be nice if this could be discovered more easily (who knows, perhaps this bug report will help). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1245461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
The workaround with common-session allowed me to log in on my pbis activated machine as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245226] Re: HDMI: audio-video playback too fast
https://wiki.ubuntu.com/Audio/AlsaInfo https://wiki.ubuntu.com/PulseAudio/Log pactl list pactl stat -- 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/1245226 Title: HDMI: audio-video playback too fast Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 13.10, selecting HDMI as audio output device is broken. Audio is played back at high speed. When playing back video clips, the video frames are also too fast. This is similar to an old bug I reported some time ago, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008 . In that case, adding radeon.audio=1 to the kernel command line solved. Now, the configuration is unchanged since when Ubuntu 13.04 was running $cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 vt.handoff=7 yet audio is broken. Note that, when selecting headphone as audio output device, everything works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 18:00:53 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2010-11-07 (1085 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
I am experiencing some of the same problems as reported by Hife above. The disabled network problem doesn't happen every time I wake my machine up, but on some of the occasions when it does I also find that sleep is disabled from the menu and from the function key, although I can still sudo pm-suspend from the terminal. Rebooting from the Unity pull-down menu seems to be permanently disabled, regardless of whether networking or sleep are working, so I don't know if this is part of the same problem. -- 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/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245468] [NEW] libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash
Public bug reported: Newer Versions of libglib2.0-0 (2.38.0-1ubuntu1, saucy salamander, aka 13.10) causes eclipse/swt to crash. This is bug is triggered from an 'official' eclipse install. I haven't tried the eclipse that comes with ubuntu because it is not what a professional java programmer needs. Observed behaviour: - Eclipse regulary crashes (see included VM dumps). The bug is normally trigger by hitting a SWT Button (e.g. Search - File Search - Cancel Button). Expected behaviour: - libglib2.0-0 in saucy should work without any issue against a 'offical' eclipse/swt. ** Affects: glib Importance: Unknown Status: Unknown ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1245468 Title: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash Status in The G Library - GLib: Unknown Status in “glib2.0” package in Ubuntu: New Bug description: Newer Versions of libglib2.0-0 (2.38.0-1ubuntu1, saucy salamander, aka 13.10) causes eclipse/swt to crash. This is bug is triggered from an 'official' eclipse install. I haven't tried the eclipse that comes with ubuntu because it is not what a professional java programmer needs. Observed behaviour: - Eclipse regulary crashes (see included VM dumps). The bug is normally trigger by hitting a SWT Button (e.g. Search - File Search - Cancel Button). Expected behaviour: - libglib2.0-0 in saucy should work without any issue against a 'offical' eclipse/swt. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1245468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245468] Re: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash
** Attachment added: VM crash file (from oracle jdk 1.7.0_45) https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1245468/+attachment/3893687/+files/hs_err_pid17462.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1245468 Title: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash Status in The G Library - GLib: Unknown Status in “glib2.0” package in Ubuntu: New Bug description: Newer Versions of libglib2.0-0 (2.38.0-1ubuntu1, saucy salamander, aka 13.10) causes eclipse/swt to crash. This is bug is triggered from an 'official' eclipse install. I haven't tried the eclipse that comes with ubuntu because it is not what a professional java programmer needs. Observed behaviour: - Eclipse regulary crashes (see included VM dumps). The bug is normally trigger by hitting a SWT Button (e.g. Search - File Search - Cancel Button). Expected behaviour: - libglib2.0-0 in saucy should work without any issue against a 'offical' eclipse/swt. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1245468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245468] Re: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash
** Attachment added: Another VM crash file (from oracle jdk 1.7.0_45) https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1245468/+attachment/3893688/+files/hs_err_pid15380.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1245468 Title: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash Status in The G Library - GLib: Unknown Status in “glib2.0” package in Ubuntu: New Bug description: Newer Versions of libglib2.0-0 (2.38.0-1ubuntu1, saucy salamander, aka 13.10) causes eclipse/swt to crash. This is bug is triggered from an 'official' eclipse install. I haven't tried the eclipse that comes with ubuntu because it is not what a professional java programmer needs. Observed behaviour: - Eclipse regulary crashes (see included VM dumps). The bug is normally trigger by hitting a SWT Button (e.g. Search - File Search - Cancel Button). Expected behaviour: - libglib2.0-0 in saucy should work without any issue against a 'offical' eclipse/swt. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1245468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245473] [NEW] Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Public bug reported: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed saucy -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245468] Re: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash
** Bug watch added: Eclipse bugs #420499 https://bugs.eclipse.org/bugs/show_bug.cgi?id=420499 ** Also affects: glib via https://bugs.eclipse.org/bugs/show_bug.cgi?id=420499 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1245468 Title: libglib2.0-0 (2.38.0-1ubuntu1) causes eclipse/swt to crash Status in The G Library - GLib: Unknown Status in “glib2.0” package in Ubuntu: New Bug description: Newer Versions of libglib2.0-0 (2.38.0-1ubuntu1, saucy salamander, aka 13.10) causes eclipse/swt to crash. This is bug is triggered from an 'official' eclipse install. I haven't tried the eclipse that comes with ubuntu because it is not what a professional java programmer needs. Observed behaviour: - Eclipse regulary crashes (see included VM dumps). The bug is normally trigger by hitting a SWT Button (e.g. Search - File Search - Cancel Button). Expected behaviour: - libglib2.0-0 in saucy should work without any issue against a 'offical' eclipse/swt. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1245468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245477] [NEW] Show in folder for downloads does not work
Public bug reported: In almost freshly installed Ubuntu 13.10 nothing happens if Show in folder clicked for downloads, both clicking bottom panel dropdown menu or clicking link on chrome://downloads/. Related: #606544, but it is old and that report says that opening files does not work too. Opening files works for me, only show in folder does not work. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 29.0.1547.65-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:57:22 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Bug watch added: code.google.com/p/chromium/issues #19987 http://code.google.com/p/chromium/issues/detail?id=19987 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1245477 Title: Show in folder for downloads does not work Status in “chromium-browser” package in Ubuntu: New Bug description: In almost freshly installed Ubuntu 13.10 nothing happens if Show in folder clicked for downloads, both clicking bottom panel dropdown menu or clicking link on chrome://downloads/. Related: #606544, but it is old and that report says that opening files does not work too. Opening files works for me, only show in folder does not work. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 29.0.1547.65-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:57:22 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1245477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245477] Re: Show in folder for downloads does not work
Related: https://code.google.com/p/chromium/issues/detail?id=19987, but for non-GNOME/KDE Ubuntu systems. I use default desktop. Also: kolen@kolen-ThinkPad-L412:~/items$ mimeopen ~ Please choose a default application for files of type inode/directory 1) Files (nautilus-folder-handler) 2) Files (nautilus) 3) Disk Usage Analyzer (baobab) 4) Other... use application # Choosing 1 works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1245477 Title: Show in folder for downloads does not work Status in “chromium-browser” package in Ubuntu: New Bug description: In almost freshly installed Ubuntu 13.10 nothing happens if Show in folder clicked for downloads, both clicking bottom panel dropdown menu or clicking link on chrome://downloads/. Related: #606544, but it is old and that report says that opening files does not work too. Opening files works for me, only show in folder does not work. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 29.0.1547.65-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:57:22 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1245477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245155] Re: Menus are very slow to load
same here, too. Did an upgrade from 13.04 to 13.10 and all the menus are very slow (gimp, libreoffice, etcetera). the ugly solution is to disable the global menu stuff from unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1245155 Title: Menus are very slow to load Status in “gimp” package in Ubuntu: Confirmed Bug description: When trying to use menu (File - Edit - Select - etc) it takes at time over 10 sec to appear and further 3-5sec to load the drop down menus. Often when switching from another program the previous program is still there. This does not happen in other programs. This happens with one small file and with many big files open in Gimp. Gimp used to be nice and fast, even in 13.10. Not sure which update caused it to slow down, been running 13.10 beta for a while. Shortcuts work just fine, I just can't remember them all and therefore has to use the menu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gimp 2.8.6-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 10:29:30 2013 ExecutablePath: /usr/bin/gimp-2.8 InstallationDate: Installed on 2013-08-04 (83 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to saucy on 2013-08-19 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1245155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245213] Re: Wine doesn't find 32-bit OpenGL drivers
No, it's with wine 1.4-0ubuntu4.1 from Precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1245213 Title: Wine doesn't find 32-bit OpenGL drivers Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Incomplete Bug description: Wine doesn't find the 32-bit opengl drivers on a 64bit system. I have to use LD_PRELOAD to tell where the 32-bit opengl libs are, like this: $ LD_PRELOAD=/usr/lib32/nvidia-319-updates/libGL.so wine exefile.exe If I don't use this, I get this: X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your 32-bit OpenGL drivers haven't been installed correctly (using GL renderer GeForce 8800 GT/PCIe/SSE2, version 1.4 (2.1.2 NVIDIA 319.32)) Here's the needed info: 1) $ lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 2) $ apt-cache policy nvidia-319-updates nvidia-319-updates: Installed: 319.32-0ubuntu0.0.1 Candidate: 319.32-0ubuntu0.0.1 Version table: *** 319.32-0ubuntu0.0.1 0 500 http://ftp.astral.ro/mirrors/ubuntu.com/ubuntu/ precise-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 3) I expected the 32-bit opengl to be automatically loaded and the application to work 4) The app never loaded, and I found this in the output: err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your 32-bit OpenGL drivers haven't been installed correctly (using GL renderer GeForce 8800 GT/PCIe/SSE2, version 1.4 (2.1.2 NVIDIA 319.32)). err:d3d:WineD3D_CreateFakeGLContext Failed to find a suitable pixel format. err:d3d:wined3d_adapter_init Failed to get a GL context for adapter 0x1794f8. err:d3d:WineD3D_CreateFakeGLContext Failed to find a suitable pixel format. err:d3d:wined3d_adapter_init Failed to get a GL context for adapter 0x1794f8. I found another bug, #764200, that was opened against Natty, and expired. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-319-updates 319.32-0ubuntu0.0.1 [modified: usr/lib/nvidia-319-updates/alt_ld.so.conf] ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51 Uname: Linux 3.2.0-55-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Oct 27 17:56:11 2013 InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120327) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-319-updates UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1245213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245492] [NEW] Output window freezes when pressing record video
Public bug reported: When I open cheese, click the video icon, and Record a Video the display for the video/display output for the webcam freezes. The video is then never recorded and I am unable to also take pictures unless I restart cheese. This problem did not occur in Ubuntu 13.04 - which is why I created this new report. When running cheese from the terminal, I get the following output right after pressing Record a Video: (cheese:15522): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed (cheese:15522): cheese-WARNING **: Filter caps do not completely specify the output format (cheese:15522): cheese-WARNING **: Internal data flow error. The same happens (problem and terminal error) for another computer that I have where cheese also worked with Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cheese 3.8.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 15:11:31 2013 InstallationDate: Installed on 2013-10-18 (9 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1245492 Title: Output window freezes when pressing record video Status in “cheese” package in Ubuntu: New Bug description: When I open cheese, click the video icon, and Record a Video the display for the video/display output for the webcam freezes. The video is then never recorded and I am unable to also take pictures unless I restart cheese. This problem did not occur in Ubuntu 13.04 - which is why I created this new report. When running cheese from the terminal, I get the following output right after pressing Record a Video: (cheese:15522): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed (cheese:15522): cheese-WARNING **: Filter caps do not completely specify the output format (cheese:15522): cheese-WARNING **: Internal data flow error. The same happens (problem and terminal error) for another computer that I have where cheese also worked with Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cheese 3.8.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 15:11:31 2013 InstallationDate: Installed on 2013-10-18 (9 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1245492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp