[Desktop-packages] [Bug 1299322] Re: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all
This was the info before user tried ALSA dkms. I'm not sure why apport failed to capture this info... !!Sysfs Files !!--- /sys/class/sound/hwC0D0/init_pin_configs: 0x12 0x99a30140 0x14 0x90170110 0x15 0x0321101f 0x16 0x03211020 0x18 0x40030008 0x19 0x03a11030 0x1a 0x41f0 0x1b 0x41f0 0x1d 0x4101 0x1e 0x41f0 0x1f 0x41f0 /sys/class/sound/hwC0D0/driver_pin_configs: /sys/class/sound/hwC0D0/user_pin_configs: /sys/class/sound/hwC0D0/init_verbs: /sys/class/sound/hwC0D0/hints: /sys/class/sound/hwC1D0/init_pin_configs: 0x04 0x585600f0 0x05 0x185600f0 0x06 0x585600f0 0x07 0x185600f0 /sys/class/sound/hwC1D0/driver_pin_configs: /sys/class/sound/hwC1D0/user_pin_configs: /sys/class/sound/hwC1D0/init_verbs: /sys/class/sound/hwC1D0/hints: -- 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/1299322 Title: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: To get any sound out of the speakers I need to close the lid of the laptop, let it go to sleep, then re-open it. When I unlock the computer the sound will then work from the speakers. Sound from the speakers is not using all of the speakers, and appears to only come out the subwoofer channel or center channel on the bottom of the laptop. There's no sound from the 'speakers' on the front. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 2265 F pulseaudio /dev/snd/controlC0: kevin 2265 F pulseaudio Date: Fri Mar 28 23:16:26 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.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_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Alienware dmi.bios.version: A02 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A02 dmi.modalias: dmi:bvnAlienware:bvrA02:bd07/15/2013:svnAlienware:pnAlienware18:pvr1747:rvnAlienware:rn01W2J2:rvrA00:cvnAlienware:ct8:cvrA02: dmi.product.name: Alienware 18 dmi.product.version: 1747 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299363] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1286766 *** https://bugs.launchpad.net/bugs/1286766 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1286766, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1299363/+attachment/4050221/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1299363/+attachment/4050223/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1299363/+attachment/4050225/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1299363/+attachment/4050226/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1299363/+attachment/4050227/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1299363/+attachment/4050228/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1299363/+attachment/4050229/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1286766 nautilus crashed with SIGABRT in bsearch() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1299363 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in “nautilus” package in Ubuntu: New Bug description: Tried to start nautils through gksudo ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sat Mar 29 07:35:59 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcCmdline: nautilus Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1299363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1166540] Re: brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress()
Same bug with Ubuntu 14.04 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1166540 Title: brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress() Status in “brasero” package in Ubuntu: Confirmed Bug description: Brasero doesn't normalize the song from mp3 and when I close it I get this crash. So the way to reproduce this bug is trying to burn a Audio disc from mp3's and exiting while it is stalled. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: brasero 3.6.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 19:00:53 2013 ExecutablePath: /usr/bin/brasero InstallationDate: Installed on 2013-03-29 (10 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130328) MarkForUpload: True ProcCmdline: brasero SegvAnalysis: Segfault happened at: 0x7f83fb34a20e brasero_task_ctx_stop_progress+46: mov0x50(%rbx),%rdi PC (0x7f83fb34a20e) ok source 0x50(%rbx) (0x0050) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: brasero StacktraceTop: brasero_task_ctx_stop_progress () from /usr/lib/libbrasero-burn3.so.1 ?? () from /usr/lib/libbrasero-burn3.so.1 ?? () from /usr/lib/libbrasero-burn3.so.1 ?? () from /usr/lib/libbrasero-burn3.so.1 ?? () from /usr/lib/libbrasero-burn3.so.1 Title: brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1166540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299366] [NEW] PCI sound card not detected
Public bug reported:
Hi I have a sound card PCI Encore ENM232-6VIA 5.1 . I installe Ubuntu 12.04.4
LTS RElease 12.04 and it doesn recognise it (as a result there is no sound at
all...) . I have pulseaudio sw.
let me know if you need more information
Thank you!
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-18-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: U0x46d0x8c1 [USB Device 0x46d:0x8c1], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: boos 1923 F pulseaudio
/dev/snd/controlC1: boos 1923 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xeeffc000 irq 16'
Mixer name : 'Nvidia GPU 1c HDMI/DP'
Components : 'HDA:10de001c,10b0104a,00100100'
Controls : 14
Simple ctrls : 2
Card1.Amixer.info:
Card hw:1 'U0x46d0x8c1'/'USB Device 0x46d:0x8c1 at usb-:00:0b.1-3, high
speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:08c1'
Controls : 2
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 3072
Mono: Capture 1536 [50%] [24.00dB] [on]
Date: Sat Mar 29 10:12:37 2014
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N32-E SLI PLUS ACPI BIOS Revision 0801
dmi.board.name: P5N32-E SLI PLUS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIPLUSACPIBIOSRevision0801:bd07/06/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLIPLUS:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise running-unity
--
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/1299366
Title:
PCI sound card not detected
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
Hi I have a sound card PCI Encore ENM232-6VIA 5.1 . I installe Ubuntu 12.04.4
LTS RElease 12.04 and it doesn recognise it (as a result there is no sound at
all...) . I have pulseaudio sw.
let me know if you need more information
Thank you!
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-18-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: U0x46d0x8c1 [USB Device 0x46d:0x8c1], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: boos 1923 F pulseaudio
/dev/snd/controlC1: boos 1923 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xeeffc000 irq 16'
Mixer name : 'Nvidia GPU 1c HDMI/DP'
Components : 'HDA:10de001c,10b0104a,00100100'
Controls : 14
Simple ctrls : 2
Card1.Amixer.info:
Card hw:1 'U0x46d0x8c1'/'USB Device 0x46d:0x8c1 at usb-:00:0b.1-3, high
speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:08c1'
Controls : 2
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 3072
Mono: Capture 1536 [50%] [24.00dB] [on]
Date: Sat Mar 29 10:12:37 2014
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
[Desktop-packages] [Bug 799869] Re: vinagre crashed with SIGABRT in raise()
** Changed in: vinagre Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/799869 Title: vinagre crashed with SIGABRT in raise() Status in Vinagre: VNC client for GNOME: Expired Status in “vinagre” package in Ubuntu: Triaged Bug description: Binary package hint: vinagre Started a vinagre with vinagre pure-b5:1 in the background. Then tried to connect to a second VNC session (without closing the original or touching it in any way) with vinagre pure-b5:2, and the vinagre process crashed. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: vinagre 3.0.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Mon Jun 20 11:35:10 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/vinagre InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101206) ProcCmdline: vinagre pure-b5:1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LC_MESSAGES=en_US.utf8 LANG=en_US.utf8 LANGUAGE=en_US:en Signal: 6 SourcePackage: vinagre StacktraceTop: raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 abort () at abort.c:92 g_assertion_message (domain=value optimized out, file=value optimized out, line=value optimized out, func=0x7f5d6de6cff0 g_type_instance_get_private, message=0x1caada0 assertion failed: (parent_node-data NODE_REFCOUNT (parent_node) 0)) at /build/buildd/glib2.0-2.29.8/./glib/gtestutils.c:1425 g_assertion_message_expr (domain=0x7f5d6de6452e GLib-GObject, file=0x7f5d6de6ad58 /build/buildd/glib2.0-2.29.8/./gobject/gtype.c, line=4531, func=0x7f5d6de6cff0 g_type_instance_get_private, expr=value optimized out) at /build/buildd/glib2.0-2.29.8/./glib/gtestutils.c:1436 g_type_instance_get_private (instance=0x1b81aa0, private_type=29610912) at /build/buildd/glib2.0-2.29.8/./gobject/gtype.c:4531 Title: vinagre crashed with SIGABRT in raise() UpgradeStatus: Upgraded to oneiric on 2011-06-03 (17 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/vinagre/+bug/799869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299377] [NEW] Update to bug-fix release 3.0.2 in Trusty
Public bug reported: Overview of changes in Rhythmbox 3.0.2 == * Assorted bug fixes Bugs fixed: 678938 - Selectable text for playing song interferes with dragging by toolbar 692485 - application hangs clicking on devices with undefined playlist_path 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build 705105 - Rhythmbox while playing disables automatic screen lock 707144 - Rhythmbox doesn't support itmss:// links 707525 - Last.fm radio stations can't be properly deleted 707618 - Trying to play a file missing on disk crashes rhythmbox in rb-player-gst.c:516 708084 - podcast: Local file name is not escaped 708201 - Core dumped when running on Wayland 708341 - Transfer to mass storage player hangs after last song 710493 - Gdk assertion failed: invalid cairo image surface format 710832 - Removing a song from the Play Queue removes it from the Library 711285 - Cannot play remote files (sftp/gvfs) in library 712237 - Rhythmbox segfaults on broken cover images 712699 - Take into account the size of header button for column width 715177 - running rhythmbox-client --play-uri file:///path/to/song with rhythmbox closed only starts the app, not the song 719514 - cairo crash on playback whenever coverart search plugin is enabled 719777 - data: Add audio/mp4 as a supported mime-type 720116 - app menu: standardize Help/About/Quit 720217 - If transfer to device fails with non-sanitized filename, try with sanitized one 720819 - header: vertically centralize the Not playing label 721550 - License text contains obsolete FSF postal address 721758 - Please add search by genre 722069 - Incorrect links to the website 722782 - link to Rhythmbox Home Page is invalid 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() 724931 - rhythmbox crashed with SIGSEGV in rb_list_model_find() 725625 - Absolute Radio Stations Should No Longer Be Included as Default (not streaming outside of UK) 726167 - .linked class is set on toolbar buttons instead of their container Translation updates: - cs, courtesy of Marek Černocký - de, courtesy of Christian Kirbach - es, courtesy of Daniel Mustieles - fr, courtesy of Claude Paroz - gl, courtesy of Fran Dieguez - hu, courtesy of Gabor Kelemen - it, courtesy of Milo Casagrande - lt, courtesy of Aurimas Černius - pl, courtesy of Piotr Drąg - pt_BR, courtesy of Rafael Ferreira - pt, courtesy of Tiago S. - ru, courtesy of Yuri Myasoedov - sl, courtesy of Matej Urbančič - sr, courtesy of Мирослав Николић - sr@latin, courtesy of Miroslav Nikolić - zh_CN, courtesy of YunQiang Su ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: trusty upgrade-software-version -- 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/1299377 Title: Update to bug-fix release 3.0.2 in Trusty Status in “rhythmbox” package in Ubuntu: New Bug description: Overview of changes in Rhythmbox 3.0.2 == * Assorted bug fixes Bugs fixed: 678938 - Selectable text for playing song interferes with dragging by toolbar 692485 - application hangs clicking on devices with undefined playlist_path 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build 705105 - Rhythmbox while playing disables automatic screen lock 707144 - Rhythmbox doesn't support itmss:// links 707525 - Last.fm radio stations can't be properly deleted 707618 - Trying to play a file missing on disk crashes rhythmbox in rb-player-gst.c:516 708084 - podcast: Local file name is not escaped 708201 - Core dumped when running on Wayland 708341 - Transfer to mass storage player hangs after last song 710493 - Gdk assertion failed: invalid cairo image surface format 710832 - Removing a song from the Play Queue removes it from the Library 711285 - Cannot play remote files (sftp/gvfs) in library 712237 - Rhythmbox segfaults on broken cover images 712699 - Take into account the size of header button for column width 715177 - running rhythmbox-client --play-uri file:///path/to/song with rhythmbox closed only starts the app, not the song 719514 - cairo crash on playback whenever coverart search plugin is enabled 719777 - data: Add audio/mp4 as a supported mime-type 720116 - app menu: standardize Help/About/Quit 720217 - If transfer to device fails with non-sanitized filename, try with sanitized one 720819 - header: vertically centralize the Not playing label 721550 - License text contains obsolete FSF postal address 721758 - Please add search by genre 722069 - Incorrect links to the website 722782 - link to Rhythmbox Home Page is invalid 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() 724931 - rhythmbox crashed with SIGSEGV in
[Desktop-packages] [Bug 1299386] [NEW] LG Flatron IPS LED monitor resolution incorrect
Public bug reported: After starting up Fujitsu Siemen Amilo Pro laptop, connected to Flatron IPS LED monitor, this monitor's screen resolution does not show its native resolution of 1920x1080 but defaults to lower, laptop screen resolution. I have to reset at each session using xrandr command. Ubuntu does not recognise that the resolution needs to be that of the second separate monitor. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1299386 Title: LG Flatron IPS LED monitor resolution incorrect Status in “xorg-server” package in Ubuntu: New Bug description: After starting up Fujitsu Siemen Amilo Pro laptop, connected to Flatron IPS LED monitor, this monitor's screen resolution does not show its native resolution of 1920x1080 but defaults to lower, laptop screen resolution. I have to reset at each session using xrandr command. Ubuntu does not recognise that the resolution needs to be that of the second separate monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1299386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297101] Re: Window hide headers for the top panel Ubuntu and it is not possible to reset compiz
confirm bug on trusty x64 . If the window Libre office is not in full- screen mode, the header of the browser window closes top panel unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1297101 Title: Window hide headers for the top panel Ubuntu and it is not possible to reset compiz Status in Compiz: New Status in “compiz” package in Ubuntu: Incomplete Bug description: Window hide headers for the top panel Ubuntu and trying to replace/fix with CompizConfig Settings Manager (ccsm) disables plugin Unity (a system without launcher, the top panel, hotkeys). dropped: 1. through the standard reset compiz (ccsm-settings-reset on typical), 2. removing the config files: gconftool-2 --recursive-unset /apps/compiz-1 gconftool-2 --recursive-unset /apps/compizconfig-1 unity --reset rm -rf ~/.config/compiz-1/compizconfig/* 3. unity-tweak-tool --reset-unity The first method leads to disabling the plugin Unity (see above). Third - does not reset anything. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 25 10:14:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-19-generic, i686: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0da] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-03-22 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140321) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=9599876d-6f9c-484c-9444-6399762dd3c2 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P09AAN dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355V5X-S01RU dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 355V4C/356V4C/3445VC/3545VC dmi.product.version: P09AAN.031.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 25 10:10:51 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1297101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295665] Re: Can't change desktop resolution (xrandr and desktop app)
** Summary changed: - changing resolution with menu or with xrandr command fails + Can't change desktop resolution (xrandr and desktop app) ** Tags added: resolution xrandr ** Package changed: xorg (Ubuntu) = libxrandr (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/1295665 Title: Can't change desktop resolution (xrandr and desktop app) Status in “libxrandr” package in Ubuntu: New Bug description: When changing resolution with menu or with xrandr command fails. Random colors and figures appear on the screen. I have tried both xorg-ati and fglrx drivers and the problem appears. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-18.38-lowlatency 3.13.6 Uname: Linux 3.13.0-18-lowlatency x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 21 13:48:28 2014 DistUpgraded: 2014-03-07 12:48:53,211 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-18-lowlatency, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-lowlatency, x86_64: installed virtualbox, 4.3.6, 3.13.0-18-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244] InstallationDate: Installed on 2014-02-08 (40 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-lowlatency root=UUID=94224f17-82cd-44ee-91a4-2243806ae66c ro debug ignore_loglevel crashkernel=384M-:128M SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-03-07 (14 days ago) dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V19.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD65 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV19.9:bd10/08/2012:svnMSI:pnMS-7640:pvr3.0:rvnMSI:rn990FXA-GD65(MS-7640):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7640 dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 21 13:46:31 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 9 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1295665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294311] Re: Compiz process continuously uses too much cpu.
Hi, After upgrading compiz to 1:0.9.11+14.04.20140328-0ubuntu1, important improvements to solve this have been achieved. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1294311 Title: Compiz process continuously uses too much cpu. Status in “compiz” package in Ubuntu: New Bug description: cpu = AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ ram = 6GB uname -r Linux 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:44:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy compiz compiz: Instaŀlat: 1:0.9.11+14.04.20140310-0ubuntu1 Candidat: 1:0.9.11+14.04.20140310-0ubuntu1 Taula de versió: *** 1:0.9.11+14.04.20140310-0ubuntu1 0 500 http://es.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Compiz proces is always using too much cpu. Some examples: - When I use ALT+F2 and I type something compiz uses 170% cpu. - When I use ALT+TAB compiz uses 120% cpu. - While I'm writing this text compiz is using 30% cpu - My system running only a terminal with top but compiz using 12% cpu ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140310-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 18 20:01:47 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G72 [GeForce 7200 GS / 7300 SE] [10de:01d3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:5001] InstallationDate: Installed on 2014-03-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7369 ProcEnviron: LANGUAGE=ca PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic root=UUID=65b6b4ee-5d53-4762-8b40-e5d13e0035c3 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7369 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV2.9:bd03/17/2009:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7369 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 18 19:55:32 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1294311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1298737] Re: Disabling screen on 14.04
** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) = Vitaliy (tsvitaliy) -- 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/1298737 Title: Disabling screen on 14.04 Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 amd64 gnome-screensaver 3.6.1 Doesn't work Disabling screen on locking screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1298737/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock screen
** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) = Vitaliy (tsvitaliy) -- 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/1244548 Title: Keyboard shortcut for changing keyboard layout does not work on lock screen Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Shortcut for changing keyboard layout does not work on lock screen (to change keyboard layout for entering password). - Switch to some non-english layout (otherwise lock screen will not have layout indicator at all) - Lock the screen - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it will not change layout - Clicking layout indicator near password entry box works -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 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 x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 11:01:10 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 (1 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/1244548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296017] Re: ALSA Not Selecting Correct Output Channel Map
@David With all due respect, I want to report a bug in ALSA, and I don't understand how joining a developers mailing list will further that goal. Please keep in mind I know very little about the whole Linux world, so where to go, and who to contact about a driver problem is... a problem :) The initial link I was given (https://bugs.launchpad.net/bugs/bugtrackers/alsa-mantis) took me to a page without any report bug action I could find. All roads link to https://bugtrack.alsa-project.org/alsa-bug; - a dead end. Search-engine-ing ALSA lead me here, where such a button existed. Clearly I need help in getting the right info to the right people. Including diagnostics on my limited-capability OS (http://openelec.tv/). Thank you for patience and any advice. -- 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/1296017 Title: ALSA Not Selecting Correct Output Channel Map Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Hi All As preface to this question, please know that I'm a complete noob with Linux - forgive my lack of understanding the basics, and any dumb questions that may give rise to. The issue - possible ALSA driver bug - is experienced when running xbmc, via OpenELEC. Playback of multichannel FLAC files is failing with 4.0-CH surround music (ie: Quadraphonic). PB fails inasmuch as xbmc sends the audio (MCH-PCM HDMI AVR) in a format incompatible with the AVR. After much dialogue with the relevant xbmc devs, I've been told this is a driver problem (ALSA), and to report it here at Launchpad. (FYI: discussion begins here - http://forum.xbmc.org/showthread.php?tid=170338pid=1638835#pid1638835, see posts by gjwAudio ) What Happens: 4.0 audio is output over HDMI as FL,FR,BL,BR, but my AVR does not recognize this format, and defaults to 2-CH (stereo) - no back channel information. What Should Happen: 4.0 audio should be sent as 5.1 PCM, with appropriate extra channels muted. Hypothesis: ALSA is not flagging 4.0 channel map as invalid for this receiver (based on audio-related EDID info), and xbmc configures 1:1 output mapping (FL,FR,BL,BR FL,FR,BL,BR). Testing in OpenELEC: Three FLAC sample files were used: 3.0, 4.0 and 5.1 channels. xbmc configured both 3.0 5.1 files as 5.1 PCM, and played correctly through the AVR. The 4.0 file was configured 1:1, and the back channels failed to play. When setting xbmc for global fixed output of 5.1 channels, all three files played correctly - however, this fixed setting also locks the sample rate, and forces unnecessary re-sampling, depending on the particular song being played. It also prevents legitimate upmixing of 2.0 video soundtracks to surround. The xbmc devs explain the behaviour thus: ( http://forum.xbmc.org/showthread.php?tid=170338pid=1651346#pid1651346 ) This happens when opening 3.0 (FL,FR,FC) - you can't have gaps, and in ALSA map, FC is at pos 5 (FL,FR,BL,BR,FC) - only even numbers of channels are allowed This is why 3.0 opens as 5.1. 4.0 as FL,FR,BL,BR is valid, and most devices don't have issues with this. We can't just open 5.1 for this case. --and-- (regarding the new audio engine ActiveAE) ( http://forum.xbmc.org/showthread.php?tid=170338pid=1651708#pid1651708 ) ActiveAE plays no role in this scenario. It is the ALSA sink and the driver. The driver should not open in 4.0 mode if the device does not support it. This needs to be fixed in the driver. Others will complain if we opened 4.0 as 5.1 because this would disable upmixing in the AVR. --and-- ( http://forum.xbmc.org/showthread.php?tid=170338pid=1655015#pid1655015 ) If you don't have configured fixed mode, XBMC tries to open the channels layout with best match to the input stream. In case this is FL,FR,BL,BR - which also matches ALSA channel map, we try to open this layout. If the audio device does not support this format, ALSA should fail opening. Then we try the next layout which would be 5.1 in this case. --and-- ( http://forum.xbmc.org/showthread.php?tid=170338pid=1655895#pid1655895 ) If ALSA opens that mask, then that's a driver problem and should be reported upstream to the ALSA devs. Testing in Windows: As another check on the xbmc audio output logic, I was asked to run the same FLACs through a Windows install (same beta release version of xbmc). All files played correctly under Windows. Please note the 5.1 PCM indicator lit up on the AVR, for every file. This suggests the correct EDID info was available to xbmc through the Windows driver(s). Linux Setup: OpenELEC v4.0 beta 2 (Gotham) - Generic x86_64; Intel 847 Celeron NUC, KVR1333D3S9/4G RAM, Kingston SMS200S3/30G mSATA 2m HDMI Anthem Statement D2 (AVR) Samsung PN51E6500. Windows Setup: xbmc v13.0 beta2 (Gotham), Asus X502C - i3-3217U, 4 GB RAM,
[Desktop-packages] [Bug 1293548] Re: Indicator disappears when switching to non default layout
Looking into it a bit more, it might be a GTK+ bug, but luckily it's easy enough to just fix it in libindicator. ** Also affects: libindicator Importance: Undecided Status: New ** Also affects: libindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1293548 Title: Indicator disappears when switching to non default layout Status in Libindicator: New Status in “indicator-keyboard” package in Ubuntu: Confirmed Status in “libindicator” package in Ubuntu: New Bug description: I am experiencing this problem with a non-default icon theme (Numix icons). I have two layouts: English and Latin American. When I switch layouts (with Shift+Shift_R) from English to Spanish, the indicator disappears. When I switch back to English, the indicator reappears. I've checked with adding a third layout, but the indicator won't show unless the layout is set to English (my default layout). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 08:31:59 2014 InstallationDate: Installed on 2014-03-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/1293548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296334] Re: please SRU and package rhythmbox v3.0.2 for Trusty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New = Confirmed -- 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/1296334 Title: Update to bug-fix release 3.0.2 in Trusty Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Upstream has released 3.0.2 of Rhythmbox. This is just a bug-fix release - see the NEWS for the release. - https://github.com/GNOME/rhythmbox/commit/72b998294cba6af6d6a1b8077482a9df1c787ac4 Overview of changes in Rhythmbox 3.0.2 == * Assorted bug fixes Bugs fixed: 678938 - Selectable text for playing song interferes with dragging by toolbar 692485 - application hangs clicking on devices with undefined playlist_path 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build 705105 - Rhythmbox while playing disables automatic screen lock 707144 - Rhythmbox doesn't support itmss:// links 707525 - Last.fm radio stations can't be properly deleted 707618 - Trying to play a file missing on disk crashes rhythmbox in rb-player-gst.c:516 708084 - podcast: Local file name is not escaped 708201 - Core dumped when running on Wayland 708341 - Transfer to mass storage player hangs after last song 710493 - Gdk assertion failed: invalid cairo image surface format 710832 - Removing a song from the Play Queue removes it from the Library 711285 - Cannot play remote files (sftp/gvfs) in library 712237 - Rhythmbox segfaults on broken cover images 712699 - Take into account the size of header button for column width 715177 - running rhythmbox-client --play-uri file:///path/to/song with rhythmbox closed only starts the app, not the song 719514 - cairo crash on playback whenever coverart search plugin is enabled 719777 - data: Add audio/mp4 as a supported mime-type 720116 - app menu: standardize Help/About/Quit 720217 - If transfer to device fails with non-sanitized filename, try with sanitized one 720819 - header: vertically centralize the Not playing label 721550 - License text contains obsolete FSF postal address 721758 - Please add search by genre 722069 - Incorrect links to the website 722782 - link to Rhythmbox Home Page is invalid 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() 724931 - rhythmbox crashed with SIGSEGV in rb_list_model_find() 725625 - Absolute Radio Stations Should No Longer Be Included as Default (not streaming outside of UK) 726167 - .linked class is set on toolbar buttons instead of their container Translation updates: - cs, courtesy of Marek Černocký - de, courtesy of Christian Kirbach - es, courtesy of Daniel Mustieles - fr, courtesy of Claude Paroz - gl, courtesy of Fran Dieguez - hu, courtesy of Gabor Kelemen - it, courtesy of Milo Casagrande - lt, courtesy of Aurimas Černius - pl, courtesy of Piotr Drąg - pt_BR, courtesy of Rafael Ferreira - pt, courtesy of Tiago S. - ru, courtesy of Yuri Myasoedov - sl, courtesy of Matej Urbančič - sr, courtesy of Мирослав Николић - sr@latin, courtesy of Miroslav Nikolić - zh_CN, courtesy of YunQiang Su As such, it is a perfect candidate to allow this in for an exception for Trusty given that we are still over a month away from release. I've confirmed that all current git patches included in Rhythmbox v3.0.1 in Trusty are included in this v3.0.2 release. Also I've confirmed that the Ubuntu specific patch work also works in v3.0.2 that is as follows: The debian/series file needs only contain the following entries - everything else in the v3.0.1 version can be removed from this file and the associated patches folder: 02_use_escaped_podcast_uri.patch 03_magnatune_partner.patch 05_hide_on_quit.patch 07_quicklists.patch 10_encoding_use_ubuntu_profiles.patch make-shuffle-repeat-proper-toggle-actions.patch restore-traditional-menubar.patch ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 16:54:24 2014 InstallationDate: Installed on 2014-02-22 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1296334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
I believe that so called #18 fix is not an actual solution. It disables multitouch features and makes your touchpad recognized as a normal mouse (and since touchpad doesn't come with separate physical scroll wheel, you won't get scrolling while using that option). You keep an ability to move your cursor and click, but that's not what I would call a usable touchpad. I wonder whether it's related specifically to the touchpad drivers, or is it just about the amount of cursor-related events which are sent to xorg? While it happens only with nvidia drivers, there migh be a possibility to fix it by pathing the touchpad-related protocols in psmouse kernel module or something in xorg (related to xrandr protocol, possibly?). ** Also affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in “nvidia-graphics-drivers-319” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Status in “nvidia-prime” package in Ubuntu: Opinion Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296017] Re: ALSA Not Selecting Correct Output Channel Map
@Raymond Sorry for slow reply. did you install libasound2-dev and compile chmap.c ? gcc chmap.c -o chmap -l asound OpenELEC (OE) is designed to do one thing - run xbmc - and the creators have stripped out much of the usual Linux environment, and block things like apt-get. I don't think there is any way to compile on OE. I am aware of the even-numbers-only channel mapping in ALSA, but thank you for pointing to a definitive reference. The upmix code you link to has no use in this discussion. As in post #8 above: Is there a way to compile chmap.c into a portable (standalone) script, that could be run on my OE machine ? Thanks again for your help. -- 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/1296017 Title: ALSA Not Selecting Correct Output Channel Map Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Hi All As preface to this question, please know that I'm a complete noob with Linux - forgive my lack of understanding the basics, and any dumb questions that may give rise to. The issue - possible ALSA driver bug - is experienced when running xbmc, via OpenELEC. Playback of multichannel FLAC files is failing with 4.0-CH surround music (ie: Quadraphonic). PB fails inasmuch as xbmc sends the audio (MCH-PCM HDMI AVR) in a format incompatible with the AVR. After much dialogue with the relevant xbmc devs, I've been told this is a driver problem (ALSA), and to report it here at Launchpad. (FYI: discussion begins here - http://forum.xbmc.org/showthread.php?tid=170338pid=1638835#pid1638835, see posts by gjwAudio ) What Happens: 4.0 audio is output over HDMI as FL,FR,BL,BR, but my AVR does not recognize this format, and defaults to 2-CH (stereo) - no back channel information. What Should Happen: 4.0 audio should be sent as 5.1 PCM, with appropriate extra channels muted. Hypothesis: ALSA is not flagging 4.0 channel map as invalid for this receiver (based on audio-related EDID info), and xbmc configures 1:1 output mapping (FL,FR,BL,BR FL,FR,BL,BR). Testing in OpenELEC: Three FLAC sample files were used: 3.0, 4.0 and 5.1 channels. xbmc configured both 3.0 5.1 files as 5.1 PCM, and played correctly through the AVR. The 4.0 file was configured 1:1, and the back channels failed to play. When setting xbmc for global fixed output of 5.1 channels, all three files played correctly - however, this fixed setting also locks the sample rate, and forces unnecessary re-sampling, depending on the particular song being played. It also prevents legitimate upmixing of 2.0 video soundtracks to surround. The xbmc devs explain the behaviour thus: ( http://forum.xbmc.org/showthread.php?tid=170338pid=1651346#pid1651346 ) This happens when opening 3.0 (FL,FR,FC) - you can't have gaps, and in ALSA map, FC is at pos 5 (FL,FR,BL,BR,FC) - only even numbers of channels are allowed This is why 3.0 opens as 5.1. 4.0 as FL,FR,BL,BR is valid, and most devices don't have issues with this. We can't just open 5.1 for this case. --and-- (regarding the new audio engine ActiveAE) ( http://forum.xbmc.org/showthread.php?tid=170338pid=1651708#pid1651708 ) ActiveAE plays no role in this scenario. It is the ALSA sink and the driver. The driver should not open in 4.0 mode if the device does not support it. This needs to be fixed in the driver. Others will complain if we opened 4.0 as 5.1 because this would disable upmixing in the AVR. --and-- ( http://forum.xbmc.org/showthread.php?tid=170338pid=1655015#pid1655015 ) If you don't have configured fixed mode, XBMC tries to open the channels layout with best match to the input stream. In case this is FL,FR,BL,BR - which also matches ALSA channel map, we try to open this layout. If the audio device does not support this format, ALSA should fail opening. Then we try the next layout which would be 5.1 in this case. --and-- ( http://forum.xbmc.org/showthread.php?tid=170338pid=1655895#pid1655895 ) If ALSA opens that mask, then that's a driver problem and should be reported upstream to the ALSA devs. Testing in Windows: As another check on the xbmc audio output logic, I was asked to run the same FLACs through a Windows install (same beta release version of xbmc). All files played correctly under Windows. Please note the 5.1 PCM indicator lit up on the AVR, for every file. This suggests the correct EDID info was available to xbmc through the Windows driver(s). Linux Setup: OpenELEC v4.0 beta 2 (Gotham) - Generic x86_64; Intel 847 Celeron NUC, KVR1333D3S9/4G RAM, Kingston SMS200S3/30G mSATA 2m HDMI Anthem Statement D2 (AVR) Samsung PN51E6500. Windows Setup: xbmc v13.0 beta2 (Gotham), Asus X502C - i3-3217U, 4 GB RAM, Intel HD 4000 graphics, Win 8.1 2m HDMI Anthem Statement D2 (AVR) Samsung PN51E6500. It is useful to
[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
I'm not sure if this fits into this particular bug, but maybe it helps to locate the problem... I have a netbook with Intel Atom N455 and GMA3150. The netbook has an external monitor attached to it via a KVM switch (USB mouse and keyboard, VGA) and has run Ubuntu since 11.10 (13.10 upto yesterday and now 14.04). The dual monitor setup has worked for nearly 2,5 years without any real issues. A few days ago, the external monitor broke. It was an old Samtron CRT which I ran at 1152x864/75 Hz. I got a new monitor, a LCD flatscreen with 1366x768, to replace it. Booting with the new monitor works. It shows the plymouth screen, LightDM's login screen and also Unity. But compiz now eats roughly 50% of the CPU as reported by top, and all graphical effects are utterly slow. This happened under 13.10 and now with 14.04 as well, with all updates installed. I've tried the things mentioned above and some others I've found while searching for this bug: - Renamed ~/.compiz folder. That actually worked once, but the high CPU usage was back after a reboot. Didn't do anything when I tried it again. - Disabled sync to vblank in CCSM. Didn't do anything. - CCSM - Preferences - Reset Unity profile. Worked, but high CPU usage was back after a reboot. - Set MESA_GL_VERSION_OVERRIDE=1.4 in /etc/environment. Didn't do anything. - Installed the latest packages from Oibaf's PPA. Didn't do anything. - Guest session instead of my regular account. Had high CPU usage as well. I then decided to install 14.04, hoping the bug would be fixed. Unfortunately, it's still there. BTW, /usr/lib/nux/unity_support_test -p shows (under 14.04): 8 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) IGD OpenGL version string: 1.4 Mesa 10.1.0 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes 8 I had yes everywhere under 13.10 as well, with both default mesa from the Ubuntu repositories and the version from Oibaf's PPA. Yesterday, after installing 14.04 and re-installing my favourite software packages, I got a few updates. Two dozen packages or so, including the 3.13.0-20-generic #42 kernel. I installed those and rebooted. After logging in, THE HIGH CPU USAGE WAS GONE. But after another reboot, compiz ate half the CPU again. Huh??? Anyway, I've now found a solution. Well, not really, but it works for now until the problem is properly fixed. I simply unplug the KVM switch's USB cable before booting to prevent the external monitor from being seen by the system. Once I'm logged in into Unity, I plug the KVM switch back in, then the external monitor turns on, the internal one turns off (as it should), and everything works as expected, without high CPU usage or slow graphical effects. I hope this helps someone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Confirmed Status in Release Notes for Ubuntu: Invalid Status in “mesa” package in Ubuntu: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True
[Desktop-packages] [Bug 1299392] [NEW] [A17, Conexant CX20585, Speaker, Internal] No sound at all
Public bug reported: No sound after ~30 min work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grinlin1632 F pulseaudio /dev/snd/pcmC0D0p: grinlin1632 F...m pulseaudio Date: Sat Mar 29 16:31:21 2014 InstallationDate: Installed on 2014-02-15 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grinlin1632 F pulseaudio /dev/snd/pcmC0D0p: grinlin1632 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [A17, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A17 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr202:bd08/03/2011:svnPEGATRONCORPORATION:pnA17:pvr1.0:rvnPEGATRONCORPORATION:rnA17:rvr1.0:cvnPEGATRONComputerInc.:ct9:cvr1.0: dmi.product.name: A17 dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1299392 Title: [A17, Conexant CX20585, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: No sound after ~30 min work ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grinlin1632 F pulseaudio /dev/snd/pcmC0D0p: grinlin1632 F...m pulseaudio Date: Sat Mar 29 16:31:21 2014 InstallationDate: Installed on 2014-02-15 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grinlin1632 F pulseaudio /dev/snd/pcmC0D0p: grinlin1632 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [A17, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A17 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr202:bd08/03/2011:svnPEGATRONCORPORATION:pnA17:pvr1.0:rvnPEGATRONCORPORATION:rnA17:rvr1.0:cvnPEGATRONComputerInc.:ct9:cvr1.0: dmi.product.name: A17 dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299396] [NEW] Sound break at high volume level
Public bug reported: While paying music when i increse the volume more than 70% sound start breaking.works ok in low volume ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic-pae 3.2.55 Uname: Linux 3.2.0-60-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aneesh 2098 F rhythmbox /dev/snd/pcmC0D0p: aneesh 2098 f...m rhythmbox /dev/snd/timer: aneesh 2098 F rhythmbox Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c0 irq 43' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0888,80860021,00100202 HDA:80862805,80860101,0010' Controls : 52 Simple ctrls : 23 CurrentDmesg: [ 22.150711] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 23.122759] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1600, was 1206 [ 32.719325] eth0: no IPv6 routers present [ 94.062970] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 0011, was 1600 Date: Sat Mar 29 15:17:16 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BC1DLP02 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DL-H61MXEL dmi.board.vendor: DIGILITE dmi.board.version: FAB 1.0 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.:bvrBC1DLP02:bd07/02/2012:svnDIGILITE:pnDL-H61MXEL:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXEL:rvrFAB1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: DL-H61MXEL dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: DIGILITE ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- 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/1299396 Title: Sound break at high volume level Status in “alsa-driver” package in Ubuntu: New Bug description: While paying music when i increse the volume more than 70% sound start breaking.works ok in low volume ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic-pae 3.2.55 Uname: Linux 3.2.0-60-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aneesh 2098 F rhythmbox /dev/snd/pcmC0D0p: aneesh 2098 f...m rhythmbox /dev/snd/timer: aneesh 2098 F rhythmbox Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c0 irq 43' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0888,80860021,00100202 HDA:80862805,80860101,0010' Controls : 52 Simple ctrls : 23 CurrentDmesg: [ 22.150711] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 23.122759] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 1600, was 1206 [ 32.719325] eth0: no IPv6 routers present [ 94.062970] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 0011, was 1600 Date: Sat Mar 29 15:17:16 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BC1DLP02 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DL-H61MXEL dmi.board.vendor: DIGILITE dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3
[Desktop-packages] [Bug 1299377] Re: Update to bug-fix release 3.0.2 in Trusty
*** This bug is a duplicate of bug 1296334 *** https://bugs.launchpad.net/bugs/1296334 ** This bug has been marked a duplicate of bug 1296334 Update to bug-fix release 3.0.2 in Trusty -- 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/1299377 Title: Update to bug-fix release 3.0.2 in Trusty Status in “rhythmbox” package in Ubuntu: New Bug description: Overview of changes in Rhythmbox 3.0.2 == * Assorted bug fixes Bugs fixed: 678938 - Selectable text for playing song interferes with dragging by toolbar 692485 - application hangs clicking on devices with undefined playlist_path 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build 705105 - Rhythmbox while playing disables automatic screen lock 707144 - Rhythmbox doesn't support itmss:// links 707525 - Last.fm radio stations can't be properly deleted 707618 - Trying to play a file missing on disk crashes rhythmbox in rb-player-gst.c:516 708084 - podcast: Local file name is not escaped 708201 - Core dumped when running on Wayland 708341 - Transfer to mass storage player hangs after last song 710493 - Gdk assertion failed: invalid cairo image surface format 710832 - Removing a song from the Play Queue removes it from the Library 711285 - Cannot play remote files (sftp/gvfs) in library 712237 - Rhythmbox segfaults on broken cover images 712699 - Take into account the size of header button for column width 715177 - running rhythmbox-client --play-uri file:///path/to/song with rhythmbox closed only starts the app, not the song 719514 - cairo crash on playback whenever coverart search plugin is enabled 719777 - data: Add audio/mp4 as a supported mime-type 720116 - app menu: standardize Help/About/Quit 720217 - If transfer to device fails with non-sanitized filename, try with sanitized one 720819 - header: vertically centralize the Not playing label 721550 - License text contains obsolete FSF postal address 721758 - Please add search by genre 722069 - Incorrect links to the website 722782 - link to Rhythmbox Home Page is invalid 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() 724931 - rhythmbox crashed with SIGSEGV in rb_list_model_find() 725625 - Absolute Radio Stations Should No Longer Be Included as Default (not streaming outside of UK) 726167 - .linked class is set on toolbar buttons instead of their container Translation updates: - cs, courtesy of Marek Černocký - de, courtesy of Christian Kirbach - es, courtesy of Daniel Mustieles - fr, courtesy of Claude Paroz - gl, courtesy of Fran Dieguez - hu, courtesy of Gabor Kelemen - it, courtesy of Milo Casagrande - lt, courtesy of Aurimas Černius - pl, courtesy of Piotr Drąg - pt_BR, courtesy of Rafael Ferreira - pt, courtesy of Tiago S. - ru, courtesy of Yuri Myasoedov - sl, courtesy of Matej Urbančič - sr, courtesy of Мирослав Николић - sr@latin, courtesy of Miroslav Nikolić - zh_CN, courtesy of YunQiang Su To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1299377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296334] Re: please SRU and package rhythmbox v3.0.2 for Trusty
** Tags added: upgrade-software-version ** Summary changed: - please SRU and package rhythmbox v3.0.2 for Trusty + Update to bug-fix release 3.0.2 in Trusty ** Description changed: - Upstream has released v3.0.2 of rhythmbox. + Upstream has released 3.0.2 of Rhythmbox. This is just a bug-fix release - see the NEWS for the release. - - + - https://github.com/GNOME/rhythmbox/commit/72b998294cba6af6d6a1b8077482a9df1c787ac4 - As such, it is a perfect candidate to allow this in for an exception for - Trusty given that we are still over a month away from release. + Overview of changes in Rhythmbox 3.0.2 + == + + * Assorted bug fixes + + Bugs fixed: + + 678938 - Selectable text for playing song interferes with dragging by toolbar + 692485 - application hangs clicking on devices with undefined playlist_path + 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build + 705105 - Rhythmbox while playing disables automatic screen lock + 707144 - Rhythmbox doesn't support itmss:// links + 707525 - Last.fm radio stations can't be properly deleted + 707618 - Trying to play a file missing on disk crashes rhythmbox in + rb-player-gst.c:516 + 708084 - podcast: Local file name is not escaped + 708201 - Core dumped when running on Wayland + 708341 - Transfer to mass storage player hangs after last song + 710493 - Gdk assertion failed: invalid cairo image surface format + 710832 - Removing a song from the Play Queue removes it from the Library + 711285 - Cannot play remote files (sftp/gvfs) in library + 712237 - Rhythmbox segfaults on broken cover images + 712699 - Take into account the size of header button for column width + 715177 - running rhythmbox-client --play-uri file:///path/to/song with + rhythmbox closed only starts the app, not the song + 719514 - cairo crash on playback whenever coverart search plugin is enabled + 719777 - data: Add audio/mp4 as a supported mime-type + 720116 - app menu: standardize Help/About/Quit + 720217 - If transfer to device fails with non-sanitized filename, try with + sanitized one + 720819 - header: vertically centralize the Not playing label + 721550 - License text contains obsolete FSF postal address + 721758 - Please add search by genre + 722069 - Incorrect links to the website + 722782 - link to Rhythmbox Home Page is invalid + 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() + 724931 - rhythmbox crashed with SIGSEGV in rb_list_model_find() + 725625 - Absolute Radio Stations Should No Longer Be Included as Default + (not streaming outside of UK) + 726167 - .linked class is set on toolbar buttons instead of their container + + Translation updates: + + - cs, courtesy of Marek Černocký + - de, courtesy of Christian Kirbach + - es, courtesy of Daniel Mustieles + - fr, courtesy of Claude Paroz + - gl, courtesy of Fran Dieguez + - hu, courtesy of Gabor Kelemen + - it, courtesy of Milo Casagrande + - lt, courtesy of Aurimas Černius + - pl, courtesy of Piotr Drąg + - pt_BR, courtesy of Rafael Ferreira + - pt, courtesy of Tiago S. + - ru, courtesy of Yuri Myasoedov + - sl, courtesy of Matej Urbančič + - sr, courtesy of Мирослав Николић + - sr@latin, courtesy of Miroslav Nikolić + - zh_CN, courtesy of YunQiang Su + + + As such, it is a perfect candidate to allow this in for an exception for Trusty given that we are still over a month away from release. I've confirmed that all current git patches included in Rhythmbox v3.0.1 in Trusty are included in this v3.0.2 release. Also I've confirmed that the Ubuntu specific patch work also works in v3.0.2 that is as follows: The debian/series file needs only contain the following entries - everything else in the v3.0.1 version can be removed from this file and the associated patches folder: 02_use_escaped_podcast_uri.patch 03_magnatune_partner.patch 05_hide_on_quit.patch 07_quicklists.patch 10_encoding_use_ubuntu_profiles.patch make-shuffle-repeat-proper-toggle-actions.patch restore-traditional-menubar.patch ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 16:54:24 2014 InstallationDate: Installed on 2014-02-22 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1) SourcePackage: rhythmbox 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 rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1296334 Title: Update to bug-fix release 3.0.2 in Trusty Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Upstream has released 3.0.2 of Rhythmbox. This is
[Desktop-packages] [Bug 956608] Re: unity-greeter crashed with signal 5 in g_settings_get_value()
This happened for me on reboot after doing a dist-upgrade to latest Trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/956608 Title: unity-greeter crashed with signal 5 in g_settings_get_value() Status in “unity-greeter” package in Ubuntu: Expired Bug description: Hm... I really don't know what exactly happened on this one... I was giving it to my system pretty hard when running World of Warcraft inside Wine on one virtual Desktop, Firefox on another with many tabs and thunderbird on a third desktop. One single Firefox window (chat non-java) was running on the fourth Desktop. The bug occured after i watched a Youtube Video in Fullscreen (flashplayer) on the virt. Desktop that had Firefox with the many tabs running when the flash video finished I had 2 crashed apps. this maybe some memory issue cause i probably used up all my memory but just in case it is not i submit these bugs. I add the second crash in the comments of this one. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-greeter 0.2.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Thu Mar 15 22:44:44 2012 ExecutablePath: /usr/sbin/unity-greeter InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /usr/sbin/unity-greeter ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: unity-greeter StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () Title: unity-greeter crashed with signal 5 in g_settings_get_value() UpgradeStatus: Upgraded to precise on 2012-03-14 (1 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/956608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1179049] Re: no vertical scrol bar, cannot resize graphical window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: baobab (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1179049 Title: no vertical scrol bar, cannot resize graphical window Status in “baobab” package in Ubuntu: Confirmed Bug description: If I descend into 4th level folders, I connet see the percentage and size anymore: * there is no possbility to disable the treeview * there is no vertical scroll bar * there is possibility to resize the treeview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1179049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175820] Re: disable treemap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: baobab (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1175820 Title: disable treemap Status in “baobab” package in Ubuntu: Confirmed Bug description: I need a analysis result without the graphic on the right part of the screen, That graphic occupies 1/2 part of the window. Thus it does not allow me to decend into 4th level diretories. Please add a possibility to disable the graphical window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1175820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239087] Re: Safely remove is not working (or broken) in Gnome Disks
** Changed in: gnome-disk-utility (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1239087 Title: Safely remove is not working (or broken) in Gnome Disks Status in GNOME Disks: Fix Released Status in abstraction for enumerating and managing block devices: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Fix Released Status in “gnome-disk-utility” package in Fedora: Unknown Status in “gnome-disk-utility” package in openSUSE: Confirmed Bug description: In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD (do a spin down). In 13.04 this option is missed. In 13.10 it is appeared again, but not working as expected: +Gnome Disks normally powers off the USB flash (tested on 4 different flashes and 2 USB cardreaders). - Gnome Disks does not spin down USB HDD (but udisks --detach does) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-disk-utility 3.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sat Oct 12 13:39:21 2013 InstallationDate: Installed on 2013-03-06 (219 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130306) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270574] Re: keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard
I got the same results today with Ubuntu 14.04 final beta (4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso). -- 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/1270574 Title: keyboard layout settings must be consistent between gnome-control- center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard Status in One Hundred Papercuts: Confirmed Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “gnome-tweak-tool” package in Ubuntu: Confirmed Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: Dear Ubuntu developers. Ubuntu 14.04 LTS will be released very soon. It seems that it will be based on GNOME 3.8 or 3.10 (you know exact version). It seems that because of modern GNOME Ubuntu users will have very reduced set of keyboard layout options. Previous Ubuntu LTS version (12.04) was based on GNOME 3.4 and have very wide spectrum of keyboard layout options. But in newer GNOME versions, on which for example, Ubuntu 13.10 is based, this options are very limited. Many options are moved from gnome-control-center keyboard to gnome- tweak-tool (see bug 1245064). I have suggested already to include gnome-tweak-tool in default Ubuntu 14.04 installation (see bug 1270572). But for now it seems that settings between gnome-tweak-tool, gnome-control-center and indicator-keyboard are not consistent. For example, if I set Use keyboard LED to show alternative layout to Scroll Lock on Typing section of gnome-tweak-tool the Scroll Lock does not indicate alternative keyboard layout as expected (it is a bug). So please, keep settings between gnome-tweak-tool, gnome-control- center and indicator-keyboard consistent. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 16:55:42 2014 InstallationDate: Installed on 2013-10-20 (90 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1270574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299410] [NEW] PCI/internal sound card not detected
Public bug reported: No audio through headphone audio channel (Intel Corporation Device) No HDMI/DP audio for Intel Lynx Point-LP HD Audio Controller Related (I think) to: Ubuntu “linux-lts-saucy” package Bugs Bug #1278265 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: hid_generic usbhid hid ahci r8169 libahci mii ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Mar 29 09:58:12 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MMLP3AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/29/2013:svnGIGABYTE:pnMMLP3AP-00:pvr1.x:rvnGIGABYTE:rnMMLP3AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: MMLP3AP-00 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-03-29T09:55:56.578768 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1299410 Title: PCI/internal sound card not detected Status in “alsa-driver” package in Ubuntu: New Bug description: No audio through headphone audio channel (Intel Corporation Device) No HDMI/DP audio for Intel Lynx Point-LP HD Audio Controller Related (I think) to: Ubuntu “linux-lts-saucy” package Bugs Bug #1278265 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: hid_generic usbhid hid ahci r8169 libahci mii ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Mar 29 09:58:12 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MMLP3AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/29/2013:svnGIGABYTE:pnMMLP3AP-00:pvr1.x:rvnGIGABYTE:rnMMLP3AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: MMLP3AP-00 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-03-29T09:55:56.578768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299409] [NEW] Crash when moving files to mtp android device (after some time)
Public bug reported: Syslog shows: Mar 29 11:15:41 Arbeits-PC kernel: [ 6791.820138] nautilus[7322]: segfault at 0 ip 7fa7dab4f0d9 sp 7fff8f2546b0 error 4 in libgtk-3.so.0.1000.7[7fa7da96d000+4ff000] ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- 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/1299409 Title: Crash when moving files to mtp android device (after some time) Status in “nautilus” package in Ubuntu: New Bug description: Syslog shows: Mar 29 11:15:41 Arbeits-PC kernel: [ 6791.820138] nautilus[7322]: segfault at 0 ip 7fa7dab4f0d9 sp 7fff8f2546b0 error 4 in libgtk-3.so.0.1000.7[7fa7da96d000+4ff000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1299409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286845] Re: Duplicity crashes with UnicodeEncode error
Hi, Same here, since the upgrade from 12.04 to 14.04 every scheduled backup fails with this error. PS My system language is Galician gl_ES.UTF-8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1286845 Title: Duplicity crashes with UnicodeEncode error Status in Déjà Dup Backup Tool: New Status in “duplicity” package in Ubuntu: Incomplete Bug description: When duplicity tries to do an incremental backup today it crashes with the following Traceback: Traceback (most recent call last): File /usr/bin/duplicity, line 1493, in module with_tempdir(main) File /usr/bin/duplicity, line 1487, in with_tempdir fn() File /usr/bin/duplicity, line 1336, in main do_backup(action) File /usr/bin/duplicity, line 1469, in do_backup incremental_backup(sig_chain) File /usr/bin/duplicity, line 656, in incremental_backup print_statistics(diffdir.stats, bytes_written) File /usr/bin/duplicity, line 594, in print_statistics print diffdir.stats.get_stats_logstring(_(Backup Statistics)) UnicodeEncodeError: 'ascii' codec can't encode character u'\xf6' in position 27: ordinal not in range(128) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: duplicity 0.6.23-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 2 17:40:44 2014 InstallationDate: Installed on 2013-04-30 (305 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: duplicity UpgradeStatus: Upgraded to trusty on 2014-01-14 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1286845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297831] Re: Input method set to ibus in Ubuntu Kylin, while fcitx is the desired default
** Branch linked: lp:ubuntu/trusty-proposed/im-config -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1297831 Title: Input method set to ibus in Ubuntu Kylin, while fcitx is the desired default Status in Ubuntu Kylin: Fix Committed Status in “im-config” package in Ubuntu: Fix Committed Status in “language-selector” package in Ubuntu: Fix Released Bug description: the default input method is ibus , not fcitx as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1297831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297101] Re: Window hide headers for the top panel Ubuntu and it is not possible to reset compiz
Attached a screenshot of an open window LibreOffice, the cap of which is blocked by the header is open to full screen FireFox ** Attachment added: Снимок экрана от 2014-03-29 14:43:24.png https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1297101/+attachment/4050591/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202014-03-29%2014%3A43%3A24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1297101 Title: Window hide headers for the top panel Ubuntu and it is not possible to reset compiz Status in Compiz: New Status in “compiz” package in Ubuntu: Incomplete Bug description: Window hide headers for the top panel Ubuntu and trying to replace/fix with CompizConfig Settings Manager (ccsm) disables plugin Unity (a system without launcher, the top panel, hotkeys). dropped: 1. through the standard reset compiz (ccsm-settings-reset on typical), 2. removing the config files: gconftool-2 --recursive-unset /apps/compiz-1 gconftool-2 --recursive-unset /apps/compizconfig-1 unity --reset rm -rf ~/.config/compiz-1/compizconfig/* 3. unity-tweak-tool --reset-unity The first method leads to disabling the plugin Unity (see above). Third - does not reset anything. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 25 10:14:42 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-19-generic, i686: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0da] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-03-22 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140321) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=9599876d-6f9c-484c-9444-6399762dd3c2 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P09AAN dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355V5X-S01RU dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 355V4C/356V4C/3445VC/3545VC dmi.product.version: P09AAN.031.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 25 10:10:51 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1297101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
** Branch linked: lp:ubuntu/trusty-proposed/indicator-power -- 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/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in Application Indicators: New Status in The Date and Time Indicator: New Status in Indicator keyboard: New Status in The Messaging Menu: New Status in The Power Indicator: New Status in The Session Menu: New Status in Sound Menu: New Status in Libindicator: New Status in “gnome-panel” package in Ubuntu: Triaged Status in “indicator-application” package in Ubuntu: Triaged Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “indicator-messages” package in Ubuntu: Triaged Status in “indicator-power” package in Ubuntu: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Status in “libindicator” package in Ubuntu: Triaged Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1263228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
Jackson, Thanks, but please attach a debdiff, I can't review that right now with internet issues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297831] Re: Input method set to ibus in Ubuntu Kylin, while fcitx is the desired default
This bug was fixed in the package im-config - 0.24-1ubuntu4 --- im-config (0.24-1ubuntu4) trusty; urgency=medium * debian/patches/01_fcitx-default-if-installed.patch, debian/im-config.user-session.upstart: Make fcitx the system default if installed (LP: #1297831). -- Gunnar Hjalmarsson gunna...@ubuntu.com Thu, 27 Mar 2014 16:17:00 +0100 ** Changed in: im-config (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1297831 Title: Input method set to ibus in Ubuntu Kylin, while fcitx is the desired default Status in Ubuntu Kylin: Fix Committed Status in “im-config” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Bug description: the default input method is ibus , not fcitx as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1297831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
This bug was fixed in the package indicator-power - 12.10.6+14.04.20140328-0ubuntu1 --- indicator-power (12.10.6+14.04.20140328-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * If there are two batteries detected, combine their percentages and their time-remainings as per the revised spec. (LP: #880881) [ Lars Uebernickel ] * Use com.canonical.indicator.basic menu item for device items That menu item can handle non-square icons. (LP: #1263228) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Mar 2014 16:10:45 + ** Changed in: indicator-power (Ubuntu) Status: In Progress = Fix Released -- 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/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in Application Indicators: New Status in The Date and Time Indicator: New Status in Indicator keyboard: New Status in The Messaging Menu: New Status in The Power Indicator: New Status in The Session Menu: New Status in Sound Menu: New Status in Libindicator: New Status in “gnome-panel” package in Ubuntu: Triaged Status in “indicator-application” package in Ubuntu: Triaged Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “indicator-messages” package in Ubuntu: Triaged Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Status in “libindicator” package in Ubuntu: Triaged Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1263228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296233] Re: increase in number of wakeups in recent release in indicator-datetime
This bug was fixed in the package indicator-datetime - 13.10.0+14.04.20140328-0ubuntu1 --- indicator-datetime (13.10.0+14.04.20140328-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Short-term workaround for the GIO GAppInfo wakeup bug discussed in bug 1296233 (LP: #1296233) * Improved translator comments for better time/date localization. (LP: #1001595) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Mar 2014 16:11:23 + ** Changed in: indicator-datetime (Ubuntu) Status: In Progress = Fix Released -- 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/1296233 Title: increase in number of wakeups in recent release in indicator-datetime Status in The Date and Time Indicator: In Progress Status in “glib2.0” package in Ubuntu: Triaged Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The number of wakeup events has quadrupled in a recent release of indicator datetime on Trusty 14.04, so this looks like a minor regression. http://ci.ubuntu.com/power/eventstat/image/3101/machine/1/task /indicator-datetime-service/details In the previous set of runs it was down to ~2 wakeups a minute, now it's up to 8 again. Attached is the output of a heath-check analysis of indicator- datetime-service showing the activity over 5 minutes. It seems that there is a poll occurring every 4 seconds which may be the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1296233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 272749] Re: Set window manager URGENT hint on bell.
Mikel, I have used the patches from your website: http://mikelward.com/software/gnome/flashing-terminal, and obviously missed the config schema stuff. Does this patch after all is able to just forward the terminal bell by setting the X client window's urgent property? Because that's all I want it to do. For monitoring activity etc I would use tmux then, but without gnome-terminal forwarding/handling the terminal bell from tmux, this does not work currently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/272749 Title: Set window manager URGENT hint on bell. Status in GNOME Terminal: New Status in Terminator: Fix Released Status in Gnome Virtual Terminal Emulator: Fix Released Status in “gnome-terminal” package in Ubuntu: Triaged Status in “vte” package in Ubuntu: Fix Released Bug description: I would like to see an option to set the window manager URGENT hint on a visual bell or audible bell when silent_bell is active. Currently the visual notifications for bells are not as effective as actually flashing the entry in the window list and this would solve the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/272749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292407] Re: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component
i have the same issue with 1:4.2.3~rc2-0ubuntu1 -- 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/1292407 Title: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component Status in “libreoffice” package in Ubuntu: New Bug description: Every time I want to open a component of Libreoffice 1:4.2.1-0ubuntu1 on Lubuntu 14.04 (everything is up-to-date and i enabled nvidia drivers) i get this fatal error message and nothing gets opened: The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/*user name*/.config/libreoffice/4 --- ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-02-26 (17 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) Package: libreoffice 1:4.2.1-0ubuntu1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: third-party-packages trusty Uname: Linux 3.13.0-17-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1292407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299245] Re: Rhythmbox fails to start
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. ** Changed in: rhythmbox (Ubuntu) Status: New = Incomplete -- 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/1299245 Title: Rhythmbox fails to start Status in “rhythmbox” package in Ubuntu: Incomplete Bug description: (rhythmbox:3488): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed Unable to open ~/.mtpz-data for reading, MTPZ disabled. (rhythmbox:3488): GLib-GObject-CRITICAL **: object SoupServer 0xa49b730 finalized while still in-construction (rhythmbox:3488): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead. Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Fri Mar 28 23:35:19 2014 InstallationDate: Installed on 2014-03-05 (23 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140304) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1299245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299433] [NEW] gnome-control-center crashes testing sound effects with alert volume set to off
Public bug reported: 1. open gnome-control-center 2. click sound 3. clock sound effects tab 4. set alert volume to off using the button on the right 5. select one of the alert sounds in the list 6. gnome-control-center segfaults In fact, it looks like just clicking around the alert sounds with the alert volume on or off can trigger it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu54 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. CurrentDesktop: GNOME Date: Sat Mar 29 11:36:56 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 (20140326.1) ProcCmdline: /usr/bin/gnome-control-center.real sound Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=0x7f6b977f81db ../../src/xcb_io.c, line=298, function=0x7f6b977f86d0 poll_for_response) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-control-center.real assert failure: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1299433 Title: gnome-control-center crashes testing sound effects with alert volume set to off Status in “gnome-control-center” package in Ubuntu: New Bug description: 1. open gnome-control-center 2. click sound 3. clock sound effects tab 4. set alert volume to off using the button on the right 5. select one of the alert sounds in the list 6. gnome-control-center segfaults In fact, it looks like just clicking around the alert sounds with the alert volume on or off can trigger it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu54 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. CurrentDesktop: GNOME Date: Sat Mar 29 11:36:56 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 (20140326.1) ProcCmdline: /usr/bin/gnome-control-center.real sound Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=0x7f6b977f81db ../../src/xcb_io.c, line=298, function=0x7f6b977f86d0 poll_for_response) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-control-center.real assert failure: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1299433]
StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 __PRETTY_FUNCTION__.14376 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 __PRETTY_FUNCTION__.14376 poll_for_response) at assert.c:101 poll_for_response (dpy=dpy@entry=0x24b79f0) at ../../src/xcb_io.c:296 _XEventsQueued (dpy=dpy@entry=0x24b79f0, mode=mode@entry=2) at ../../src/xcb_io.c:363 XPending (dpy=0x24b79f0) at ../../src/Pending.c:55 -- 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/1299433 Title: gnome-control-center crashes testing sound effects with alert volume set to off Status in “gnome-control-center” package in Ubuntu: New Bug description: 1. open gnome-control-center 2. click sound 3. clock sound effects tab 4. set alert volume to off using the button on the right 5. select one of the alert sounds in the list 6. gnome-control-center segfaults In fact, it looks like just clicking around the alert sounds with the alert volume on or off can trigger it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu54 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. CurrentDesktop: GNOME Date: Sat Mar 29 11:36:56 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 (20140326.1) ProcCmdline: /usr/bin/gnome-control-center.real sound Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=0x7f6b977f81db ../../src/xcb_io.c, line=298, function=0x7f6b977f86d0 poll_for_response) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-control-center.real assert failure: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299433] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1299433/+attachment/4050712/+files/Stacktrace.txt -- 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/1299433 Title: gnome-control-center crashes testing sound effects with alert volume set to off Status in “gnome-control-center” package in Ubuntu: New Bug description: 1. open gnome-control-center 2. click sound 3. clock sound effects tab 4. set alert volume to off using the button on the right 5. select one of the alert sounds in the list 6. gnome-control-center segfaults In fact, it looks like just clicking around the alert sounds with the alert volume on or off can trigger it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu54 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. CurrentDesktop: GNOME Date: Sat Mar 29 11:36:56 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 (20140326.1) ProcCmdline: /usr/bin/gnome-control-center.real sound Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=0x7f6b977f81db ../../src/xcb_io.c, line=298, function=0x7f6b977f86d0 poll_for_response) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-control-center.real assert failure: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
this is a kernel bug. git bisect completed and reported on the upstream report https://bugs.freedesktop.org/show_bug.cgi?id=76520 -- 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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
this is a kernel bug ** Package changed: lightdm (Ubuntu) = linux-meta (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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299433] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1299433/+attachment/4050714/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1299433/+attachment/4050702/+files/CoreDump.gz ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided = Medium ** Tags removed: need-amd64-retrace -- 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/1299433 Title: gnome-control-center crashes testing sound effects with alert volume set to off Status in “gnome-control-center” package in Ubuntu: New Bug description: 1. open gnome-control-center 2. click sound 3. clock sound effects tab 4. set alert volume to off using the button on the right 5. select one of the alert sounds in the list 6. gnome-control-center segfaults In fact, it looks like just clicking around the alert sounds with the alert volume on or off can trigger it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu54 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. CurrentDesktop: GNOME Date: Sat Mar 29 11:36:56 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 (20140326.1) ProcCmdline: /usr/bin/gnome-control-center.real sound Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=0x7f6b977f81db ../../src/xcb_io.c, line=298, function=0x7f6b977f86d0 poll_for_response) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-control-center.real assert failure: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299433] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1299433/+attachment/4050713/+files/StacktraceSource.txt -- 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/1299433 Title: gnome-control-center crashes testing sound effects with alert volume set to off Status in “gnome-control-center” package in Ubuntu: New Bug description: 1. open gnome-control-center 2. click sound 3. clock sound effects tab 4. set alert volume to off using the button on the right 5. select one of the alert sounds in the list 6. gnome-control-center segfaults In fact, it looks like just clicking around the alert sounds with the alert volume on or off can trigger it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu54 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. CurrentDesktop: GNOME Date: Sat Mar 29 11:36:56 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Beta amd64 (20140326.1) ProcCmdline: /usr/bin/gnome-control-center.real sound Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __assert_fail_base (fmt=0x7f6b96309718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=file@entry=0x7f6b977f81db ../../src/xcb_io.c, line=line@entry=298, function=function@entry=0x7f6b977f86d0 poll_for_response) at assert.c:92 __GI___assert_fail (assertion=0x7f6b977f8390 !xcb_xlib_threads_sequence_lost, file=0x7f6b977f81db ../../src/xcb_io.c, line=298, function=0x7f6b977f86d0 poll_for_response) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-control-center.real assert failure: gnome-control-center.real: ../../src/xcb_io.c:298: poll_for_response: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286845] Re: Duplicity crashes with UnicodeEncode error
If System Language is set to English (System Settings → User Accounts → Language → English), then back-up completes flawlessly. This is confirmation to the observation of Alexander Kubashin (kubashin-a). For el_GR.UTF-8 (as for ru_RU.UTF-8), the last line of errors is: UnicodeEncodeError: 'ascii' codec can't encode characters in position 16-25: ordinal not in range(128) This bug, maybe it is the same as Bug #1276327 and similar to Bug #989496 and Bug #554412 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1286845 Title: Duplicity crashes with UnicodeEncode error Status in Déjà Dup Backup Tool: New Status in “duplicity” package in Ubuntu: Incomplete Bug description: When duplicity tries to do an incremental backup today it crashes with the following Traceback: Traceback (most recent call last): File /usr/bin/duplicity, line 1493, in module with_tempdir(main) File /usr/bin/duplicity, line 1487, in with_tempdir fn() File /usr/bin/duplicity, line 1336, in main do_backup(action) File /usr/bin/duplicity, line 1469, in do_backup incremental_backup(sig_chain) File /usr/bin/duplicity, line 656, in incremental_backup print_statistics(diffdir.stats, bytes_written) File /usr/bin/duplicity, line 594, in print_statistics print diffdir.stats.get_stats_logstring(_(Backup Statistics)) UnicodeEncodeError: 'ascii' codec can't encode character u'\xf6' in position 27: ordinal not in range(128) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: duplicity 0.6.23-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 2 17:40:44 2014 InstallationDate: Installed on 2013-04-30 (305 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: duplicity UpgradeStatus: Upgraded to trusty on 2014-01-14 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1286845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192028] Re: Compiz refresh rate resets to 50 Hz automatically
If this bug isn't going to be fixed the correct way, at least hard code compiz to default to 60Hz. How often is 50Hz really the correct default these days? Mind you, the default stuttery performance with the nvidia binary driver on 14.04 could hardly be called 50Hz. My Amiga 1200 did 50Hz scrolling in the early 1990s and that was extremely smooth, even on a CRT running at 15.6kHz/50Hz. ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1192028 Title: Compiz refresh rate resets to 50 Hz automatically Status in Compiz: Confirmed Status in “compiz” package in Ubuntu: Confirmed Bug description: There have been similar bug reports to this one, such as bug #1009338 and bug #1027868, but I believe this case is different. The problem I am having is that even after I set the refresh rate options in compiz to 60 Hz (after disabling the Detect Refresh Rate option), a reboot will have the settings revert. If I change settings in the compiz config settings manager, they should remain even after a reboot. --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-04-28 10:18:35,447 DEBUG enabling apt cron job DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022e] InstallationDate: Installed on 2011-10-16 (611 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. XPS M1530 MarkForUpload: True NonfreeKernelModules: nvidia Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=67324911-aae9-47ca-a177-6c818959ed59 ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-23-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-28 (50 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare vboxusers video dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Jun 17 17:22:09 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1192028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282776] Re: Don't work item 'Logout' in Ubuntu 14.04
*** This bug is a duplicate of bug 1242112 *** https://bugs.launchpad.net/bugs/1242112 ** This bug has been marked a duplicate of bug 1242112 Upgrade to Saucy Salamander (13.10) Causes shutdown/restart dialogue to not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1282776 Title: Don't work item 'Logout' in Ubuntu 14.04 Status in “compiz” package in Ubuntu: New Bug description: When i press 'Logout' in Unity nothing happen. How i can fix it? Ubuntu 14.04 Daily Build with updates. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140218-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 21 01:05:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c2] InstallationDate: Installed on 2014-01-22 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140122) MachineType: FUJITSU LIFEBOOK A512 ProcEnviron: LANGUAGE=ru_RU PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed root=UUID=7a576123-092a-4bdd-ad40-1d60656894b7 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.12 dmi.board.name: FJNBB29 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.12:bd04/25/2013:svnFUJITSU:pnLIFEBOOKA512:pvr:rvnFUJITSU:rnFJNBB29:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A512 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 20 21:35:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1282776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1254092] Re: Touchpad not recognised on Acer Aspire 5720 after upgrade to 13.10
If that is what it takes to fix this problem then yes, a backport to Saucy is what I need. However, could I confirm that when 14.04 is released I will: A) still be able to upgrade from 13.10 to 14.04? and B) The fix (backport) will still work? Are there any other implications of a backport that I should know about? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1254092 Title: Touchpad not recognised on Acer Aspire 5720 after upgrade to 13.10 Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: After upgrading from ubuntu 13.04 to 13.10 the touchpad on my Acer Aspire 5720 laptop is no longer recognised by the kernel. Running xinput I get: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=12 [slave pointer (2)] ⎜ ↳ MCE IR Keyboard/Mouse (ene_ir) id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Acer Crystal Eye webcam id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] ↳ ENE eHome Infrared Remote Receiver id=14 [slave keyboard (3)] System Settings Mouse Touchpad only shows settings for mice (no touchpad settings present). Using Google I see various other reports of the same problem on different laptops and the consensus is that it is a problem with the kernel NOT with synaptics. ***The Acer Aspire 5720 has three physical buttons below the touchpad*** - Left, Right, and a middle 4-way button, which has previously always worked for scrolling up/down/left/right. Only up and down works but it only scrolls up or down one line at a time (no continuous scrolling by holding the up/down button down). I have managed to get a partial fix by adding options psmouse proto=imps to /etc/modprobe.d/options.conf and then running: sudo modprobe -r psmouse sudo modprobe psmouse That gets the physical middle button scrolling up/down working correctly but still no left/right scroll and no way to turn off touchpad tap to click (Grrr! Grrr! and thrice Grrr!) Help! --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistUpgraded: 2013-10-18 16:47:07,834 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2011-10-14 (770 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MachineType: Acer Aspire 5720 MarkForUpload: True Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/51-synaptics-quirks.conf] PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=2da6d337-44c6-4370-8808-47a269485bc3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Tags: saucy ubuntu Uname: Linux 3.11.0-13-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-18 (35 days ago) UserGroups: adm admin lpadmin sambashare dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: eMachine dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5720:pvrV1.45:rvnAcer:rneMachine:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.name: Aspire 5720 dmi.product.version: V1.45 dmi.sys.vendor: Acer 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 9.2.1-1ubuntu3 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
[Desktop-packages] [Bug 257376] Re: gnome-panel crashed with signal 5 in _XError()
** Changed in: gtk Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/257376 Title: gnome-panel crashed with signal 5 in _XError() Status in GTK+ GUI Toolkit: Expired Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: Binary package hint: gnome-panel Gnome-panel froze at login. When I pressed a quick-launch button it died, and restarted. ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/gnome-panel NonfreeKernelModules: nvidia Package: gnome-panel 1:2.23.6-0ubuntu3 ProcAttrCurrent: unconfined ProcCmdline: gnome-panel ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=sv_SE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/libgdk-x11-2.0.so.0 ?? () from /usr/lib/libbonoboui-2.so.0 _XError () from /usr/lib/libX11.so.6 ?? () from /usr/lib/libX11.so.6 _XReply () from /usr/lib/libX11.so.6 Title: gnome-panel crashed with signal 5 in _XError() Uname: Linux 2.6.26-5-generic i686 UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/257376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299448] Re: soffice.bin crashed with SIGSEGV in TemplateLocalView::copyFrom()
*** This bug is a duplicate of bug 1297504 *** https://bugs.launchpad.net/bugs/1297504 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1297504, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1299448/+attachment/4050792/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1299448/+attachment/4050794/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1299448/+attachment/4050796/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1299448/+attachment/4050797/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1299448/+attachment/4050798/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1299448/+attachment/4050799/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1299448/+attachment/4050800/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1297504 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1299448 Title: soffice.bin crashed with SIGSEGV in TemplateLocalView::copyFrom() Status in “libreoffice” package in Ubuntu: New Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.1-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.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 13:15:03 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-09-15 (194 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5 SegvAnalysis: Segfault happened at: 0x7f97e183ca9d _ZN17TemplateLocalView8copyFromERKN3rtl8OUStringE+61: movzwl 0x118(%rbx),%r14d PC (0x7f97e183ca9d) ok source 0x118(%rbx) (0x0149) not located in a known VMA region (needed readable region)! destination %r14d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: TemplateLocalView::copyFrom(rtl::OUString const) () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so ToolBox::MouseButtonDown(MouseEvent const) () from /usr/lib/libreoffice/program/libmergedlo.so ?? () from /usr/lib/libreoffice/program/libmergedlo.so Title: soffice.bin crashed with SIGSEGV in TemplateLocalView::copyFrom() UpgradeStatus: Upgraded to trusty on 2014-03-21 (8 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1299448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1296288] Re: pcscd crashes when disconnecting / reconnecting USB device
Sorry for the latency. I was very busy during the week. I unpacked the crash file with apport-unpack. Unfortunately there is no dbg package available so all binaries are stripped. Perhaps you can have a look to the attached crash file and give a hint if it is the libifd-cyberjack6 driver. On Sunday 23 Mar 2014 14:54:31 you wrote: I can't find the attached /var/crash/_usr_sbin_pcscd.0.crash I guess the crash occurs in the libifd-cyberjack6 driver and the bug should be reassigned to this package. ** Attachment added: _usr_sbin_pcscd.0.crash.gz https://bugs.launchpad.net/bugs/1296288/+attachment/4050844/+files/_usr_sbin_pcscd.0.crash.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1296288 Title: pcscd crashes when disconnecting / reconnecting USB device Status in “pcsc-lite” package in Ubuntu: New Bug description: $ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 $ apt-cache policy pcscd pcscd: Installed: 1.8.10-1ubuntu1 Candidate: 1.8.10-1ubuntu1 Version table: *** 1.8.10-1ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status The HW used is a Reiner SCT supported by the following package: $ apt-cache policy libifd-cyberjack6 libifd-cyberjack6: Installed: 3.99.5final.sp03-2 Candidate: 3.99.5final.sp03-2 Version table: *** 3.99.5final.sp03-2 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status The error occures mostly when disconnecting or reconnecting the device. Please wait a few seconds after changing conection state. I am unsure if the deamon is stable over time when the connection state is unchanged. I found the service missing in various scenarios. After crashing I found the following entries in syslog: Mar 23 14:13:51 einstein kernel: [ 560.029754] pcscd[2560]: segfault at 7f062128c248 ip 7f062128c248 sp 7f0620a5cee0 error 14 in libc-2.19.so[7f06216d3000+1bb000] Mar 23 14:14:30 einstein kernel: [ 599.765633] pcscd[2572]: segfault at 7f7840e4f248 ip 7f7840e4f248 sp 7f784061fee0 error 14 in libc-2.19.so[7f7841296000+1bb000] I attached the crash report from /var/crash/_usr_sbin_pcscd.0.crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1296288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299454] [NEW] Display needs to be unlocked twice
Public bug reported: I've had this issue since the new lock screen: 1) Wait for the display to get locked 2) Unlock the display by entering you password What should happen: - The display should unlock and stay unlocked What happens instead: - The display gets unlocked, but after ~15 secs the display gets locked again by itself - Unlocking the display once more makes it now stay unlocked This happens something like 7/10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 29 15:11:06 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: I've had this issue since the new lock screen: - 1) Wait or the display to get locked + 1) Wait for the display to get locked 2) Unlock the display by entering you password What should happen: - - The display should stay unlocked + - The display should unlock and stay unlocked What happens instead: - - After ~15 secs the display gets locked again by itself + - The display get unlocked, but after ~15 secs the display gets locked again by itself - Unlocking the display once more makes it now stay unlocked This happens something like 7/10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 29 15:11:06 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I've had this issue since the new lock screen: 1) Wait for the display to get locked 2) Unlock the display by entering you password What should happen: - The display should unlock and stay unlocked What happens instead: - - The display get unlocked, but after ~15 secs the display gets locked again by itself + - The display gets unlocked, but after ~15 secs the display gets locked again by itself - Unlocking the display once more makes it now stay unlocked This happens something like 7/10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 29 15:11:06 2014 SourcePackage: unity 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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1299454 Title: Display needs to be unlocked twice Status in “unity” package in Ubuntu: New Bug description: I've had this issue since the new lock screen: 1) Wait for the display to get locked 2) Unlock the display by entering you password What should happen: - The display should unlock and stay unlocked What happens instead: - The display gets unlocked, but after ~15 secs the display gets locked again by itself - Unlocking the display once more makes it now stay unlocked This happens something like 7/10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 29 15:11:06 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1299454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299455] [NEW] deja-dup crashes
Public bug reported: deja-dup cannot create a backup copy ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 17:16:59 2014 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2013-10-20 (160 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1299455 Title: deja-dup crashes Status in “deja-dup” package in Ubuntu: New Bug description: deja-dup cannot create a backup copy ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 17:16:59 2014 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2013-10-20 (160 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) 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/1299455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
does surround21 really work since it use route plugin but route plugin does not support rewind ? -- 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: Triaged 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 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-23T22:27:03.314416 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040873/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1191898] Re: [USB-Audio - USB Sound Blaster HD, playback] fails after reboot
Actually, it hasn't really solved it. It just made it happen slightly less often, but it still happens. -- 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/1191898 Title: [USB-Audio - USB Sound Blaster HD, playback] fails after reboot Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: To get the sound card to work, I have to go through this complicated process of: 1) Starting the computer without the card plugged in; 2) Plugging it in; 3) At this point, it does NOT work. I have to select it in the audio settings, try to make it lay a test sound, which it fails, and then select the on-board sound; 4) Reboot with onboard sound selected. Just logging out does NOT work; 5) After reboot, select USB Analogue Output, and it will work, however 6) After a subsequent reboot, it will fail again, and I have to unplug the card and reboot again, starting the whole cycle over. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasco 2151 F pulseaudio /dev/snd/controlC1: vasco 2151 F pulseaudio /dev/snd/pcmC1D0p: vasco 2151 F...m pulseaudio Date: Mon Jun 17 18:57:29 2013 InstallationDate: Installed on 2012-01-20 (514 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Sound Blaster HD - USB Sound Blaster HD Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - USB Sound Blaster HD, playback] fails after a while UpgradeStatus: Upgraded to raring on 2013-05-06 (42 days ago) dmi.bios.date: 05/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/24/2012:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1191898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299322] Re: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all
It's apparently three speakers, but only two channels. The sub outputs the merged left and right channels. When I ran the 'ubuntu-bug audio' command the tone test it did wasn't alternating channels in any way. The !!Sysfs Files section of the script doesn't appear to output anything since the switch to ALSA DKMS. Is there some other way I can provide that information, or is the above from Daniel enough? -- 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/1299322 Title: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: To get any sound out of the speakers I need to close the lid of the laptop, let it go to sleep, then re-open it. When I unlock the computer the sound will then work from the speakers. Sound from the speakers is not using all of the speakers, and appears to only come out the subwoofer channel or center channel on the bottom of the laptop. There's no sound from the 'speakers' on the front. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 2265 F pulseaudio /dev/snd/controlC0: kevin 2265 F pulseaudio Date: Fri Mar 28 23:16:26 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.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_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Alienware dmi.bios.version: A02 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A02 dmi.modalias: dmi:bvnAlienware:bvrA02:bd07/15/2013:svnAlienware:pnAlienware18:pvr1747:rvnAlienware:rn01W2J2:rvrA00:cvnAlienware:ct8:cvrA02: dmi.product.name: Alienware 18 dmi.product.version: 1747 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1025616] Re: Resume from suspend does not work on Samsung NP305V5A-S06 (AMD A6)
Check if there is an updated BIOS version available for this model. ** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1025616 Title: Resume from suspend does not work on Samsung NP305V5A-S06 (AMD A6) Status in “pm-utils” package in Ubuntu: Confirmed Bug description: Resume does notwork on this laptop: Make/Model: Samsung NP305V5A-S06 CPU: AMD Quad-Core A6-3410MX Accelerated (1,6 GHz, 4 MB) Video: AMD Radeon™ HD6540G2 Dual Graphics VRAM: 1GB DDR3 Full spec. (it's on Russian, sorry): http://www.samsung.com/ru/consumer/computers- peripherals/notebooks/essential/NP305V5A-S06RU-spec OS: Kubuntu 12.04. The problem is very similar to the one in Bug #925646, but I'll repeat them here as well: The desktop correctly goes to suspend, with fans silenced, audio turned off and screen output stopped. Neither the keyboard nor mouse (USB both of them) are able to wake the machine. On attempting to resume with a single short touch of the power button, the fans spin up to full speed and stay spinning at full speed, the power light comes on as expected, however the screen remains black. Moving the mouse or pressing keyboard keys does nothing. Did the machine break while going to sleep or waking up? - Waking up (resume) Is it reproducible? - Yes on 10 out of every 10 sleeps, it failed to resume Did it work before? - I've not tried any other distributions/versions of Linux n this laptop before. So, I can only say that it doesn't work in Kubuntu 12.04. Do you end up with flashing Caps Lock light or similar? - Don't have these indicators on my keyboard. The computer does not reboot until forced by holding down the power button etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1025616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062631] Re: [soundnua]: gnome-control-center crashed with SIGSEGV in gvc_mixer_control_change_input()
This one is not relevant anymore I believe. Feel free to close it, if I may add... -- 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/1062631 Title: [soundnua]: gnome-control-center crashed with SIGSEGV in gvc_mixer_control_change_input() Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: Sound config panel appears, but immediately renders grey. A few seconds after that window disappears completely. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu18 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Sat Oct 6 02:51:19 2012 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center sound-nua ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f395dfc0a5b vfprintf+155: callq 0x7f395e00ad00 strchrnul PC (0x7f395dfc0a5b) ok source 0x7f395e00ad00 (0x7f395e00ad00) ok destination (%rsp) (0x7fffb2102000) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/control-center-1/panels/libsoundnua.so ?? () from /usr/lib/control-center-1/panels/libsoundnua.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: [soundnua]: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1062631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 821233] Re: indicator-weather crashed with AttributeError in export_location_details(): Location instance has no attribute 'location_code'
Not fixed Precise: Traceback (most recent call last): File /usr/bin/indicator-weather, line 1883, in on_apply (location_code, location_details) = self.location.export_location_details() File /usr/bin/indicator-weather, line 405, in export_location_details return (self.location_code, self.location_details) AttributeError: Location instance has no attribute 'location_code' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/821233 Title: indicator-weather crashed with AttributeError in export_location_details(): Location instance has no attribute 'location_code' Status in Raring Backports: Invalid Status in Indicator-Weather: Fix Released Status in “indicator-weather” package in Ubuntu: Fix Released Status in “indicator-weather” source package in Precise: Fix Released Status in “indicator-weather” source package in Quantal: Fix Released Status in “indicator-weather” package in Baltix: Fix Released Bug description: TEST CASE: 1. install indicator-weather, and run it from the commandline (or if you have it already, the guest session works too) 2. click on Setup weather 3. add a location and click on the wizard until apply 4. verify the crash 5. install the new version 6. repeat step 2,3 and verify that it does not crash anymore On Oneiric Alpha3 on trying to set up this application at the apply stage ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: indicator-weather 11.05.31-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic i686 Architecture: i386 Date: Fri Aug 5 03:16:15 2011 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110802.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/indicator-weather ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/indicator-weather'] SourcePackage: indicator-weather Title: indicator-weather crashed with AttributeError in export_location_details(): Location instance has no attribute 'location_code' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/raring-backports/+bug/821233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 22887] Re: [CAN-2005-0023] /usr/sbin/gnome-pty-helper: writes arbitrary utmp records
** Changed in: vte Status: Unknown = Confirmed ** Changed in: vte Importance: Unknown = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/22887 Title: [CAN-2005-0023] /usr/sbin/gnome-pty-helper: writes arbitrary utmp records Status in Gnome Virtual Terminal Emulator: Confirmed Status in “vte” package in Ubuntu: Won't Fix Status in “vte” package in Debian: Confirmed Bug description: Automatically imported from Debian bug report #330907 http://bugs.debian.org/330907 http://bugzilla.gnome.org/show_bug.cgi?id=317312: http://bugzilla.gnome.org/show_bug.cgi?id=317312 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/22887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282649] Re: Unable to make screenshot with PrintScreen key in Unity session in Trusty
Made a clean install of 14.04 beta2 (4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso) and got all shortcuts for screenshots working on all sessions - Unity, GMOME Compiz, GNOME Metacity. It's great! Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1282649 Title: Unable to make screenshot with PrintScreen key in Unity session in Trusty Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: In Trusty with all installed updates it is not possible to make ScreenShot with Print Screen keyboard button. The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and desired screenshot is not saved in ~/Pictures. Tested in guest and normal sessions. Please fix this bug. Do not forget about Alt+PrintScreen, Ctrl+PrintScreen and Ctrl+Shift+PrintScreen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 20 19:40:24 2014 DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:907a] InstallationDate: Installed on 2013-10-20 (123 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Sony Corporation VPCF13Z1R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago) dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF13Z1R dmi.product.version: C607OEHZ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 20 19:32:11 2014 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) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971051] Re: No Alt+Tab in gnome classic session (switcher plugin not loaded)
Made a clean install of 14.04 beta2 (4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso), installed gnome-panel package and launched GNOME session FlashBack (Compiz) - there is not application switcher on Alt+Tab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/971051 Title: No Alt+Tab in gnome classic session (switcher plugin not loaded) Status in Compiz: New Status in “compiz” package in Ubuntu: Triaged Status in “compiz” source package in Precise: Triaged Status in “compiz” source package in Quantal: Confirmed Status in Baltix GNU/Linux: New Bug description: When using the Gnome Classic session (with Compiz) in Ubuntu Precise Pangolin, I cannot use alt + tab to switch applications. WORKAROUND: 1. Install packages: sudo apt-get install compiz-plugins compizconfig-settings-manager 2. Run ccsm 3. Scroll down to Window Management and enable (tick) Application Switcher. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-panel 1:3.4.0-0ubuntu1 Uname: Linux 3.3.0-030300-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 21:01:11 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120108) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/971051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295592] Re: Unable to make screenshot to clipboard with Ctrl+PrintScreen, Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keys in Unity session in Trusty
Made a clean install of 14.04 beta2 (4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso) and got all shortcuts for screenshots working on all sessions - Unity, GMOME Compiz, GNOME Metacity. It's great! Thank you! ** Changed in: unity-settings-daemon (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1295592 Title: Unable to make screenshot to clipboard with Ctrl+PrintScreen, Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keys in Unity session in Trusty Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: In Trusty with all installed updates it is not possible to make ScreenShot to clipboard with Ctrl+PrintScreen, Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen keyboard buttons. Steps to reproduce: 1. Install Ubuntu 14.04. 2. Login to Unity session. 3a. Try to make screenshot of the whole desktop with Ctrl+PrintScreen 3b. Try to make screenshot of active window with Ctrl+Alt+PrintScreen 3c. Try to make screenshot of selected area with Ctrl+Shift+PrintScreen Expected results: * Corresponding screenshot is saved in clipboard and may be inserted to other applications with Ctrl+V. Actual results: * Screenshot is not saved to clipboard. Notes: 1. This bug is complementary to bug 1282649 (Unable to make screenshot with PrintScreen key in Unity session in Trusty). 2. I use default shortcuts Super+Space and Shift+Super+Space for keyboard layout switching. 3. I did some tests (see my Google Docs table - https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dHpGYVlMZ2JuYXdXdEtmUi1QbGxsYXcusp=sharing). In Ubuntu 12.04 (with no matter Unity or GNOME sessions) the full working list of shortcuts used for screenshoting is as follows: PrintScreen, Alt+PrintScreen, Ctrl+PrintScreen, Shift+PrintScreen, Ctrl+Alt+PrintScreen, Ctrl+Shift+PrintScreen. All these hotkeys work normally in 14.04 too on GNOME FlashBack session (Compiz and Metacity). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Fri Mar 21 13:29:53 2014 InstallationDate: Installed on 2014-03-17 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140316) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) upstart.unity-settings-daemon.log: (gnome-terminal:2677): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1295592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 278966] Re: No default player selected, so launch-media-player button does nothing
** Changed in: gnome-control-center Status: Unknown = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/278966 Title: No default player selected, so launch-media-player button does nothing Status in GNOME Control Center: Invalid Status in “libgnome” package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-control-center Steps to repeat: 1) Get yourself a multimedia keyboard with a launch-media-player button (or just enable some other shortcut in system - preferences - shortcuts - Media Player ) 2) Press that launch-media-player-button or whatever shortcut you defined 3) Notice it doesn't work 4) Go to System - Preferences - Default applications - Multimedia- player and select either rhythmbox or totem 5) Press the launch-media-player-button or whatever shortcut you defined 6) Notice that it now works To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/278966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294192] Re: Multiple errors at login again
@Timo Aaltonen Where exactly? ** Changed in: xorg-server (Ubuntu) Status: Invalid = Confirmed -- 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/1294192 Title: Multiple errors at login again Status in “xorg-server” package in Ubuntu: Confirmed Bug description: L14.04 all updates installed including latest bios ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 Uname: Linux 3.14.0-031400rc4-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Mar 15 10:10:57 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-02-08 (38 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64 (20140110) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: audio video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1294192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294188] Re: I get several errors again and again at login (I dont know why)
@Timo Aaltonen I would but this issue doesn't occur anymore since long ago -- 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/1294188 Title: I get several errors again and again at login (I dont know why) Status in “xorg-server” package in Ubuntu: Incomplete Bug description: I dont know what happens but on first login clicking to submit error about any error ignores me. Now Ive logged in again and got several errors again L14.04 all updates installed including bios ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 Uname: Linux 3.14.0-031400rc4-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Mar 15 10:10:57 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-02-08 (38 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64 (20140110) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: audio video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1294188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 126333] Re: Regression - Volume Control using gnome panel applet and keyboard shortcut alternates mute / % volume during sliding
** Changed in: gstreamer Status: Unknown = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/126333 Title: Regression - Volume Control using gnome panel applet and keyboard shortcut alternates mute / % volume during sliding Status in The Gnome Panel Applets: Fix Released Status in The GStreamer Multimedia Framework: Invalid Status in “gnome-applets” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Bug description: On my sony vaio VGN-FZ11M, running metacity, and having been upgraded successfully from feisty, volume change on the keyboard shortcut used to produce a small box on screen showing the volume level. On gutsy, I get a larger grey square at the bottom somewhat offcenter from the screen with just a grey square, no controls. In Ubuntu 7.04, Volume Control was no issue; the QuickKeys (Volume Up/Down/Mute) on the side worked very well. Also the keyboard shortcuts (Fn/PageUp and Fn/PageDown) were equally smooth. When I clicked on the Panel's Sound Icon, moving the volume slider was also smooth and accurate. In Ubuntu 7.10, the Quick Keys and shortcut keys are erratic, meaning that a single tap of a key can one time mute the sound or move it to maximum. When I click on the Panel's Sound icon and move the slider up and/or down, the display on the mouse pointer alternates from a number (percentage) to Muted to a number to Muted, etc (but it doesn't affect the real sound itself) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/126333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 255768] Re: evolution asking for a password, even though it should be remembered
** Changed in: evolution Status: Unknown = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/255768 Title: evolution asking for a password, even though it should be remembered Status in The Evolution Mail Calendaring Tool: Invalid Status in “evolution” package in Ubuntu: Invalid Bug description: Binary package hint: evolution I have an imap account set up in evolution. the password is set to remember, and has been working fine for weeks. It has also been working fine today. then all of a sudden evolution pops up a Enter Password for myname@myserver Please enter the password for myname on host myserver why has it forgotten my password all of a sudden? My suspicion is that authentication failed once (maybe the server was busy for a minute), and now it thinks my password is wrong. If this is so it should have a message like: authentication failed, maybe you have changed you password on the server. do you wish to keep trying with the old password, or enter a new password this is evolution 2.22.3.1-0ubuntu1 on hardy To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/255768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 209284] Re: evince crashed with SIGSEGV in g_closure_invoke()
** Changed in: evince (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/209284 Title: evince crashed with SIGSEGV in g_closure_invoke() Status in Evince document viewer: Expired Status in “evince” package in Ubuntu: Confirmed Bug description: Binary package hint: evince Crash happened after clicking the link inside pdf. ProblemType: Crash Architecture: amd64 Date: Sun Mar 30 18:27:35 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: fglrx Package: evince 2.22.0-0ubuntu2 PackageArchitecture: amd64 ProcCmdline: evince file:///home/username/Documents/FER/JAVA/zadaci/java_tecaj_09_zadaci-1.pdf ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: evince StacktraceTop: ?? () g_closure_invoke () ?? () from /usr/lib/libgobject-2.0.so.0 g_signal_emit_valist () g_signal_emit () from /usr/lib/libgobject-2.0.so.0 Title: evince crashed with SIGSEGV in g_closure_invoke() Uname: Linux 2.6.24-12-generic x86_64 UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/209284/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1192028] Re: Compiz refresh rate resets to 50 Hz automatically
Indeed! Or at least respect the user-set frequency instead of resetting it On 29 Mar 2014 06:30, Lem 1192...@bugs.launchpad.net wrote: If this bug isn't going to be fixed the correct way, at least hard code compiz to default to 60Hz. How often is 50Hz really the correct default these days? Mind you, the default stuttery performance with the nvidia binary driver on 14.04 could hardly be called 50Hz. My Amiga 1200 did 50Hz scrolling in the early 1990s and that was extremely smooth, even on a CRT running at 15.6kHz/50Hz. ** Tags added: regression-release -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1192028 Title: Compiz refresh rate resets to 50 Hz automatically Status in Compiz: Confirmed Status in “compiz” package in Ubuntu: Confirmed Bug description: There have been similar bug reports to this one, such as bug #1009338 and bug #1027868, but I believe this case is different. The problem I am having is that even after I set the refresh rate options in compiz to 60 Hz (after disabling the Detect Refresh Rate option), a reboot will have the settings revert. If I change settings in the compiz config settings manager, they should remain even after a reboot. --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-04-28 10:18:35,447 DEBUG enabling apt cron job DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022e] InstallationDate: Installed on 2011-10-16 (611 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. XPS M1530 MarkForUpload: True NonfreeKernelModules: nvidia Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=67324911-aae9-47ca-a177-6c818959ed59 ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-23-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-28 (50 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare vboxusers video dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Jun 17 17:22:09 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1192028/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1192028 Title: Compiz refresh rate resets to 50 Hz automatically Status in Compiz: Confirmed Status in “compiz” package in Ubuntu: Confirmed Bug description: There have been similar bug reports to this one, such as bug #1009338 and bug
[Desktop-packages] [Bug 1288206] Re: vlc crashed with SIGSEGV in memcpy()
quickfix:
diff -r vlc-2.1.2-orig/modules/codec/avcodec/video.c
vlc-2.1.2-orig-1/modules/codec/avcodec/video.c
891a892,895
if(!p_src){
//msg_Err( p_dec, ffmpeg_CopyPicture`:
p_ff_pic-data[%d]==0, p_pic-i_planes==%d, i_plane, p_pic-i_planes );
continue;
}
this doesn't fix the source of the problem but at least vlc doesn't
crash
--
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/1288206
Title:
vlc crashed with SIGSEGV in memcpy()
Status in “libav” package in Ubuntu:
Confirmed
Status in “vlc” package in Ubuntu:
Confirmed
Status in “vlc” package in Debian:
Incomplete
Bug description:
was playing and all of a sudden it stopped playing and my system
froze.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: vlc-nox 2.1.2-2build1
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 5 11:31:42 2014
ExecutablePath: /usr/bin/vlc
ProcCmdline: /usr/bin/vlc --started-from-file
SegvAnalysis:
Segfault happened at: 0x7f7d5cc25c70 __memcpy_sse2_unaligned+32: movdqu
(%rsi),%xmm8
PC (0x7f7d5cc25c70) ok
source (%rsi) (0x) not located in a known VMA region (needed
readable region)!
destination %xmm8 ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
?? () from /usr/lib/vlc/plugins/codec/libavcodec_plugin.so
?? () from /usr/lib/libvlccore.so.7
?? () from /usr/lib/libvlccore.so.7
start_thread (arg=0x7f7d01d0c700) at pthread_create.c:312
clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: vlc crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to trusty on 2014-01-07 (57 days ago)
UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1288206/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299488] [NEW] In system settings, mouse touchpad, turning touchpad off is not persistant through a boot, not sure if this is bug if not, would like the option of being persi
Public bug reported: Should not have to turn off touchpad on every boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 29 08:14:18 2014 InstallationDate: Installed on 2014-03-27 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu2 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1299488 Title: In system settings, mouse touchpad, turning touchpad off is not persistant through a boot, not sure if this is bug if not, would like the option of being persistant if mouse is plugged in Status in “unity-control-center” package in Ubuntu: New Bug description: Should not have to turn off touchpad on every boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 29 08:14:18 2014 InstallationDate: Installed on 2014-03-27 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1299488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299322] Re: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all
try hda-jack-sense-test to find out which node is used for headset Jack icon https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=73bdd597823e2231dc882577dbbaf8df92fe1775 the headset Mic may use node 0x1a similar to other dell notebook the missing internal speakers are connected to the two remaining nodes 0x18 and 0x1b which pincap support OUT and widcap support stereo try hdajackretask to change them to speaker Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name=Headphone Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Headphone Front Jack, index=0, device=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0001001c: OUT HP EAPD Detect EAPD 0x2: EAPD Pin Default 0x0321101f: [Jack] HP Out at Ext Left Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=01, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 3 0x0c* 0x0d 0x0e Node 0x16 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name=Headphone Playback Switch, index=1, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name=Headphone Surround Jack, index=0, device=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x001c: OUT HP Detect Pin Default 0x03211020: [Jack] HP Out at Ext Left Conn = 1/8, Color = Black DefAssociation = 0x2, Sequence = 0x0 Pin-ctls: 0xc0: OUT HP Unsolicited: tag=02, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 3 0x0c 0x0d* 0x0e -- 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/1299322 Title: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: To get any sound out of the speakers I need to close the lid of the laptop, let it go to sleep, then re-open it. When I unlock the computer the sound will then work from the speakers. Sound from the speakers is not using all of the speakers, and appears to only come out the subwoofer channel or center channel on the bottom of the laptop. There's no sound from the 'speakers' on the front. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 2265 F pulseaudio /dev/snd/controlC0: kevin 2265 F pulseaudio Date: Fri Mar 28 23:16:26 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.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_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Alienware dmi.bios.version: A02 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A02 dmi.modalias: dmi:bvnAlienware:bvrA02:bd07/15/2013:svnAlienware:pnAlienware18:pvr1747:rvnAlienware:rn01W2J2:rvrA00:cvnAlienware:ct8:cvrA02: dmi.product.name: Alienware 18 dmi.product.version: 1747 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299322] Re: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all
you should verify the two headphone jacks and Mic jacks are node 0x15, 0x16 and 0x19 by using hda jack sense test and plug and unplug you have to use advanced override option and make sure the two new speaker pins use same Def association 1, the sequence number determine the speaker is used for front, rear, center/lfe -- 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/1299322 Title: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: To get any sound out of the speakers I need to close the lid of the laptop, let it go to sleep, then re-open it. When I unlock the computer the sound will then work from the speakers. Sound from the speakers is not using all of the speakers, and appears to only come out the subwoofer channel or center channel on the bottom of the laptop. There's no sound from the 'speakers' on the front. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 2265 F pulseaudio /dev/snd/controlC0: kevin 2265 F pulseaudio Date: Fri Mar 28 23:16:26 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.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_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Alienware dmi.bios.version: A02 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A02 dmi.modalias: dmi:bvnAlienware:bvrA02:bd07/15/2013:svnAlienware:pnAlienware18:pvr1747:rvnAlienware:rn01W2J2:rvrA00:cvnAlienware:ct8:cvrA02: dmi.product.name: Alienware 18 dmi.product.version: 1747 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
It's hard to believe a LTS version is about to be released without a solution to this bug. -- 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/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Triaged Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-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 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1240957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1200829] Re: Regression: Enabling typical bindings in Desktop-based Viewport Switching breaks scrollwheel scrolling in some windows with a usb mouse on a laptop
It's hard to believe a LTS version is about to be released without a solution to this bug. -- 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/1200829 Title: Regression: Enabling typical bindings in Desktop-based Viewport Switching breaks scrollwheel scrolling in some windows with a usb mouse on a laptop Status in Compiz: Invalid Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Triaged Bug description: Test Case: On a laptop connect a usb mouse (using a logitech wireless Anywhere mouse mx here Enable theses Desktop-based Viewport Switching binding's Set prev next to typical settings, (next = button 5, prev = button 4 Try to scroll in any of these windows using the mouse scroll-wheel - nautilus gedit synaptic dconf-editor help (Ubuntu Desktop guide Software-updater details 'Open files' window sidebar windows in RB totem preferences in audacious There could be a few more On the other hand many others work ok, short list - Dash Scroll on Desktop gnome-terminal libreoffice-writer ccsm all browsers preferences playlist in vlc Note all of the no scroll apps work fine with touchpad scrolling Have tried disabling the touchpad, ect. to no avail Related to this bug, same workaround to alleviate https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1184159 Commit reverted packages for 13.10 are here https://launchpad.net/~mc3man/+archive/test-scroll ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-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: Fri Jul 12 23:46:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-06-23 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=c6ab7418-5252-48e1-b7ab-cc21291285f4 ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier My Graphics Driver nouveau Option GLXVBlank on EndSection dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1200829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 and 14.04
Made a clean install of Ubuntu 14.04 beta2 ( 4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso). I unable to start gnome-terminal in GNOME FlashBack session (Metacity) with Ctrl+Alt+t on non-latin (cyriliic layout Ctrl+Alt+е). But I can start in Unity and GNOME FlashBack (Compiz) sessions. Also I can confirm bug 1280759. Also there is a big problem with shortcuts, which start from Ctrl+Shift (Ctrl+Shift+C/V in gnome-terminal, Ctrl+Shift+PrintScreen, Ctrl+Shift+Arrows for selecting text in gedit or LibreOffice Writer ) if layout switching key is set to Ctrl+Shift in GNOME sessions (Compiz and Metacity). This is bug 1245473. Please fix these bugs before Ubuntu 14.04 final release. For all non-latin shortcut problems you can see my Google Docs table (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing , Sheet !!! Non-latin shortcuts (14.04)). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Fedora: Unknown 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. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Made a clean install of Ubuntu 14.04 beta2 ( 4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso). There is a big problem with shortcuts, which start from Ctrl+Shift if layout switching key is set to Ctrl+Shift in GNOME sessions (Compiz and Metacity): 1. I can't copy and paste text in gnome-terminal with Ctrl+Shift+C/V 2. I can't make Screenshot of desired area to clipboard with Ctrl+Shift+PrintScreen 3. I can't select text with Ctrl+Shift+arrows in gedit 4. I can't select text with Ctrl+Shift+arrows in LibreOffice Writer Please fix these bugs before Ubuntu 14.04 final release. You can see all non-latin shortcut problems in my Google Docs table (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing , Sheet !!! Non-latin shortcuts (14.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/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: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed 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/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 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys
** Also affects: unity-settings-daemon Importance: Undecided Status: New ** Changed in: unity-settings-daemon Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1280759 Title: Unity shortcuts (Super+A/F/M/C/V) do not work on-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys Status in Unity Settings Daemon: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: There are shortcuts to open lenses in Unity, for example Super + A for App Lens, or Super + F for Files Lens, etc. There are also shortcuts in the Launcher Super + 1 to 9 to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator -- Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press Super + F. WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press Ctrl + S (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press Ctrl + S while Persian layout is active, I am typing Ctrl + س. But keyboard-wise, I am always pressing the same keyboard binding. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-settings-daemon/+bug/1280759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299497] [NEW] Translationsrelated wish: Don't use the same Installed string for both programstate-description and menu
Public bug reported: In the po-file for softwarecenter, notice that the same string - Installed - is used both in the software center menu, and besides the programs installed to the right of their descriptions. This works fine in English, but for example in Swedish we would like to separate them as it becomes a strange situtation. Installed in the menu would be Installerade or Installerat, a plural form, and in the description itself it would be Installerad, an historical verbform, singular, preteritum. I'm sure other translations have the same issue with this to. Please separate the Installed-string in the menu and in the programstate-descriptions to two different tokens and the problem would be solved. Thanks. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1299497 Title: Translationsrelated wish: Don't use the same Installed string for both programstate-description and menu Status in “software-center” package in Ubuntu: New Bug description: In the po-file for softwarecenter, notice that the same string - Installed - is used both in the software center menu, and besides the programs installed to the right of their descriptions. This works fine in English, but for example in Swedish we would like to separate them as it becomes a strange situtation. Installed in the menu would be Installerade or Installerat, a plural form, and in the description itself it would be Installerad, an historical verbform, singular, preteritum. I'm sure other translations have the same issue with this to. Please separate the Installed-string in the menu and in the programstate-descriptions to two different tokens and the problem would be solved. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1299497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245097] Re: Internal data flow error playing dvds
can someone please run me through ho to do all this im good with computers but never used linux before thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1245097 Title: Internal data flow error playing dvds Status in The GStreamer Multimedia Framework: Unknown Status in “gst-plugins-ugly1.0” package in Ubuntu: Confirmed Status in “totem” package in Ubuntu: Confirmed Bug description: Since upgrading to saucy salamander, with totem 3.8.2-0ubuntu1, I have errors playing DVDs. They start playing, but after a little while, I get the Internal data flow error and playback stops. This didn't happen before upgrading ubuntu. The dvds are actually iso files created with ddrescue, but I don't expect that would change things. The same files play without problem in mplayer. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1245097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299497] Re: Translationsrelated wish: Don't use the same Installed string for both programstate-description and menu
** Description changed: - In the po-file for softwarecenter, notice that the same string - Installed - is used both in the software center menu, and besides the programs installed to the right of their descriptions. This works fine in English, but for example in Swedish we would like to separate them as it becomes a strange situtation. Installed in the menu would be Installerade or Installerat, a plural form, and in the description itself it would be Installerad, an historical verbform, preteritum. + In the po-file for softwarecenter, notice that the same string - Installed - is used both in the software center menu, and besides the programs installed to the right of their descriptions. This works fine in English, but for example in Swedish we would like to separate them as it becomes a strange situtation. Installed in the menu would be Installerade or Installerat, a plural form, and in the description itself it would be Installerad, an historical verbform, singular, preteritum. I'm sure other translations have the same issue with this to. Please separate the Installed-string in the menu and in the programstate-descriptions to two different tokens and the problem would be solved. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1299497 Title: Translationsrelated wish: Don't use the same Installed string for both programstate-description and menu Status in “software-center” package in Ubuntu: New Bug description: In the po-file for softwarecenter, notice that the same string - Installed - is used both in the software center menu, and besides the programs installed to the right of their descriptions. This works fine in English, but for example in Swedish we would like to separate them as it becomes a strange situtation. Installed in the menu would be Installerade or Installerat, a plural form, and in the description itself it would be Installerad, an historical verbform, singular, preteritum. I'm sure other translations have the same issue with this to. Please separate the Installed-string in the menu and in the programstate-descriptions to two different tokens and the problem would be solved. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1299497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296378] Re: Activate VP9 codec in libav
I'm not completely sure of the relationship between libvpx and libav, but it seems that libvpx is a shared library and it has to be actually hooked up to a decoder, or possibly that libvpx is an encoding libraray only. Libav 10 was released on 23rd March 2014 and has added a VP9 decoder - see http://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v10 Libav 10 is available for download from https://libav.org/download.html#release_10 ** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1296378 Title: Activate VP9 codec in libav Status in “libav” package in Ubuntu: New Bug description: avconv -encoders | grep vp gives only : V... libvpx libvpx VP8 (codec vp8) It does not give the encoder libvpx-vp9, which seems to be necessary to encode with VP9. Or maybe I missed something? Based on http://git.libav.org/?p=libav.git;a=commit;h=9aa053ceded5550b2e538578af383fd89d82364c , VP9 is available in libvpx since version 1.3.0 , which is the version libav is built with : http://packages.ubuntu.com/trusty/libvpx1 VP9 is also mentioned in the changelog of the libvpx1 package : http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvpx/libvpx_1.3.0-2/changelog Same issue when trying to read a file with VP9 codec. I tried with http://base-n.de/webm/out9.webm avplay out9.webm gives : [matroska,webm @ 0x7f1a80005be0] Unknown/unsupported AVCodecID V_VP9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1296378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298047] Re: Network-manager fails to retrieve VPN secrets
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1298047 Title: Network-manager fails to retrieve VPN secrets Status in “network-manager” package in Ubuntu: Confirmed Bug description: I have several VPN configurations, that used to work some days (wekks ?) ago. Now, most of them fail, using several VPN software (vpnc and openvpn at least). The error seems to be the same in each case: error [1395865654.87082] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 26 21:27:24 2014 InstallationDate: Installed on 2013-02-16 (402 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.10 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-01-22 (63 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-01-18T13:13:34.565032 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1298047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?
I have applied Ciprian's fix from #127 to no avail. Here are my new logs, with the change applied. I didn't spot any difference. ** Attachment added: new-logs.tar https://bugs.launchpad.net/upstart/+bug/969489/+attachment/4051131/+files/new-logs.tar -- 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/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: Confirmed Status in “lightdm” package in Ubuntu: Triaged Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.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/upstart/+bug/969489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1296378] Re: Activate VP9 codec in libav
Libav10 will not make it into trusty, largely because we did not manage to get all packages in trusty built against libav10 in time. I've started staging this transition in https://launchpad.net/~motumedia/+archive/libav10-trusty/+packages, but did not receive enough help with that. Currently, I'm trying to get this transition started in Debian. Progress on that is tracked here: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=libav10;users=j...@debian.org -- regards, Reinhard -- 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/1296378 Title: Activate VP9 codec in libav Status in “libav” package in Ubuntu: New Bug description: avconv -encoders | grep vp gives only : V... libvpx libvpx VP8 (codec vp8) It does not give the encoder libvpx-vp9, which seems to be necessary to encode with VP9. Or maybe I missed something? Based on http://git.libav.org/?p=libav.git;a=commit;h=9aa053ceded5550b2e538578af383fd89d82364c , VP9 is available in libvpx since version 1.3.0 , which is the version libav is built with : http://packages.ubuntu.com/trusty/libvpx1 VP9 is also mentioned in the changelog of the libvpx1 package : http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvpx/libvpx_1.3.0-2/changelog Same issue when trying to read a file with VP9 codec. I tried with http://base-n.de/webm/out9.webm avplay out9.webm gives : [matroska,webm @ 0x7f1a80005be0] Unknown/unsupported AVCodecID V_VP9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1296378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
I made a clean install of Ubuntu 14.04 beta2 ( 4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso). Tested almost all layout switching shortcuts in my Google Docs table (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing , sheet !!! Layout switching hotkeys (14.04)). The result is very positive: all non-exotic usable shortcuts work on Unity and GNOME sessions (Compiz and Metacity). Thank you, dear Ubuntu developers! -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type 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'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === 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. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04
[Desktop-packages] [Bug 1299506] [NEW] VLC: Menu does not show up
Public bug reported: The new menu in the application window does not always show up on hover in VLC. In order to reproduce the probem, perform the following steps: 1. Start VLC 2. Click Help-About 3. Close the popup again by clicking the x in the new window 4. Again hover the menu, it will not show up again ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Package changed: unity-greeter (Ubuntu) = vlc (Ubuntu) -- 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/1299506 Title: VLC: Menu does not show up Status in “vlc” package in Ubuntu: New Bug description: The new menu in the application window does not always show up on hover in VLC. In order to reproduce the probem, perform the following steps: 1. Start VLC 2. Click Help-About 3. Close the popup again by clicking the x in the new window 4. Again hover the menu, it will not show up again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1299506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
@Stephan you are now the 3. or 4. who has this issue when an external screen is connected at booting. That seems to call for a new ticket. But I installed todays updates (14.04), rebooted and all good. Currently compiz does not use 50% of cpu power any longer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Confirmed Status in Release Notes for Ubuntu: Invalid Status in “mesa” package in Ubuntu: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 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-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299509] [NEW] freeze while installing package
Public bug reported: While installing Ubuntu restricted extras, the software center window became completely unresponsive, as evidenced by the window manager rendering its window to gray scale. Although I've waited for over 30 minutes, the progress bar remains stuck at about 60%. I've included the relevant part of my syslog. In the hanging state the main software-center process had 7 child software-center processes and 1 debconf-communi process. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-center 13.10-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 17:40:43 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: syslog https://bugs.launchpad.net/bugs/1299509/+attachment/4051186/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1299509 Title: freeze while installing package Status in “software-center” package in Ubuntu: New Bug description: While installing Ubuntu restricted extras, the software center window became completely unresponsive, as evidenced by the window manager rendering its window to gray scale. Although I've waited for over 30 minutes, the progress bar remains stuck at about 60%. I've included the relevant part of my syslog. In the hanging state the main software-center process had 7 child software-center processes and 1 debconf-communi process. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-center 13.10-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 17:40:43 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1299509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299511] [NEW] Small viewport in Sounds peferences
Public bug reported: On the Sounds preferences tab, the viewport for Play sound for events is tiny, showing only a single item at a time, with a huge amount of whitespace underneath it. See attached screenshot. Empathy 3.8.6-0ubuntu7 ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screenshot from 2014-03-29 11:53:43.png https://bugs.launchpad.net/bugs/1299511/+attachment/4051193/+files/Screenshot%20from%202014-03-29%2011%3A53%3A43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1299511 Title: Small viewport in Sounds peferences Status in “empathy” package in Ubuntu: New Bug description: On the Sounds preferences tab, the viewport for Play sound for events is tiny, showing only a single item at a time, with a huge amount of whitespace underneath it. See attached screenshot. Empathy 3.8.6-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1299511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245137] Re: hotkeys for keyboard layout switching do not work in unity-greeter in Saucy
I made a clean install of Ubuntu 14.04 beta2 ( 4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso). The bug is still here. Please fix it before final Ubuntu 14.04 release. ** Summary changed: - hotkeys for keyboard layout switching do not work in unity-greeter in Saucy + hotkeys for keyboard layout switching do not work in unity-greeter in Saucy and Trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1245137 Title: hotkeys for keyboard layout switching do not work in unity-greeter in Saucy and Trusty Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and Shift+Super+Space are default options for keyboard layout change. But they do not work in Unity greeter. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 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 12:43:18 2013 InstallationDate: Installed on 2013-10-20 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) 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/1245137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock screen
I made a clean install of Ubuntu 14.04 beta2 ( 4cf9e5ef2c1c362317c90312c76cfda0 *ubuntu-14.04-beta2-desktop-i386.iso). The bus is still here. Please fix it before final Ubuntu 14.04 release. -- 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/1244548 Title: Keyboard shortcut for changing keyboard layout does not work on lock screen Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Shortcut for changing keyboard layout does not work on lock screen (to change keyboard layout for entering password). - Switch to some non-english layout (otherwise lock screen will not have layout indicator at all) - Lock the screen - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it will not change layout - Clicking layout indicator near password entry box works -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 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 x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 11:01:10 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 (1 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/1244548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299514] [NEW] [VGC-LS30E, SigmaTel STAC9872AK, Black Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: In Ubuntu 13.04 Sound worked perfectly, then updating to Ubuntu 13.10 sound stopped working on my All in ones internal speakers and I've tried every forum and nothing has helped ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Mar 29 13:01:47 2014 InstallationDate: Installed on 2014-03-09 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Black Speaker, Internal Title: [VGC-LS30E, SigmaTel STAC9872AK, Black Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0122W2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: R0120W2 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0122W2:bd07/24/2007:svnSonyCorporation:pnVGC-LS30E:pvrC3LNXCWG:rvnSonyCorporation:rnVAIO:rvrR0120W2:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGC-LS30E dmi.product.version: C3LNXCWG dmi.sys.vendor: Sony Corporation ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1299514 Title: [VGC-LS30E, SigmaTel STAC9872AK, Black Speaker, Internal] Pulseaudio fails to detect card Status in “pulseaudio” package in Ubuntu: New Bug description: In Ubuntu 13.04 Sound worked perfectly, then updating to Ubuntu 13.10 sound stopped working on my All in ones internal speakers and I've tried every forum and nothing has helped ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Mar 29 13:01:47 2014 InstallationDate: Installed on 2014-03-09 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Black Speaker, Internal Title: [VGC-LS30E, SigmaTel STAC9872AK, Black Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0122W2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: R0120W2 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0122W2:bd07/24/2007:svnSonyCorporation:pnVGC-LS30E:pvrC3LNXCWG:rvnSonyCorporation:rnVAIO:rvrR0120W2:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGC-LS30E dmi.product.version: C3LNXCWG dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1299514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182814] Re: [saucy] usb-modeswitch-data bad packaging forces removal of usb-modeswitch
Workaround: the Debian maintainer has an PPA with the latest version os usb-modeswitch. https://launchpad.net/~odyx/+archive/usb-modeswitch sudo add-apt-repository ppa:odyx/usb-modeswitch sudo apt-get dist-upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1182814 Title: [saucy] usb-modeswitch-data bad packaging forces removal of usb- modeswitch Status in One Hundred Papercuts: Confirmed Status in “usb-modeswitch-data” package in Ubuntu: Confirmed Bug description: Ubuntu saucy has usb-modeswitch-data-20120815-1. Attempting to upgrade to the latest version usb-modeswitch-data-20121109-3 is impossible because of bad packaging which forces removal of usb-modeswitch!!! To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1182814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299519] [NEW] Unable to change keyboard layout while creating new folder in GtkFileChooserDialog
Public bug reported: Steps to reproduce: 1. Open Firefox, gedit, LibreOffice or other program with GTK GUI 2. Press Save 3. In opened GtkFileChooserDialog press Create Folder and try to change keyboard layout. Expected results: 1. Keyboard layout changed 2. You can enter desired name of a folder on desired keyboard layout 3. New folder in desired location is appeared in file tree. Actual results: * After keyboard layout change the desired folder disappears and is not created. The aforementioned procedure works normally in Ubuntu 12.04, but does not work in Ubuntu 14.04. Tested on Unity session. Please fix this bug before Ubuntu 14.04 final release. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-0 3.10.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 30 05:20:36 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1299519 Title: Unable to change keyboard layout while creating new folder in GtkFileChooserDialog Status in “gtk+3.0” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Firefox, gedit, LibreOffice or other program with GTK GUI 2. Press Save 3. In opened GtkFileChooserDialog press Create Folder and try to change keyboard layout. Expected results: 1. Keyboard layout changed 2. You can enter desired name of a folder on desired keyboard layout 3. New folder in desired location is appeared in file tree. Actual results: * After keyboard layout change the desired folder disappears and is not created. The aforementioned procedure works normally in Ubuntu 12.04, but does not work in Ubuntu 14.04. Tested on Unity session. Please fix this bug before Ubuntu 14.04 final release. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-0 3.10.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 30 05:20:36 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1299519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
** Description changed: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type 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'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === 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. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) -* Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637) + * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637) +* Unable to change keyboard layout while creating new folder in GtkFileChooserDialog (bug 1299519) Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space: * Unity greeter (bug 1245137); * Unity session (bug 1245136); * lock screen - gnome-screensaver (bug 1245138, bug 1245256); * ubiquity installer (bug 1242572). Alt+Shift: * Unity greeter (bug 1245258) * Can't set keyboard layout change to Alt+Shift (bug 1245926) * Shift must be pressed pressed first (bug 1266179) Ctrl+Shift: * lock screen - gnome-screensaver (bug 1245270) * Unity greeter (bug 1245268) * Can't set keyboard layout change to Ctrl+Shift (bug 1245991) * If keyboard layout switching hotkey is
