Re: [Desktop-packages] [Bug 1193525] Re: rhythmbox crashed with SIGSEGV in sem_post()
I don't use either rhythmbox or Ubuntu anymore, so I can't say. On 1 Nov 2017 11:55 p.m., "rithik g" <1193...@bugs.launchpad.net> wrote: > Is this still a problem ? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1199159). > https://bugs.launchpad.net/bugs/1193525 > > Title: > rhythmbox crashed with SIGSEGV in sem_post() > > Status in Rhythmbox: > Expired > Status in rhythmbox package in Ubuntu: > Confirmed > > Bug description: > Possible Workaround: > > Try disabling all the python based plugins: > * Context Pane > * Cover art search > * IM status > * Magnatune store > * Python console > * Send tracks > * Song lyrics > * Ubuntu One > * Zeitgeist > > Crashed while clicking 'next' > > ProblemType: Crash > DistroRelease: Ubuntu 13.10 > Package: rhythmbox 2.99.1-0ubuntu1 > ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 > Uname: Linux 3.9.0-6-generic x86_64 > ApportVersion: 2.10.2-0ubuntu2 > Architecture: amd64 > CrashCounter: 1 > Date: Sat Jun 22 11:12:40 2013 > ExecutablePath: /usr/bin/rhythmbox > InstallationDate: Installed on 2012-09-09 (285 days ago) > InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 > (20120905.2) > MarkForUpload: True > ProcCmdline: rhythmbox > ProcEnviron: >XDG_RUNTIME_DIR= >SHELL=/bin/bash >LANGUAGE=en_AU:en >PATH=(custom, no user) >LANG=en_AU.UTF-8 > SegvAnalysis: >Segfault happened at: 0x7f76731561e0 : mov(%rdi),%eax >PC (0x7f76731561e0) ok >source "(%rdi)" (0x) not located in a known VMA region (needed > readable region)! >destination "%eax" ok >Stack memory exhausted (SP below stack segment) > SegvReason: reading NULL VMA > Signal: 11 > SourcePackage: rhythmbox > StacktraceTop: >sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0 >PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/ > libpython2.7.so.1.0 >g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: rhythmbox crashed with SIGSEGV in sem_post() > UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > > To manage notifications about this bug go to: > https://bugs.launchpad.net/rhythmbox/+bug/1193525/+subscriptions > -- 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/1193525 Title: rhythmbox crashed with SIGSEGV in sem_post() Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Confirmed Bug description: Possible Workaround: Try disabling all the python based plugins: * Context Pane * Cover art search * IM status * Magnatune store * Python console * Send tracks * Song lyrics * Ubuntu One * Zeitgeist Crashed while clicking 'next' ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Sat Jun 22 11:12:40 2013 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2012-09-09 (285 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MarkForUpload: True ProcCmdline: rhythmbox ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76731561e0 : mov(%rdi),%eax PC (0x7f76731561e0) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0 PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in sem_post() UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1193525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239204] Re: keys get stuck often on a bluetooth keyboard
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Description changed: I have a Logitech K810 Bluetooth keyboard. The trouble is as follows: every now and then a pressed key causes Ubuntu to think that the key is being held; for instance, when I try to type “google”, I may get something like “oogee”. It happens to any key including arrows and Backspace; sometimes multiple times over typing a single word, sometimes I can type for five or ten minutes without experiencing the bug. The laptop’s original keyboard is unaffected. It is not a hardware bug, as a) the keyboard works fine when connected to an iPad, and b) the keyboard worked fine on 13.04. The bug isn’t limited to any particular program and is also present while typing in terminal (the Ctrl-F1 one) or at login. + The bug disappears when I load Ubuntu with old (3.8) kernel from 13.04. + + --- + ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,resize,vpswitch,imgpng,unitymtgrabhandles,regex,move,gnomecompat,place,snap,animation,expo,mousepoll,workarounds,wall,fade,session,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 13 00:25:35 2013 DistUpgraded: 2013-10-02 05:31:23,728 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:8446] -Subsystem: ASUSTeK Computer Inc. Device [1043:8446] - NVIDIA Corporation GT218 [ION 2] [10de:0a76] (rev ff) (prog-if ff) + Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:8446] + Subsystem: ASUSTeK Computer Inc. Device [1043:8446] + NVIDIA Corporation GT218 [ION 2] [10de:0a76] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-01 (437 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: ASUSTeK Computer INC. 1215N MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=74d20978-496e-40a4-9cc5-d22d57c062b5 ro quiet splash acpi_osi= vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-02 (10 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1215N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0203:bd07/14/2010:svnASUSTeKComputerINC.:pn1215N:pvrx.x:rvnASUSTeKComputerINC.:rn1215N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1215N dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 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-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 12 02:55:07 2013 xserver.configfile: default xserver.errors: - Failed to load module "modesetting" (module does not exist, 0) - Failed to load module "modesetting" (module does not exist, 0) + Failed to load module "modesetting" (module does not exist, 0) + Failed to load module "modesetting" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id1206 - vendor HSD + product id1206 + vendor HSD xserver.version: 2:1.14.3-3ubuntu1 -- 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/1239204 Title: keys get stuck
[Desktop-packages] [Bug 1239204] Re: keys get stuck often on a bluetooth keyboard
** Tags added: regression -- 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/1239204 Title: keys get stuck often on a bluetooth keyboard Status in “xorg” package in Ubuntu: New Bug description: I have a Logitech K810 Bluetooth keyboard. The trouble is as follows: every now and then a pressed key causes Ubuntu to think that the key is being held; for instance, when I try to type “google”, I may get something like “oogee”. It happens to any key including arrows and Backspace; sometimes multiple times over typing a single word, sometimes I can type for five or ten minutes without experiencing the bug. The laptop’s original keyboard is unaffected. It is not a hardware bug, as a) the keyboard works fine when connected to an iPad, and b) the keyboard worked fine on 13.04. The bug isn’t limited to any particular program and is also present while typing in terminal (the Ctrl-F1 one) or at login. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,resize,vpswitch,imgpng,unitymtgrabhandles,regex,move,gnomecompat,place,snap,animation,expo,mousepoll,workarounds,wall,fade,session,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 13 00:25:35 2013 DistUpgraded: 2013-10-02 05:31:23,728 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8446] Subsystem: ASUSTeK Computer Inc. Device [1043:8446] NVIDIA Corporation GT218 [ION 2] [10de:0a76] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-01 (437 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: ASUSTeK Computer INC. 1215N MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=74d20978-496e-40a4-9cc5-d22d57c062b5 ro quiet splash acpi_osi= vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-02 (10 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1215N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0203:bd07/14/2010:svnASUSTeKComputerINC.:pn1215N:pvrx.x:rvnASUSTeKComputerINC.:rn1215N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1215N dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 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-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 12 02:55:07 2013 xserver.configfile: default xserver.errors: Failed to load module "modesetting" (module does not exist, 0) Failed to load module "modesetting" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1206 vendor HSD xserver.version: 2:1.14.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1239204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239204] [NEW] keys get stuck often on a bluetooth keyboard
Public bug reported: I have a Logitech K810 Bluetooth keyboard. The trouble is as follows: every now and then a pressed key causes Ubuntu to think that the key is being held; for instance, when I try to type “google”, I may get something like “oogee”. It happens to any key including arrows and Backspace; sometimes multiple times over typing a single word, sometimes I can type for five or ten minutes without experiencing the bug. The laptop’s original keyboard is unaffected. It is not a hardware bug, as a) the keyboard works fine when connected to an iPad, and b) the keyboard worked fine on 13.04. The bug isn’t limited to any particular program and is also present while typing in terminal (the Ctrl-F1 one) or at login. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,resize,vpswitch,imgpng,unitymtgrabhandles,regex,move,gnomecompat,place,snap,animation,expo,mousepoll,workarounds,wall,fade,session,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 13 00:25:35 2013 DistUpgraded: 2013-10-02 05:31:23,728 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8446] Subsystem: ASUSTeK Computer Inc. Device [1043:8446] NVIDIA Corporation GT218 [ION 2] [10de:0a76] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-01 (437 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: ASUSTeK Computer INC. 1215N MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=74d20978-496e-40a4-9cc5-d22d57c062b5 ro quiet splash acpi_osi= vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-02 (10 days ago) dmi.bios.date: 07/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1215N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0203:bd07/14/2010:svnASUSTeKComputerINC.:pn1215N:pvrx.x:rvnASUSTeKComputerINC.:rn1215N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1215N dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 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-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 12 02:55:07 2013 xserver.configfile: default xserver.errors: Failed to load module "modesetting" (module does not exist, 0) Failed to load module "modesetting" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1206 vendor HSD xserver.version: 2:1.14.3-3ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1239204 Title: keys get stuck often on a bluetooth keyboard Status in “xorg” package in Ubuntu: New Bug description: I have a Logitech K810 Bluetooth keyboard. The trouble is as follows: every now and then a pressed key causes Ubuntu to think that the key is being held; for instance, when I try to type “google”, I may get something like “oogee”. It happens to any key including arrows and Backspace; sometimes multiple times over typing a single word, sometimes I can type for five or ten minutes without experiencing the bug. The laptop’s original keyboard is unaffected. It is not a hardware bug, as a) the keyboard works fine when connected to an iPad, and b) the keyboard worked fine on 13.04. The bug isn
[Desktop-packages] [Bug 1155975] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in __strlen_ia32()
Still remains on 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1155975 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in __strlen_ia32() Status in “usb-modeswitch” package in Ubuntu: Confirmed Bug description: usb_modeswitch_[2088]: segfault at 0 ip b758b6f1 sp bfdb7fcc error 4 in libc-2.17.so[b750d000+1ad000] ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: usb-modeswitch 1.2.3+repack0-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic i686 ApportVersion: 2.9.1-0ubuntu1 Architecture: i386 Date: Sat Mar 16 16:29:20 2013 ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher InstallationDate: Installed on 2013-03-15 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 (20130313) MarkForUpload: True ProcCmdline: usb_modeswitch_dispatcher --switch-mode /7-1:1.0 /lib/udev/usb_modeswitch ProcEnviron: SegvAnalysis: Segfault happened at: 0xb758b6f1:mov(%eax),%ecx PC (0xb758b6f1) ok source "(%eax)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: usb-modeswitch StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 strdup () from /lib/i386-linux-gnu/libc.so.6 ?? () ?? () __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1155975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat
I’ve never experienced this problem on 13.04, but strangely enough, it happens very often to me with 13.10. Laptop’s keyboard works fine, but Bluetooth one stutters every now and then. ** Tags added: saucy -- 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/124406 Title: Keyboard keys get stuck and repeat Status in GNU Emacs: Invalid Status in The Linux Kernel: Confirmed Status in X.Org X server: In Progress Status in “linux” package in Ubuntu: Won't Fix Status in “xorg-server” package in Ubuntu: Won't Fix Status in “linux” source package in Jaunty: Won't Fix Status in “xorg-server” source package in Jaunty: Invalid Status in Gentoo Linux: New Bug description: Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often get 'stuck' and continue being 'clicked' even after they are physically released. For example when clicking Alt-F4, sometimes it gets stuck so all the windows are closed instead of just one. My configuration is Feisty + Xgl + Compiz Fusion. My previous configuration was Edgy + Xgl + Beryl, where this didn't happen. Others have reported the same problem without using either Xgl or Compiz. The keyboard itself isn't the problem. When dual-booting to Windows, everything works fine. Also, the problem happens with two different keyboards (internal laptop, external USB). My best guess is that the problem occurs at time of high system load. Somehow during these times the key-release signal gets lost and the key-press is repeated indefinitely. This happens more often with Compiz configurations because Compiz tends to increase system load. It also happens more often with power-hungry apps like Firefox and Acrobat Reader for similar reasons. PS: When the keys would repeat all input devices would be locked up. ie. mouse won't move, clicks don't do anything, keyboard presses don't register. Then when it becomes unstuck, the mouse moves around and everything. Hope this helps. See also this forum thread for other people with the same problem: http://ubuntuforums.org/showthread.php?t=432057 To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/124406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235924] [NEW] rhythmbox menu bar is broken
Public bug reported: The global menu of Rhythmbox is now a single “Rhythmbox” label, containing “Plugins”, “View”, “Preferences”… everything that used to be a separate menu entry. This is highly inconvenient. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- 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/1235924 Title: rhythmbox menu bar is broken Status in “rhythmbox” package in Ubuntu: New Bug description: The global menu of Rhythmbox is now a single “Rhythmbox” label, containing “Plugins”, “View”, “Preferences”… everything that used to be a separate menu entry. This is highly inconvenient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1235924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 785631] Re: Rhythmbox Party Mode can't be exited in Unity
When in party mode, a button appears in the upper right corner which provides access to the menu (and allows disabling party mode). I think the bug can be closed. -- 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/785631 Title: Rhythmbox Party Mode can't be exited in Unity Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Binary package hint: rhythmbox If one runs Unity and switches to the Party Mode in Rhythmbox (View- Menu), he is unable to switch back to normal mode (if he forgot the correct key) as the panel and the launcher disapear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/785631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 944836] Re: menu not global
Does not happen to me. Is the bug still present on 12.10 or 13.04? -- 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/944836 Title: menu not global Status in “rhythmbox” package in Ubuntu: New Bug description: menu displayed as before, in the application window. not in panel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.95-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Fri Mar 2 16:10:19 2012 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/944836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218327] Re: Keyboard shortcuts not working on russian layout
*** This bug is a duplicate of bug 1226962 *** https://bugs.launchpad.net/bugs/1226962 ** This bug has been marked a duplicate of bug 1226962 Hotkeys not functional in non-latin keyboard layout -- 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/1218327 Title: Keyboard shortcuts not working on russian layout Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: Keyboard shortcuts not working on russian layout in any aplication . For ex. I can't copy something with "ctrl+c" ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:28:14 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1218327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228142] Re: Hotkeys doesn't works with cyrillic outlay
*** This bug is a duplicate of bug 1226962 *** https://bugs.launchpad.net/bugs/1226962 ** This bug has been marked a duplicate of bug 1226962 Hotkeys not functional in non-latin keyboard layout -- 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/1228142 Title: Hotkeys doesn't works with cyrillic outlay Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: Hotkeys doesn't works with cyrillic outlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1228142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199159] Re: rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1()
For me, Rhythmbox crashes just when I try to open it. However, if I delete its music library (rhythmdb.xml file), it loads normally, rebuilds the library… and crashes again after I restart it. -- 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/1199159 Title: rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1() Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: rhythmbox falló cuando pare la reproducción de una canción de un CD de audio e intenté reproducir otra del mismo CD. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Mon Jul 8 23:22:49 2013 ExecutablePath: /usr/bin/rhythmbox MarkForUpload: True ProcCmdline: rhythmbox /run/user/1000/gvfs/cdda:host=sr0/Track\ 1.wav ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb7374e15 :mov (%ebx),%eax PC (0xb7374e15) ok source "(%ebx)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: sem_post@@GLIBC_2.1 () from /lib/i386-linux-gnu/libpthread.so.0 PyThread_release_lock () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0 PyEval_ReleaseLock () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0 PyThreadState_DeleteCurrent () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0 PyGILState_Release () from /usr/lib/i386-linux-gnu/libpython2.7.so.1.0 Title: rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1() 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/rhythmbox/+bug/1199159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 991666] Re: VPN Connects Successfully & Then Shortly Thereafter Fails
Weird. It has stopped disconnecting once I moved custom routes from VPN connection to Wi-Fi connection settings. -- 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/991666 Title: VPN Connects Successfully & Then Shortly Thereafter Fails Status in NetworkManager-PPTP: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: I am able to successfully establish a PPTP VPN connection in Ubuntu 12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to 1.5 minutes it will fail. During the connection time I am only able to load about 1-2 webpages and then they freeze and I cannot access resources on the VPN network. I do not believe this is related to my VPN server as I am able to establish VPN connections with my Windows machines and Smartphones all day long with no problems. Is there a solution to this problem? Description: Ubuntu 12.04 LTS Release: 12.04 network-manager: 0.9.4.0-0ubuntu3 Here is the syslog: Apr 30 00:17:50 satellite-p755 NetworkManager[994]: Starting VPN service 'pptp'... Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 15069 Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' appeared; activating connections Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN plugin state changed: starting (3) Apr 30 00:17:51 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (Connect) reply received. Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 <--> /dev/pts/2 Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 0). Apr 30 00:17:55 satellite-p755 pppd[15073]: CHAP authentication succeeded Apr 30 00:17:55 satellite-p755 pppd[15073]: MPPE 128-bit stateless compression enabled Apr 30 00:17:55 satellite-p755 pppd[15073]: local IP address 192.168.1.20 Apr 30 00:17:55 satellite-p755 pppd[15073]: remote IP address 192.168.1.1 Apr 30 00:17:55 satellite-p755 pppd[15073]: primary DNS address 8.8.8.8 Apr 30 00:17:55 satellite-p755 pppd[15073]: secondary DNS address 8.8.4.4 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (IP Config Get) reply received. Apr 30 00:17:55 satellite-p755 NetworkManager[994]: VPN Gateway: 75.75.79.330 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Tunnel Device: ppp0 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Address: 192.168.1.20 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Prefix: 32 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Point-to-Point Address: 192.168.1.1 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Maximum Segment Size (MSS): 0 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Forbid Default Route: no Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 DNS: 8.8.8.8 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 DNS: 8.8.4.4 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: DNS Domain: '(none)' Apr 30 00:17:56 satellite-p755 dnsmasq[14712]: exiting on receipt of SIGTERM Apr 30 00:17:56 satellite-p755 NetworkManager[994]: DNS: starting dnsmasq... Apr 30 00:17:56 satellite-p755 NetworkManager[994]: (ppp0): writing resolv.
[Desktop-packages] [Bug 991666] Re: VPN Connects Successfully & Then Shortly Thereafter Fails
Happens to me with two different providers. Sometimes it’s “closing control connection due to missing echo reply”, sometimes it’s different (irrelevant parts skipped): Feb 10 16:24:06 artyom-1215N NetworkManager[1036]: Starting VPN service 'pptp'... … Feb 10 16:24:10 artyom-1215N NetworkManager[1036]: VPN connection 'ADSL.BY' (IP Config Get) complete. Feb 10 16:24:10 artyom-1215N NetworkManager[1036]: Policy set 'ADSL.BY' (ppp0) as default for IPv4 routing and DNS. Feb 10 16:24:10 artyom-1215N NetworkManager[1036]: ((null)): writing resolv.conf to /sbin/resolvconf Feb 10 16:24:10 artyom-1215N dnsmasq[1969]: setting upstream servers from DBus Feb 10 16:24:10 artyom-1215N dnsmasq[1969]: using nameserver 81.25.32.99#53 Feb 10 16:24:10 artyom-1215N dnsmasq[1969]: using nameserver 81.25.32.34#53 Feb 10 16:24:10 artyom-1215N dnsmasq[1969]: using nameserver 81.25.32.9#53 Feb 10 16:24:10 artyom-1215N NetworkManager[1036]: VPN plugin state changed: started (4) Feb 10 16:24:10 artyom-1215N dbus[941]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Feb 10 16:24:11 artyom-1215N dbus[941]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Feb 10 16:24:29 artyom-1215N ntpdate[31288]: no server suitable for synchronization found Feb 10 16:24:41 artyom-1215N pptp[31230]: nm-pptp-service-31208 log[pptp_read_some:pptp_ctrl.c:544]: read returned zero, peer has closed Feb 10 16:24:41 artyom-1215N pptp[31230]: nm-pptp-service-31208 log[callmgr_main:pptp_callmgr.c:258]: Closing connection (shutdown) Feb 10 16:24:41 artyom-1215N pptp[31230]: nm-pptp-service-31208 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Feb 10 16:24:41 artyom-1215N pptp[31230]: nm-pptp-service-31208 log[pptp_read_some:pptp_ctrl.c:544]: read returned zero, peer has closed Feb 10 16:24:41 artyom-1215N pptp[31230]: nm-pptp-service-31208 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state) Feb 10 16:24:41 artyom-1215N pppd[31213]: Modem hangup Feb 10 16:24:41 artyom-1215N pppd[31213]: Connect time 0.6 minutes. Feb 10 16:24:41 artyom-1215N pppd[31213]: Sent 10384 bytes, received 0 bytes. Feb 10 16:24:41 artyom-1215N pppd[31213]: Connection terminated. -- 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/991666 Title: VPN Connects Successfully & Then Shortly Thereafter Fails Status in NetworkManager-PPTP: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: I am able to successfully establish a PPTP VPN connection in Ubuntu 12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to 1.5 minutes it will fail. During the connection time I am only able to load about 1-2 webpages and then they freeze and I cannot access resources on the VPN network. I do not believe this is related to my VPN server as I am able to establish VPN connections with my Windows machines and Smartphones all day long with no problems. Is there a solution to this problem? Description: Ubuntu 12.04 LTS Release: 12.04 network-manager: 0.9.4.0-0ubuntu3 Here is the syslog: Apr 30 00:17:50 satellite-p755 NetworkManager[994]: Starting VPN service 'pptp'... Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 15069 Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' appeared; activating connections Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN plugin state changed: starting (3) Apr 30 00:17:51 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (Connect) reply received. Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 <--> /dev/pts/2 Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:773]
