Source ID 48 was not found when attempting to remove it

[anonymous]

I saw this on my WeeChat console when connecting to Bitlbee, not sure if it's an issue with Weechat or Bitlbee, but file it here as a start

(process:19474): GLib-CRITICAL : Source ID 48 was not found when attempting to remove it

[dx]

If it's in the weechat console then it's a weechat issue. Bitlbee runs independently from weechat, that error would appear in the bitlbee stderr (which is usually thrown to /dev/null with most setups)

[bluephoenix47@…]

I've been seeing the same issues the past few days. I do not run weechat; I'm connected through irssi.

[19:22] (process:26779): GLib-CRITICAL **: Source ID 6196 was not found when attempting to remove it
[19:23] (process:26779): GLib-CRITICAL **: Source ID 6210 was not found when attempting to remove it
[19:23] (process:26779): GLib-CRITICAL **: Source ID 6207 was not found when attempting to remove it
[19:24] (process:26779): GLib-CRITICAL **: Source ID 6221 was not found when attempting to remove it
[19:24] (process:26779): GLib-CRITICAL **: Source ID 6217 was not found when attempting to remove it
[19:25] (process:26779): GLib-CRITICAL **: Source ID 6231 was not found when attempting to remove it
[19:25] (process:26779): GLib-CRITICAL **: Source ID 6228 was not found when attempting to remove it
[19:26] (process:26779): GLib-CRITICAL **: Source ID 6242 was not found when attempting to remove it
[19:26] (process:26779): GLib-CRITICAL **: Source ID 6239 was not found when attempting to remove it
[19:27] (process:26779): GLib-CRITICAL **: Source ID 6252 was not found when attempting to remove it
[19:27] (process:26779): GLib-CRITICAL **: Source ID 6249 was not found when attempting to remove it
[19:28] (process:26779): GLib-CRITICAL **: Source ID 6264 was not found when attempting to remove it
[19:28] (process:26779): GLib-CRITICAL **: Source ID 6261 was not found when attempting to remove it
[19:29] (process:26779): GLib-CRITICAL **: Source ID 6274 was not found when attempting to remove it
[19:29] (process:26779): GLib-CRITICAL **: Source ID 6271 was not found when attempting to remove it
[19:30] (process:26779): GLib-CRITICAL **: Source ID 6284 was not found when attempting to remove it
[19:30] (process:26779): GLib-CRITICAL **: Source ID 6281 was not found when attempting to remove it
[19:31] (process:26779): GLib-CRITICAL **: Source ID 6295 was not found when attempting to remove it
[19:31] (process:26779): GLib-CRITICAL **: Source ID 6292 was not found when attempting to remove it
[19:32] (process:26779): GLib-CRITICAL **: Source ID 6305 was not found when attempting to remove it
[19:32] (process:26779): GLib-CRITICAL **: Source ID 6302 was not found when attempting to remove it
[19:33] (process:26779): GLib-CRITICAL **: Source ID 6316 was not found when attempting to remove it
[19:33] (process:26779): GLib-CRITICAL **: Source ID 6313 was not found when attempting to remove it

FYI, process 26779 is in fact bitlbee.

[dx]

Oh hey, thanks for reopening this one. I was fixing this exact bug yesterday, completely forgot that I had closed this one before.

[dx]

I've got the patch for this one somewhere, but i should mention: this is not a "critical" bug, these are just warnings that something redundant is being done, only labeled as "critical" because that's the error level that glib gives to potential "​programming errors", but it really is harmless in this case.

[anonymous]

Understood. I didn't think it was a serious error, since Bitlbee has been running just fine, but it is annoying to see all these messages.

Thanks for getting this fixed!

[anonymous]

This issue is not present when compiled with --events=libevent. Kind of workaround for those who don't mind libevent.

[anonymous]

I also got a whole bunch of these warnings in systemd journal under a recent version of Arch Linux running BitlBee 3.2.2.

I do not notice any further problems with bitlbee and connected clients, but I get the logs filled up with this warnings. About 15 messages per second, depending on the amount of connected clients.

A first short test with the development version of bitlbee, shows up the same problem.

[dx]

Hopefully fixed all of these in revision 1051!

If there are more of these, please try to find a way to reproduce them (for example, when connecting to certain IM protocols)

