Bug#599144: Also causes ekiga to crash
Hi,
On Sat, Apr 02, 2011 at 07:30:33PM -0400, Dylan Thurston wrote:
severity 599144 critical
I agree with Rolf on severity.
thanks
This bug also affected me; it caused ekiga to crash on startup, and
the same fix works. Running 'strace ekiga' ends with:
Please describe system configuration when you report.
...
read(50, \240\34\353P, 4) = 4
gettimeofday({1301786530, 60705}, NULL) = 0
select(51, [50], NULL, NULL, {1, 0})= 1 (in [50], left {0, 96})
gettimeofday({1301786530, 60768}, NULL) = 0
read(50, \1\2\0\0\0\4\16\0\0\0SocketFrontEnd\3\200\203\223n, 29) = 29
rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTART}, {SIG_IGN, [PIPE],
SA_RESTART}, 8) = 0
write(50, \0\0\0\0SCIM\n\0\0\0P\10\0\0\1\2\0\0\0\1\3\0\0\0, 26) = 26
rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTART}, {SIG_IGN, [PIPE],
SA_RESTART}, 8) = 0
close(50) = 0
open(/usr/lib/scim-1.0/1.4.0/Config/socket.la, O_RDONLY) = -1 ENOENT (No
such file or directory)
We are not shipping *.la file as I understand in deb. If application
was conpiled with such option, that application should be the one to be
blamed as I understand. (Excuse me if I am wrong. I am not library guru.)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault
This bug should be 'critical', since it causes unrelated software to break.
But if this is due to hidden problem in the unrelated software, it is
not. Until it is proven, let's be calm.
gedit used to crash since it was not initializing and closing process
properly. There were precidences. It was solved by the application
program side.
Since SCIM interact with IO tightly, it is prone to expose such hidden
issues.
I can not help much, though. If anyone can help, plese feed us with So
HELP us with patches.
Osamu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599144: Also causes ekiga to crash
severity 599144 critical
thanks
This bug also affected me; it caused ekiga to crash on startup, and
the same fix works. Running 'strace ekiga' ends with:
...
read(50, \240\34\353P, 4) = 4
gettimeofday({1301786530, 60705}, NULL) = 0
select(51, [50], NULL, NULL, {1, 0})= 1 (in [50], left {0, 96})
gettimeofday({1301786530, 60768}, NULL) = 0
read(50, \1\2\0\0\0\4\16\0\0\0SocketFrontEnd\3\200\203\223n, 29) = 29
rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTART}, {SIG_IGN, [PIPE],
SA_RESTART}, 8) = 0
write(50, \0\0\0\0SCIM\n\0\0\0P\10\0\0\1\2\0\0\0\1\3\0\0\0, 26) = 26
rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTART}, {SIG_IGN, [PIPE],
SA_RESTART}, 8) = 0
close(50) = 0
open(/usr/lib/scim-1.0/1.4.0/Config/socket.la, O_RDONLY) = -1 ENOENT (No such
file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault
This bug should be 'critical', since it causes unrelated software to break.
Best,
Dylan Thurston
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599144: Also causes ekiga to crash
On 03.04.2011 07:30, Dylan Thurston wrote:
Running 'strace ekiga' ends with:
...
open("/usr/lib/scim-1.0/1.4.0/Config/socket.la", O_RDONLY) = -1 ENOENT (No such file or directory)
Hm, that path looks funny. Off the top of my hat, I'm not sure how
that gets in there. I do remember we emptied the dependency_libs
fields in .la files in 1.4.9-4. Not sure if that has anything to do
with it. Does "find /usr/lib -name socket.la" return anything? It
does not here. Does moving your ~/.scim to a backup location and
rebooting help?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
