Bug 104585 - [test case] Browsing directories with # in the name of the directory
Summary: [test case] Browsing directories with # in the name of the directory
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 134946 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-26 13:37 UTC by Jaime Torres
Modified: 2008-08-06 20:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Jaime Torres A.vcf (1.62 KB, application/octet-stream)
2005-04-26 16:36 UTC, Jaime Torres
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaime Torres 2005-04-26 13:37:04 UTC
Version:           3.4.0 (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.4.3
OS:                Linux (i686) release 2.6.11

When I browse the disk and enter in a directory with # in the name (I am not sure if this is the problem) and konqueror has the file:// prefix in the address bar, it uses an index.html that I have previously used. When I remove the file://, it opens the rigth directory tree.

When I use the navegation panel tree I can see the directory content and the address bar shows the path without file://. When I press enter in the address bar, the file:// is added to it and it goes to the last (or deeper index.html) instead of opening the directory.

When the file:// is in the address bar, I can substituye the # by %23 and it goes again to the directory view, but when I press enter again in the address bar, it goes again to index.html with the file:// and # in the adddress bar.

Best regards.
Comment 1 Thiago Macieira 2005-04-26 13:55:13 UTC
It is working fine here, KDE 3.4.0 branch 20050313 (that is, post 3.4.0).

I remember seeing this bug, so I think it has been fixed already. Can someone else confirm?
Comment 2 Maksim Orlovich 2005-04-26 14:56:09 UTC
You are perhaps thinking of bug #79475, which isn't quite the same.
This is odd, though: note the use of file://, as opposed to the proper file:/ or file:///. It probably needs "Use index.html" on, too. Can't reproduce it here, since I don't have the SMB slave installed.



Comment 3 Jaime Torres 2005-04-26 16:36:58 UTC
Konqueror adds file:// (I think), because I already have a
beginning /, but the final address has file:/// .

I can reproduce this behaviour in only one directory here. I have tried in
others that I have created and I can't. 
I do not know what makes this directory exceptional.But It happens every
time
I've tried.

Regards.

> ------- Additional Comments From maksim kde org  2005-04-26 
> 14:56 -------
> You are perhaps thinking of bug #79475, which isn't quite the same.
> This is odd, though: note the use of file://, as opposed to 
> the proper file:/ or file:///. It probably needs "Use 
> index.html" on, too. Can't reproduce it here, since I don't 
> have the SMB slave installed.
> 


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [Bug 104585] Browsing directories with # in the name of the directory   </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Konqueror adds <A HREF="file://" TARGET="_blank">file://</A> (I think), because I already have a</FONT>
<BR><FONT SIZE=2>beginning /, but the final address has <A HREF="file:///" TARGET="_blank">file:///</A> .</FONT>
</P>

<P><FONT SIZE=2>I can reproduce this behaviour in only one directory here. I have tried in</FONT>
<BR><FONT SIZE=2>others that I have created and I can't. </FONT>
<BR><FONT SIZE=2>I do not know what makes this directory exceptional.But It happens every time</FONT>
<BR><FONT SIZE=2>I've tried.</FONT>
</P>

<P><FONT SIZE=2>Regards.</FONT>
</P>

<P><FONT SIZE=2>&gt; ------- Additional Comments From maksim kde org&nbsp; 2005-04-26 </FONT>
<BR><FONT SIZE=2>&gt; 14:56 -------</FONT>
<BR><FONT SIZE=2>&gt; You are perhaps thinking of bug #79475, which isn't quite the same.</FONT>
<BR><FONT SIZE=2>&gt; This is odd, though: note the use of <A HREF="file://" TARGET="_blank">file://</A>, as opposed to </FONT>
<BR><FONT SIZE=2>&gt; the proper <A HREF="file:/" TARGET="_blank">file:/</A> or <A HREF="file:///" TARGET="_blank">file:///</A>. It probably needs &quot;Use </FONT>
<BR><FONT SIZE=2>&gt; index.html&quot; on, too. Can't reproduce it here, since I don't </FONT>
<BR><FONT SIZE=2>&gt; have the SMB slave installed.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

<P><FONT FACE="Arial" SIZE=2 COLOR="#000000"></FONT>&nbsp;

</BODY>
</HTML>


Created an attachment (id=10797)
Jaime Torres A.vcf
Comment 4 Philip Rodrigues 2006-09-02 17:50:46 UTC
Jaime, does this problem still occur in KDE 3.5?
Comment 5 Jaime Torres 2006-09-04 10:59:57 UTC
It is still there. I am now able to show more information:

Creating a directory structure like the following you are able to reproduce part of the problem, and maybe the main problem.

test/TESTC#/doc/html
test/TESTC/doc/html
with a file index.html in the both html directories.

When I put the directory in the konqueror address bar in this way
/home/jtorres/test/TESTC#/doc/html
it shows the directory contents

When I put the directory in the konqueror address bar in this way
file:///home/jtorres/test/TESTC#/doc/html/
it shows the doc directory, and when I press in the direcoty, it shows the following address:
file:///home/jtorres/test/TESTC/doc#/doc/html (note the change in the # from TESTC# to doc#)
and shows the html directory of the TESTC directory.

Best Regards and I hope this is enougth to solve it.
Comment 6 Alex Merry 2007-01-06 17:11:43 UTC
I can reproduce this with KDE 3.5.5.  A more enlightening testcase, possibly, is this:

Create the directory structure (html files not needed).
/tmp/test/TESTC#/doc/html
/tmp/test/TESTC/foo/bar

Go to /tmp/test and click into each folder.  Everything works fine.

Go to
/tmp/test/TESTC#/doc/html
by typing it in the address bar.  Note how the autosuggest function of the address bar works correctly (it suggests the doc and html components of the path).

The address bar changes to file:///tmp/test/TESTC#/doc/html and displays the folder foo (ie: the contents of /tmp/test/TESTC/).  Clicking on foo displays the folder bar (the conents of /tmp/test/TESTC/foo/) and the address bar shows file:///home/alex/test/TESTC/foo#.
Comment 7 Philip Rodrigues 2007-01-06 19:11:16 UTC
*** Bug 134946 has been marked as a duplicate of this bug. ***
Comment 8 Alex Merry 2007-01-06 19:21:22 UTC
Note that this bug affects files with # in the name as well as directories (see Bug 134946).
Comment 9 Jaime Torres 2007-08-13 17:25:28 UTC
This bug is still in KDE 4.0 beta 1, using dolphin.
Comment 10 Frank Reininghaus 2008-05-16 00:21:09 UTC
I can reproduce the behaviour described in comment #6 in 3.5.9 (Kubuntu 8.04) with Konqueror and Dolphin.

However, when I try this in Konqueror from SVN trunk rev. 808111, I get a crash due to a failed assertion right after entering "[...]/test/TESTC#/doc/html" in the location bar and pressing enter (see backtrace below). Dolphin from SVN trunk seems to work fine.

Application: Konqueror (konqueror), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb5df3720 (LWP 6928)]
[KCrash handler]
#6  0xb7f2e410 in __kernel_vsyscall ()
#7  0xb614d085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb614ea01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6fab204 in qt_message_output (msgType=QtFatalMsg, 
    buf=0xbff0f090 "ASSERT: \"result.second\" in file /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/kdirmodel.cpp, line 308") at global/qglobal.cpp:2058