[rprabhu@…]

I still see this spamming the logs in bitlbee 3.2.2.

Mar 19 05:37:15 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7618 was not found when attempting to remove it
Mar 19 05:37:27 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7627 was not found when attempting to remove it
Mar 19 05:37:34 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7641 was not found when attempting to remove it
Mar 19 05:37:41 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7648 was not found when attempting to remove it
Mar 19 05:37:44 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7656 was not found when attempting to remove it
Mar 19 05:37:56 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7663 was not found when attempting to remove it
Mar 19 05:37:56 li273-173 bitlbee[1417]: (process:1884): GLib-CRITICAL **: Source ID 7667 was not found when attempting to remove it

[dx]

3.2.2 is older than the fix for this.

3.4 should be released soonish.

[henrik]

This still happens with 3.4.

204400  bitlbee  -- │ - Welcome to the BitlBee server at localhost.
204400  bitlbee  -- │ -
204400  bitlbee  -- │ - This server is running BitlBee version 3.4.
204400  bitlbee  -- │ - The newest version can be found on http://www.bitlbee.org/
204400  bitlbee  -- │ -
204400  bitlbee  -- │ - You are getting this message because the server administrator has not
204400  bitlbee  -- │ - yet had the time (or need) to change it.
204400  bitlbee  -- │ -
204400  bitlbee  -- │ - For those who don't know it yet, this is not quite a regular Internet
204400  bitlbee  -- │ - Relay Chat server. Please see the site mentioned above for more
204400  bitlbee  -- │ - information.
204400  bitlbee  -- │ -
204400  bitlbee  -- │ - The developers of the Bee hope you have a buzzing time.
204400  bitlbee  -- │ - -- BitlBee development team.
204400  bitlbee  -- │ -
204400  bitlbee  -- │ - ... Buzzing, haha, get it?
204400  bitlbee  -- │ End of MOTD
204400  bitlbee  -- │ User mode [+s] by henrik  
204400  bitlbee  -- │ User mode [+R] by henrik
204400  bitlbee =!= │ irc: command "(process:15256):" not found:
204400  bitlbee =!= │ (process:15256): GLib-CRITICAL **: Source ID 17 was not found when attempting to remove it
204401  bitlbee =!= │ irc: command "(process:15256):" not found:
204401  bitlbee =!= │ (process:15256): GLib-CRITICAL **: Source ID 40 was not found when attempting to remove it
204402  bitlbee =!= │ irc: command "(process:15256):" not found:

[dx]

Well, i've already fixed the most obvious cases, and some not-so-obvious ones, but you'll have to be more specific for the rest (the error message doesn't say anything)

If there are more of these, please try to find a way to reproduce them (for example, when connecting to certain IM protocols)

Also, again,

this is not a "critical" bug, these are just warnings that something redundant is being done, only labeled as "critical" because that's the error level that glib gives to potential "​programming errors", but it really is harmless in this case

[wilmer]

dx, we could consider telling GLib to log these elsewhere (say, /dev/null). A daemon logging stuff like this to stdout is pretty ridiculous, and really this is what we check return values for.

[i.am.inuyasha@…]

I'm still getting this with Bitlbee connected to one Twitter account and one AIM account.

[rena@gabumon ~]$ bitlbee -V BitlBee 3.2.2 API version 030202 [rena@gabumon ~]$ uname -a Linux gabumon 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:15:20 CEST 2015 i686 GNU/Linux

Mostly when the internet connection drops, I see a flood of these messages spamming my syslog. It's not harmful but a bit annoying.

[dx]

BitlBee 3.2.2

There's your problem. 3.4 is out.

[i.am.inuyasha@…]

Derp. How long ago did it come out? Seems my repo is out of date...

[roni.laukkarinen@…]

I still see this in 3.4.1. How to hide those messages?

[dx]

Replying to roni.laukkarinen@…:

I still see this in 3.4.1. How to hide those messages?

This was answered on irc, turned out to be an old version of telegram-purple.

In the general case, though:

1. It's highly unlikely to be our fault, check plugins.
2. These messages are only visible in the irc client when using inetd mode, not with forkdaemon. In the latter case they may be sent to syslog, which is less annoying unless you love staring at logs.