Opened 9 years ago

Closed 9 years ago

#10219 closed Bug Report - Crash (Duplicate)

Segmentation fault when running second instance of mythfrontend on seperate monitor

Reported by: fuxxociety@… Owned by:
Priority: minor Milestone:
Component: MythTV - General Version: 0.24.1
Severity: medium Keywords: segmentation fault simultaneous
Cc: Ticket locked: no


Adding a monitor for my daughter in the next room. I have xorg configured with two seperate screens, The first instance of mythfrontend's mysql.txt is unchanged, and started without any options. The second instance of mythfrontend's mysql.txt has the hostname set to 'mythpandora' and is started with the command 'mythfrontend -display :0.1'.

When I start the second session, (from the user mythpandora), I get a flash of the brown background from the Terra theme, and then the program segfaults.

Program output is here: gdb output is here:

Attachments (2)

New Text Document.txt (8.1 KB) - added by fuxxociety@… 9 years ago.
mythfrontend program output
New Text Document.2.txt (12.6 KB) - added by fuxxociety@… 9 years ago.
gdb.txt output

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by fuxxociety@…

Attachment: New Text Document.txt added

mythfrontend program output

Changed 9 years ago by fuxxociety@…

Attachment: New Text Document.2.txt added

gdb.txt output

comment:1 Changed 9 years ago by fuxxociety@…

Went into settings on the second (mythpandora) instance, changed the network control port from 6546 to 6548, and attempted again, this time I get the error "QMutex::lock: mutex lock failure:" It does not segfault, but nothing is shown on screen aside from the brown Terra background.

I'm also reading something about changing the 'serviceport', but I see no option for changing that anywhere.

comment:2 Changed 9 years ago by fuxxociety@…

Okay, added <ServicePort?>6549</ServicePort?> under the <MythFrontend> section of config.xml, and it started! Looks like this bug is closed!

comment:3 Changed 9 years ago by Raymond Wagner

Resolution: Duplicate
Status: newclosed

Ref #9590

Note: See TracTickets for help on using tickets.