[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
** Changed in: telepathy-mission-control-5 (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Since this bug has a moderate impact on a large portion of Ubuntu users, it's high priority. ** Changed in: telepathy-mission-control-5 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Triaged Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Since this bug is: - Valid. - Well described. - Reported in the upstream bug tracker (Launchpad). - Ready to be worked on by a developer. it's also triaged. ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Triaged Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Same with Saucy for me, using latest gnome envirenment (GNOME-Shell 3.10 from gnome3-team/staging ppa). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Same with saucy for me, using latest gnome environment. tend to happen a bit randomly but more often when using Deluge (Torrent) or Firefox... if that can help in any way... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Yes, I have the bug in Ubuntu-Gnome saucy Alpha2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
attach the thread... ?field.comment=attach the thread... ** Attachment added: thread for this bug https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+attachment/3786562/+files/bt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
In a fresh Saucy Alpha2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Still here, from raring to saucy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
same here with saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+attachment/3636337/+files/CoreDump.gz ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: New Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 g_slice_alloc+178:mov (%edi),%edx PC (0xb71ce912) ok source (%edi) (0x0001) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