#10 0xb6fab289 in qFatal (msg=0xb7122908 "ASSERT: \"%s\" in file %s, line %d")
    at global/qglobal.cpp:2260
#11 0xb6fab725 in qt_assert (assertion=0xb7dad62f "result.second", 
    file=0xb7dad200 "/home/kde-devel/kde/src/KDE/kdelibs/kio/kio/kdirmodel.cpp", line=308) at global/qglobal.cpp:1828
#12 0xb7c8ef10 in KDirModelPrivate::_k_slotNewItems (this=0x86fe920, 
    items=@0x81423d0)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/kdirmodel.cpp:308
#13 0xb7c8f64c in KDirModel::qt_metacall (this=0x85c3968, 
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbff112ac)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/kdirmodel.moc:76
#14 0xb70d8f63 in QMetaObject::activate (sender=0x85e0a58, 
    from_signal_index=13, to_signal_index=13, argv=0xbff112ac)
    at kernel/qobject.cpp:3010
#15 0xb70d94ed in QMetaObject::activate (sender=0x85e0a58, m=0xb7dd0ffc, 
    local_signal_index=9, argv=0xbff112ac) at kernel/qobject.cpp:3080
#16 0xb7c773be in KDirLister::newItems (this=0x85e0a58, _t1=@0x81423d0)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/kdirlister.moc:253
#17 0xb7c779e0 in KDirLister::Private::emitItems (this=0x8707920)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/kdirlister.cpp:2201
#18 0xb7c7c96c in KDirListerCache::slotEntries (this=0x85c4598, job=0x8294fe8, 
    entries=@0xbff11768)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/kdirlister.cpp:976
#19 0xb7c82322 in KDirListerCache::qt_metacall (this=0x85c4598, 
    _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbff114e8)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/kdirlister_p.moc:97
#20 0xb70d8f63 in QMetaObject::activate (sender=0x8294fe8, 
    from_signal_index=40, to_signal_index=40, argv=0xbff114e8)
    at kernel/qobject.cpp:3010
