putty triggers GLib-CRITICAL Source ID not found on console

Bug #1458033 reported by Bryce Nesbitt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
putty (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

While using putty in serial mode (/dev/ttyS0) the following appears on the console for each line:

(putty:9401): GLib-CRITICAL **: Source ID 5015 was not found when attempting to remove it
(putty:9401): GLib-CRITICAL **: Source ID 5120 was not found when attempting to remove it
(putty:9401): GLib-CRITICAL **: Source ID 5223 was not found when attempting to remove it
(putty:9401): GLib-CRITICAL **: Source ID 5295 was not found when attempting to remove it

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: putty 0.63-4
ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
Uname: Linux 3.13.0-52-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 22 12:45:04 2015
ExecutablePath: /usr/bin/putty
SourcePackage: putty
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Bryce Nesbitt (bryce2) wrote :
Revision history for this message
Bryce Nesbitt (bryce2) wrote :

This happens once per character typed in putty.

Revision history for this message
Jacob Nevins (0jacobnk-ulp) wrote :
Download full text (5.8 KiB)

I can reproduce this in 0.63-4 (built from Ubuntu source) on Xubuntu 14.04 if I start a serial session, set "Local echo" to "Force on", and press some keys.

Setting a breakpoint on g_log I get this backtrace:

#0 0x00007ffff683fcf0 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007ffff6837c5c in g_source_remove ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x0000000000467a75 in timer_change_notify (next=2367632)
    at unix/gtkwin.c:1431
#3 0x0000000000458899 in schedule_timer (ticks=ticks@entry=20,
    fn=fn@entry=0x44fe30 <term_timer>, ctx=ctx@entry=0xa15200) at timing.c:145
#4 0x000000000044d1f0 in term_schedule_update (term=term@entry=0xa15200)
    at terminal.c:1101
#5 0x000000000045819e in term_schedule_update (term=0xa15200)
    at terminal.c:1099
#6 seen_disp_event (term=0xa15200) at terminal.c:1112
#7 term_reset_cblink (term=0xa15200) at terminal.c:1151
#8 term_data (term=0xa15200, is_stderr=is_stderr@entry=0,
    data=data@entry=0xa5d8b0 "aw<\366\377\177", len=len@entry=1)
    at terminal.c:6136
#9 0x000000000046729c in from_backend (frontend=<optimised out>,
    is_stderr=is_stderr@entry=0, data=data@entry=0xa5d8b0 "aw<\366\377\177",
    len=len@entry=1) at unix/gtkwin.c:210
#10 0x0000000000415801 in c_write (ldisc=0x90f9a0, len=<optimised out>,
    buf=0xa5d8b0 "aw<\366\377\177") at ldisc.c:26
#11 ldisc_send (handle=handle@entry=0x90f9a0,
    buf=buf@entry=0xa5d8b0 "aw<\366\377\177", len=<optimised out>,
    interactive=interactive@entry=1) at ldisc.c:314
#12 0x0000000000415bac in luni_send (handle=handle@entry=0x90f9a0,
    widebuf=widebuf@entry=0xab1a10 L"a翿\xa5d8a0", len=1,
    interactive=interactive@entry=1) at ldiscucs.c:96
#13 0x0000000000415c23 in lpage_send (handle=handle@entry=0x90f9a0,
    codepage=codepage@entry=55, buf=buf@entry=0x966e40 "a", len=1,
    interactive=interactive@entry=1) at ldiscucs.c:32
#14 0x0000000000466df6 in input_method_commit_event (imc=<optimised out>,
    str=0x966e40 "a", data=0x6d86b0) at unix/gtkwin.c:1227
#15 0x00007ffff6b0af29 in g_cclosure_marshal_VOID__STRINGv ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x00007ffff6b085e7 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007ffff6b21088 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007ffff6b22212 in g_signal_emit_by_name ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007ffff6b0af29 in g_cclosure_marshal_VOID__STRINGv ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007ffff6b085e7 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007ffff6b21088 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007ffff6b21ce2 in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x00007ffff6b0af29 in g_cclosure_marshal_VOID__STRINGv ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x00007ffff6b085e7 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x00007ffff6b21088 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x00007ffff6b22212 in g_signal_emit_by_name ()
  ...

Read more...

Revision history for this message
Jacob Nevins (0jacobnk-ulp) wrote :

...in fact I see this clutch of upstream fixes *was* already backported to the Debian/Ubuntu packages as of 0.63-6, so this bug is already fixd in Utopic (14.10) and Vivid (15.04).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in putty (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.