|
Bugzilla – Full Text Bug Listing |
| Summary: | digikam export to CD archive fails | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Volker Kuhlmann <bugz57> |
| Component: | X11 Applications | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | skript to solve the problem | ||
|
Description
Volker Kuhlmann
2005-09-04 10:03:14 UTC
Created attachment 57185 [details]
skript to solve the problem
You need to call k3b with the --nofork option. Otherwise the system call from digikam will return immediately after starting k3b, and that is the reason, while the exported files get already whiped out before k3b can initialize itself. The attached shell skript "k3b-nofork" can be registered as burning application in digikam it does just this.
works fine with 10.1 beta3 |