#21 0xb70d94ed in QMetaObject::activate (sender=0x8294fe8, m=0xb7dd0360, 
    local_signal_index=0, argv=0xbff114e8) at kernel/qobject.cpp:3080
#22 0xb7c54b21 in KIO::ListJob::entries (this=0x8294fe8, _t1=0x8294fe8, 
    _t2=@0xbff11768)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/jobclasses.moc:763
#23 0xb7c5e1dc in KIO::ListJobPrivate::slotListEntries (this=0x82c6d38, 
    list=@0xbff11768)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/job.cpp:2303
#24 0xb7c5e538 in KIO::ListJob::qt_metacall (this=0x8294fe8, 
    _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff1168c)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/jobclasses.moc:750
#25 0xb70d8f63 in QMetaObject::activate (sender=0x86af7f8, 
    from_signal_index=10, to_signal_index=10, argv=0xbff1168c)
    at kernel/qobject.cpp:3010
#26 0xb70d94ed in QMetaObject::activate (sender=0x86af7f8, m=0xb7dd2ce4, 
    local_signal_index=6, argv=0xbff1168c) at kernel/qobject.cpp:3080
#27 0xb7d01f72 in KIO::SlaveInterface::listEntries (this=0x86af7f8, 
    _t1=@0xbff11768)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/slaveinterface.moc:175
#28 0xb7d03e8d in KIO::SlaveInterface::dispatch (this=0x86af7f8, _cmd=106, 
    rawdata=@0xbff117c8)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:195
#29 0xb7d03cb9 in KIO::SlaveInterface::dispatch (this=0x86af7f8)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slaveinterface.cpp:90
#30 0xb7cf6a58 in KIO::Slave::gotInput (this=0x86af7f8)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/slave.cpp:319
#31 0xb7cf7e92 in KIO::Slave::qt_metacall (this=0x86af7f8, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbff118b4)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/slave.moc:75
#32 0xb70d8f63 in QMetaObject::activate (sender=0x82c8638, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#33 0xb70d94ed in QMetaObject::activate (sender=0x82c8638, m=0xb7dcf9a0, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#34 0xb7c28a5b in KIO::Connection::readyRead (this=0x82c8638)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/connection.moc:84
#35 0xb7c2999b in KIO::ConnectionPrivate::dequeue (this=0x8674560)
    at /home/kde-devel/kde/src/KDE/kdelibs/kio/kio/connection.cpp:82
#36 0xb7c2a8c9 in KIO::Connection::qt_metacall (this=0x82c8638, 
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x8380ab8)
    at /home/kde-devel/kde/build/KDE/kdelibs/kio/connection.moc:72
#37 0xb70d2b36 in QMetaCallEvent::placeMetaCall (this=0x8567ae0, 
    object=0x82c8638) at kernel/qobject.cpp:535
#38 0xb70d80ee in QObject::event (this=0x82c8638, e=0x8567ae0)
    at kernel/qobject.cpp:1140
#39 0xb653bb4b in QApplicationPrivate::notify_helper (this=0x805cc40, 
    receiver=0x82c8638, e=0x8567ae0) at kernel/qapplication.cpp:3766
#40 0xb653be3d in QApplication::notify (this=0xbff1229c, receiver=0x82c8638, 
    e=0x8567ae0) at kernel/qapplication.cpp:3360
#41 0xb78431cd in KApplication::notify (this=0xbff1229c, receiver=0x82c8638, 
    event=0x8567ae0)
    at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#42 0xb70c2381 in QCoreApplication::notifyInternal (this=0xbff1229c, 
    receiver=0x82c8638, event=0x8567ae0) at kernel/qcoreapplication.cpp:587
#43 0xb70c679b in QCoreApplication::sendEvent (receiver=0x82c8638, 
    event=0x8567ae0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#44 0xb70c2922 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x804b6c8) at kernel/qcoreapplication.cpp:1198
#45 0xb70c2b97 in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0) at kernel/qcoreapplication.cpp:1091
#46 0xb70f83e0 in QCoreApplication::sendPostedEvents ()
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#47 0xb70f72d3 in postEventSourceDispatch (s=0x805ef10)
    at kernel/qeventdispatcher_glib.cpp:211
#48 0xb5fcdbf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#49 0xb5fd0e5e in ?? () from /usr/lib/libglib-2.0.so.0
#50 0x0805ee90 in ?? ()
#51 0x00000000 in ?? ()
#0  0xb7f2e410 in __kernel_vsyscall ()
Comment 11 Jaime Torres 2008-08-06 20:40:24 UTC
It works for me in 4.1.60 svn trunk 838250