Re: [Licq] #1595: Licq crashes everytime I close it

[Licq]

#1595: Licq crashes everytime I close it
--+-
  Reporter:  Knusper  |   Owner:   
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  1.3.6
 Component:  qt-gui   | Version:  1.3.5
Resolution:   |Keywords:   
--+-
Comment (by Crazy_Hopper):

 Ah, openSUSE 10.2, right... :-)
 But what's the Qt version?

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1594: Licq crashes everytime I close it

[Licq]

#1594: Licq crashes everytime I close it
+---
  Reporter:  Knusper|   Owner:
  Type:  defect |  Status:  closed
  Priority:  normal |   Milestone:  1.3.6 
 Component:  None   | Version:  1.3.5 
Resolution:  duplicate  |Keywords:
+---
Changes (by emostar):

  * status:  new => closed
  * resolution:  => duplicate

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

[Licq] #1594: Licq crashes everytime I close it

[Licq]

#1594: Licq crashes everytime I close it
-+--
 Reporter:  Knusper  |   Owner:   
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  1.3.6
Component:  None | Version:  1.3.5
 Keywords:   |  
-+--
 I use Licq under openSUSE 10.2 ... I do not use the KDE Desktop, rather I
 use Fluxbox.
 Everytime I close Licq it crashes and I get that error message, that Licq
 crashed. Everything works good untill I close the app.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

[Licq] #1595: Licq crashes everytime I close it

[Licq]

#1595: Licq crashes everytime I close it
-+--
 Reporter:  Knusper  |   Owner:   
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  1.3.6
Component:  None | Version:  1.3.5
 Keywords:   |  
-+--
 I use Licq under openSUSE 10.2 ... I do not use the KDE Desktop, rather I
 use Fluxbox.
 Everytime I close Licq it crashes and I get that error message, that Licq
 crashed. Everything works good untill I close the app.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

[Licq] #1593: New broken or unknown contacts after connecting

[Licq]

#1593: New broken or unknown contacts after connecting
-+--
 Reporter:  dehpeh   |   Owner:   
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  1.3.6
Component:  licq daemon  | Version:  1.3.5
 Keywords:   |  
-+--
 Sometimes, when i connect to icq server, one oder two new contacts appear
 in my contactlist. They have a aol-icon and a curious description. I had
 this problem with version 1.3.4 and 1.3.5.

 {{{
 $ cat .licq/users.conf
 ...
 User35 = <87>¹.Licq
 User36 = .Licq
 User37 = Á^A.Licq
 User38 = ^S<8d>.Licq
 User39 = !z.Licq
 }}}

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1445: licq 1.3.4 does not receive message from icq 5.1

[Licq]

#1445: licq 1.3.4 does not receive message from icq 5.1
--+-
  Reporter:  chaos|   Owner:  emostar 
  Type:  defect   |  Status:  assigned
  Priority:  highest  |   Milestone:  1.3.6   
 Component:  licq daemon  | Version:  1.3.4   
Resolution:   |Keywords:  icq5
--+-
Comment (by dehpeh):

 I can't recall the moment when my problem started. Is it maybe related to
 my system change to UTF8?

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1568: crash in 1.3.5-rc2

[Licq]

#1568: crash in 1.3.5-rc2
--+-
  Reporter:  jth  |   Owner:   
  Type:  defect   |  Status:  new  
  Priority:  highest  |   Milestone:  1.3.6
 Component:  message  | Version:  devel
Resolution:   |Keywords:   
--+-
Comment (by erijo):

 Any updates on this issue?

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #699: [ERR] Invalid UIN and password combination

[Licq]

#699: [ERR] Invalid UIN and password combination
---+
  Reporter:  guge54|   Owner:
  Type:  defect|  Status:  closed
  Priority:  normal|   Milestone:  1.3.6 
 Component:  registration  | Version:  1.3.0 
Resolution:  fixed |Keywords:
---+
Changes (by erijo):

  * status:  new => closed
  * resolution:  None => fixed

