What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try on jaunty now?
This will help us to find and resolve the problem.
* Is this reproducible?
only if a server sends null messages (jabber.org was doing quite a lot
for a while, you would have to set up a local server for testing)
* If so, what specific steps should we take to recreate this bug?
send null messages to a pidgin client
* Could you try on jaunty now
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
I am using Jaunty with pidgin 2.5.4
I installed the debug info but was unable to get a meaningful backtrace
(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
I am using Jaunty with pidgin 2.5.4
I installed the debug info but was unable to get a meaningful backtrace
(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try on jaunty now?
This will help us to find and resolve the problem.
* Is this reproducible?
only if a server sends null messages (jabber.org was doing quite a lot
for a while, you would have to set up a local server for testing)
* If so, what specific steps should we take to recreate this bug?
send null messages to a pidgin client
* Could you try on jaunty now
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
I am using Jaunty with pidgin 2.5.4
I installed the debug info but was unable to get a meaningful backtrace
(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try on jaunty now?
This will help us to find and resolve the problem.
* Is this reproducible?
only if a server sends null messages (jabber.org was doing quite a lot
for a while, you would have to set up a local server for testing)
* If so, what specific steps should we take to recreate this bug?
send null messages to a pidgin client
* Could you try on jaunty now
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
I am using Jaunty with pidgin 2.5.4
I installed the debug info but was unable to get a meaningful backtrace
(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try on jaunty now?
This will help us to find and resolve the problem.
* Is this reproducible?
only if a server sends null messages (jabber.org was doing quite a lot
for a while, you would have to set up a local server for testing)
* If so, what specific steps should we take to recreate this bug?
send null messages to a pidgin client
* Could you try on jaunty now
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
I am using Jaunty with pidgin 2.5.4
I installed the debug info but was unable to get a meaningful backtrace
(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try on jaunty now?
This will help us to find and resolve the problem.
* Is this reproducible?
only if a server sends null messages (jabber.org was doing quite a lot
for a while, you would have to set up a local server for testing)
* If so, what specific steps should we take to recreate this bug?
send null messages to a pidgin client
* Could you try on jaunty now
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try on jaunty now?
This will help us to find and resolve the problem.
* Is this reproducible?
only if a server sends null messages (jabber.org was doing quite a lot
for a while, you would have to set up a local server for testing)
* If so, what specific steps should we take to recreate this bug?
send null messages to a pidgin client
* Could you try on jaunty now
What do you mean by "Null" message? What is the XML (check the ebug log
-- `pidgin -d`) that you receive that makes it crash?
--
pidgin seg fault when xmpp server sends NULL conversation
https://bugs.launchpad.net/bugs/335511
You received this bug notification because you are a member of Ubuntu
B
A typo, it should read 'debug'.
Start pidgin from a terminal and pass it the -d command-line option. You
can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
file afterward. You probably don't need to attach the full log but the
last 20 lines or so before it crashes should be su
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
I am using Jaunty with pidgin 2.5.4
I installed the debug info but was unable to get a meaningful backtrace
(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8
the client reported a Null message error before the seg fault,
where might I find the "ebug" log?
darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>
--
Disclaimer:
By sending an email to ANY
No server currently is sending malformed packets
I do not have time to set one up locally
This could possibly be exploited as a security issue
(its certainly effective DoS)
I've upgraded since no idea if this is still a bug mine...
darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start p
the client reported a Null message error before the seg fault,
where might I find the "ebug" log?
darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>
--
Disclaimer:
By sending an email to ANY
No server currently is sending malformed packets
I do not have time to set one up locally
This could possibly be exploited as a security issue
(its certainly effective DoS)
I've upgraded since no idea if this is still a bug mine...
darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start p
the client reported a Null message error before the seg fault,
where might I find the "ebug" log?
darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>
--
Disclaimer:
By sending an email to ANY
No server currently is sending malformed packets
I do not have time to set one up locally
This could possibly be exploited as a security issue
(its certainly effective DoS)
I've upgraded since no idea if this is still a bug mine...
darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start p
the client reported a Null message error before the seg fault,
where might I find the "ebug" log?
darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>
--
Disclaimer:
By sending an email to ANY
No server currently is sending malformed packets
I do not have time to set one up locally
This could possibly be exploited as a security issue
(its certainly effective DoS)
I've upgraded since no idea if this is still a bug mine...
darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start p
the client reported a Null message error before the seg fault,
where might I find the "ebug" log?
darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>
--
Disclaimer:
By sending an email to ANY
No server currently is sending malformed packets
I do not have time to set one up locally
This could possibly be exploited as a security issue
(its certainly effective DoS)
I've upgraded since no idea if this is still a bug mine...
darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start p
the client reported a Null message error before the seg fault,
where might I find the "ebug" log?
darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>
--
Disclaimer:
By sending an email to ANY
No server currently is sending malformed packets
I do not have time to set one up locally
This could possibly be exploited as a security issue
(its certainly effective DoS)
I've upgraded since no idea if this is still a bug mine...
darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start p
48 matches
Mail list logo
