https://bugs.kde.org/show_bug.cgi?id=360882
Bug ID: 360882
Summary: 16.07.70 git master - dialog boxes are missing button
icons and features on non-KDE desktops. (video example
included)
Product: kdenlive
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: jesse.dub...@gmail.com
When using Ubuntu GNOME (GNOME 3.18), the "Open" Dialog box and the "Add Clip"
dialog box have button icons missing, and the open dialog box won't allow for
proper folder navigation.
See video in URL field for example.
I know that Kdenlive works best in its natural environment, but there are many
more users, statistically, who use GNOME and Unity for their primary desktop.
Fortunately, with recent enhancements, the look and functionality of Kdenlive
across the three major desktops is almost seamless (which is awesome!).
That said, I'd appreciate if this could be looked at before the 16.04 release.
Reproducible: Always
Steps to Reproduce:
1. Install Kdenlive on Ubuntu or Ubuntu GNOME distros: the latest melt .deb
builds first, then Kdenlive (I'm not sure if there are any dependencies
missing, but other than this issue, Kdenlive runs more than fine.)
2. Open Kdenlive
3. Click "Open" or "Add Clip" or go to the Render window and select the output
folder.
Actual Results:
Dialog windows are missing button icons, and navigation functionality isn't
working.
Expected Results:
The dialog box to open and operate as it does in KDE Plasma desktop.
Bug discovered while using Kdenlive 16.07.70 latest git master build on Ubuntu
GNOME x64, GNOME 3.18.
Navigating through the filesystem is a pretty significant part of interaction
between program and operating system, which is the only reason I'm marking this
bug as "Major". I know that the feature freeze is soon (if not already); this
would be a great fix to konk out before the major release.
Also if this is because of missing dependencies that didn't install with the
Kdenlive package, maybe they could be added to the dependency list during
install? (I'm not sure how it all works with installing from software
centers... or any method for that matter. :) )
If it is a dependency issue and it - for whatever reason - can't be added to
the list of dependencies for install, if I can be made aware of what packages
are needed, I could contribute some easy step-by-step documentation for users
on non-KDE desktops to get things running properly.
Thanks all.
--
You are receiving this mail because:
You are watching all bug changes.