Comment:

 This is possible already fixed. Please reopen this ticket if it still
 doesn't work with latest licq.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #846: licq crashes while trying to log on

[Licq]

#846: licq crashes while trying to log on
--+-
  Reporter:  domdorn  |   Owner:
  Type:  defect   |  Status:  closed
  Priority:  high |   Milestone:  1.3.6 
 Component:  system   | Version:  1.3.2 
Resolution:  invalid  |Keywords:
--+-
Changes (by erijo):

  * status:  new => closed
  * resolution:  None => invalid

Comment:

 Seems like something strange happened with glibc. Closing this since
 nobody appears to have seen this in a long time.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #839: Segmentation Violation /libpthread/ /libc/

[Licq]

#839: Segmentation Violation /libpthread/ /libc/
--+-
  Reporter:  nobody   |   Owner:
  Type:  defect   |  Status:  closed
  Priority:  high |   Milestone:  1.3.6 
 Component:  licq daemon  | Version:
Resolution:  invalid  |Keywords:
--+-
Changes (by erijo):

  * status:  new => closed
  * resolution:  None => invalid

Comment:

 Old and not enough details.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1572: crash

[Licq]

#1572: crash
--+-
  Reporter:  stephan2503  |   Owner:   
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  1.3.6
 Component:  qt4-gui  | Version:  devel
Resolution:   |Keywords:   
--+-
Comment (by erijo):

 Could you please install gdb and recompile licq (./configure --enable-
 debug) and qt4-gui plugin (cmake -DCMAKE_BUILD_TYPE=Debug) with debug
 symbols?

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1572: crash

[Licq]

#1572: crash
--+-
  Reporter:  stephan2503  |   Owner:   
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  1.3.6
 Component:  qt4-gui  | Version:  devel
Resolution:   |Keywords:   
--+-
Comment (by erijo):

 #1578 is a duplicate of this so it seems to be reproducible.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1578: crash

[Licq]

#1578: crash
--+-
  Reporter:  stephan2503  |   Owner:
  Type:  defect   |  Status:  closed
  Priority:  normal   |   Milestone:  1.3.6 
 Component:  qt4-gui  | Version:  devel 
Resolution:  duplicate|Keywords:
--+-
Changes (by erijo):

  * status:  reopened => closed
  * resolution:  => duplicate

Comment:

 Duplicate of #1572.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1578: crash

[Licq]

#1578: crash
--+-
  Reporter:  stephan2503  |   Owner:  
  Type:  defect   |  Status:  reopened
  Priority:  normal   |   Milestone:  1.3.6   
 Component:  qt4-gui  | Version:  devel   
Resolution:   |Keywords:  
--+-
Changes (by erijo):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 Closing it as invalid may have been a bit premature since #1572 has an
 identical backtrace.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1578: crash

[Licq]

#1578: crash
--+-
  Reporter:  stephan2503  |   Owner:
  Type:  defect   |  Status:  closed
  Priority:  normal   |   Milestone:  1.3.6 
 Component:  qt4-gui  | Version:  devel 
Resolution:  invalid  |Keywords:
--+-
Changes (by erijo):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 Since the crash seems to be in QBasicAtomic::ref() and it isn't
 reproducible I'm closing this. Please reopen if it ever happens again.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.

Re: [Licq] #1516: NULL ptr dereferences found with Calysto static checker

[Licq]

#1516: NULL ptr dereferences found with Calysto static checker
--+-
  Reporter:  anonymous|   Owner:   
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  1.3.6
 Component:  licq daemon  | Version:  1.3.4
Resolution:   |Keywords:   
--+-
Old description:

