Your message dated Mon, 6 Nov 2006 14:57:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line konqueror: Crash when renaming
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: konqueror
Version: 4:3.5.4-2
Severity: important
When I rename a file, using Konqueror's right click menu rename
option, from something like file.pdf to .file.pdf and clicking outside
the editable zone, konqueror crashes. To reproduce this bug I: open
konqueror, open some directory wich contains at least one file (at
least one because I need something to rename), the file to be renamed
must be 'previewable' (binary files doesn't crash konqueror), right
click the file, rename, prepend a . (dot) to the file name, click
outside the edit zone, CRASH.
Notes to get a successful crash:
1.- file must be 'previewable', even .psd files and directories
work (of course they must be marked to be previewed in the konqueror
settings), but not binary-like files (because they can't be
previewed).
2.- The view menu option 'Show Hidden Files' must _not_ be checked
(if checked, konqueror doesn't crash).
3.- Use the 'Icon view' view (only tested on icon view and list
view modes) mode.
Appended file is the backtrace generated by kcrash.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-a64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages konqueror depends on:
ii kcontrol 4:3.5.4-2 control center for KDE
ii kdebase-kio-plugins 4:3.5.4-2 core I/O slaves for KDE
ii kdelibs4c2a 4:3.5.4-3 core libraries and binaries for al
ii kdesktop 4:3.5.4-2 miscellaneous binaries and files f
ii kfind 4:3.5.4-2 file-find utility for KDE
ii libacl1 2.2.41-1 Access control list shared library
ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi
ii libattr1 2.4.32-1 Extended attribute shared library
ii libaudio2 1.8-2 The Network Audio System (NAS). (s
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libfam0 2.7.0-10 Client library to control the FAM
ii libfontconfig1 2.3.2-7 generic font configuration library
ii libfreetype6 2.2.1-2 FreeType 2 font engine, shared lib
ii libgcc1 1:4.1.1-5 GCC support library
ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library
ii libidn11 0.6.5-1 GNU libidn library, implementation
ii libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libkonq4 4:3.5.4-2 core libraries for Konqueror
ii libpng12-0 1.2.8rel-5.2 PNG library - runtime
ii libqt3-mt 3:3.3.6-2 Qt GUI Library (Threaded runtime v
ii libsm6 1:1.0.0-4 X11 Session Management library
ii libstdc++6 4.1.1-5 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.0-8 X11 client-side library
ii libxcursor1 1.1.5.2-5 X cursor management library
ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar
ii libxft2 2.1.8.2-8 FreeType-based font drawing librar
ii libxi6 1:1.0.0-5 X11 Input extension library
ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library
ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra
ii libxt6 1:1.0.0-5 X11 toolkit intrinsics library
ii zlib1g 1:1.2.3-13 compression library - runtime
konqueror recommends no packages.
-- no debconf information
konqueror1.log
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 4:3.5.5a-2
requested by submitter:
> After few tests with renaming various 'file'/'folder' to '.file'/'.folder'
> with the options that caused Konqueror to crash before, the bug doesn't
> appear in the latest Etch version (informations below).
>
> As it seems resolved, I think you can close this reportbug.
--- End Message ---
