licq deletes UIN from config file on startup

Bug #4601 reported by Felix Maibaum
4
Affects Status Importance Assigned to Milestone
licq (Ubuntu)
Fix Released
Medium
MOTU

Bug Description

licq deletes UIN from config file on startup. After I set up my account with the owner manager, everything is fine. After I exit licq the Uin in the file .licq/owner.Licq is still correct. As soon as I restart Licq the Uin gets set to 0. This is reproducable every time. All other information is kept intact (even password). The same upstream revision works fine on my laptop running debian. Version is 1.3.0-3ubuntu1. Using kde UI, same effect in QT-UI.

Changed in licq:
assignee: nobody → motu
Revision history for this message
krupaj (jan-krupa) wrote :

See Debian Bug #331712
licq: buffer overflow in icqd.cpp, resulting in bad licq.conf

Unfortunately, this bug makes licq unusable for me :-(
Any fix for Ubuntu?

Revision history for this message
Yann Rouillard (yann-pleiades) wrote :

The bug was fixed in debian and hence in the dapper package.
So this bug can be closed.

Changed in licq:
status: Unconfirmed → Fix Released
Revision history for this message
Daniel (daccle) wrote :

I have a workaround for the current breezy version:

1.) Fire up licq, enter your UIN as requested.
2.) Open .licq/licq.conf in your favourite editor
3.) Search the section [owner] in the file.
4.) Chage the zero in 'Owner1.Id = 0' to your UIN
     it should look like 'Owner1.Id = 123123123' where
     123123123 should be your UIN
5.) Save the file.

 That's it!
                    Daniel

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.