[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#292531: marked as done (kmail: Kmail silently exits after choosing "Open With" on an attachment)



Your message dated Tue, 25 Apr 2006 02:59:25 -0400
with message-id <444DC8CD.3040501@vif.com>
and subject line Bug#292531: Exit status?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: kmail
Version: 4:3.3.1-3
Severity: normal

I have an email with multiple graphic attachements (PNG files) in my Inbox.
I choose one picture in the Description window (list of attachements) and
then click right mouse button in the displayed picture and choose"Open With"
from menu. After few seconds of busy 100% load kmail silently exits.

Here is the end of output from strace:

access("/usr/lib/qt3/plugins/codecs/.", F_OK) = -1 ENOENT (No such file or
directory)
open("/home/sojka/.DCOPserver_glab__0", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=51, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(3, "local/glab:/tmp/.ICE-unix/dcop53"..., 4096) = 51
close(3)                                = 0
munmap(0xb7ffe000, 4096)                = 0
socket(PF_FILE, SOCK_STREAM, 0)         = 3
uname({sys="Linux", node="glab", ...})  = 0
connect(3, {sa_family=AF_FILE, path="/tmp/.ICE-unix/dcop5335-1106811332"},
37) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
write(3, "\0\1\0\0\0\0\0\0", 8)         = 8
read(3, "\0\1\0\0\0\0\0\0", 8)          = 8
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
read(4, "", 4096)                       = 0
close(4)                                = 0
munmap(0xb7ffe000, 4096)                = 0
write(3, "\0\2\1\1\6\0\0\0\0\0\0\0\0\0\0\0\3\0MIT\0\0\0\3\0001.0"..., 56) =
56
read(3, "\0\3\0\0\1\0\0\0", 8)          = 8
read(3, "\0\0\0\0\0\0\0\0", 8)          = 8
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
close(4)                                = 0
munmap(0xb7ffe000, 4096)                = 0
write(3, "\0\4\1\1\3\0\0\0\20\0\0\0\0\0\0\0R\30\255eh\271N\257\307"..., 32)
= 32
read(3, "\0\6\0\0\2\0\0\0", 8)          = 8
read(3, "\3\0MIT\0\0\0\3\0001.0\0\0\0", 16) = 16
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
read(4, "", 4096)                       = 0
close(4)                                = 0
munmap(0xb7ffe000, 4096)                = 0
write(3, "\0\7\1\0\7\0\0\0\1\1\0\0\0\0\0\0\4\0DCOPN\257\3\0KDE?\336"..., 64)
= 64
read(3, "\0\3\0\0\1\0\0\0", 8)          = 8
read(3, "\0\0MIT\0\0\0", 8)             = 8
access("/home/sojka/.ICEauthority", R_OK) = 0
open("/home/sojka/.ICEauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=185, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7ffe000
read(4, "\0\3ICE\0\0\0-local/glab:/tmp/.ICE-un"..., 4096) = 185
close(4)                                = 0
munmap(0xb7ffe000, 4096)                = 0
write(3, "\0\4\1\0\3\0\0\0\20\0\0\0\0\0\0\0R\30\255eh\271N\257\307"..., 32)
= 32
read(3, "\0\10\0\2\2\0\0\0", 8)         = 8
read(3, "\3\0KDE\0\0\0\3\0002.0\0\0\0", 16) = 16
getsockopt(3, SOL_SOCKET, SO_PEERCRED, "\327\24\0\0\350\3\0\0\350\3\0\0",
[12]) = 0
getuid32()                              = 1000
getpid()                                = 7877
write(3, "\1\2\1\0H\0\0\0\0\0\0\0", 12) = 12
write(3, "\0\0\0\0\0\0\0\vDCOPServer\0\0\0\0\1\0\0\0\0\25regi"..., 53) = 53
write(3, "\0\0\0\17anonymous-7877\0", 19) = 19
read(3, "\2\3\0\0027\0\0\0", 8)         = 8
read(3, "\240\0\0\0", 4)                = 4
read(3, "\0\0\0\vDCOPServer\0\0\0\0\0\0\0\0\tQCString\0"..., 55) = 55
write(3, "\1\2\1\0[\0\0\0\240\0\0\0", 12) = 12
write(3, "\0\0\0\17anonymous-7877\0\0\0\0\vDCOPServe"..., 81) = 81
write(3, "\0\0\0\6kmail\0", 10)         = 10
read(3, "\2\3\0\0023\0\0\0", 8)         = 8
read(3, "\240\0\0\0", 4)                = 4
read(3, "\0\0\0\vDCOPServer\0\0\0\0\17anonymous-787"..., 51) = 51
write(3, "\1\2\1\0a\0\0\0\2\0\0\0", 12) = 12
write(3, "\0\0\0\17anonymous-7877\0\0\0\0\6kmail\0\0\0\0"..., 61) = 61
write(3, "\0\0\0\f/home/sojka\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0"..., 36) =
36
read(3, "\2\5\0\2!\0\0\0", 8)           = 8
read(3, "\2\0\0\0", 4)                  = 4
read(3, "\0\0\0\6kmail\0\0\0\0\17anonymous-7877\0\0\0\0"..., 33) = 33
read(3, "\2\6\0\0021\0\0\0", 8)         = 8
read(3, "\2\0\0\0", 4)                  = 4
read(3, "\0\0\0\6kmail\0\0\0\0\17anonymous-7877\0\0\0\0"..., 49) = 49
close(3)                                = 0
exit_group(0)                           = ?


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)

Versions of packages kmail depends on:
ii  kdelibs4                 4:3.3.2-1       KDE core libraries
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  libgcc1                  1:3.4.3-7       GCC support library
ii  libice6                  4.3.0.dfsg.1-10 Inter-Client Exchange library
ii  libkcal2                 4:3.3.1-3       KDE calendaring library
ii  libkdenetwork2           4:3.3.2-1       KDE Network library
ii  libkdepim1               4:3.3.1-3       KDE PIM library
ii  libkleopatra0a           4:3.3.2-1       KDE GnuPG interface libraries
ii  libkpimidentities1       4:3.3.1-3       KDE PIM user identity information 
ii  libksieve0               4:3.3.2-1       KDE mail/news message filtering li
ii  libmimelib1a             4:3.3.2-1       KDE mime library
ii  libpng12-0               1.2.8rel-1      PNG library - runtime
ii  libqt3c102-mt            3:3.3.3-8       Qt GUI Library (Threaded runtime v
ii  libsm6                   4.3.0.dfsg.1-10 X Window System Session Management
ii  libstdc++5               1:3.3.5-6       The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  perl                     5.8.4-5         Larry Wall's Practical Extraction 
ii  xlibs                    4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu
ii  zlib1g                   1:1.2.2-4       compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Michal Sojka a écrit :

On Tuesday 25 April 2006 8:16, Filipus Klutiero wrote:
Hi Michal,
considering that you, as the bug submitter, and the only person who
reported experiencing this bug, cannot reproduce it anymore, do you
think this bug should be closed, or perhaps tagged unreproducible?

I don't know what are consequences of tagging the bug unreproducible. If nobody else had the same problem, do whatever you thing is the best :)

Michal

The difference between tagging unreproducible and closing is that if somebody else ends up reproducing the bug, it will be easier for that person to find the bug report, instead of opening a new report and losing information.

Since you don't know what to do, I guess this bug looks fixed and is better closed.
If anybody can reproduce it in any current release, please reopen.

--- End Message ---

Reply to: