Ticket #2052 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

SIGSEGV with certain idleaway prefs

Reported by: ljbuesch Owned by:
Milestone: Component: libpurple
Version: 2.0.2 Keywords: prefs idleaway sigsegv
Cc: nwalp

Description

I have been getting SIGSEGV faults with Pidgen 2.0.2. I tracked it down to the following changes in my prefs.xml file:

<pref name='savedstatus'>
-                       <pref name='default' type='int' value='1183610226'/>
-                       <pref name='startup' type='int' value='1183610226'/>
+                       <pref name='default' type='int' value='0'/>
+                       <pref name='startup' type='int' value='0'/>
                        <pref name='startup_current_status' type='bool' value='0'/>
-                       <pref name='idleaway' type='int' value='1182719850'/>
-                       <pref name='isidleaway' type='bool' value='1'/>
+                       <pref name='idleaway' type='int' value='0'/>
+                       <pref name='isidleaway' type='bool' value='0'/>
</pref>

I compiled a debug version of 2.0.2 for which here is the backtrace:

(01:03:11) prefs: Finished reading /home/ljbuesch/.purple/prefs.xml
(01:03:11) prefs: removing pref /purple/debug/timestamps
(01:03:11) pounce: Error reading pounces: Failed to open file '/home/ljbuesch/.purple/pounces.xml': No such file or directory
(01:03:11) Session Management: ICE initialized.
(01:03:11) Session Management: Connecting with no previous ID
(01:03:11) Session Management: Handling new ICE connection... (01:03:11) done.
(01:03:11) Session Management: Connected to manager (GnomeSM) with client ID 117f000101000118369819100000060830088
(01:03:11) Session Management: Using /usr/local/bin/pidgin as command
(01:03:11) prefs: /purple/savedstatus/default changed, scheduling save.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222858528 (LWP 28817)]
0xb76f0be5 in purple_signal_emit_vargs (instance=0xb771de08, signal=0xb770c3a6 "update-idle", args=0xbf05c048 "h�\005��#n�") at signals.c:439
439     {
(gdb) bt
#0  0xb76f0be5 in purple_signal_emit_vargs (instance=0xb771de08, signal=0xb770c3a6 "update-idle", args=0xbf05c048 "h�\005��#n�") at signals.c:439
#1  0xb76f0d9c in purple_signal_emit (instance=0xb771de08, signal=0xb770c3a6 "update-idle") at signals.c:433
#2  0xb76d4131 in check_idleness () at idle.c:125
#3  0xb76d4487 in check_idleness_timer () at idle.c:223
#4  0xb76ee555 in purple_savedstatus_set_idleaway (idleaway=0) at savedstatuses.c:836
#5  0xb76d4424 in check_idleness () at idle.c:168
#6  0xb76d4487 in check_idleness_timer () at idle.c:223
#7  0xb76ee555 in purple_savedstatus_set_idleaway (idleaway=0) at savedstatuses.c:836
#8  0xb76d4424 in check_idleness () at idle.c:168
#9  0xb76d4487 in check_idleness_timer () at idle.c:223
#10 0xb76ee555 in purple_savedstatus_set_idleaway (idleaway=0) at savedstatuses.c:836
#11 0xb76d4424 in check_idleness () at idle.c:168

...snip...

#550 0xb7769487 in check_idleness_timer () at idle.c:223
#551 0xb7783555 in purple_savedstatus_set_idleaway (idleaway=0) at savedstatuses.c:836
#552 0xb7769424 in check_idleness () at idle.c:168
#553 0xb7769487 in check_idleness_timer () at idle.c:223
#554 0xb7783555 in purple_savedstatus_set_idleaway (idleaway=0) at savedstatuses.c:836
#555 0xb7769424 in check_idleness () at idle.c:168
#556 0xb7769487 in check_idleness_timer () at idle.c:223
#557 0xb7783555 in purple_savedstatus_set_idleaway (idleaway=0) at savedstatuses.c:836
#558 0xb7769424 in check_idleness () at idle.c:168
#559 0xb7769487 in check_idleness_timer () at idle.c:223

(and many more of these calls...)

As far as how those settings were put into the file, I changed my settings from auto-away to never go away, because of problems I've been having on Linux with this feature.

Please let me know if there is more information necessary.

Change History

Changed 3 years ago by khc

  • cc nwalp added
  • status changed from new to closed
  • resolution set to fixed

pretty sure this is fixed, nwalp can correct me

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!