Bug 17055

Summary:	impossible to setup any html portfolio generator
Product:	Mageia	Reporter:	David LUCAS <davlucas>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davlucas, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kphotoalbum-4.6.2-1.mga6	CVE:
Status comment:

Description David LUCAS 2015-10-31 15:31:38 CET

[root@linux html]# rpm -qa|grep kphotoalbum
kphotoalbum-4.6.2-1.mga6
[root@linux html]# urpmi zip
Le paquetage zip-3.0-8.mga5.x86_64 est déjÃ  installé


kphotoalbum(31721) KArchive::createDevice: KSaveFile creation for  "/tmp/kde-root/kphotoalbumFdkuNo//file:///root/Documents.kim"  failed,  "Insufficient permissions in target directory." 
kphotoalbum(31721)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Message did not receive a reply (timeout by message bus)" 
kphotoalbum(31721) KArchive::createDevice: KSaveFile creation for  "/tmp/kde-root/kphotoalbumfoTUgQ///var/www/html/gallery/1.kim"  failed,  "Insufficient permissions in target directory." 
kphotoalbum(31721)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Message did not receive a reply (timeout by message bus)" 
^C
[root@linux html]# whoami
root


Reproducible: 

Steps to Reproduce:

Samuel Verschelde 2015-11-16 12:19:22 CET

Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:23:50 CEST

Assignee: mageia => kde

Comment 1 Nicolas Lécureuil 2017-03-16 21:46:40 CET

is it still valid for you with latest cauldron ?

CC: (none) => mageia

Comment 2 David LUCAS 2017-03-16 22:00:13 CET

1- Workaround was found with a webapp called "piwigo" , cf ryokoshinohara.com designed with Mageia, self hosted with a raspberry pi with a debian, but just an install.php script was enough  
2- so, you can close this case , not so important for me now. 
3- Thanks for your follow up

CC: (none) => davlucas

Comment 3 Aurelien Oudelet 2021-05-17 01:15:36 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.

Status: NEW => RESOLVED
Resolution: (none) => OLD