Bug 20137 - smb4k won't mount share, if path contains more then one /
Summary: smb4k won't mount share, if path contains more then one /
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: Mageia 6
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard: smb4K mounting
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-18 13:56 CET by Jaroslav Å olc
Modified: 2021-05-17 01:28 CEST (History)
3 users (show)

See Also:
Source RPM: smb4k-1.9.80-1.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jaroslav Å olc 2017-01-18 13:56:17 CET 
Description of problem:

After aktualization OS (4.9.4-desktop-1.mga6) smb4k can mount using open mount dialogue shares only with one / in path - for example //server/vyuka

It is not able mount share with more than one / in the path - for example
//server/zamestnanci/ucitele not reading the second / (reading without / this zamestnanciucitele)
 
Version-Release number of selected component (if applicable):

1.9.80-1.mga6

How reproducible:

Every time I attemp to mount

Steps to Reproduce:
1. smb4k
2. open mount dialogue with //server/zamestnanci/ucitele
3. .... zamestnanciucitele ... mount error(6) No such device or adress ...
Jaroslav Å olc 2017-01-18 13:58:24 CET

Keywords: (none) => 6dev1
Target Milestone: --- => Mageia 6
Summary: won't mount share, if path contains more then one / => smb4k won't mount share, if path contains more then one /
Whiteboard: (none) => smb4K mounting

Comment 1 Marja Van Waes 2017-01-18 15:33:03 CET 
Assigning to all packagers collectively, since there is no registered maintainer for this package.

Source RPM: smb4k 1.9.80-1.mga6 => smb4k-1.9.80-1.mga6
Assignee: bugsquad => pkg-bugs
CC: (none) => marja11

Nicolas Lécureuil 2017-03-12 09:26:08 CET

Assignee: pkg-bugs => kde
CC: (none) => mageia

Comment 2 Aurelien Oudelet 2021-05-17 01:28:18 CEST 
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.