Opened 3 years ago

Closed 3 years ago

#173 closed defect (fixed)

last version qutecom does not start @ubuntu 9.10

Reported by: hrw Owned by: laurent
Priority: blocker Milestone: QuteCom 2.2-RC4
Component: GUI Version: 2.2
Keywords: Segmentation fault Cc:

Description

error: Segmentation fault

sometimes qutecom starts, but crashes with errors:

(<unknown>:2305): GLib-GObject-CRITICAL : g_object_ref: assertion `object->ref_count > 0' failed

(<unknown>:2305): GLib-GObject-CRITICAL : g_object_unref: assertion `G_IS_OBJECT (object)' failed

(<unknown>:2305): GLib-GObject-CRITICAL : g_object_ref: assertion `G_IS_OBJECT (object)' failed

(<unknown>:2305): GLib-GObject-CRITICAL : g_object_unref: assertion `G_IS_OBJECT (object)' failed

(<unknown>:2305): Pango-CRITICAL : pango_layout_get_iter: assertion `PANGO_IS_LAYOUT (layout)' failed
Segmentation fault

Change History (9)

comment:1 Changed 3 years ago by chris-mac

I would suggest to mark this ticket as "Invalid" as last version of QuteCom compiles and runs on Ubuntu 9.10 fine for me.

comment:2 Changed 3 years ago by laurent

Sorry Chris-mac,

This bug is still reproducible if a contact has 'specials' character ...

comment:3 follow-up: Changed 3 years ago by chris-mac

What does the 'special' characters in contact has to do with ability to compile/run QuteCom on Ubuntu 9.10 as reported in this bug?

comment:4 in reply to: ↑ 3 Changed 3 years ago by laurent

Replying to chris-mac:

What does the 'special' characters in contact has to do with ability to compile/run QuteCom on Ubuntu 9.10 as reported in this bug?

"(<unknown>:2305): Pango-CRITICAL : pango_layout_get_iter: assertion `PANGO_IS_LAYOUT (layout)' failed"
For example if you got arabic character in a contact name, QuteCom will crash randomly ...

comment:5 Changed 3 years ago by chris-mac

Right, I see. So probably we need to change bug title from:

"last version qutecom does not start @ubuntu 9.10"

"Allow UTF-8 characters in contact name"

??

comment:6 Changed 3 years ago by laurent

UTF-8 characters is allowed in contact name, and this bug seems to not be reproductible on Windows or Macosx

comment:7 Changed 3 years ago by laurent

It seems that this bug only occurs on Gnome, impossible to reproduce on KDE !

comment:8 Changed 3 years ago by chris-mac

  • Milestone changed from QuteCom 2.2-RC2 to QuteCom 2.2-RC4
  • Version changed from 2.2-RC3 to 2.2

comment:9 Changed 3 years ago by nikita

  • field_os set to all
  • Resolution set to fixed
  • Status changed from new to closed

Now, if Qt is configured with glib eventloop, we will use that loop instead of create a new one.
The problem was due to two glib eventloop in two different thread, but i'm not an expert of glib...

Note: See TracTickets for help on using tickets.