> Hi,
>
> I've ran my static checker [http://www.calysto.org/ Calysto] on licq
> v1.3.4.
> Here is the (postprocessed) report that I got:
>
> + licq-1.3.4/src/support.c:41
> Function with external linkage dereferences szDest without checking it
> first.
>
> + licq-1.3.4/src/support.c:57
> Function with external linkage dereferences szDest without checking it
> first.
>
> + licq-1.3.4/src/support.c:53
> Function with external linkage dereferences szSource without checking it
> first.
>
> + licq-1.3.4/src/support.c:110
> Function with external linkage dereferences _szBuf without checking it
> first.
>
> + licq-1.3.4/src/support.c:159
> Function with external linkage dereferences namelist without checking it
> first.
>
> + licq-1.3.4/src/pthread_rdwr.c:29
> Function with external linkage dereferences rdwrp without checking it
> first.
>
> + licq-1.3.4/src/pthread_rdwr.c:38
> Function with external linkage dereferences rdwrp without checking it
> first.
>
> + licq-1.3.4/src/pthread_rdwr.c:49
> Function with external linkage dereferences rdwrp without checking it
> first.
>
> + licq-1.3.4/src/pthread_rdwr.c:66
> Function with external linkage dereferences rdwrp without checking it
> first.
>
> + licq-1.3.4/src/pthread_rdwr.c:77
> Function with external linkage dereferences rdwrp without checking it
> first.
>
> + licq-1.3.4/src/sighandler.c:81
> backtrace_symbols can return NULL.
>
> The first 10 warnings are reported in functions that are not called
> anywhere, but
> have external linkage. Since those functions can be called in any
> context,
> Calysto assumes the worst case assumptions for the input parameters and
> globals
> (undefined). Hence, any parameter dereferencing, without checking it
> first, is
> considered a bug.
>
> I'd appreciate your feedback on these warnings. Please email me directly,
> as I'm not
> following licq development lists (please find the email on my page).
>
> I hope this report will be helpful.
>
> Kind regards,
>  Domagoj Babic
>
>  http://www.domagoj.info/

New description:

 Hi,

 I've ran my static checker [http://www.calysto.org/ Calysto] on licq
 v1.3.4.
 Here is the (postprocessed) report that I got:
 {{{
 + licq-1.3.4/src/support.c:41
 Function with external linkage dereferences szDest without checking it
 first.

 + licq-1.3.4/src/support.c:57
 Function with external linkage dereferences szDest without checking it
 first.

 + licq-1.3.4/src/support.c:53
 Function with external linkage dereferences szSource without checking it
 first.

 + licq-1.3.4/src/support.c:110
 Function with external linkage dereferences _szBuf without checking it
 first.

 + licq-1.3.4/src/support.c:159
 Function with external linkage dereferences namelist without checking it
 first.

 + licq-1.3.4/src/pthread_rdwr.c:29
 Function with external linkage dereferences rdwrp without checking it
 first.

 + licq-1.3.4/src/pthread_rdwr.c:38
 Function with external linkage dereferences rdwrp without checking it
 first.

 + licq-1.3.4/src/pthread_rdwr.c:49
 Function with external linkage dereferences rdwrp without checking it
 first.

 + licq-1.3.4/src/pthread_rdwr.c:66
 Function with external linkage dereferences rdwrp without checking it
 first.

 + licq-1.3.4/src/pthread_rdwr.c:77
 Function with external linkage dereferences rdwrp without checking it
 first.

 + licq-1.3.4/src/sighandler.c:81
 backtrace_symbols can return NULL.
 }}}

 The first 10 warnings are reported in functions that are not called
 anywhere, but have external linkage. Since those functions can be called
 in any context, Calysto assumes the worst case assumptions for the input
 parameters and globals (undefined). Hence, any parameter dereferencing,
 without checking it first, is considered a bug.

 I'd appreciate your feedback on these warnings. Please email me directly,
 as I'm not following licq development lists (please find the email on my
 page).

 I hope this report will be helpful.

 Kind regards,
  Domagoj Babic

  http://www.domagoj.info/

Comment (by erijo):

 backtrace_symbols can return NULL: fixed in r5870.

-- 
Ticket URL: 
Licq 
Licq - an instant messaging client for UNIX.