Bug 21588

Summary:	Banshee segfaults when trying to start it.
Product:	Mageia	Reporter:	jean-françois mauzé <jean-francois.mauze>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	geiger.david68210, kde, marja11, ouaurelien
Version:	6	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	banshee	CVE:
Status comment:

Description jean-françois mauzé 2017-08-21 22:17:59 CEST

Description of problem: banshee was OK on mageia 5, when I updated to mageia 6,

I found the issue : I work with KDE 


Running Banshee 2.6.2: [Mageia 6 (linux-gnu, i586) @ 2017-02-19 06:55:07 UTC]
Stacktrace:

at <unknown> <0xffffffff>
at (wrapper managed-to-native) Mono.Unix.Native.Stdlib.free (intptr) <0xffffffff>
at Mono.Unix.UnixMarshal.FreeHeap (intptr) <0x00013>
at Mono.Unix.Catalog.Init (string,string) <0x00163>
at Banshee.ServiceStack.Application.Run () <0x00037>
at Banshee.Gui.GtkBaseClient.Initialize (bool) <0x0045b>
at Banshee.Gui.GtkBaseClient..ctor (bool,string) <0x0004f>
at Banshee.Gui.GtkBaseClient..ctor () <0x00023>
at Nereid.Client..ctor () <0x00013>
at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>
at <unknown> <0xffffffff>
at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke (System.Reflection.MonoCMethod,object,object[],System.Exception&) <0xffffffff>
at System.Reflection.MonoCMethod.InternalInvoke (object,object[]) <0x00033>
at System.RuntimeType.CreateInstanceMono (bool) <0x00137>
at System.RuntimeType.CreateInstanceSlow (bool,bool,bool,System.Threading.StackCrawlMark&) <0x00043>
at System.RuntimeType.CreateInstanceDefaultCtor (bool,bool,bool,System.Threading.StackCrawlMark&) <0x00047>
at System.Activator.CreateInstance (System.Type,bool) <0x00093>
at System.Activator.CreateInstance (System.Type) <0x0001b>
at Banshee.Gui.GtkBaseClient.Startup () <0x00017>
at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.CleanRoomStartup/StartupInvocationHandler) <0x0007f>
at Banshee.Gui.GtkBaseClient.Startup<T_REF> () <0x00097>
at Banshee.Gui.GtkBaseClient.Startup<T_REF> (string[]) <0x000ef>
at Nereid.Client.Main (string[]) <0x00017>
at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>
at <unknown> <0xffffffff>
at (wrapper managed-to-native) System.AppDomain.ExecuteAssembly (System.AppDomain,System.Reflection.Assembly,string[]) <0xffffffff>
at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly,string[]) <0x00043>
at System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0x0002f>
at (wrapper remoting-invoke-with-check) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at System.AppDomain.ExecuteAssembly (string) <0x0002b>
at (wrapper remoting-invoke-with-check) System.AppDomain.ExecuteAssembly (string) <0xffffffff>
at Booter.Booter.BootClient (string) <0x00067>
at Booter.Booter.Main () <0x0019b>
at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

banshee() [0x80ea42e]
banshee() [0x812e944]
banshee() [0x806ae39]
linux-gate.so.1(__kernel_rt_sigreturn+0) [0xb77a3d00]
/usr/lib/libc.so.6(+0x71a20) [0xb51e3a20]
/usr/lib/libc.so.6(cfree+0x50) [0xb51e6ee0]
[0xb2b932dc]
[0xb2b9328c]
[0xb2b910bc]
[0xb2b902f0]
[0xb4fce8fc]
[0xb4fce418]
[0xb4fce3b4]
[0xb4fce37c]
[0xb586a2b0]
banshee() [0x806a9a3]

Debug info from gdb:


=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Abandon (core dumped)

Comment 1 Marja Van Waes 2017-08-22 22:32:01 CEST

(In reply to jean-françois mauzé from comment #0)
> Description of problem: banshee was OK on mageia 5, when I updated to mageia
> 6,
> 
> I found the issue : I work with KDE 
> 

Does that mean that Banshee only segfaults in KDE/Plasma5, but not in other desktop environments?
> 
> Running Banshee 2.6.2: [Mageia 6 (linux-gnu, i586) @ 2017-02-19 06:55:07 UTC]
> Stacktrace:
> 
<snip>

Assigning to all packagers collectively, since there is no registered maintainer for Banshee

CC'ing KDE team, because of the remark
> I found the issue : I work with KDE

Assignee: bugsquad => pkg-bugs
Keywords: (none) => NEEDINFO
CC: (none) => kde, marja11
Summary: issue with starting Banshee => Banshee segfaults when trying to start it.

Comment 2 jean-françois mauzé 2017-08-23 20:11:44 CEST

I don't know the comportment with another desktop, it's difficult for me to check with another desktop

Comment 3 David GEIGER 2017-08-27 08:37:52 CEST

We have a serious issue with mono in mga6 but only on 32bit system, see:

https://bugs.mageia.org/show_bug.cgi?id=21512

Maybe some others packages who needs mono segfault too.

CC: (none) => geiger.david68210

Comment 4 Aurelien Oudelet 2020-08-06 16:41:31 CEST

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Resolution: (none) => OLD
Status: NEW => RESOLVED